As expected I get connection issues where the ‘Link Status changes to’ ‘Unknown’, ‘Connected’, ‘Rejoining’ - these are issues with the connection to the meter, and I have alerts built on them.
But several times a year the Eagle itself stops working properly - and returns a 404 error. Probably the internal web server crashes, and it takes a full reboot to restore. The problem is - the ‘Link Status’ in Vera remains as Connected. I think the Eagle does set a communication failure - like a Z-Wave device, but not something in the normal GUI that you can alert on an individual device level.
The problem I see is that when the 404 is being returned, Vera is taking 6 seconds to try to poll before giving up. Causing issues with other processes - in fact I found this investigating an unexpected LUA restart.
|02|09/25/20 10:16:20.248|e[33;1mluup_log:255: SmartMeterHAN1(0.74): Connection problem, nil status e[0m <0x7224e520>|
|01|09/25/20 10:16:20.249|e[31;1mLuaInterface::CallFunction_Timer device 255 refreshCache took 6 secondse[0m <0x7224e520>|
For now I think I need to delete the notifications based on Link Status which can get too chatty anyway, and instead pull the “LastUpdate” variable into a PLEG, and calculate the how long has passed since a good read - and alert on that as opposed to Link Status.
But something to think about for any revisions to this plug-in. (Also the Eagle might be more trouble than it is worth!)