Quick question? I know you’ve not contributed to this thread, but I have an interesting scenario happening with this LAN edge driver that I don’t understand (I’m not the developer), so I’d like your perspective or suggestions if you have time?
For a very long time this driver worked very well to control this device, and to update the attributes/capabilities (detailsview or dashboard) in the mobile app. Unfortunately this driver has stopped being able to update the mobile app, BUT is still able to send commands to the device to control it.
Where should I start trying to debug this issue? Unfortunately the original developer is no longer using ST and has left the community a couple years ago.
I’ve also experienced some issues recently. My HW Primary Partition 1 now shows the status as ‘No Connection to Panel,’ but the switches to turn the alarm on or disarm are still working, so I am connected. Additionally, the contacts, motion detectors, etc., turn on when they are open, but they don’t turn off immediately after they are closed – it takes several minutes or over an hour to finally show as closed.
I’ve power cycled my EVL4, ST, and router, but no fix. I then deleted everything, removed the driver, and re-added it, but it works as described above.
Is anyone else having any issues? Since philh30 stopped using ST is there anyone else who can take a look at this? Maybe another user who is proficient enough can start supporting this driver (this was a suggestion from philh30).
Hi @fpadar, I’ve asked for some help from @nayelyz because I believe it’s related to the latest hub firmware release. A change there was supposed to be backward compatible, but it seems like it’s not.
Rebooting and rebuilding will not solve this issue. I’ve already tried that too.
Thanks for the follow up @Cory_Heuschkel. Since the original developer, @philh30, is no longer on the platform and supporting the driver, several community members would like to know options to resolve this.
Wasn’t this change supposed to be backwards compatible? Seems like other edge drivers would be impacted too?
Since this driver uses custom capabilities defined by another developer, could another developer use the published github code to fix this and create their own new driver?
This driver was trying to access state for a device through the driver cache instead of using methods on the device itself. I am unsure how widespread this would be because it is up to the driver maintainer on how device states are managed.
With the maintainer no longer active, we should be able to fix this internally. We will check back next week with a Pull Request for the repo.
I’ve just had an issue that sounds like ‘stale information’ could be the root cause.
I armed my security system. Normally this causes cameras to come on because the status of the security system (panel) changes to ‘armed’.
I noticed that my cameras were NOT coming on. I checked and the panel status was “not ready”. It was reporting a fault with a sensor, yet the security system had no faults. I rebooted Envisalink, rebooted the hub and even unplugged the hub for about 20 minutes. All of this to no avail. The Panel still shows the same zone faulted and, even while the system is armed, the status is showing ‘not ready’.
I hope that you’ll be able to find a fix for this!
FYI (I responded to the post above with this….)
I’ve just had an issue that sounds like ‘stale information’ could be the root cause.
I armed my security system. Normally this causes cameras to come on because the status of the security system (panel) changes to ‘armed’.
I noticed that my cameras were NOT coming on. I checked and the panel status was “not ready”. It was reporting a fault with a sensor, yet the security system had no faults. I rebooted Envisalink, rebooted the hub and even unplugged the hub for about 20 minutes. All of this to no avail. The Panel still shows the same zone faulted and, even while the system is armed, the status is showing ‘not ready’.
I hope that you’ll be able to find a fix for this!
