Whats the best way of making a Motion Sensor QuickApp

[RohitNz 7]

I have a number of security PIRS that are connected to fibaro switches.  With HC2, there was always a danger of users turning them off, because they are switches, thus masking the status from the input.

 

So, I am going to make them into QuickApps as motion sensors.

 

I can't decide if I should just update the status in a loop or make it event-based on the switch status

 

• If it's in a loop, it can't be slower than every five seconds, otherwise it will be useless.  Will this be too much activity (I have nearly 200 devices and 5 of these to do)
• If it's event-based, 
  • I still have to find out how to integrate an event from a device.
  • Will the QA get overwhelmed if someone is dancing in front of the PIR sensor?

 

Has anyone done this sort of thing yet?

[jgab 1,983]

5 pirs? you can do a 1sec loop.

[jgab 1,983]

or you could install the TriggerQA

 

Then it's easy to get sourceTriggers in your own QA - almost like a Scene...

Please login or register to see this code.

 

Edited April 22, 2023 by jgab

[RohitNz 7]

On 4/22/2023 at 5:08 PM, jgab said:

5 pirs? you can do a 1sec loop.

I am trying to make things more efficient this time with HC3.  On the HC2, on the advice of the installer, I had to suspend a lot of my stuff as the HC was too slow.  Including Heatpump controllers that I had purchased. In fact, they were the worst offenders.  It was so bad, that I had to disable all scenes before a backup or it would never start up after. I had a scene to disable/enable all other scenes.