SmartThings Community

Fibaro Light Switches NO LONGER SYNC Configuration Changes after SmartThings Hub Firmware Upgrade to 000.025.00026

Now that the SmartThings firmware upgrade has occurred, I have noticed a change in the way in which the Fibaro light switches (Dimmer 2 and Single Switch 2) function when they are added to the SmartThings Hub. In short, they no longer appear to sync configuration changes, requiring me to use Z-Wave Tweaker in the IDE to sync the changes.

I have v2 of the SmartThings Hub and use the Classic App.

All of the Fibaro light switches I added AFTER the recent firmware upgrade seem to have a problem syncing the configuration changes using the Classic App. When the configuration is saved, they no longer “sync” the parameters. They appear to store the changes immediately, but no longer display a cycling thru the parameters for a few seconds of a sync process. But the changes arent really implemented - ie, they dont appear to be synced/downloaded to the Fibaro light switch itself (just stored in the SmartThings Hub).

In addition, the interface in the app no longer shows one part of the energy usage. See my attached image, showing the switch interface of a Fibaro added BEFORE the firmware upgrade (on the left) next to the switch interface of a Fibaro added AFTER the firmware upgrade. My annotated red arrow points to the “dashes” in the “after” picture, as opposed to the wattage info on the “before” picture. A minor loss of display functionality, but still a bit annoying.

More importantly, as a result, whenever I want to make a configuration change to these Fibaro switches (added after the firmware upgrade), I need to use the IDE. I change the Device Handler from the “Fibaro Dimmer 2 ZW5” (or “Fibaro Single Switch 2 ZW5”) handler to the “Z-Wave Tweaker” device handler, and then make the changes in the Classic app using Z-Wave Tweaker. This works, but it is a bit of a pain.

Does anyone know why this occurred, or how to fix it? Havent yet contacted Fibaro support, but they may well blame this on the SmartThings Hub firmware upgrade.

Under discussion in the hub firmware thread:

@cbaumler

1 Like

Still without fix

Has anyone else noticed the symptoms I am having with the Fibaro switches (in my post above)?
Not sure if they were caused by the FW update or related back-end server changes by SmartThings.

I am using the workaround I mentioned (using the IDE and Z-Wave Tweaker) to implement parameter changes to the Fibaro switches. But, it would be great to know if others have experienced the same symptoms and how they have addressed them. Again, this only happens with Fibaro switches installed recently. My previously installed switches do not exhibit these symptoms.

I have the same issue.

I did some more troubleshooting and called Samsung tech support (elevated to Tier 2 - no info so far).
I am also going to alert tpmanley who is on this forum (tom manley - head of Zigbee at Samsung’s SmartThings Staff).

I bought and installed a V3 hub today - created a new location for the V3 hub while leaving my V2 hub connected as well (with 60+ devices). The V3 hub shows the current firmware (25.27). Samsung believes all Hubs should now be on 25.27, though my V2 hub is stuck on 25.26 (which may be related to the problem they caused, whether in the firmware itself, or in the back-end cloud server or the combination of the two).

Anyway, I removed one of my devices from my V2 hub (a Fibaro Dimmer 2 switch installed in the last week or so, which exhibits this Config problem). I then added it to the V3 Hub. Unfortunately, it still exhibits the same problem. I could not change the Config parameters without using Zwave Tweaker (which still works). And the UI still shows the same symptom (see picture in my prior post above with the red arrow pointing to the visible symptom of this problem).

While I cannot be certain, it does appear that the problem is not resolved by the 25.27 firmware or the V3 hub.
I suspect there is still a problem on SmartThing’s back-end cloud server, which is causing a partial incompatibility with Fibaro switches (and perhaps other devices from other manufacturers).

Would be nice to get some info from the Samsung engineers. Glad I didnt migrate all of my devices from my V2 hub to the V3 hub. Will wait for a resolution of this issue before even considering such a move.

Anybody else seeing this problem on V2 or V3 (with firmware 25.26 or 25.27)?

Yep, I have the same problem. If I use the "Fibaro Dimmer 2 ZW5 " device handler that runs locally there there are issues with the config sync. For instance, forced calibration (parameter 13) doesn’t run. A change from momentary to toggle ( parameter 20) for my switches and that does seem to update. I also notice a distinct lack of logging with this DTH.

If I switch back the Codersaur DTH one that I had been using successfully for a couple of years then the issue goes away. The problem there is it does not work with the new ST app and I lose the local processing.