-
-
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
[dbquery] Thing status unknown since openhab 4.2 #17064
Comments
What was the last known version for you that seemed to work? From 4.1.0 to 4.2.0 there is only one PR: #16458. That PR bumped two dependency's: Can you provide a debug log when you enable enagble the bridge and or thing? Can you share some configuration? |
Hi, i have also the same Problem. Here is my Bridge Code
When i enable the bridge, i see this log.
The influxdb2 is working well. All values are saved as expected. if you need more let me know. |
Gentle ping @Skinah do you have any clue why this is not working? We might have to revert changes for dbquery. |
Last known version for me was 4.1.3. This my debug log when enabling dbquery Thing.
My dbquery bridge thing config:
|
Did some more testing. Fresh install of openhab 4.2.0 with only dbquery as add-on installed.
Downgraded openhab to version 4.1.3
So it definitely works with openhab version 4.1.3, but not with 4.2.0. And it is just a felling from my side, but I don't know if it is really caused by dbquery directly or maybe there was a change at a different code and dbquery is no longer compatible to it. E.g. the log output seems to have a different structure --> I searched for thing changes in release notes and found openhab/openhab-core#3957 |
@lsiepel I have no idea why. I would recommend people install the InfluxDB binding even if they do not want/need it as it may install some missing dependencies when you install that binding. I had a huge pain getting that influxdb binding to work as it also uses the okio library. influxdb binding was building fine and then having issues during runtime, so it may be the same cause. If installing influxDB solves the issue for dbquery, then the fix should be easier to track down, so if a user can try and report back that would be great. If there is an issue, then I would try dropping only okio back to 3.6 or 3.8 for just the one dbquery binding and leaving everything else as merged. In the meantime I am currently installing a test server onto a pi3 to run a test to see if I can reproduce it here. |
Hi @Skinah, thanks a lot for debugging. I have installed InfluxDB Persistence add-on and that is working fine, but still the same issue with dbquery. (for openhab version 4.2.0) |
Can someone try this new jar please? Uninstall the merged copy first, then UNZIP this into your addons folder. A number of dependencies have changed in this build but its basically a copy of what fixed the influxdb bundle. http://pcmus.com/openhab/org.openhab.binding.dbquery-4.3.0-SNAPSHOT.zip |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/openhab-4-2-release-discussion/157076/110 |
Great thank you very much, you´re fix works. |
Works for me :-) |
Thanks for the testing and reporting back as openhabian only installs influx V1.8 and the binding needs v2 minimum, if what I read is correct. I could reproduce the issue, but can not test further without wasting a lot of time learning about influxDB2 and setting it up. Glad that it is fixed. |
Thanks a lot @Skinah! Also works for me. |
Hi all,
it's about add-on dbquery.
The status for the Bridge-Thing stays at "unknown" and queries are not working anymore.
The dbquery thing query says, that the belonging bridge is offline.
Problem exists since update to openhab version 4.2.0.
openhab version: 4.2.0
dbquery addon version: 4.2.0
I tried to reinstall add-on, delete and add again the Bridge Thing and deleted openhab cache with openhab-cli clean-cache.
On influxdb site nothing was changed (like updates, config, user, password, tokens, etc)
Kind Regards
Robert
Here some lines from openhab.log:
The text was updated successfully, but these errors were encountered: