I just excluded it, but I'll try to do a factory reset on it. As far as I can tell there isn't a parameter to enable / disable crc16.
I tried a factory reset. Also tried connecting it to my Fibaro Home Center to see if it had a firmware updated. It did not and still wants to talk mostly with crc16. I'm not sure what is unique about this model, but I think most of my Fibaro switch modules use crc16.
Trying to control it in Hubitat doesn't work of course:
I don't know how involved the CRCEncap implementation will be, some of these classes are cake, some not so much.
In any event I've added to my white board...
No problem, personally I'm not in a huge hurry to get it. As long as it is somewhere on the list.
Well this is a bit frustrating. I updating the hub and now all my Fibaro Dimmer 2's are not working. I originally had it on a bespoke driver from the community:
- Fibaro Dimmer 2 (FGD-212) Driver - For use on Hubitat
- Author: Robin Winbourne
- Date: 2018-04-01
It took me hours to get them working with this driver. Now none of them work with this driver or the new Hubitat driver.
What's the best plan of attack for this? I guess I'm going to have to go through the process of re-adding them all again, which is not great over Xmas when I've got guests in.
This is one of the reasons I moved away from the Fibaro Home Centre. Each time the hub was updated many things just broke. I hope this isn't going to be the norm.
You have the option to revert, to go back to a previous version. You'll want a saved backup from then too.
Two parts, ok?
The backup is of the DB, your UNIQUE stuff. the names you call devices, automations, everything You did to make the hub work for you.
Reverting the OS will, on boot, try using the DB as is.. may not work. The Hub keeps 4 backups on board. If needed it will try the previous DB and so on.. the point being, it may take more than 15 mins for the boot to be complete. Do Not Reboot in this process or you you may find you've corrupted the DB. Keep doing that and pretty soon all you have on the Hub is 4 dead copies of the DB.
To be fair @csteele, the lights had stopped working with Alexa before the update too, so I knew I'd have to start taking a look at where the issue was. That was the reason for updating the hub.
Anyways, I bit the bullet and re-added them all with the new HE driver. Thankfully, this driver is much more stable and adding them was nowhere near as slow as the bespoke one. Also, I can use a simple on/off with them (whilst I wait for my momentary switches to be installed).
I will pay much more attention to the updates from now on though.
Any love on this? As its a dedicated driver and you already have a option to select the type of switch, adding the scene to button conversion to the driver then with a option drop down to enable/ disable scene (send the parameter 28 1/0 and enable the bit of code) would be great
Your idea would also be great
But as both S1 and S2 can be used but diffrently you may need it for both.