I just changed my parameter 5 from 1 (the default) to 2. In post 113, SteveMSJ said he changed parameter 5 to 2, and it resolved his problem. However, I did more search and found more detailed discussion about this in another thread: I think it's with the Aeotec sensors, since I don't have this delay problem with any of my other devices.Īny suggestions? Pretty disappointed with the Aeotecs so far.Īh, SteveMSJ mentioned parameter 5 earlier above, but I got the impression in later posts that parameter 5 should be 1 (send Basic Set CC, whatever that means). I'm not sure if the delay is with the Aeotec sensors or with Homeseer. Now, with the Aeotec Multisensor 6's, Homeseer doesn't update the device status until 10 or 15 seconds after the motion/green LED occurs. (Aside: Optex sensors are the best for outdoor use - I have Optex sensors outdoors hardwired to Mimolites indoors). I also have Optex motion detectors wired to Mimolites, and any motion shows up in Homeseer immediately. Hence, I got the 3 Aeotec sensors for these 3 rooms. I prefer HSM200s, but for three rooms, the outlets aren't in a good location for HSM200. Once they detect motion, their status in Homeseer updates almost instantaneously, and my events fire immediately. Why so slow? I have eleven Homeseer HSM200 sensors. Turning off lights in an unoccupied room), but useless for turning on lights. I would have turned on the lights manually myself). However, it takes another 10 to 15 seconds before the status on Homeseer updates to motion.Īt this speed, it makes the sensors useless for turning on lights (by then, I configured Homeseer events to respond to motion on and off.Īs soon as motion is detected, the green LED turns on. I changed wakeup and alert to 10 minutes. Parameter 5 is 1 (send Basic Set CC), the default value.
I configured them with a timeout of 60 seconds, and sensitivity of 5. According to the Node Information page, their route to my Z-NET is "Direct (100K)". I just got 3 Aeotec Multisensor 6 (Model ZW100-A). With parameter 4 set to 5, which is enabled and maximum sensitivity, mine actually shows 'disabled' in the dropdown box on the settings page. I don't think the HS settings page is aware of this as it was a change introduced in a firmware revision. I would check parameter 4 (1 byte) as you can set different values for different sensitivities. Incidentally I notice on your settings page you have motion set to 'enabled'. HS detects it as a routing mode when you include it on power and that doesn't change when you remove the power so it doesn't seem a good idea. This is contrary to other advise which says the opposite.
The manual recommends including and setting it up on USB power even if you are going to ultimately run it on batteries. The manual says if you hold the button for 3 seconds it will wake up for 10 minutes but I had trouble getting that to work successfully. It needs to be woken up before HS can open the settings section and it can be quite tricky to keep it awake to do this. I was certainly able to configure settings on the one I have running on batteries. Having one powered one with batteries.Your two screen shots seem to be identical, maybe I'm missing something. About Second Quote, My Sensor wouldn't open the Menu to control parameters until I set it in Power, It was the difference I notice as I set my second one.