Following remark/question about Z-wave and Indigo in specific.
Is there a way to teach indigo that it should ignore if a device does not respond in order to keep the whole scene running and not slowing down the whole network?
Background is the following: Sometimes our cleaning woman or my wife takes a device (eg. a z-wave RGB bulb) from the electricity and forgets to put it in.
When a scene like all lights out is triggered than this light can not respond. This leads to quite strange behavior of the rest of the network. Like seamingly arbitrate switching of lights. And that’s I think because the system tries to finish the task and switch also the RGB bulb off and get it confirmed.
A better solution would be if the light is ignored until it comes back up and still executions and finalizing the scene.
To me it seems that a little disturbance of the network (in form of an unreachable node) brings the basic functionality into danger. Of cause for some scenes this might be useful. Eg. Do not close window shutters when the window does not respond (and could be still open). But for others it seems to be absurd to create a disco light because one of the nodes is not responding.
Are there possibilities to tell Indigo to be more flexible there?
Gesendet von iPad mit Tapatalk