Good new/bad news: I think the latest firmware update broke something. I set up a test, and there is something that’s not working right. I don’t know if it has to do with the problems you are seeing, but it has to do with the Edge driver socket server. It doesn’t seem to be working right and the result is that it is hanging edgebridge when it tries to forward a message. This would affect multiple drivers potentially… ugh.
Give me some time to look at this and I’ll keep you posted. No sense you doing anything more until I get this figured out.
@TAustin My hub got an update at 2023-01-19 8:12 PM UTC, which is when phonepresence stopped working for me as well as a custom LAN Device Trigger. The POST requests to the hub simply hang and timeout. Hopefully you are able to figure out how to fix it. Awesome work!
As I mentioned above and some of you have found out the hard way, there seems to be a change in the socket library in recent firmware updates that has resulted in communications no longer working between edgebridge and the Edge driver. (TMI for most, but it appears to be in the Thread:register_socket method.)
I will take this issue up with the SmartThings staff, but in the meantime, in order to get things working again I had to make some code changes in the following drivers:
LAN Motion
LAN Presence
LAN Contact
LAN Trigger
LAN Trigger Multi
Not everyone has experienced these issues yet, so you may not see any change with these updates. But for those that have reported their motion or presence no longer being triggered, hopefully this will fix that.
I found in my testing that there are some cases where this problem may cause your edgebridge app to get ‘stuck’. There are no tell-tail messages in the log output, so you won’t know just by looking at the log. So if after the driver updates, you are still having problems or your edgebridge app seems to be locked up, you should restart it.
For example on Linux:
sudo systemctl restart edgebridge
If you are running it in a terminal window or command prompt window, then just Ctrl-c/Ctrl-break out of it and restart it again.
I hope this averts this particular crisis. Please let me know if things are working ok.
Be sure you get the driver updates first. If you still have the earlier ones, they can just hang edgebrige up if edgebridge tries to send anything to the hub.
I just set this up and everything seems to be working. Has anyone experimented with sending data the other direction. With the previous integration I could update Blue Iris profiles based on the Security status in Smarthings. Arm (stay), Arm (away) and Disarmed. This seems a little more complicated then what the bridge does today. I guess it would have to be more specific to blue iris itself
