Forwarding does not work #143
Comments
|
Hi, |
|
Since I'm new to IOBroker, I'm not sure, if this log is the one you are looking for... But it looks for me, that the adapter is not trying to forward at all. At least I can't see any debug information regarding this. |
|
Ok, I see the forward URL is set. Let me check the codebase on when this is actually used. Can't find another output with that. What I do see though is your weather station seems to send the data every 1 second. This is a high frequency as ioB needs almost a full second to process. In case your ioB is really busy (high load) this could be a reason. Might be an idea to lower the frequency for updates a little bit in the weather station. |
|
The weatherstation is set to send data every 60 seconds. An this ist what I can see in IOBroker, too.
|
|
Which port is used for forwarding? 45000? 80? |
|
Forwarding uses standard http port (80). |
|
I just created a workaround: I set up my custom server within the weatherstation again (as it was before using sainlogic). Then I created a ssh tunnel from my custom server to the device my IObroker is running on (forwarding http traffic to port 45000 on the device). |
|
Hm.. ok. this seems a viable choice if you can run a custom server. Based on the code, the forwarding will happen anytime I get a request just after processing all the data internally. A log message will be generated IF the receiving servers is giving any kind of response to the request. OR if there is any exception thrown. As there is no log message in your case, it seems the receiving server just accepted it and didn't respond? Is that an option? I can add more debug statements to try, or you could - sounds like you are quite good on linux hosts :D - use tcpdump to monitor outgoing traffic from your iob host. |
|
AH.. if you need a specific port in the forward, you need to specify it as part of the URL. Like https://my.host:45000/upload. This should work for custom ports. |
I took a look into you code, too, and noticed the same: data should be forwarded every time. Maybe
The nginx server logs every access attempt, even it would result in an error (not found, not allowed, etc.). As there is no connection attempt logged, my guess is, that there is no traffic going out from IObroker/sainlogic.
I will check in the next days what traffic is generated using tcpdump. |
Nope, my server is using port 80 for incoming weather data. |
|
I am also trying to forward information, but don't succeed. Added: If I copy the used forward URL and add "?winddir=230&windspeedmph=12&windgustmph=12&tempf=70&rainin=0&baromin=29.1&dewptf=68.2&humidity=90" I get a successful upload answer. So the URL seems to be okay. |
|
Hi devs, no idea how to fix it? |
|
No, not dead... just slow as so many other things to do :) Looking into this, issue could be in the code, retry policy is wrongly used -> need update |
|
Added to release 0.10.1 |
|
Unfortunately same bahavior with 0.10.3 as described in #154 . Here some logs from my test:
|
|
there is actually a log message once the forwarding has happened. |
|
0.10.4 has updated logging, it should not the URL as well as the response received from the request. |
|
Can you confirm this still be an issue? If yes, check the logs. |
Hi,
I'm trying to forward my ecowitt data (ecowitt protocol) to my (custom) server. On this server I'm logging my data, too.
The setup looks like this:
/index.phpEcowitthttp://wetterupdate.flaemig42.de/index.phpI can read all weather data from the objects within IOBroker, so basically the adapter and instance is working.
But I can read from my access logs of my server, that the plugin does not forward any data, since there is no POST request on the index.php from the IP of my IObroker (home).
How can I do further debugging?
The text was updated successfully, but these errors were encountered: