-
15th February 2015, 10:45 AM
#1
Automated Home Sr Member
Disable Macro oddness
Hi all,
I'm having some difficulty with a "disable macro" connection. I have a connection from a "going bright" output of a light level sensor to disable a macro. This has been working fine, but now doesn't seem to do anything.
I've tried starting a dummy macro with the going bright output and that works fine and I've also tried disabling a macro from another macro and that's fine. I can of course introduce a dummy macro, but that seems to be a bit messy. I'm not sure but it might have been around the time of the last update, have I missed something?
Peter
-
15th February 2015, 03:42 PM
#2
Automated Home Ninja
The behaviour of the macro Disable and Enable inputs was changed in update 26.10.4.
As stated in the summary...
"Macro Object
Enable and Disable inputs now require
Sender to be 'True' to action.
"
What this means is when an object triggers its output and sends a message to the Macro the Sender needs to be 'True' on that connection.
However the Light Level on going bright simply triggers its output but does not assert a true state for having gone bright. This can be considered a bug and will be fixed in next update.
Their is a work around.
In the Light Level object create a User Defined Threshold with Name say 'My Bright threshold'. Set the threshold to a suitable level. In The State output connection for the threshold connect that to the Macro Enable input. This should do what is required.
Viv
-
15th February 2015, 07:26 PM
#3
Automated Home Sr Member
Thanks for the speedy reply Viv.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules