Aeotec Smart Home Hub/2018/2015 Model Hub Firmware Release Notes - 0.48.03

There’s a seperate topic on this. I asked if these drivers count toward the total number of installed drivers but haven’t gotten an answer.
Why SmartThings has installed unnecessary Wemo etc drivers to my hubs

3 Likes

Must be just the first I’ve noticed them.

And I’ll amend my earlier post - I thought I deleted them, since got no error with CLI, but they are still showing up :slight_smile:

Saw the wemo driver too, but it had found a Linksys range extender, so at least had one device. But the driver was reporting comms errors trying to reach it, so I deleted the device. Wouldn’t doubt if it pops back up again the next time I do an Add device…

1 Like

With the force install of the ST unwanted drivers i find devices start to drop off my hub, they put me near 40 drivers, deleting them and 2 or 3 drivers now unused, stability returns and devices remain connected

For whatever reason the devices that drop off my hub are Ikea smart outlets, Ikea movement sensors and or a single Xiaomi temp sensor

I’m nowhere near the 40 driver limits, but also experiencing drop off issues with the Ikea Outlets

I removed the Linked Account information. I even deauthorised in Hue account. I selected the Hub to Hub connection, not the Linked Account connection.

Okay I can now see the Edge connection details in Meethue.com portal.

Follow up to my post regarding a problem caused by this firmware update to one of my drivers:

The SmartThings team has found the issue and will address it in their next update. In the meantime they’ve recommended a workaround which I’ve tried and it works.


Details For LAN driver developers:

When using the tcp socket receive() method, you can pass as a parameter the number of bytes you want to receive. YOU MUST NOW FORCE THIS VALUE TO BE AN INTEGER by using math.floor(), as in:

local number_of_bytes = 10
socket:receive(math.floor(number_of_bytes))

Otherwise, with the latest firmware update, Edge (C code) sees this parameter as a floating point number and this causes the error I reported earlier.

3 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.