If your webthing library/server supports WebSockets, the devices are not polled, as propertyStatus messages should be sent through the WebSocket.
If WebSockets are not supported, properties are polled every 5 seconds by default. However, that can be configured in Settings -> Add-ons by clicking Configure on the “Web Thing” add-on entry.
I do not use Websockets. And that one Thing property is not updated seem like a bug in the Gateway to me. I could provide some info if needed - the Thing is still stuck in the Gateway.
Hmm, strange. It appears to be polling 4 other properties, but not KOT1. Can you attach your gateway log from when this started happening? You can access it in the UI via Settings -> Developer -> View Internal Logs.
It seems that it started when the RaspberryPi (rpi.lan aka 19.168.1.120) was restarted by the watchdog because it got stuck (I do not know yet why this happens but configured the watchdog to restart it automatically) around 2020-03-24 23:15.
But there is one entry on 2020-03-25 22:13 but I have not idea if the value was correct at that time.
It seems to me the RaspberryPi works ok - I have my own interface also running there and it works ok. I think the issue is in the Gateway that something gets in the wrong state when it cannot connect to the rest api and does not recover after its available.
2020-03-24 23:15:48.937 INFO : thing-url-adapter: getValue for property KOT1 for: Kotel returning 62
2020-03-24 23:17:19.265 INFO : thing-url-adapter: Failed to poll device: FetchError: request to http://rpi.lan/iot/rad_prop.php?id=CHO2 failed, reason: connect ETIMEDOUT 192.168.1.120:80
2020-03-24 23:17:42.817 INFO : thing-url-adapter: Failed to poll device: FetchError: request to http://rpi.lan/iot/rad_prop.php?id=TARGET failed, reason: connect EHOSTUNREACH 192.168.1.120:80
2020-03-24 23:17:47.826 INFO : thing-url-adapter: Failed to poll device: FetchError: request to http://rpi.lan/iot/rad_prop.php?id=TARGET failed, reason: connect ECONNREFUSED 192.168.1.120:80
2020-03-24 23:18:10.291 INFO : thing-url-adapter: getValue for property CHO2 for: Radiátory returning 21.6
Currently I am using latest 0.11.0 from debian package. But when I reported this it seems I was using 0.10.0.
Isn’t there some tool for javascript to dump current state of the process like jstack for Java or procdump to analyze the state of the threads - what function are there waiting or something?