06.10.2023, 04:53
Hi Erwin, thanks for your post here! Most helpful.
There's so many times I've wanted to update a visualisation object from a script but not have it trigger the event script associated with that object. I only want the script executed if the user changes the object value via the visualisation. Many examples for this that I've written - set point for air conditioners, or a master slider for multiple lights, Hue scenes that change the individual light globe brightnesses, etc. I have been using flags that would be set and reset by interdependent scipts but it quickly becomes very unwieldy.
I see I can now check event["sender"] in my script and quit, for example, if the event was called by another script, and not by the user via the Visualisation.
I've been using the Schneider CBus Automation Controllers, and have tentatively found that sender seems to take these values:
us - if script is triggered by the user updating an object via the visualisation.
cl - if script is triggered by updating the object in another script.
cb - if script is triggered by the object being updated by a wall switch button (and maybe other hardware input devices?).
Do you have any listing and description of what values event["sender"] may return?
Also, this appears to be a somewhat undocumented feature, so is it likely to remain unchanged in future firmware updates?
Thanks for any help you can give.
Phil
There's so many times I've wanted to update a visualisation object from a script but not have it trigger the event script associated with that object. I only want the script executed if the user changes the object value via the visualisation. Many examples for this that I've written - set point for air conditioners, or a master slider for multiple lights, Hue scenes that change the individual light globe brightnesses, etc. I have been using flags that would be set and reset by interdependent scipts but it quickly becomes very unwieldy.
I see I can now check event["sender"] in my script and quit, for example, if the event was called by another script, and not by the user via the Visualisation.
I've been using the Schneider CBus Automation Controllers, and have tentatively found that sender seems to take these values:
us - if script is triggered by the user updating an object via the visualisation.
cl - if script is triggered by updating the object in another script.
cb - if script is triggered by the object being updated by a wall switch button (and maybe other hardware input devices?).
Do you have any listing and description of what values event["sender"] may return?
Also, this appears to be a somewhat undocumented feature, so is it likely to remain unchanged in future firmware updates?
Thanks for any help you can give.
Phil