Poll vs. schedule: issue with HubAction

[SDmitry]

We developed Service Manager and Device Type for LAN device.
After all it works well: we can control device via REST calls by HubAction API
But there is a problem with periodic status update.
“Polling” capability gives the call of poll() once per 5 minutes - too rare!
So we used schedule(“0 * * * * ?”, my_func) which calls my_func once per minute perfectly.
But the problem is that HubAction does not work in my_func - the command is not issued!
Meanwhile the same code operates well in poll().
It looks like scheduled function is executed in different context or something…
Is there any way to overcome?

[geko]

Yes, just call your device poll() function from my_func. That’s how Pollster does it.

[OBSOLETE] "Pollster" - A SmartThings Polling Daemon

Please note that excessive polling of some devices (particularly Zigbee and Z-Wave) may cause network congestion and lead to degraded system performance. Therefore, polling rate faster than 5 minutes is not recommended. The author of this software bears no responsibility for your system performance. Use it at your own risk. I don’t claim originality of the idea, but I needed one badly for some of my projects and didn’t find anything among the shared apps. So there it is… Many SmartThings devices rely on polling to periodically update their status. These devices have ‘polling’ capability and provide poll() function that the SmartThings polling engine calls approximately once every 10 minutes. Unfortunately, SmartThings polling engine proved to be unreliable and sometimes it stops working…

[SDmitry]

Thank you, geko. Indeed this method works.
Meanwhile, we switched to “subscription” approach to reduce traffic.
Thanks again!