![]() My plan is to replace the switch inside the house with a Z-Wave equivalent (probably Zooz). It is installed under an eave, so relatively protected from rain and snow. It doesn't really need to work at these temperatures, just not be damaged by them. I found this HomeSeer Z-Wave Floodlight Sensor and was wondering if anyone had any experience with it and can comment on if it will function during Minnesota winters where the temperature can occasionally get to -20F (-30C). My preference is for a line-voltage powered sensor that has the ability to directly control the attached lights. So I've been looking for a motion sensor and switch I can pair with HE to control these lights. And recently this sensor started flaking out, so now nothing really works. Then repeat as needed or until I get so frustrated I just turn them off and walk away. Then to get back into "motion" mode I have to turn them off for a while, then back on, then hope the motion sensor takes over. If I want to turn the lights on manually, I have to flip the switch on-off a couple times to get them to turn on. If the sensor detects motion, the lights turn on. If the switch is on, the motion sensor is active. If the switch is off, the lights are off. I’ll have to let you know how that goes.īTW… the Occupancy vs.So, I've got three lights on the front of my house that are controlled by a traditional motion sensor and a switch. Now, the last test is that I added back in the before sunrise/after sunset condition, so I can only test that after sundown tonight. I changed it back to turning on the light, and then that worked as well, almost like it had to be coaxed into using a trigger. I changed nothing other than the service it called, and it worked. I did actually change the outdoor automations to state, and played with that, both with the Motion detection state (on/off), and with Occupancy detection state (on/off), but it’s not working on the outdoor at all.īut get this… instead of having “…became occupied” try and turn on lights, I had it send my iphone a notification… THAT WORKED. This works for every single one of my other automations using Hue motion sensors, but not the outdoor ones (so far). Indeed, looking at one of my other automations that works perfectly with an indoor Hue motion sensor, you can see that I’m using it as device, not state, but literally that same mechanism of saying when the Occupancy is triggered (state=on), do “something”. What I found interesting and hopeful is that you are using the “state” trigger type, when I had been using device. Maybe that’s part of the difference? I’m running 2021.10.5 right thank you for the reply! I had so much hope that it was that simple, but to no avail. I checked sensors connected to Hue and those connected via ZHA, and they look like this: Maybe try the entity state version of the triggers and see if that helps for your situation? You can also use that type of trigger from the UI if you prefer that method:Īlso, while I was looking at the UI for creating automations, I noticed that none of my motion sensors have a “became occupied” trigger. I use that same trigger (or a close variant) all my motion sensors, and it works with Hue Indoor (ConBeeII/ZHA or Hue Bridge), Hue Outdoor(ConBeeII/ZHA or Hue Bridge), and UniFi Camera sensors. For example: trigger:Įntity_id: binary_sensor.driveway_motion_sensor_motion I’m not using the device-level triggers, but rather the entity state triggers. After the recent change to the core Hue integration that modifies the sensors from local poll to local push, I moved the outdoor sensor from my ConBeeII network to the Hue Bridge network. ![]() I still have my outdoor sensor in the driveway and it’s working great.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |