It works fine when using google chrome and just posting the event directly to the device.
But when I try to activate (push) that switch via OH, it does not work at all.
I have tried it via the REST API and also via normal switch which I have created in the sitemap:
I get this in /var/log/openhab2/events.log when activating the switch:
2020-01-02 09:09:50.701 [ome.event.ItemCommandEvent] - Item ‘Leselampe’ received command ON
I am not able to determine the root cause.
I have had it already working until I have upgraded from openHAB 2.5.0~S1660-1 to my current release.
From time to time I keep getting this error in the log, but I am not able to link this one to my actual problem (/var/log/openhab2/openhab.log):
2020-01-02 08:59:22.490 [ERROR] [org.openhab.io.net.http.HttpUtil ] - Fatal transport error: java.net.ConnectException: Connection timed out (Connection timed out)
Perhaps somebody of you is able to help and to give me some advice how to analyse further.
I have created an own log for the http binding and found only the following entries:
[08:32:10] openhabian@openHABianPi:/var/log/openhab2$ cat http.log | grep Exec
08-Jan-2020 08:21:18.582 [DEBUG] [org.openhab.binding.http.internal.HttpBinding ] - Executing url ‘http://192.168.229.37/control?cmd=event,s20_2_off’ via method POST
08-Jan-2020 08:30:11.521 [DEBUG] [org.openhab.binding.http.internal.HttpBinding ] - Executing url ‘http://192.168.229.37/control?cmd=event,s20_2_on’ via method POST
No additional suspicious entries around.
Would anybody have some ideas how to further analyse this problem?
Is there a way to log the result of the executiion of the POST command?