Hi,

I have a LOGO! 8.3 connected to AWS IoT Core. The device correctly updates the reported state in the shadow when values are sent from AWS (via a Lambda function) to logo.

However, when I set a value in the desired field, the LOGO! only applies it if I first stop the device and then start it again (STOP → RUN).

I'm using an analog output mark (e.g. AM..4:41-1) that is not connected on the left side in the LOGO! program, so it should be writable via AWS according to this post :Forum Community - Siemens SiePortal 

******  1. While LOGO! is in RUN mode: ***********

{
 "state": {
   "reported": {
         "AM..4:41-1": "0000"
   }
 }
}

******** 2. While LOGO! is in STOP mode: *********

{
 "state": {
   "desired": {
     "AM..4:41-1": "0020"
   },
   "reported": {
          "AM..4:41-1": "0000"
   }
 }
}

******* 3. After switching back to RUN mode: *****

{
"state": {
"reported": {
"AM..4:41-1": "0020"
}
}
}

"

Questions:

•  Is this a known limitation in LOGO! firmware version 8.3?
•  Is there any way to make the LOGO! apply the desired state dynamically while in RUN mode?

I’ve searched extensively through documentation, forums, and example projects, but haven’t found any clear explanation or solution. Still, it’s hard to believe this functionality wouldn’t be supported — it seems like a basic expectation for any IoT-enabled device.

Any insights or suggestions would be greatly appreciated.

Thank you! Happy to hear your thoughts.

Please note: The issue has not been resolved with update V1.83.02.

Hi all,

Just a quick update — the issue seems to be resolved now, although I can't pinpoint exactly why.

After deleting the original data table and creating a very basic test program, I reloaded my original setup and rewrote the data table identically. Now it works perfectly in RUN mode without needing to toggle STOP → RUN anymore.

It’s possible I missed something in the AWS shadow updates, or maybe there was some kind of glitch or outdated state lingering somewhere. Honestly, it feels a bit like magic 🪄 — but at least it's working now.

Thanks to everyone who read or considered this. Leaving this here in case someone else runs into a similar situation.

Cheers,