so today i bought the sonof v3 and a parasoll contact sensor.
i use the zha intergration and it seems to connect fine but the only sensor entity is IAS zone. also it doesnt show battery life.
does anyone know how to fix this?
so today i bought the sonof v3 and a parasoll contact sensor.
i use the zha intergration and it seems to connect fine but the only sensor entity is IAS zone. also it doesnt show battery life.
does anyone know how to fix this?
Battery can take up to 24 hours before it shows.
Hi!
I’ve installed 13 Parasoll and all of them but one worked perfectly. The last one also shows up as an IAS zone entity but nothing else. Did you solve this problem?
Did you manage to make the device work properly? I tried repairing it multiple time and always get the same result. Removing and re-adding the device didn’t help. Still IAS zone and Firmware Unknown
Hi there, I have the same issue. Installed one Parasoll sensor, it connects just fine but the only entity I see is the IAS zone. I can see the LEDs light up when the window opens and closes, and the device checks in every hour, yet there are no ZHA events sent AFAICT when the window opens. I the text below in the diagnostics when I look at the IAS zone cluster. TBH I have no idea what this means but it seems the connectivity of the device is not the problem, but somehow we’re not getting the right information from it. Could it be it’s simply not properly supported in ZHA? (checks Blakadder database. It’s not even in there at all )
"0x0500": {
"endpoint_attribute": "ias_zone",
"attributes": {
"0x0010": {
"attribute": "ZCLAttributeDef(id=0x0010, name='cie_addr', type=<class 'zigpy.types.named.EUI64'>, zcl_type=<DataTypeId.EUI64: 240>, access=<ZCLAttributeAccess.Read|Write: 3>, mandatory=True, is_manufacturer_specific=False)",
"value": [
114,
51,
170,
254,
255,
35,
164,
96
]
},
"0x0013": {
"attribute": "ZCLAttributeDef(id=0x0013, name='current_zone_sensitivity_level', type=<class 'zigpy.types.basic.uint8_t'>, zcl_type=<DataTypeId.uint8: 32>, access=<ZCLAttributeAccess.Read|Write: 3>, mandatory=False, is_manufacturer_specific=False)",
"value": null
},
"0x0012": {
"attribute": "ZCLAttributeDef(id=0x0012, name='num_zone_sensitivity_levels_supported', type=<class 'zigpy.types.basic.uint8_t'>, zcl_type=<DataTypeId.uint8: 32>, access=<ZCLAttributeAccess.Read: 1>, mandatory=False, is_manufacturer_specific=False)",
"value": null
},
"0x0011": {
"attribute": "ZCLAttributeDef(id=0x0011, name='zone_id', type=<class 'zigpy.types.basic.uint8_t'>, zcl_type=<DataTypeId.uint8: 32>, access=<ZCLAttributeAccess.Read: 1>, mandatory=True, is_manufacturer_specific=False)",
"value": null
},
"0x0000": {
"attribute": "ZCLAttributeDef(id=0x0000, name='zone_state', type=<enum 'ZoneState'>, zcl_type=<DataTypeId.enum8: 48>, access=<ZCLAttributeAccess.Read: 1>, mandatory=True, is_manufacturer_specific=False)",
"value": 1
},
"0x0002": {
"attribute": "ZCLAttributeDef(id=0x0002, name='zone_status', type=<flag 'ZoneStatus'>, zcl_type=<DataTypeId.map16: 25>, access=<ZCLAttributeAccess.Read: 1>, mandatory=True, is_manufacturer_specific=False)",
"value": 48
},
"0x0001": {
"attribute": "ZCLAttributeDef(id=0x0001, name='zone_type', type=<enum 'ZoneType'>, zcl_type=<DataTypeId.uint16: 33>, access=<ZCLAttributeAccess.Read: 1>, mandatory=True, is_manufacturer_specific=False)",
"value": 541
}
},
"unsupported_attributes": []
},
Thanks, but I really don’t plan to use Z2M, I have a 64 device network and all in all I am pretty happy with ZHA. @Vanguar in this thread seems to have made 12 out of his 13 work (edit: I assumed that was in ZHA but there’s no info about that in the post), and over on Reddit https://www.reddit.com/r/tradfri/comments/18l79xb/parasoll_zha_with_home_assistant/?rdt=43685 some people are very satisfied about them, and a few can’t make them work. So there’s something odd going on. I’ve had more issues with some of the IKEA stuff like the styrbar remotes and the vallhorn motion detectors, some work better than others. IKEA is convenient for me because they are cheap and located close to where I live, and build quality of their stuff is excellent for the price, but compatibility with ZHA is not great.
Good evening all, my first post here
I have 9 Parasoll running well since a while. Bought number 10 today, I can confirm, it just offers IAS Zone, and the device_class is not opening (like the others), but identify
Maybe it needs some time? Tomorrow I will connect it to my IKEA router, and check if it runs there.
Dear community,
I continued my investigations today, with success!
Beside my HA I have also a running IKEA Dirigera hub. After a reset of the Parasoll (and removing it from HA) I added it to the Dirigera, what worked fine. Waiting some time, I thought, there might be an update waiting at IKEA. After ca an hour I removed it again, and added it again in HA. And now (after 2 tries) it appears with the well known device class, and it works fine now. No IAS-Zone anymore.
Now also the light inside my bedroom wardrobe goes on when I open the door, and goes off when I close the door again
Ah, dat is thanks for the information! Since I do not have a different hub than my sonoff stick, I will re-acquaintmmyself with manually pushing updates to zigbee devices. I remember I did that once some year and a half ago but I completely forgot how