I use 8.0.2 from https://github.com/darkxst/silabs-firmw ... r/releases and that version fixed some issues I had with OTA upgrades of devices (but that is from February and not March). I saw something that 8.0.3 had issues so I do not dare to upgrade at this point.

Interesting, it works for me. But I am starting to think about reolink_aio version and Python version combinations.
You have Python 3.11 with a later reolink_aio version I guess?

But can you also restart your camera and see if that helps?

Ah! And I realized I should change the CSS instead. Class "screen" might be ok in the scenario the OP has.

function deviceHook(device) {
if (device.idx==<DEVICEID>) {
var col = (device.Data === 'Off') ? 'green' :'blue';
var elements = document.getElementsByClassName("screen");
for(var i=0 ; i ...

I wish, I just jotted it down while eating breakfast (stupid, I know but I got a bit inspired, it won't happen again).

I have updated the example to something a tad bit more useful. But the key Google word was persistent data in DzVents something I have not tried before but seems really useful ...

I would consider DzVents and the use of persistant variables - you can see more here: https://wiki.domoticz.com/DzVents:_next_generation_Lua_scripting#Script_level_persistent_variables and look at the special History variable.

This is completely untested but might serve as an idea of how you might ...

Well, I assume you can do this in several ways. This is one I just tried with.

You need to add (or change) your custom.js file and add something that changes the background. I suggest adding the code in beforeFirstRenderHook().

In this code I have a switch device (<YOUR DEVICE ID>) that can be on ...

I am sorry for the late reply. I have done a slight change to the plugin and it might have caused issues. I have the same doorbell (it's the reason I wanted the module for myself).

What happens if you update the plugin and try again? If it doesn't work please PM me the logs from the module and we ...

3402 is a Phillips Hue LWG004
f17d is an IKEA TRADFRI control outlet

I get these type of errors from z4d "Error: Z4D: _send_and_retry - Unexpected Exception - rawaps_read_attribute_req 00:17:88:01:08:3c:63:e3/0x3402 0x104 0x8 payload: b'\x10\x08\x00\x00\x00' AckIsDisable: True RETRY: 1/1 (NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT)"

and now the controller ...

Interesting, I made a simple version for temperature (but didn't bother with a click function etc). Perhaps not something to build on, but an example where a linear gauge chart also might be applicable.

Thanks for the report. None of my cameras have support for detection of animals (dog_cats). I hope I have fixed this now so please update the plugin.

If not please PM me with the logs of Domoticz for the startup of the plugin.

I saw that 7.1.015 had a fix to OTA. I got this error after an upgrade and Z4D trying to do an OTA on a Hue LWG004.

Hmm, I got the same type of error again after a restart of Domoticz.
Update: This time a reboot solved it, it seems.

2024-11-30 15:58:32.826 Z4D: Worker thread started.
2024-11-30 15:58:32.826 Status: Z4D: Started.
2024-11-30 15:58:32.826 Status: Z4D: Entering work loop.
2024-11-30 15:58:33.500 ...

I have been using Z4D with Sonoff-E dongle since summer and everything has been working ok. But on Thursday night the controller started to not turn on and off lamps (which doesn't impress the wife) so I tried some stuff, reverting back to an older Z4D plugin version, I installed the plugin and ...

I got it to work (I hope). I simply did a reset of the controller (using another PI and a fresh install of Z4D) and then started to re-pair all the sensors. 16 out of 32 done and the plugin seem to be stable thus far.

I have an old Conbee II and simply changed the settings in the plugin. From what I have read in other threads that should work and giving me the opportunity to keep all sensors (and if needed simply re-pair with the plugin again). Currently I am running the Conbee II. I am changing sensor for two ...

I just bought at new SONOFF ZBDongle-E and tried to install it to Zigbee for Domoticz. The device is found, and the first try worked for a while before the plugin restarted. I then rebooted and now I get a "restart-loop" as illustrated in the logs:

024-09-27 20:26:01.391 Status: Z4D: Started.
2024 ...

I got mine today. A bit tricky to manage to press the button (to large fingers :) ?). But when that worked the led-flashed and I got this as a response from Z4D (and it includes an error).

2024-09-09 18:23:47.089 Z4D: Assisted Pairing: Polling: []
2024-09-09 18:23:47.089 Z4D: --> Empty queue
2024 ...

Hi, I have not seen that error message before. A Google gave this link https://stackoverflow.com/questions/75608323/how-do-i-solve-error-externally-managed-environment-every-time-i-use-pip-3

You can read that page to see if something helps. I think this might solve this issue (and seems at least ...

Hi, I think I spotted the bug. It should be fixed in latest commit ie update the plugin.

I have used the XML-file from Rik60 as verification test and that message parses OK.