Edgebridge

Devices & Integrations Community Created Device Types
, , , ,
167

Other LAN Edge drivers have reported issues with the new hub update (0.54.10).

The culprit appears to be the getpeername() function which I can confirm is being called in the watch_socket function (line 188) of the LAN Motion Driver.

It appears @TAustin isn’t actively monitoring these threads but is there someone on the Dev Team (@nayelyz can you help?) that knows why this call to getpeername() appears to cause things to “blow up” since the 0.54.10 hub update?

3 Likes
168

Hi, @Puzzling
I already opened a report for the engineering team as they mentioned this required further investigation, so, once I get more info, I’ll let you know.

3 Likes
169

Thanks for following up, @nayelyz. I’ll keep my eyes open for updates.

170

Hi, everyone!
The engineering team announced this release to fix the issue with the function of getpeername(), once it’s rolled out, please check if the devices start working again, if not, open the logcat using the CLI and see if an error starting with “caused by: Watchdog error” appears:

  1. For this, you need to set up the ST CLI and run the command below:
smartthings edge:drivers:logcat
  1. The CLI will prompt you to select from which hub and driver you want to listen to events
  2. Then, try to send commands to the device and see what’s registered there.
5 Likes
171

I can verify that everything is working normally again on firmware version 054.00013. Thanks everyone!

3 Likes
172

Same here. LAN Motion driver is working again.

2 Likes