New firmware hub 54.10 it Broken edge shelly drivers and tasmota edge drivers

Developer Programs
1

Devices created in Smartthings with @TAustin edge drivers for shelly are broken when updating the Hub with the new firmware 54.10. The devices are online but do not respond to manual activation or routines.

1 Like
2

Are you still having issues with Tasmota Edge driver?

1 Like
3

Hi @hongtat, thank you so much, your last update edge tasmota drivers solve all issues with my tasmota devices.

Pdt: edge shelly drives are still broken

1 Like
4

Hi, @cljara80, @hongtat

@hongtat, which change did you apply to the driver to make it work again? We’ve seen other reports about custom LAN drivers failing. I’m just curious in case this can help with the other cases.

For now, @cljara80, can you replicate the error and provide the following info?

  1. Screen recording of you trying to control one of those devices
  2. Driver logs (you need to start listening to them before sending a command to the device)
How to get them?
  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, send commands to the devices so they get registered there
  3. Copy those logs in a file and share it with us, you can send it to build@smartthings.com.
  1. Hub logs
How to get them?
  1. In the Advanced Users app, enter the “Hubs” section
  2. Enter the corresponding Hub and click on “Dump Hub logs”
  3. Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
  4. You’ll get a green box at the top confirming the Hub logs were requested.
  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (â‹®) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
1 Like
5

It is the getpeername() function. It freezes and restarts the driver.

I remove the getpeername() call, as the driver already has the IP addresses of all the LAN devices, so there is no need to get the incoming IP address.

2 Likes
6

Any news about implementing the fix in Shelly drivers? @TAustin?

1 Like
7

Unfortunately TAustin has not posted on the form since April.

1 Like
8

Oh, I hope he’s all right. Nothing critical here, just a mouse trap made smart with Shelly Uni. Maybe I have to go with official (cloud) integration.

2 Likes
9

hi @nayelyz, sorry for the delay, but I had problems with the CLI installation.

  1. Done (send video to email build@smartthings.com)
  2. Done (send logs of Shelly device driver 1.9 to email build@smartthings,com )
  3. Done (hub logs)
  4. Done (share my account smartthings, that no same account forum)
  5. Done (Enable support access)

PDT: I am currently using cloud to cloud shelly integration to be able to use shelly devices

1 Like
10

Hi, Claudio

I checked your logs and noticed the following error:

caused by: Watchdog error ....

The devices shown in your video are included there. The engineering team mentioned this error appears when the devices are in a deadlock.
Each operation on the Hub happens in “coroutines” which allows us to pause a function if it’s waiting for data to arrive. If there are two tasks waiting on each other, it would result in the driver not able to make progress.
Currently, the engineering team is checking the issue with the function “getpeername()” so, once we have more information, we’ll let you know.

1 Like
11

Thank you @nayelyz , I will be waiting for new news.

1 Like
12

Fix is on its way for beta users:

3 Likes
13

Hi, @cljara80 as @mocelet mentioned above, there will be a release to fix this issue, however, as we saw your devices presented the error "caused by: Watchdog error".
After you receive the new version, open the logcat and send commands to the devices to see if it’s still showing up.

1 Like
14

Hi @nayelyz, as soon as I have the new update I will send the logs.

Do you have a planned release date for the new firmware for non-beta users?
Thanks

1 Like
15

Hi, @cljara80. The team mentioned the dates will be updated on the status page: https://status.smartthings.com/

So, please keep an eye on that for a better reference but it shouldn’t take too long.

3 Likes
16

0.54.13

Sep 24, 2024 14:00 - Oct 18, 2024 22:00 UTC

1 Like
17

I received the update 54.13 (non beta tester) and all my LAN devices are back online, no errors or crashes on the driver logs so far.

Thank you!!

4 Likes
18

Good news !!, may be, do you have shelly edge drivers??

1 Like
19

Hi @nayelyz , my hub update to firmware 54.13 and the problems with the shelly edge drivers are resolved, they are operational again.

Thank you !!

4 Likes
20

Hey @cljara80 that’s great news! Thanks for taking one for the team :hugs:

My Hubs had not yet updated from v53.19, so I was very concerned having a bunch of Shelly Devices.

My Hub that has the Shelly Devices connected has now updated to v54.13 and all of the Shelly Devices are functional !!! :hugs: :hugs: :hugs: