Occ. Sensor Enable/Disable Toggle

[beotownsend]

So I just did something pretty pimp in my showroom; we have an Occ. Sensor in there, and I just got it so that when you walk into one of our demo rooms, it automatically starts playing music.

What I'd like to be able to do is to be able to toggle the Sensor Enable/Disable like you can in the Time Clock modes. I'm 99.9% sure you can't assign it to a scene/single action toggle button, but is there a way to do it via 3rd Party integration? My system works based off integration IDs and buttons; it will either sense the button push or issue one.

Looking at the integration report, I can see that there are other phantom button IDs available, does anyone know if one of these is a toggle for what I'm trying to do?

[hanshi]

You could do it with a 3rd party system. The only way to have it work would be to use time clock events at this point. So you would have one event to enable and another to disable. Then you can use a 3rd party control to send a signal to turn the event on (#timeclock,(ID),5,(event number)) where the event number is sequential based on where it is listed in list of all events.

Since it is your showroom, set the events for the early morning so it does not accidentally affect the performance of the showroom.

[shoop22]

So, could I create 2 timeclock events that are 1 minute apart that disable and then enable an occupancy sensor at 3:00AM and 3:01AM (for instance). Then I can send the command: #timeclock,(ID),5,(event number) at anytime to force the enable or disable event?

[hanshi]

Yes, that is exactly how it would work.

[shoop22]

That is really awesome, thanks for that info. It adds some nice functionality!

[shoop22]

I found Project Time Clock in the integration report to get my timeclock ID .

Also, it appears that the event index is just where your timeclock event happens to fall in the total list of timeclock events. So, if you manually move or add an event at the top of the list all of the indexes will now be off by '1'. As a result, a best practice would be to only add new timeclock events at the bottom of the list, don't delete old timeclock events and don't reorder timeclock events either.