Only now do I notice that none of my Z-Wave Fibaro flood sensors have their tamper binary sensors anymore. Apparently the integration no longer creates those, and the old ones can be deleted? When did this happen, if indeed it is the case, and I didnt run into an issue....
I did try to reinstall one, and tampered wi
th the cover (it squeeks heavily, indicating something is messing wpth the packing), but no alert in Z-wave integration anymore.
#Zwave Fibaro tamper cover binaries are gone?
gloomy portal
silent topaz
For questions like these, post the device diagnostic file (go to device page, ..., download diagnostic).
These also include the entity IDs, so you can clearly indicate which are the binary sensors, and which are the "old ones".
gloomy portal
yes, thx. Let me check that.
I believe I've found the change, they are renamed into these, and found in the Diagnostic section now. Should have noticed that before posting.
silent topaz
There was a change to omit creation of sensor, not binary_sensor. Nothing is renamed.
gloomy portal
probably misremember the exact change, and I cant reproduce them because I deleted the no longer available ones...
gloomy portal
There was a change to omit creation of `sensor`, not `binary_sensor`. Nothing i...
do you know which release that was, so I can re-read that please?
silent topaz
You seem to be saying the opposite though.
Not clear if deleting the "old ones" was the correct move, hence need to see diagnostic.
silent topaz
You're confusing me, are the binary_sensor gone, or sensor? The latter is expected.
You initially said binary...
I see there is currently binary_sensor.attic_flood_sensor_home_security_tampering_product_cover_removed
gloomy portal
sorry... I am confused too... I remembered the binaries to have different names and another place in the device overview. Hence my ask for binaries
I then found the tamper binaries in the diagnostics section and as you say they werent renamed
silent topaz
I would not expect the entity IDs to change. I don't think HA will ever do that.
gloomy portal
I see there is currently `binary_sensor.attic_flood_sensor_home_security_tamperi...
yes I have those for all 4 of my flood sensors.
silent topaz
So seems to be working fine then, besides confusion introduced by the change?
silent topaz
Usually the corresponding sensor was disabled by default. Having both was confusing.
gloomy portal
thanks for taking the time
silent topaz
Those ones also require having knowledge about Z-Wave specification details to use properly
gloomy portal
explaining
silent topaz
No problem. Not sure how HA can communicate breaking changes like this (someone could have been using old entities in an automation) since there's no such category in the release notes now.
gloomy portal
yeah, that can be difficult. but since there almost always is a dedicated section for Z-wave required latest version, maybe use that spot to indicate why, and reference the PR's?
silent topaz
Yeah, that's in the "Backwards compatible" section, which doesn't quite make sense.
gloomy portal
and probably in the All changes
which I always read completely before installing..... seems it didnt ring a bell this time
final question please: the tamper cover, is that for lifting the device, and for opening it? Or cant you tell that from the device diagnostics
silent topaz
Removing the cover.
Possible the device could implement it for the former, but it's meant for opening it.
I think Zooz is using it for vibration in one of their sensors.
gloomy portal
right, I ask because when I lift it, it starts beeping
silent topaz
Seems your device has a configuration option for that.
Actually that's for association groups. Looks like it considers both as tamper.
"commandClassName": "Configuration",
"property": 74,
"propertyName": "Alarm frame for movement/tamper",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": true,
"description": "Movement/tamper alarm sent to 1st & 4th assoc. group",
"label": "Alarm frame for movement/tamper",
"default": 2,
"min": 0,
"max": 3,
"states": {
"0": "Tamper alarm inactive",
"1": "Button tamper alarm active",
"2": "Movement tamper alarm active",
"3": "Button and movement tampers alarm active"
},
Yours is set to 3
Try changing it to 1.
gloomy portal
this one? this is the current setting
gloomy portal
wow thats all very crafty 😉
silent topaz
Fibaros, for all their downsides, have a lot of config options.
gloomy portal
Your diagnostic said it was set to the last one.
well, I didnt change it, so that needs some closer inspection... thanks! I now know where to check these things, appreciated!
silent topaz
Here's the entry from your diagnostic:
"23-112-0-74": {
"endpoint": 0,
"commandClass": 112,
"commandClassName": "Configuration",
"property": 74,
"propertyName": "Alarm frame for movement/tamper",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": true,
"description": "Movement/tamper alarm sent to 1st & 4th assoc. group",
"label": "Alarm frame for movement/tamper",
"default": 2,
"min": 0,
"max": 3,
"states": {
"0": "Tamper alarm inactive",
"1": "Button tamper alarm active",
"2": "Movement tamper alarm active",
"3": "Button and movement tampers alarm active"
},
"valueSize": 1,
"format": 0,
"allowManualEntry": false,
"isFromConfig": true
},
"value": 3
},
and these trigger the binary in HA? or just the beep on the device