sensor.front_door_motion_sensor_alarm_level is the name of the sensor. That sensor does go from 0 to 255 immediately when motion is detected, but the template never changes to on.
NOTE: I’ve found that the reported battery is not very accurate or reliable - lol. You’ll notice the battery shows 0% but it’s still working… been this way for a few months.
Got it You’re right I was looking at alarm level. I only see 255 and 0 for alarm level, but burgler has 254, 8, and 0, and probably 3 like you said if I get a tamper alert. Good deal, thanks
One super minor typo (probably), I was doing a find/replace and this one got missed. Noticed an extra underscore. I mean I dont even know what that sensor does anyway, so its not a big deal.haha Just letting you know. Thanks for this, its awesome
I could not get the customize to work in the package. Not sure if it was because I already had a customize.yaml file? I moved the items from the customize part of the package into my customize.yaml, and it worked fine.
Thanks again
Edit: A few more minor typos. There was a space for motion and tamper in the is_state. and a few of the customize items had an extra space., but It’s all working great now (except for having to seperate out the customize. which is not a big deal at all.
How are you able to use numbers for the states? My states are represented as strings: ‘Not Active’ and ’ Burglar - Unknown’. I am using the Dev branch of open-zwave. Maybe that’s why.
I think it depends on the sensor. I would look at your entity list and see what the states and attributes look like there. If you don’t like the default, you can use templates to have it display however you’d like (numbers or different text). The device class can also affect how sensor states are displayed as well (open/close, safe/unsafe, etc.). In kylerrw’s code, he creates two new binary sensors (based on non-binary states from the motion and tamper sensors). The ‘8’ and ‘3’ he is using could easily be replaced with ‘Burglar’ if that is what your sensor state is. The device class motion will display clear/detected and the safety will display safe/unsafe. I hope that makes some sense! I’m sure Kylerrw could explain better as I just pirated his code!
any ideas on how to change teh zwave config parameters? when i try to turn off the led (parameter 7) the change doesnt stick. I try waking up the device with the button before issuing the command, but when i read it back it still doesnt change
I’ve got two Zooz 4-in-1s hooked up to HA without much fuss, but am having some inconsistent issues related to the attributes found within the node and simplifying the display. This post seems to be the best resource for this particular sensor.
First off, the battery_level attribute is nowhere to be found on either of my sensors. Also, when I added the sensors (which are identical) they didn’t add with the same attributes. The living room has sensor.living_room_multisensor_emergency and sensor.living_room_multisensor_homehealth and the basement sensor doesn’t have those values. The basement sensor also has sensor.basement_multisensor_appliance which the living room doesn’t have. What’s going on here? Both nodes report “query_stage: Complete” and seemingly are reporting good data.
I really like what @kylerw has done with his script and would love to recreate it. Problem is I’m brandy new to this and I’m clueless by a lot so far. I haven’t really wrapped my head around templates yet, nevermind packages. I tried to recreate his code to match my environment, but I honestly have no idea where I should be putting that. Not to mention, I don’t even have the battery level attributes showing anywhere.
Any help with those two points would be really appreciated!
Hey @borsaid, check out the packages documentation where you can see where/how to configure. I’m using the include option in my configuration.yaml so I can have each package in it’s own file.
I’m guessing you mean Sensors, try leaving the cover off for a while longer and all sensors should populate, as this will force the sensor to stay awake and report more often, The sensor’s wake-up interval is set to 12 hours by default to save battery life.
You have to wake it up a couple of times so it can read the complete configuration. If you only add it and then restart HA it may not have finished reporting it’s sensors.
CP from manual:
MANUAL WAKE-UP
Press and release the Z-Wave button once to wake the device up.
The LED indicator will flash once (blue or orange).
You may need to wake the sensor up manually IF:
1. It doesn’t fully configure during set-up (values are not displayed or errors pop up in your hub’s interface).
2. You change advanced settings for the sensor and want them to update.