-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Motion accessory does not work on Trigger Control Application #120
Comments
Hi BradJJ2000, The motion detector works by a simple binary ON/OFF scenario that takes the standard lighting application response from C-Bus of 0/255 for OFF/On and converts it to 0/1. It is not compatible with the trigger control application messages even if you change the application address as the message format is different in C-Bus. I can only recommend that you create some logic or if possible set up your PIR to also send a trigger control message for your C-Bus and a lighting message for your Homebridge. Not sure if you can set this up in the PIR to send a message on both the primary and secondary applications at the same time. I have not done this, Otherwise, some logic in your PAC for some one-to-one mapping of a lighting GA to follow a Trigger GA will do the trick. Then define the PIR in homebridge back onto your lighting application and you will be good to go. It's a bit of a fiddle and a duplicate of GA's in two applications, but will achieve what you want. Cheers Jason |
Thanks Jason. |
No problem. Remember, writing the logic in the PAC will also give you what you want. Just chose which application you want the PIR’s to be on and write the one-to-one mapping as above for the secondary application to follow the first. There will only be a small delay. |
I’ve used my PIR’s on the trigger control application forever as I have some PAC logic to control things.
Maybe I’m breaking some CBUS rule or something.
Anyway, I setup a motion accessory in the plug-in Config with the correct ID and application 202 and the motion would not trigger in the Home app. I could see it triggering correctly on other CBUS gear.
I switched my PIR over to the lighting application (and reconfigured the plug-in) and it leapt into life.
Switched it back to 202 and it doesn’t work. Checked everything 4 times.
I’ll move my PIR’s over to lighting. Thought I’d report this as I’m guessing it’s supposed to work.
The text was updated successfully, but these errors were encountered: