I personally am not familiar with Fibaro parameters, but if this is something missing from the DTH, we can reach out to the Fibaro team and ask them to update the DTH.
I’m not sure I understand. You pointed me to this same thread.
I saw your point re the RunIn issue (before the fix), but didnt see any info about what precisely was done to implement the fix.
For example, I am assuming you did not change the standard Fibaro DTH (“Fibaro Dimmer 2 ZW5”), and made changes only to your back-end cloud server code. Is that correct, or am I missing something?
If that is the case, I was wondering why there was a slight change in the UI (see my picture above).
It now says “Sync OK” (except during the actual sync) instead of reporting energy usage.
This is not a big deal, particularly given that you fixed the “sync problem” and my Fibaro Dimmer 2 switches are now syncing as I add them to the hub. By the way, as I suspected, I did need to remove the prior ones (that were added after this sync problem occurred, but before the fix) and re-add them to the hub. This worked fine.
Just wanted a little more detail to understand why the UI has changed slightly.
Gotcha. Sorry, I was under impression about the change to fix the configuration syncing issue.
I am not sure what has changed so that UI look different. I will run that by other folks and see if they can weigh in on the matter.
Why or how the UI changed is of minor importance compared to knowing if SmartThings are thinking/have thought/are in the process of introducing Z-Wave OTA updates which would benefit ALL ST users and be of gargantuan importance.
As much as I like to not deliver false promises, I may sound like a broken record and say it is on our roadmap, will provide more details as we move forward and once S2 functionality is released, we can say that be our next major feature that we’d like to release.
Hi! So the UI didn’t change for the Fibaro Dimmer. The way Fibaro wrote the DTH, they use a “multi status” custom attribute that is responsible for conveying both sync information as well as power/energy. That’s what you see in the corner of the main tile. They also have a separate tile for power and energy. Since we moved the device to local execution, the “multi status” events (since they’re for a custom attribute) aren’t generated by the hub, so only the dedicated power and energy tiles will display this information now.
I see. Thanks for the explanation.
I now have the Fibaro dimmers working on momentary switches, up and down, thanks.
However, why does the device handler provided by Smartthings not allow the user to change all parameters, like minimum brightness, parameter 1?
Also, I still cannot get the Fibaro single switch relay to work with a momentary switch, as the standard device handler once again does not include all parameters, of which number 14 is needed.
I can’t answer any of the questions about why the stock handler does what it does, but you can use the community-created Z wave tweaker for most mains-powered Z wave devices to expose all of the parameters and associations that the device reports, change those with the tweaker and save them back to the device, and then go back to using the stock DTH for every day use.
It’s just a workaround, but it’s a popular one.
Either I am missing something, but that device handler still does not work.
I am unable to change see or change parameter 14 for a Fibaro relay switch and it doesn’t show all parameters for a Fibaro dimmer switch.
Why is SmartThings allowed to advertise the fact they work with Fibaro devices, when clearly it is not straight forward!!!
Hey Robin. I’m taking a look at this. The device info page in the IDE should show the device’s firmware version in the “Raw Description” field (‘ver’, not ‘zwv’). I’m going to try to reach out to Fibaro to get an answer to this, but if y’all can come up with a version number under which parameter 38 doesn’t exist, I can get a fix worked out.
All my Dimmer 2’s with ver 3.03 don’t have parameter 38 and fail sync. Whereas all ver 3.05 pass sync successfully.
Thanks. Great place to start. I’ll get a fix started based on those numbers and see if we get confirmation from Fibaro.
Here’s my pull request with an early attempt at a fix: https://github.com/SmartThingsCommunity/SmartThingsPublic/pull/4231
We’re not quite ready to push it yet, but I think this is the gist of what we’re looking for.
Just checked in the fix. Fibaro confirmed that fw versions <= 3.04 are missing param 38. This will go to our staging environment next Tuesday where our QA will then test it, and it should be live in production on the 21st if the test goes well.
Actually we’re going to push that timeline up a bit so it should be live on the 14th.
The fix for this was released yesterday. To apply the fix you just need to edit and then save the device in either of SmartThings apps or in Graph/IDE.
I’m having exactly same issue with Fibaro Double Switch 2 and Single Switch 2 (FGS-223 & FGS-213) . All devices are firmware version 3.3. Hub is 26.00009. Using default device handler for them all. Have to use z-wave tweaker to set parameter 20 to 0 on all of them.
I believe this is the same issue but if not i will open a new thread.
I tried that but whilst the device seems to remember the parameter from the other handler when I switch back to official handler still no sync. If I try to change a parameter again, it will not take with official DTH.
Hi I’m just gunna jump on this thread I’ve just added a fibaro dimmer 1 (211) a couple of days ago and I’m having an issue where I’m setting parameters but it isn’t making any changes to the dimmer module so I believe it isn’t syncing over, if there has been a fix it doesnt seem to have worked for the dimmer 1, its driving me crazy any help would be greatly appreciated.