Never mind - turns out the bug was elsewhere.

Not finding anything that looked fishy in the relevant Domoticz source code, I upgraded the OS to a newer snapshot, and it turns out the memory leak was a (now fixed) bug in a library.

Version: current HEAD of development branch Platform: NetBSD/amd64-current Plugin/Hardware: RFXCOM, OpenZWave, and Domoticz - Remote Server Description: I'm running two Domoticz installations, both currently running the very latest HEAD of development. The main one is on NetBSD/amd64-current, and ...

So, I hit the "refresh node info" button and....my Domoticz is stuck again. So, I have to restart the service again. Do you not have that issue? Well this is new: in the logging I see: 2021-03-20 12:49:57.931 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 71.000000 ...

Hmmmm.... there is one other thing I need to figure out: if I revive one node, select the next one and perform the same action, Domoticz becomes non responding. Let's see how this can be fixed. Yeah, I've seen this, too. I was thinking of looking for the cause, but never got around to it, and since ...

OpenZwave: temporarily ignoring possibly wrapped power meter counter (NodeID: 22, 0x16) That means that node was suddenly reporting a lower total accumulated usage than what was previously recorded, meaning it looked like it had produced power instead of using it. The "possibly wrapped" is a hint ...

I run a new enough domoticz (current, from git) to not have that config file, but I've tried, unsuccessfully, to use the openzwave control panel to delete this node. Openzwave thinks the node is sleeping, so it's not on its dead list, and it seems that leaves me with no removal option.

Did you try selecting this node from the node list and press the delete button ? Yeah, I did - and it then seems to disappear nicely, but the above mentioned error messages are logged, and when domoticz is later restarted, it shows up again (because the Aeotec Z-Wave controller USB stick still ...

Still wondering if someone might have a hint for me...

I'm running Domoticz 4.10926 with an AEON Labs ZW090 Z-Stick Gen5 EU interface, and everything is working great! However, there's this one device that accidentally got completely reset while I was adding it to the system, and then added again - leaving its first presence under another node number in ...

...and now the industrious gizmocuz has updated Domoticz for Openzwave 1.6!

Ah, I don't have the changes any more - it was just a quick test. However, it's just differences in the declaration of the functions in question: during the compilation of Domoticz, the local declaration is used, and if its parameter list doesn't agree with the one in Openzwave, it'll fail during ...

I am sure there are changes that need to be made to Domoticz before it can use Openzwave 1.6, but looking at the actual error messages generated during linking made me notice something strange: There's a copy of the header files from Openzwave sitting in hardware/openzwave/, seemingly placed there ...

Not exactly an editor issue, but I notice that Blockly "scripts" may be enabled and disabled, and the system does what you expect, but dzvents scripts, once created, are forever active: you can disable them, even delete them, but they keep on working -- even after a restart. Actually, it's much ...

BTW Any suggestions for further events editor improvements are welcome Not exactly an editor issue, but I notice that Blockly "scripts" may be enabled and disabled, and the system does what you expect, but dzvents scripts, once created, are forever active: you can disable them, even delete them ...