Nice,
Let us know when your shure.


After editting the domocookie.txt file the test-system worked for 4 days, on day five it did not start logging in the morning.

Looking at the webportal and app of solaredge that keeps working so somehow it has something to do with how domoticz handels this ...

for me, (on linux) changing the ipv6 / ipv4 priority to ipv4 first "solved" the issue.

to check the current priority (you will see the ipv6 address first in the list):
$ getent ahosts monitoringapi.solaredge.com
2606:4700::6812:1dbb STREAM monitoringapi.solaredge.com.cdn.cloudflare.net
2606:4700 ...

No you (I) don't. Connection always comes back automatically after some time. The app and web interface also have issues with displaying anything besides the live data.

I've been monitoring it for a few days now but connection does not automatically come back and there are no issues with the app ...

This: https://monitoringapi.solaredge.com/site/<site id>/currentPowerFlow.json?api_key=<api_key> is what is used in de code.
Everry url in Domoticz Solaredge.cpp ends with .json, so that should be ok. Not changed in de the last year

That does not seems to be true, it currently is missing the ...

The error 'getting http data' occurs randomly'. Mostly during the night, but also during the day. It also disappears after 1 or more errors.

So I am still not sure this is (solely) a Domoticz issue.

Edit: I read de Solaredge API sometimes has different response times from a fewe hundreds of ms ...

I'll give it a try not reporting back COP if not heating and see how that goes. Will need to update last seen on the device otherwise it will show timeout, I think.

Am testing with 3 devices and no updates if they are 0
https://i.imgur.com/p9MdVb7.png

I now take the monthly reports for ...

I'll give it a try not reporting back COP if not heating and see how that goes. Will need to update last seen on the device otherwise it will show timeout, I think.

Am testing with 3 devices and no updates if they are 0
https://i.imgur.com/p9MdVb7.png

I now take the monthly reports for ...

I've been using this plugin for a while now and there is just one thing that doesn't count in the right way and that's the COP since it also counts the moments that there is no heat-exchange. So there are a lot of zero's in the list.
For example augustgives 0,15 as COP while counting it the ...

I've been using this plugin for a while now and there is just one thing that doesn't count in the right way and that's the COP since it also counts the moments that there is no heat-exchange. So there are a lot of zero's in the list.
For example augustgives 0,15 as COP while counting it the result ...

I am able to set it directly in the GUI and see the change reflected on the Heat Pump, not sure whet is happening there. I never use Blocky
Can't you just type the required set point and save it?

Setting it directly is no problem here either, it's just in blockly that it does not register ...

waltervl wrote: Thursday 13 March 2025 16:56 Is it really a setpoint device in Domoticz or just a temperature device/custom sensor? Can you set the setpoint from Domoticz User interface?

It is aan setpoint device and it did work as a setpointdevice in blockly in the older luxtronic plugin.

Which setpoint are you talking about?
Can you set it outside of a blocky?

It's the setpoint for watertemperature and is is visible in the utility-tab.
https://tweakers.net/i/NYKPfVFgovM--Hw4pvwzJ_NFdIM=/fit-in/4920x3264/filters:max_bytes(3145728):no_upscale():strip_icc():strip_exif()/f ...

Nice piece of work and after testing on a spare system installed it.
Some extra features that are very welcome but I encountered one glitch and that is abouth the setpoints and the use of them in blockly.

The setpoints are found under devices and show up as a utility but trying to use it in ...

Nice piece of work and after testing on a spare system installed it.
Some extra features that are very welcome but I encountered one glitch and that is abouth the setpoints and the use of them in blockly.

The setpoints are found under devices and show up as a utility but trying to use it in blockly ...

Same thing happens here. It started just a few weeks ago.
Running latest version of domoticz on a RPi 3B and looking at it on a win10 PC with Firefox.
Closing the tab of the blockly and then reopen it does the trick to make it readable again.

I've been having the RFXcom 433E for abouth 9 years now and since abouth a few months a spare RFXcom 433XL.

Now that I have purchased en TFA rainmeter that should work with RFXcom I found out it is nog supported in the 433E fimware but it is supported in de 433XL firmware.

But recent testing on a ...

Just found out that the weekly update and upgrade of the raspberry also causes the login to netatmo to fail again and force into refreshing the token and doe the whole ridle of creating a new password.

As of this morning after yet another attempt to enter the credentials and resetting the token at dev.netatmo things seem to be working again and stay working now for over 8 hours now. Keeping my fingers crossed.


My longest up-time was from 15.08u till 23.11u on jun 12. That 's a little ...

JapieG wrote: Monday 10 June 2024 12:59 same here. Not working for more than a few hours. So annoying.

As of this morning after yet another attempt to enter the credentials and resetting the token at dev.netatmo things seem to be working again and stay working now for over 8 hours now. Keeping my fingers crossed.

Since a few days Domticz ends after a few days with processing the values of Netatmo. In the logfile of Domoticz i see that there is an autorisation-problem with Netatmo "No access granted". If i repair the password in Hardware/Netatmo conform the repair-procedure of Netatmo, then it works a few ...