-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[homematic] homematic RF devices not found after openhab 3.1.0 upgrade #10961
Comments
Thanks for providing the log. I am now a bit confused because the log output does not match the implementation. There should be a debug message right before the exception message. |
I took a new log from openhab startup. This was taken after the Upgrade from 3.0.2 to 3.1.0 with "org.openhab.binding.homematic:3.2.0.202107011418". This time it is not only the openhab.log but a the combined output of "openhab-cli showlogs" command. I added openhab-3.1-debug-homematic.log I noticed a weird thing. Previously I said all of my Homematic RF devices are failing with Device with address Here is an example of a device of the same type "homematic:HG-HM-TC-IT-WM-W-EU" which I have three times. One is working, the others are not.
I still do not see a Debug message around the NPE. |
@brainbug95 Thank you for the detailed log output. I think, I have found the reason for the exception. It is probably caused by the "OpenWeatherMap" device. For this device an internal variable is not set and this causes the exception because of some necessary refactorings for version 3.1 of the binding. I have uploaded a new test version here: https://github.com/MHerbst/openhab-addons-test |
@MHerbst thanks for this fix. I installed OH3.1 and used your patched Homematic binding and it works so far. I will leave it running for now and see if more issues pop up in the future. I consider the issue closed if that's fine with you? |
@brainbug95 Thanks for you feedback. The issue will be automatically closed when the fixed code is merged into the OH codebase. |
* Fixed a rare NPE introduced while replacing commons-lang * Provide additional null pointer checks It is possible that the meta data returned for some device does not contain a default or maximum value. Fixes openhab#10945 Fixes openhab#10961 Signed-off-by: Martin Herbst <develop@mherbst.de> Signed-off-by: dw-8 <davy.wong.on+github@gmail.com>
* Fixed a rare NPE introduced while replacing commons-lang * Provide additional null pointer checks It is possible that the meta data returned for some device does not contain a default or maximum value. Fixes openhab#10945 Fixes openhab#10961 Signed-off-by: Martin Herbst <develop@mherbst.de> Signed-off-by: dw-8 <davy.wong.on+github@gmail.com>
* Fixed a rare NPE introduced while replacing commons-lang * Provide additional null pointer checks It is possible that the meta data returned for some device does not contain a default or maximum value. Fixes openhab#10945 Fixes openhab#10961 Signed-off-by: Martin Herbst <develop@mherbst.de>
* Fixed a rare NPE introduced while replacing commons-lang * Provide additional null pointer checks It is possible that the meta data returned for some device does not contain a default or maximum value. Fixes openhab#10945 Fixes openhab#10961 Signed-off-by: Martin Herbst <develop@mherbst.de>
* Fixed a rare NPE introduced while replacing commons-lang * Provide additional null pointer checks It is possible that the meta data returned for some device does not contain a default or maximum value. Fixes openhab#10945 Fixes openhab#10961 Signed-off-by: Martin Herbst <develop@mherbst.de>
Expected Behavior
After the upgrade all previously configured and working homematic RF devices should be operational.
Current Behavior
All homematic RF devices are showing "COMM:ERROR" on the main UI. Homematic RF devices are bound to a Homegear bridge as opposed to HMIP-Devices which are connected to the CCU2 bridge and work fine.
I attached openhab.log with the openhab binding set to DEBUG. I cleared out some irrelevant stuff. The log also shows a nullpointer exception which might be relevant.
openhab-3.1-clean-cache-debug-homematic.log
Steps to Reproduce (for Bugs)
Your Environment
The text was updated successfully, but these errors were encountered: