Domoticz

I have to say, after the switch to OZW 1.6 I went back to the previous version as none of my secondary buttons on my Qubino's worked anymore. Running into different issues, I made the jump to 2020.2 about 2 months ago. I had to rejoin my Qubino's, and now have to hold the secondary switch for 4 seconds for them to be recognized.

On OZW 1.4 I had issues with Qubino flush switches that would go roque; I had to do a z-wave exclude and include after which they worked again. This has happened to me twice.

Besides these two issues I did not have any other issues, and all together pretty happy. I do not have any battery powered z-wave devices. On 433Mhz I always had issues with range; all of a sudden some switches further away did not work anymore. For all my plug-in needs I switched over to Zigbee (Philips Hue bridge with Osram Smart+ Plugin switches) and only had one issue so far with a switch I had to rejoin once.

So for me 433 caused me a lot more headaches, Z-Wave a little, and Zigbee only one minor hickup in about a year. Zigbee does feel like the most robust protocol so far, but does not have the 2-way capabilities z-wave has.

Guys,

I'm reading this topic and noticed that the conception op z-wave in combination with Domotics varies a lot.
I'm using it without any major issues and have aonly z-wave devices with a view script.

The only issue i'm having is with 1 battery operated light switch which does not give the battery level after a restart.
Maybe the hardware or OS of the server is propablity os some issues by some people, but i couldn't fine a a common thread in the stories.

Just my 2 cents.

I'm happy with Domoticz' stability at the moment

ArnoutZ wrote: ↑Sunday 27 December 2020 17:26 @sieth: I also thought about abandoning Z-wave an move to Xiaomi sensors. Are you still using Domoticz? What Zigbee gateway do you use?

ArnoutZ, I just use the Xiaomi gateways (version 2 I think).
I use the gateways (3 piece's) also as a notification speaker for my alarm or doorbel and as a hallway light.
I still use Domoticz as I'm happy with the combination with dashticz.

Greetings!

running Domoticz2020.2 (build 12763)

same issues: incorrect state Domoticz AND correct state Openzwave cp

commentator wrote:running Domoticz2020.2 (build 12763)

same issues: incorrect state Domoticz AND correct state Openzwave cp

12760 with all nodes refreshed: 1x non responding wall switch in 1 day (domoticz showed ON, but light was OFF. Turning it off and back on again, made it work in sync again.

12760 with all nodes refreshed: 1x non responding wall switch in 1 day (domoticz showed ON, but light was OFF. Turning it off and back on again, made it work in sync again.

Same here and also on 12760.
Yesterday installed 12763 and lost a lot of battery operated devices.
Make a backup of the image on a daily basis so quickly went back to 12760.

When will we get a stable z-wave installation

Upgraded yesterday to 12774 and, keep fingers crossed, allready 1,5 day without problems.

JuanUil wrote:Upgraded yesterday to 12774 and, keep fingers crossed, allready 1,5 day without problems.

Are there any zwave related improvements since 12760?

still on 12774 and no problems

Are there any zwave related improvements since 12760?

don't know but with 12774 all is working wel

I also have a lot of problems with zwave and domoticz. Randomly dead nodes after a reboot it works again for a few days. Then out of the blue usage devices stop updating while the switch function of the device keeps working. Frequently (mostly after a reboot or after an update of Domoticz) some battery devices get Type 0x0000 and stop working sometimes a refresh node info get it working again. I have this problems for very long time and at first i thought it was caused by a to small network so I bought more zwave devices but this did not help.
The problems are there even in the lastest beta 12803.

today updated to 12803 and all of the sudden a motion sensor (battery operated) was gone. when I wanted to reinclude another sensor disappeared.
pffffft getting tired of this.

jake wrote:: incorrect state Domoticz AND correct state Openzwave cp

12760 with all nodes refreshed: 1x non responding wall switch in 1 day (domoticz showed ON, but light was OFF. Turning it off and back on again, made it work in sync again.

I have to admit that after above error everything has been stable without further updating of domoticz.

Today I saw the message below.

OpenZwave: temporarily ignoring possibly wrapped power meter counter (NodeID: 22, 0x16)

Node 22 is a NAS-WR01ZE Power plug 12A+ from Shenzhen Neo Electronics Co Ltd
Someone knows what this mean? When I google it I find nothing.

Great to see so many responses to this thread! Great to see I am not the only one.

I will get back to this myself as well. However, as promised, I have been adding all nodes again and logging how things went. And one thing was very constant: immediately after adding everything was just fine! And then somewhere in the days/weeks following, weird stuff started happening.

I will add a post with my findings more in detail and I will most likely update Domoticz to one of the betas as well and see if it fixes the issues.

roblom wrote: ↑Monday 04 January 2021 21:07 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 that maybe that counter overflowed, in which case it would go from a large value to a small one. When the code sees this, it'll ignore the reading, in case it was just a communication glitch, but if it persists for more than an hour, it'll register the new count, and work from there.

Until very recently, this situation would lead to power consumption by that node no longer being recorded - the temporary suppression, limited to one hour, after which recording will resume, is new, which is why you haven't seen this message before.

@roblom, yes this happens A LOT with Neo Coolcam plugs... specially the new types.
What happens is that we get correct counter values like 1001, 1002, 1003, 1004 and suddenly (for some minutes/30) we get 20, 20, 20, 20, and then 1008, 1009, 1010, ....
I still have to investigate if it is always the same counter value, If it is, we could ignore those values
But this is hardware related ... specifically for these cheap nodes

I had already drafted a first response, but I've been so busy re-including devices that I didn't find the time to put it here...
23-12-2020
Thanks for the responses! Good to see, that it is not only my installation that has this.... So, before responding to the individual responses, I'd like to outline how I am trouble shooting things now.
I am gradually adding all devices again. And adding now means:

• Delete the underlying devices of a node
• Remove the node from Z-Wave by excluding it
• Factory reset the node
• Add the node again to Z-Wave
• Add the devices again

If possible I do this within reach of the controller, but in some cases that is impossible. Anyway: as long as I am able to add a node and its devices to Domoticz, I should be fine, right?

By this time, I have done this for 26 devices. However, I must point out, that three of those were added before removing the Greenwave single power nodes from my network.

In general it would have been really nice if you could appoint a node ID (the 0xsomething-something number) yourself. Then I would make sure only stuff like a1, a2 etc is used as those can be found much more easily in the devices list. If you have a number lik 53....you know how often that occurs?!?

Well, let's have a look! I am not going to point out the devices that are still working fine.... it is "trouble" shooting after all

• Overloop, Coolcam multi sensor: Had to replace the battery and somewhere in the past days all parameters had been reset to defaults.
• Woonkamer, Aeotec Gen5 multisensor: 17-12-2020: sensor does not respond to movement. On time and group 1 parameters were reset to default
• Hal, FIBARO System FGSS101 Smoke Sensor: 20-12-2020: Had to add it again. The first addition did happen before removing the Greenwave power nodes.
• GreenWave Reality Inc PowerNode 6 port: Hasn't been reporting power consumption and is unable to switch 5 of 6 outlets. Power delta to start reporting was set to default. The node itself points out last seen 2020-12-22 14:22:57, but 15 out of 18 underlying devices show last seen 13-12-2020
• One of the Coolcam power nodes seems off, but I think that is because only a LED christmas light is connected to it, that is not enough to report.
• Slaapkamer, Coolcam power node: power report value was set to default
• Slaapkamer Sanne: FIBARO System FGSS101 Smoke Sensor: Unknown: id=0000 Unknown: type=0000, id=0000. All configuration gone. Same in the control panel
• Zolder: AEON Labs DSB05 Multisensor: Last seen 21-12-2020 Underlying devices last seen: 18-12-2020. This has been included on 15-12-2020. So has been working for a while and then just quits.
• Slaapkamer: Coolcam multi sesnor: no battery indication, not on main node nor on one of the devices below it. OZW control panel says 100%
• Zolder/washok: FIBARO System FGSS101 Smoke Sensor: no battery indication. Only temperature last seen 22-12-2020. Perhaps it is a good thing that the smoke and heat alarms have not been seen recently, but they do have battery indication!
• ...and then I stopped making this list any longer. Because it goes on and on...

Basically, some devices in the attic are not responding, so it seems out of reach. However, I was able to reconnect the GreenWave Reality Inc PowerNode 6 port while it was in the attic. After adding it just get out of reach. And the strange thing is, that the Coolcam powernode that is working properly is pretty close, so that should act as a hub.
I think I do recall that these devices were not too happy when communicating not directly to the controller.

Let's focus on an Aeotec Multisensor that I am using in the living room.
This is the last entry in the logging of the movement sensor:
2020-12-23 01:35:30 On

I do see the movement in the room being noticed as the LED on the sensor blinks. Now please have a look at the following screen shots: It shows the node was last seen on 2020-12-23 at 11:42:41
Motion sensor is enabled and reporting is set to 225 and an interval of 720 seconds
Strange enough the motion has last been seen 2020-12-23 at 03:32:00 whereas other sensors (light and temperature/humidity have been last seen more recently)
And this is what I see happening all the time! The node has been seen recently, but one or more devices beneath it not. And the only way to "revive" it is by removing and re-adding.

In this case I tried the following:

• Pressed the inclusion button for 3 seconds: nothing changed.
• Pressed "Heal node" button in Domoticz: nothing changed.
• In Domoticz changed the name of the node to "Woonkamers" and then back to "Woonkamer". Both changes were reflected in the OZW CP.

If I leave it like this, without doing anything, I expect it to start detecting movement again as sudden as it stopped doing that.

In the OZW CP there is some logging as well, but most of it, I don't understand. Does anyone here understand it?

commentator wrote: ↑Saturday 19 December 2020 13:25 root cause: the incorrect state in Domoticz. Openzwave cp state is always correct

see https://github.com/domoticz/domoticz/issues/4352

I know you pointed this out before. This is one of those topics that died out, because.... no clue actually. Perhaps here different things are happening. That is why I am doing the analysis. In this case the OZW CP displays the same as the node information. So, this seems to be a different issue.

I had some additional images showing that every 5 minutes lux and temperature was nicely reported, but I am allowed to only include 3 pictures.

Update 30-12-2020 All smoke sensors that have "Manufacturer" "FIBARO System" have set the parameters to default
All smoke sensors that have "Manufacturer" null have no parameters at all.
The same goes for the Coolcam multi sensors

And for the Aeon multi sensors What causes this? Why are the parameters set to default?

Today I have updated to version 2020.2.12825 because I read that things should have been improved on the Z-Wave side. So, I am really looking forward to some improvement! I understand I need to re-include the nodes once more...let's try that.

As I understand here and there some people do not experience issues with Z-Wave. I am really curious as to what I am doing different!

As a last update, I'd like to share the Excel sheet that I used to log my efforts in re-including all nodes.