Domoticz

So disappointing ... after long time new version Domoticz (and OpenZwave) .... 3.5955 ...

Still flashing green on that despicaple thing.....

2016-09-04 22:29:12.199 OpenZWave: Received timeout notification from HomeID: 25480967, NodeID: 9 (0x09)
2016-09-04 22:29:22.204 OpenZWave: Received timeout notification from HomeID: 25480967, NodeID: 9 (0x09)
2016-09-04 22:29:22.937 OpenZWave: Received Node Dead notification from HomeID: 25480967, NodeID: 9 (0x09)

When a pi/domoticz reboot solves it, how difficult can it be to do this with software control

Just set the parameter to 255 so the led only flashes after 255 minutes.
Or use a script to repeat a signal after 250 minutes.
Or enable polling.
Or move the switch so you don't see the light.

Polling is on. Probably this helps the device faster to be declared dead as it is detected more quickly.

The issue is that when it is dead and the light flashes, the socket switching commands are not executed.

I still think that it is possible to program a workaround. I'll keep digging, perhaps it is possible to fire some command to the OpenZwave API.

Marked as dead has nothing to do with the flashing led, except that it starts flashing after x minutes of no communications.
You should figure out why it gets marked as dead, maybe something is causing interference.
Try moving the greenwave or the zwave antenna.

Or it is in fact malfunctioning. A while ago I bought 3 second hand power nodes. Two worked perfectly and are still working like a charm. One started clicking after sometime and then was presumed dead. Adding the thing again seemed to work...for a few minutes.
Didn't take long and I was sure it was just broken.

Contacted the seller and he has paid me back the money for the broken node. Very nice of him!

After that I threw the node in the bin. The only right place for the node.

Egregius wrote:Marked as dead has nothing to do with the flashing led, except that it starts flashing after x minutes of no communications.
You should figure out why it gets marked as dead, maybe something is causing interference.
Try moving the greenwave or the zwave antenna.

Correct, that's why I don't want it to be declared dead It just notifies me of the latest issue.

Interference is possible although the distance is only a few meters. It also happened when the distance to the controller was only 1,5 meter of less.
And it happens completely random, from twice a day to no issues for many weeks. The log only mentions 3 timeouts and then declares the greenwave dead. No other indications for problems or causes. There are two other mains sockets in the neighbourhood, so some communication should be possible.

What I am looking for is that I can send the same command to the greenwave after some timeouts, as the Pi/Domoticz/controller sends when rebooting the system. Then I have a software workaround. The greenwave always listens, I do not have to touch it to get it alive again.

Repeating a command every x minutes isn't that difficult.
In my pass2php script that would look like this:

Thanks, that is a good detection.

And then now for the 1M€ question: what will be the command?

Enabling and disabling the debug logging on the Aeon S2 stick will restart OpenZwave and revives the greenwave. But I'm looking for a smoother command because te Zwave restart makes my doorsensors blind for the time period of their wake-up interval. That is very long, 1-2 hrs (or eats their batteries).

The command will be whatever the status of the switch is.
So if the switch is off, the command will be to turn it off. Because of the communication the led will stop flashing.
But, if the device is marked dead before that it won't work.
Therefore you should try if you can revive the node in OZWCP with the has node failed command.
Also for that, I have a php function, if interested.

Yes I'd like to see that. I only have little knowledge of PHP. There are lots of examples on the Domoticz wiki, but not how to start them.

I'm affraid there is one catch: if openzwave has listed a timeout, the switch command probably never will be executed. The polling / reading power useage should function the same as setting a switch? In fact, any command to the greenwave may mess up and cause a timeout, I suspect.

I just remembered that I indeed did that last time, but did not press the magic buttun in OZWCP, or just did not find it

If that works you could use my 'refreshzwave' function to automagically revive dead nodes

Ok, where can I find that?

I'm not sure if it works or not in OZWCP, I am not at home there...

It is part of my pass2php script: http://www.domoticz.com/forum/viewtopic ... 23&t=12343
But you better first test in OZWCP to be sure.

I can't find the revive button/option/menu in OZWCP. Where to look or has it a different name?

Somehow those numbers don't look good: Today I discovered that the Greenwave isn't declared dead anymore (although it is flashing). The log is filled with continued
2016-09-10 21:39:44.021 OpenZWave: Received timeout notification from HomeID: 25480967, NodeID: 9 (0x09)
2016-09-10 21:39:45.652 OpenZWave: Received timeout notification from HomeID: 25480967, NodeID: 9 (0x09)
2016-09-10 21:39:46.656 OpenZWave: Received timeout notification from HomeID: 25480967, NodeID: 9 (0x09)
etc.

This software version Domotics/OZW behaves worse than previous. Now all day ALL zwave devices are dead too, no temp/door indication and switches can't be controled. Drama.

I didn't say 'revive button' but 'revive' the node with the 'has node failed' command in ozwcp.

OK. I did that too but nothing happened, on screen or on the green wave.

Does anyone has the problem with the node not being updated in Domoticz and the power button is pressed manually?

Sometimes a node stops working and when I press the button manually all works again.