I have finally tracked this annoying issue down. There were significant change on the OpenHab core side–to the code that creates the displayState which is used by default as the label for these controls. Something has changed in that code that now requires the specification of a pattern in the State Description Metadata for the related Items. To correct the issue:
Open the Item that represents the Light Mode channel linkage
The WiZ binding was just merged into openHAB main. It will be available in the 4.3.0 snapshot build tomorrow, and the 4.3.0 final build later this month. Note that there have been several changes to channels to meet openHAB standards, so if you’ve been using the community binding, you’ll need to re-create your things. Thanks to @frejos for maintaining it so long. Any problems in the future can be reported as issues on openHAB’s GitHub. We’ll still be able to release a community version of the binding to address issues rapidly if necessary, but in general this should ease installation of the binding, and maintenance in general, since it’s part of the core build now, and core maintainers generally do a good job of keeping core bindings up to date when a core change is made.
Great news.. Thank you @frejos .Wiz owes you some royalties.. i have over 45 Wiz bulbs on my Openhab because of your contributions.. Now i have to re add them all over again but it will be worth it.
Thanks @ccutrer for all the work getting the submission approved and included in the main releases. For those that didn’t follow along, @ccutrer had to make some significant changes to clean up and conform to OH UX standards. He also made several iterations in time to make the 4.3 release cut off.
Many thanks!
I am behind on upgrading and trying out the new version, but hopefully the re-adding and migration process isn’t too painful? Does anyone have any suggestions for making the process as smooth as possible? Any lessons learned? I too have a large 40+ Wiz device implementation.
Now that the binding is part of the official distribution in OH 4.3, should the marketplace version be unpublished or made available only untill OH version 4.2.x?
Congrats for merging this into main! This is great news!
Just one question: I’m running OH 4.3.3 now and want to re-add my Wiz bulbs with the new binding - which works.
The only thing that doesn’t work is getting rid of the old Things - I try to delete them, but they just won’t go away.
(More specifically: the old Things are stuck at “uninitialized” with a “HANDLER_MISSING_ERROR” (“handler factory not found”), which is obviously because the old Wizlighting binding isn’t there anymore. When I try to delete them, they are stuck at “Removing”, but don’t get any further. After a restart of OH, they’re still there with the same error as above.)
It should be possibly to delete them forcibly by attempting to delete them again while they are in the “REMOVING” state.
I believe this somewhat counterintuitive approach exists because handlers can perform cleanup tasks when a Thing is removed. For example, they might delete OAuth tokens from persistent storage. However, if no Thing handler is available, this cleanup can’t be completed, causing the process to get “stuck.” If the handler becomes available again, it may still be able to perform the necessary removal operations. Otherwise, a second deletion attempt will bypass the cleanup step and forcefully remove the Thing.
Alright, I didn’t try that one before, but it worked to force-delete the Things while being in “REMOVING”. I already thought that the binding would be asked for cleanup and fail, but I had no idea how to get past that.
Thanks!
Most of the Wiz light devices work well with the binding, however I haven’t tested the light strips personally. Maybe someone else has, but I think your best bet would be to test with the actual device.
Also this binding has been included in the main OpenHab distribution as of version 4.3, so this version of the binding is now outdated.
Confirming this Wiz LED strips works with the official OH binding 5.x out of the box.
We get color, colortemp (both percentage and Kelvin), light mode and light mode speed.
