Thanks for your reply
I've commented this line and it's solved

Thanks for this reply.
Other testing:
I've changed the Settings to test all the possible values and the results are the same for all the Settings
2 log lines only
Settings.png
Log.png
but no debug info and no log for the other values, perhaps the STATUS log in the only one working now ?

What do ...

even with the settings as Debug (everything)

and it was ok before the upgrade

Hi,
I've installed 2025.1
Version: 2025.1
Build Hash: 89d5c900d
Compile Date: 2025-05-05 09:02:49
dzVents Version: 3.1.8

and I've almost no longer log for dzVents script, even with the settings as Debug (everything).

I've tried the script template Logging
return {
on = {
devices = {
203 ...

Hi ouiouiblog,

if you have an accurate sensor, perhaps it's better to use it instead of a computed result.

I think in the formula, we have to use okta and okta is a bit different from a sensor cloudiness, but I could not found where I've read this!

I was wondering if someone on the forum understood the formulas that are in that script or had some sources to explain them.

Hi,
you could have a look there in this topic https://www.domoticz.com/forum/viewtopic.php?p=290753#p290753
and a little before.

Do you have the same issue on full sunny ...

ok,
that's the answer!
And the change!
I didn't know it was working like this Not it was like this when I set it up, some years ago

In a former version I could update the sValue of Setpoint with the GUI After an update the GUI changed and it's no longer possible to update the sValue The sValue is not in the Edit GUI

sorry, I think I wasn't clear enough.

Before an update there was only 1 temp value in the setpoint devices, the one that I could still update by dzVents.
Now the are several values!

I've found an old screen shot of the GUI in domoticz-homeautomation-workbook.pdf that shows there was only 1 temp ...

Hi,
I've upgraded to 2023.2 (build 15555) and after a while I've discovered that it's no longer possible to update the "setpoint" of my heater (temperature) by the GUI.
But still possible by dzVents.
dz.devices(SETPOINT_ID).updateSetPoint(SETPOINT_TEMP)
Screenshot 2023-12-19 213332.png

Same ...

Thanks for having tried.
I'll give a try to zigbee2mqtt
Thanks!

Thanks for the new version
But, the error is still present.
The log at the restart of dz
2023-04-01 09:55:32.741 Sunrise: 07:29:00 SunSet: 20:21:00
2023-04-01 09:55:32.741 Day length: 12:52:00 Sun at south: 13:55:00
2023-04-01 09:55:32.741 Civil twilight start: 06:57:00 Civil twilight end: 20:53:00 ...

You said earlier the error occurred on a newly installed test server. I (mistakenly) assumed you meant a clean system with only iDetect running.
In fact this server should be the new production one, when it works... so I hope it's a clean install

I think Zigbee and iDetect are both very busy ...

As far as I can tell from your log and the steps in your post you did not perform:

disable zigbeeE
(keep iDetect enabled)
restart Domoticz

I'm not sure to understand what you mean.
Anyway I was in a rush yesterday and my info were not accurate
Regarding the sequence I gave yesterday, here are ...

not sure to understand if/how MP works... We'll see if you receive them or not! (stuck in outbox)

Much easier to read with complete logs. Thanks. There is a part missing from when it didn't work. Seems like you cut a lot above "ePresence: Initialized version 2.3, author 'ESCape'", but the log is not always in the correct order. Don't think I need it right now.

I did the log by copy/paste from ...

new version installed (delete old plugin and new install)
Still the same issue
the log at the dz restart => KO
023-03-29 21:18:44.458 Sunrise: 07:35:00 SunSet: 20:16:00
2023-03-29 21:18:44.458 Day length: 12:41:00 Sun at south: 13:56:00
2023-03-29 21:18:44.458 Civil twilight start: 07:03:00 Civil ...

Thanks
My config is not so good as yours!

To install the update I did:
/PROD_domoticz/plugins/iDetect $ git pull
and I've got
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands ...

Thanks for your help!
Could you give me the command the plugin uses on the router to get the devices? So that I could run it to check if there is something on the router.

Like in the first messages you needed to restart domoticz and later it turns out you only needed to restrat the plugin. Completely normal to gain these kind of new insights while troubleshooting, but sometimes confusing when trying to assist remotely.
I was also a bit confuse about this also ...