Driver changing flow card Id - is there a migration?

Developers
1

As the driver has expanded, I am realizing that a flow card Id needs to change.
I am assuming that if I change the Id of this flow card, that people using the existing driver with the existing flow card Id will break.

Is this true? If so, is there a proper way to do a migration when installing a new driver?

2

There are no migration options for using a different ID for flows nor for driver to a new driver, people will have to fix them manually (or re-pair: remove, re-add and fix all their flows).
You can tag a flow card and/or drivers that is old as “deprecated” so it won’t show up anymore for people creating new flows.
but that’s the only “migration” option.

3

Thanks. That actually helps. I might tag it deprecated and then introduce the same flow with the new id.

BTW, I see your tag line is z-wave genius. Once I am done with these two zigbee devices, I am turning my attention to a couple of z-wave devices. Is there a good starting point example you know of for a dimmer switch?

Thanks!

4

Good starting point is the Fibaro app that is still online on Athom’s github, it is far behind on what is currently in the appstore, but the drivers haven’t changed for these example devices that i’m showing here.
Drivers like the FGD-211 (old, pretty basic with not a lot of extra fluff) and FGD-212 (also old, but with a lot of device specific additions)
I think for basic functionality the FGD-211 is the best option.

For Z-wave dimmers make sure you disable the setOnDim functionality of the onOff capability, or you’ll end up with some weird behaviours as the onOff and dim capability make use of the exact same Z-Wave command(s).
(Example on the FGD-211, Link to the documentation)

If the device has Central Scene (IE: amount of clicks if there is a switch), there’s a good example on the FGS-213/FGS-214 driver for that.

1 Like