I’m having this issue as well. I use the Luup code in scenes to adjust thermostats depending on alarm status, set times, etc. When the scene runs, nothing happens but when I copy/execute the Luup code in the “Test Luup Code” in Develop Apps, it works as expected. I’m pretty sure this issue started with 1.7.4000 but I’m not 100% sure.
Same issue with code that used to work in the past (and continues to work in the test space)
Further performed a simple test with “return false” - but actions continue to be executed
(issue occurs irrespective of wether code is enetered in the trigger or the scene logic)
Partial & full reboot did not make any difference.
I don’t know why this worked, but it did. I edited one of my scenes that has Luup code. I copied the Luup code to notepad, deleted the code from the scene, added an action to the scene (turn a light on) and saved it. Then, I edited that scene again, removed the action, pasted the Luup code back in, and saved the scene. When I ran that scene, it now worked. So, I ran my other scenes and they all work now too even though I did not change them at all.
My experience is that if a scene acquires an invalid character, it impacts a lot of other scenes, probably all the ones with later ID numbers. It’s like luup engine recompiles the scenes into a single executable or DLL and if a scene is corrupted, everything afterwards is corrupted.
No clue what causes the invalid characters. Could be firmware update, something in a web browser, solar flare, gypsy curse, anything.
Best Home Automation shopping experience. Shop at Ezlo!