For me, for example, it is critical if the “nightly zwave heal” does not work. Or if my Philips Hue dimmer and Tap switches events will not work.
They are still NOT SOLVED since 2.5.0.M1 or 2.5.0.M2.
See here:
Z-Wave heal:
Philips Hue (Dimmer and Tap Switches):
Do you seriously want to tell people that a stable release somehow works, but you better should disable the nightly zwave heal. And all your Hue Dimmer Switches and expensive Tap Switches will not work? Well then…
In the documentation, it is promoted or proclaimed that this works, actually since 18th January 2019 (Hue) and since mid-May 2019 (Zwave heal) they do no longer work. Then please change the documentation. Thank you very much.
My primary device to control everything in the house are the cheap philips hue dimmer switches. If they are not going to work i won’t be able to migrate to 2.5. However as i am not capable of contributing code to the project. I tried to make clear that i got the same issue on this forum as well as on github.
I can understand the decision of cweitkamp who did the last change in the hue binding and doesn’t use the dimmer switches anymore, as it is his free time that he is contributing to this project.
However my conclusion for this is to move to another meta smart home controller like hass.io or nodered which still supports my hardware as i won’t have any other choice than that.
If there is anything else except for contributing code what i can do i am absolutely willing to pay 50€ to get the support of the dimmer switches back, however i don’t think that this won’t be a acceptable price as the development will take more than half an hour for the contributor.
I can understand the decision of cweitkamp who did the last change in the hue binding and doesn’t use the dimmer switches anymore
You mean @cweitkamp broke the code and decided to not fix it, because the feature isn’t relevant for him? From all I know about his work over the past years, I cannot believe this…
Which is unrelated to the hue binding itself and which does not seem to be reproducible…
But there’s no issue entered over all these months about the hue binding?
Hi JNK
Have not applied the fix as could not find clear info on how to apply it. Happy to apply and test if you can point me in the right direction. Confirm stable on M6 (I’ll update the post above)
@David_deMarco linked an issue that was already merged. I’ll wait when next snapshot be out and will retest. For me only part of subscriptions were not working for some reason. No idea why.
This issue has been resolved by upgrading to the latest stable version.
Thanks @rkrisi I missed that bit (jetlag and system upgrade not good idea). Full steps in one place to help others given MQTT is used so much now. (updated with improved karaf command)
Confirmed that MQTT states are now working again - Can’t comment on retained messages. Note I also had some suspect issues with openhab-cli not stopping Openhab so playing it safe here.
There is an issue with usb-serial devices on RC1 as reported by @Andrew_Rowe, @davorf and I experienced it on Windows 10 and Raspberry PI (using openhabian 1.5): the serial items (zwave controller and RFXcom for me) keeps reinitializing on openhab level, it is fine on the command line (using lsusb, dmesg etc…). It was causing very high memory and cpu usage and even using swap, the pi was unusable after a few hours.
Switching to latest snapshot, for me it is 1774, fixes the issue