I’m currently using the zwave js ui integration but now that the official integration supports zwave LR I’m considering switching. Google search didn’t reveal any discussion about this subject though. Just a bunch of guides and videos for the reverse switch from the official integration to zwave js ui. I typically prefer an official integration if there is no lose of functionality. Not sure if that’s true in this case? Also not sure what the procedure would be to make the switch? I have less than a dozen zwave devices so now would probably be better than later to switch. Don’t really want to break all my automations though. Would appreciate any thoughts.
I don’t really see any point in switching. But you can just do the reverse of Switching Z-Wave JS Addons with Minimal Downtime! Z-Wave JS (Official) to Z-Wave JS UI (Community).
Probably not worth it to make the switch in this specific case. In the background either way you are using the same codes… the difference is one comes with an extra UI and the other one does not.
Doing the reverse of the post that @freshcoast linked would probably be all you need. That being said, I don’t see any reason why you would want to switch back. Z-Wave JS UI is almost always ahead of any features of the official integration and you get a good UI and better ability to get at diagnostics if you need.
I run several HA instances and they all have Z-Wave JS UI installed even though I have less than 5 devices connected up at the properties that they’re operating at. I’ve found it to be significantly easier to fix any problems using that vs the official integration which I tried for over year.
Thanks all for the replies. Looks like advice is the same from everyone (no need to switch). Typically I’d worry about project abandonment with HACS integrations and would switch to official integrations (if they were equal) but I don’t think there’s much worry regarding abandonment in this case.