Domoticz

Posted: **Monday 04 March 2019 11:16**

I am using a Raspberry 3B+ with "Linux domoticz 4.14.83v7-aufs #1 SMP Wed Nov 28 22:52:43 CET 2018 armv7l GNU/Linux" and Domoticz V4.10531
Yesterday I recieved a controller error.

Code: Select all

2019-03-03 16:03:08.889  Status: OpenZWave: Received timeout notification from HomeID: 4094017987, NodeID: 255 (0xff)

No other errors where found in the domoticz.log
There is no NodeID of 255. After that error the Aeotec ZW090 Z-Stick Gen5 EU stopped working totally.
In the OZW_Log.txt I found the following errors, which are not very helpfull.

Code: Select all

2019-03-03 16:03:08.887 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-03-03 16:03:08.887 Always,
2019-03-03 16:03:08.887 Always, Dumping queued log messages
2019-03-03 16:03:08.888 Always,
2019-03-03 16:03:08.888 Always,
2019-03-03 16:03:08.888 Always, End of queued log message dump

I noticed it when it got dark. I finally got it working again, luckily without loosing anything.
It took me a lot of try and error before I got it working again.

The hardware setting of the stick on the nightly heal is:

Code: Select all

3. Enable Nightly Heal Network (04:00 am):

Enable/Disable nightly heal network.
Last Update: -

That heal did run this morning with 2 nodes which did not respond in time, but are working good.
Strange is that the Last Update does not show todays date/time

Did anyone noticed this before?
Does anyone know the cause and how to prevent this?

Posted: **Monday 04 March 2019 17:19**

Hi...same devices..same behaviour..

Posted: **Monday 04 March 2019 20:50**

Same hardware, same behaviour.
This has been reported a lot, unfortunately.
No one has found a culprit or took a look.
It can't be my Mesh with 36 devices the mesh is strong.

Posted: **Monday 04 March 2019 20:52**

I have 36 devices too..I read about Zensys tools.. I guess I am gonna try that...I have read about it..it seems that its also capable of removing/deleting unknown / dead nodes

Posted: **Monday 04 March 2019 21:01**

Tnx, for the answers, I am not alone. So nobody has an idea where the NodeID 255 comes from.

Posted: **Monday 04 March 2019 21:10**

Nope, sometimes days nothing happens.
Then at a sudden out of the blue some nodes have a timeout with sometimes also the node 255 pops up.
Have been setting up all devices three times which seems logic but didn't help.
Last 14months i also have trying replacing plugs and other devices to be sure it aint my meshnetwork which didn't help.
Also have trying all other tips and tricks mentioned in this forum which also didn't help.
I know we aren't alone and unfortunately it seems the issue can't be reproduced by the devs.
So for now we are stuck...

Posted: **Monday 04 March 2019 21:36**

As far as i know node 255 is the controller broadcast. It might refer to any error related to low level issues based on serial port, hw issues, linux issues... Are you guys all using the same version of domoticz? You might need to reset your controller and redefine all nodes.

Posted: **Monday 04 March 2019 21:44**

I am on the latest Beta, whatever I do in the z-wave controlpanel doesn't seem to come through... i can only cancel the operation..

Domoticz

Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)

Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)

Re: Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)

Re: Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)

Re: Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)

Re: Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)

Re: Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)

Re: Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)

Re: Zwave Controller error (Aeotec ZW090 Z-Stick Gen5 EU)