Injecting "update" only works once or twice?

[Humancell]

I have a very simple Node-RED flow, and am using an Inject node to send the topic "update" into a temperature node.

When I deploy, the Temperature node outputs correct JSON with the last known temperature.

I have set the Inject node to send the topic "update" every 10 minutes, and so 10 minutes later I get the temperature and it appears to have been updated. But from then on, every 10 minutes I just keep getting the same temperature! If I redeploy this all starts over. I can get one temperature reading on deploy, and then one more when the Inject node fires, but then they are all the same.

Is the Inject node sending "update" triggering the Temperature node to read (e.g. call the SmartThings API to fetch) the temperature?

Why would it stop updating correctly?

I was assuming that each Inject of the topic "update" would cause the node to fetch the latest temperature reading?

[otaviojr]

Hi, @Humancell ,

did you manage to make the SmartApp work? Usually, it will update the temperature value as it changes and outputs the new value without the "update" message. This is the best way, you need no timer and get the value as it changes.

If your SmartApp is not working, you can use the "pull" message instead of the "update" one to force it to request the new value before outputting the status.

Regards

[Humancell]

Hello,

Yes, I do understand the "better" way to do this, and want to do that. I do not have the Proxy/Verification worked out yet. SmartThings has been useless trying to get support for how to work around this issue - even with numerous people asking for years. :-(

I'm going to allocate time this weekend to hopefully resolve this and get it working so that I can use the asynchronous events. I was just trying to get some things working in the mean time. The "pull" is exactly what I was looking for and will work in the short term. Thank you!

I can't wait to get this HTTPS/Proxy issue resolved this weekend to be able to use the full functionality that you put in place. And thank you again for having this "pull" workaround in the mean time. :-)

Scott