Yesterday I had a case where all my Z-Wave devices were no longer accessible (I have already created a support ticket to investigate the cause). I only noticed this by chance because the shutters did not go down automatically.
Is there any solution to notify you about this? For example, if a certain device is not accessible for a certain period of time, you get a message. Or if more than x devices are not accessible. Or when sent commands fail. Or if the controller is offline.
If you look in a Local Meshbot triggers on a Device there is a “Device State” trigger option with “Reachable” and “Unreachble” this might work if you add all the devices you want to monitor into an OR trigger group. I have not tested it and don’t know if it actually works ?
In order to receive a message that contains the exact device, you would either have to create a separate MeshBot for each device or you would have to create a single Meshbot with all devices as an OR trigger and then add an exception as an action for each device.
It would be better if you could work with placeholders here:
Trigger: [any devices] state = unreachable
Action: Notification “[List of trigger=true devices] is unreachable”
Then it would even work without any further adjustments when new devices are added.
I dont know when it appeared. I noticed it yesterday when I was creating a rule for a Wol & Ping plugin device and initially it confused me, because I thought it was referring to if my ping plugin device was reachable or not.
However I then looked at some Z-Wave devices and the “Device State” trigger was available for those as well, so then I realised it must be for Network e.g. for Z-Wave and Zigbee devices if they are reachable or not.
I think there were some kind of placeholders in the notifications in the system MeshBots. But all System Meshbots seem to have disappeared at the moment.
To receive notifications for reachable/unreachable devices, we need to wait for the controller to poll the devices at their default intervals, or we can change the default polling interval: 5,400 seconds for battery-powered devices and 10,800 seconds for always-on devices. Please note that notifications will be sent according to these polling times.
Please note that ZigBee devices have their own polling times, which depend on each device and its configuration.
So even if the controller already knows and the dashboard shows that the status is reachable or unreachable, can this only be called up when the polling interval runs through?
But this information doesn’t solve my problem.
I would like the following:
As soon as one of the devices is offline for, say, longer than x minutes, I get a message about which device it is, so that I can notice it in time and intervene.
With individual MeshBots for each device or a huge MeshBot with many exceptions, you could certainly manage this, but it would be much more elegant if there was something that simply monitors all devices and then sends a message with the name of the device that is no longer reachable. Then you don’t have to make any adjustments to each new device that is added.
Another possibility would be to solve the whole thing as a system MeshBots. So when a new device is added, a system MeshBot is automatically created that reports when the device is no longer reachable.
we can change the default polling interval: 5,400 seconds for battery-powered devices and 10,800 seconds for always-on devices to your desired value, we only need remote access for that.
System MeshBots won’t solve it because they will depend of the poll intervals too.
So if every 5400 seconds it is checked whether the device is still responding, then a notification could be sent out at this interval if it is not available. Why shouldn’t this work with a System MeshBot?
I don’t care whether I am notified 5400 or 10800 seconds after the device fails in the worst case scenario. What is important is that I am notified at all. And that should be possible somehow.
Manually creating such a MeshBot for each device and then adding another one for each new device cannot be the only solution:
