Although this time it seems more specific to Fibaro Z-Wave switches. So suspecting Edge issues on the auto-update of the device drivers. Also not able to select new (Edge) drivers to prevent this. The SmartThings Z-Wave Switch driver causing the problem is 2023-04-11T19:49:58.144153692
Who can empathize or support finding the solution? Thanks!
So, you previously couldn’t change the driver controlling the device because you didn’t have another compatible driver installed, right?
Also, could you confirm that changing the driver for the device solved the problem and going back to the driver from ST causes the same error? I’m just wondering in case there was a temporary glitch and it starts working again. If not, it means the driver is broken.
If possible, could you go back to the ST driver and collect some logs for us, please?
Driver logs. For this, you need to set up the ST CLI and run the command below:
You’ll find the Hub’s IP address in the IDE > “My Hubs” section
2. Also, please share the Hub logs that you can send from the IDE.
@Alwas, I am also experiencing this problem with over a dozen switches by Aeotec. @JDRoberts was kind enough to point me here to watch how this unfolds. If the stock driver has a problem with this new firmware release, (47.10), there will be a whole lot more than the two of us having problems.
For anyone following, I’m having trouble with on/off button functionality too.
I was merely attempting to contribute to the discussion by offering up what the changes to the Z-Wave Switch driver functionality this week were claimed to be as not everyone reads the Pull Requests. Apart from fingerprinting they seemed (to my eyes) to be specifically targeting the sub-driver for Fibaro double switches, removing code replicated from the DTH they believed was unnecessary. How this relates to the OP’s problem I couldn’t say. Update: The Fibaro double switch was one of the new fingerprints.
With the roll out of the hub firmware starting on Monday afternoon and the driver update on Tuesday evening (both in UK terms) it would be fair to suggest that this is a new combination to many users, with only users of the beta hub firmware and the production beta channel driver previously experiencing it for a week or so.
Your timeline does seem to be moving the focus to the 47.10 hub firmware release, at least to me.
I was aware that ST were changing the way they handled on/off events in dimmers and a little while ago I refreshed my memory of a PR from a couple of weeks ago in which it was noted that the Aeotec Smart Switch 6 wasn’t responding to switch multilevel commands with the new way of doing things and so they applied a fix for it.
I’d imagine that the changes may have come on stream with the new hub firmware which is why the 6 is apparently working with the stock handler. Perhaps the 7 also needed the fix but no one reported it?
Whether this is also a factor with the Fibaro switches that were the reason for this thread I couldn’t guess.
Right on. I have no idea, either, if it is related. The Aeotec problems may be related to this thread or may be a red herring altogether.
When I was searching for others with my problem and stumbled on this thread with the same symptoms at the same time (inoperable switches + firmware upgrade + on/off not working + stock drivers not working), I did what I’ve seen @JDRoberts do a lot in the forums… This:
Hi @nayelyz - I had troubles setting up the ST CLI due to some update issues locally (not linked to ST). Did revert one device to the current ST driver to see similar issues & did send over the HUB logs for you to further evaluate. Sorry to not be able to assist further & good luck on the next deploy!
Unfortunately I managed to screw up my whole system before I found this thread.
I only had 1 Zwave switch that was affected so i though the switch was faulty as it is a few years old so i bought another one but was the same. Relay works but no control from app or voice. I decided to try a hub reset only to discover that i don’t have the welcome code so now i have nothing working at all.
I have emailed, phoned, and live chatted with Samsung and so far they have either not been able to help (live chat) referred me to the live chat that cant help (phone) or not responded (email)
Anyone got any pointers or help to get a welcome code quickly. I need to get this back up and running even if the Zwave is not working.
I will see if that’s enough information for the team, can you share the approximate time when you reverted your device to use the ST driver, please? That helps the team to find the corresponding messages in the Hub log.
Also, please provide support access to your account:
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
I clicked the link in your message. Enrolled. Found the driver and clicked Install. What should I do next? I went in to the IDE and tried to edit the device handler but I could not see any new handlers to choose?