smarthomej / addons

SmartHome/J addons for openHAB
Eclipse Public License 2.0
59 stars 23 forks source link

Influxdb? #476

Closed timo12357 closed 1 year ago

timo12357 commented 1 year ago

Hello, are you the author of https://docs.smarthomej.org/3.1.4/org.smarthomej.persistence.influxdb.html too?

J-N-K commented 1 year ago

This is also part of this project, yes. Although it's a quite outdated version for openHAB 3.0.

timo12357 commented 1 year ago

I ask, because I have trouble getting OH graphs to show all influxdb data. With this older version the graphs work, but then again my automation that is based upon influxdb does not. I also the following errors in my log with the new one, whereas the older version runs clean.

2023-04-15 15:02:03.307 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'nibe_control' in registry 2023-04-15 15:02:03.307 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry 2023-04-15 15:02:03.308 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'nibe_control' in registry 2023-04-15 15:02:03.308 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry 2023-04-15 15:02:03.310 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'nibe_control' in registry 2023-04-15 15:02:03.311 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry 2023-04-15 15:02:03.312 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'nibe_control' in registry 2023-04-15 15:02:03.313 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry 2023-04-15 15:02:03.315 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry 2023-04-15 15:02:03.317 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.