gizmocuz wrote: ↑Tuesday 06 December 2022 17:57
As far as I know (except some exotic devices) there are no issues
Hello,
IMO, issue is really having to re-do most of the devices integration work. For sure, inclusion etc should be kept by controller. But having to replace all sensors/switches by new ones when they'll show up when you have ten's of nodes & hundreds of devices will not be a 1 hour job. IMO, not even a single day one.
And that's on top of a heavy layer cake software (& at the foundation, some HW driven in JS that was clearly not designed for this) compared to a clean integration. The kind of SW pile "accidentally working" with too many dependencies you're advised to containerize because that's almost impossible to reach OS/Interpreter/"driver" SW/mqtt/controller SW planet alignment of dependencies over time.
So maybe there is no issue, provided you have the right cookbook & been able to refine it on some test system, but IMO lots of traps & several days of work when you're currently full z-wave and need your working system!
Yesterday, I had to exclude/reinclude a Fibaro "eye" PIR that did not show it's temp sensor since a week and misbehaved showing wrong CO2 etc sensors. Happens sometimes, but his time a wake-up did not lead to a working again state. For this single device, having to replace devices (using an intermediate name, to be able to replace, then rename to former device name to keep all scripts that may use it working) by new ones, with only 3 used (movement detection/tamer/temperature), this was ~30 mn with a bit of testing.
I currently have 9 pages with ~25 devices under zwave category. So that's ~225 devices & even really used ones are between half and 2/3 this figure, that's a huge job & quite repetitive so error prone: For sure, issues will occurs after a very boring job. We're humans after all!