Error with new binding Luftdateninfo

milo · September 20, 2020, 8:35pm

Hello, I installed the new “luftdateninfo” binding but get always this error

2020-09-20 22:31:17.469 [hingStatusInfoChangedEvent] - 'luftdateninfo:particulate:pm_sensor_smarthome' changed from OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-20 22:26:17 to OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-20 22:31:17

2020-09-20 22:31:17.471 [hingStatusInfoChangedEvent] - 'luftdateninfo:conditions:conditions_sensor_smarthome' changed from OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-20 22:26:17 to OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-20 22:31:17

Anything what I can do for debugging?

Bruce_Osborne · September 20, 2020, 9:46pm

Did you try RTFM ?

https://www.openhab.org/addons/bindings/luftdateninfo/

milo · September 21, 2020, 5:06am

Yes…after 2 hours the thing was online…

Mikel_2 · September 27, 2020, 5:40pm

Got now the same error at several times:

the data from the sensors are online and can be seen, i checked it on the website … but …

no current data in oh

opus · September 27, 2020, 5:58pm

IMHO the scheduler shouldn’t be stopped by that error, I would expect to have log-entries after each polling time ( which is?) showing at least the same error again and again. However, if the log does give more info we could be wiser!

Mikel_2 · September 27, 2020, 7:07pm

Here are some log messages:

2020-09-27 21:02:38.404 [hingStatusInfoChangedEvent] - 'luftdateninfo:particulate:altdorf:pm_sensor' changed from OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-27 20:57:53 to OFFLINE (COMMUNICATION_ERROR): HttpConnectionOverHTTP@1ff9862::SocketChannelEndPoint@1412171{data.sensor.community/85.214.62.33:80<->/192.168.178.64:51706,ISHUT,fill=-,flush=-,to=17/0}{io=0/0,kio=0,kro=1}->HttpConnectionOverHTTP@1ff9862(l:/192.168.178.64:51706 <-> r:data.sensor.community/85.214.62.33:80,closed=false)=>HttpChannelOverHTTP@393267(exchange=HttpExchange@17a6bd6 req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@107f70(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@829aea{s=START}],recv=HttpReceiverOverHTTP@16727d7(rsp=IDLE,failure=null)[HttpParser{s=CLOSED,0 of -1}]] / 2020-09-27 21:02:38

2020-09-27 21:02:53.391 [hingStatusInfoChangedEvent] - 'luftdateninfo:particulate:schwarzenbruck:pm_sensor' changed from OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-27 20:57:53 to OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-27 21:02:53

2020-09-27 21:02:53.431 [hingStatusInfoChangedEvent] - 'luftdateninfo:particulate:oberferrieden:pm_sensor' changed from OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-27 20:57:53 to OFFLINE (COMMUNICATION_ERROR): Total timeout 15000 ms elapsed / 2020-09-27 21:02:53

may be it can help

opus · September 27, 2020, 7:45pm

No change it looks to me as if scheduled polling isn’t terminated ( no new values since 18:00 and the polling is still trying to get data at 21:00).
Why the requests are creating an error, I can’t say. Sorry.

uk59821 · September 28, 2020, 2:15pm

I have the same problem. Because I have my own sensor I check the answertime of different links for the same sensor.

http://feinstaubsensor-{nodemcu-id}.local => answer immediatly
http://api.luftdaten.info/v1/sensor/sensorid/ => answer >=3 minutes
https://api.opensensemap.org/boxes/:boxId?format=json => answer <2 seconds

Before the binding was available, I had therefore switched from the luftdateninfo-api to the opensenseorg-api for reading via Get-Request.
I’ll wait and see if the API continues to cause such problems and then I’ll think about what to do.

Mikel_2 · September 29, 2020, 8:01am

Last night after exactly 01:48:12 (UTC+02:00) (last data received) the transmission of data to OH stopped.
(Server problem? - new IP …???)

weymann · May 1, 2021, 7:14pm

During the development of this binding I also had many timeouts in http requests of the sensor data. I asked the developers in Stuttgart and they reallocated their servers during this time - it explains the long delays. After these actions it runs quite stable till now.

Nevertheless I see the need of quick local queries of your personal owned sensors. I added a config of the IP Address in this test bundle. So you’re able to configure your local sensors with an IP Address and it’s still possible to include external sensors out of your network with a sensor id.