I’m having the same issue. I just added 4 sensors, 2 different brands, and all 4 displayed as moisture sensors. Changed easily in customize.yaml but I never had this problem before so something must have changed to break it.
remove the device from ZHA config panel and trigger the device to wake it up so it could process the removal requests. Then enable full debug logging for ZHA component and zigpy/bellows/deconz. Add device and post the log of device pairing.
When IAS sensor is paired, ZHA tries to read the IAS sensor type, but some manufacturers (Smart Things multisensor) report wrong information for that attribute
I have a few 3326-L sensors that got paired as moisture sensor, just changed the device class under customization. Side note: if you pair these sensors to a ST hub, you can update the firmware on them. I had some problematic units that are working fine after a firmware update.
Also I think I remember your username from the Hubitat forums!
1 Like
I’d like to report the Bosch Motion Sensor (ISW-ZPR1-WP13) as working but the battery state still reports as unknown.
There is an issue posted for this here:
https://github.com/home-assistant/home-assistant/issues/25361
Any resolution to that issue on the horizon?
I have this device connected to my powermeter, it’s a Develco EMIZB-132 Norwegian HAN adapter. This one require a device handler as far as I have found out, but can’t find any i Home Assistant. This for both activate meter readings and do some required maths ond the return data.
The following i s what I can find in the ZHA devices:
IEEE: 00:15:bc:00:1b:02:4d:68
Nwk: 0x17e6
LQI: 255
RSSI: -88
Sist sett: 2019-12-22T22:25:25
Strømkilde: Battery or Unknown
Develco Products A/S EMIZB-132 684d021b on_off switch.develco_products_a_s_emizb_132_684d021b_on_off
Develco Products A/S EMIZB-132 684d021b smartenergy_metering
sensor.develco_products_a_s_emizb_132_684d021b_smartenergy_metering
Develco Products A/S EMIZB-132 684d021b electrical_measurement
sensor.develco_products_a_s_emizb_132_684d021b_electrical_measurement
Interesting, you get the on_off switch, but I don’t see cluster 0x0006 mentioned in https://www.develcoproducts.com/media/3747/emizb-132-technical-manual-emi-norwegian-han.pdf
Remove the device, enable debug logging, re-pair the device and post logs here. Interested to see the signature of the device. However atm there’s limited support for electrical_measurement and smart_energy_metering clusters. we are only getting instantaneous_demand and active_power.
I will do that, here is the norwegian authorithys describtion off these meters, they are in norwegian but it’s possible to translate https://www.nek.no/info-ams-han-utviklere/
This is wat I got from ZHA when I add the develco unit:
[0x0000:zdo] ZDO request 0x0036: [60, <Bool.false: 0>]
Device 0xa3e8 (00:15:bc:00:1b:02:4d:68) joined the network
[0xa3e8] Requesting ‘Node Descriptor’
[0xa3e8] Extending timeout for 0x31 request
Device 0xa3e8 (00:15:bc:00:1b:02:4d:68) joined the network
Skip initialization for existing device 00:15:bc:00:1b:02:4d:68
[0xa3e8:zdo] ZDO request 0x0013: [0xa3e8, 00:15:bc:00:1b:02:4d:68, 0]
[0xa3e8] Node Descriptor:
[0xa3e8] Discovering endpoints
[0xa3e8] Extending timeout for 0x33 request
[0xa3e8:zdo] ZDO request 0x0006: [0xfffd, 260, [25], []]
Ignoring message (b’110101001510400304050300’) on cluster 25: unknown endpoint or cluster id: 2
[0xa3e8] Discovered endpoints: [1, 2]
[0xa3e8:1] Discovering endpoint information
[0xa3e8] Extending timeout for 0x36 request
[0xa3e8:1] Discovered endpoint information: <SimpleDescriptor endpoint=1 profile=49353 device_type=1 device_version=1 input_clusters=[3, 5, 6] output_clusters=[]>
[0xa3e8:2] Discovering endpoint information
[0xa3e8] Extending timeout for 0x38 request
[0xa3e8:2] Discovered endpoint information: <SimpleDescriptor endpoint=2 profile=260 device_type=83 device_version=0 input_clusters=[0, 3, 32, 1794, 1796, 2820] output_clusters=[3, 10, 25]>
[0xa3e8] Extending timeout for 0x3a request
[0xa3e8:2:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=58 command_id=Command.Read_Attributes_rsp>
[0xa3e8:2] Manufacturer: Develco Products A/S
[0xa3e8:2] Model: EMIZB-132
Checking quirks for Develco Products A/S EMIZB-132 (00:15:bc:00:1b:02:4d:68)
Considering <class ‘zigpy.quirks.smartthings.SmartthingsMultiPurposeSensor’>
Fail because endpoint list mismatch: {1} {1, 2}
Considering <class ‘bellows.zigbee.application.EZSPCoordinator’>
Fail because endpoint list mismatch: {1} {1, 2}
Considering <class ‘zhaquirks.gledopto.soposhgu10.SoposhGU10’>
Fail because endpoint list mismatch: {11, 13} {1, 2}
Considering <class ‘zhaquirks.lutron.lzl4bwhl01remote.LutronLZL4BWHL01Remote2’>
Fail because endpoint list mismatch: {1} {1, 2}
Considering <class ‘zhaquirks.netvox.z308e3ed.Z308E3ED’>
Fail because endpoint list mismatch: {1} {1, 2}
Considering <class ‘zhaquirks.osram.a19twhite.A19TunableWhite’>
Fail because endpoint list mismatch: {3} {1, 2}
Considering <class ‘zhaquirks.philips.rwl021.PhilipsRWL021’>
Fail because profile_id mismatch on at least one endpoint
Considering <class ‘zhaquirks.smartthings.tag_v4.SmartThingsTagV4’>
Fail because endpoint list mismatch: {1} {1, 2}
Considering <class ‘zhaquirks.xbee.xbee3_io.XBee3Sensor’>
Fail because endpoint list mismatch: {232, 230} {1, 2}
Considering <class ‘zhaquirks.xbee.xbee_io.XbeeSensor’>
Fail because endpoint list mismatch: {232, 230} {1, 2}
Considering <class ‘zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor’>
Fail because endpoint list mismatch: {1} {1, 2}
device - 0xa3e8:00:15:bc:00:1b:02:4d:68 entering async_device_initialized - is_new_join: True
device - 0xa3e8:00:15:bc:00:1b:02:4d:68 has joined the ZHA zigbee network
0xa3e8: started configuration
0xa3e8:ZDO: channel: ‘async_configure’ stage succeeded
[0xa3e8] Extending timeout for 0x3c request
[0xa3e8] Extending timeout for 0x3e request
[0xa3e8] Extending timeout for 0x40 request
[0xa3e8:1:0x0006]: bound ‘on_off’ cluster: Status.SUCCESS
[0xa3e8] Extending timeout for 0x42 request
[0xa3e8:2:0x0000]: bound ‘basic’ cluster: Status.SUCCESS
[0xa3e8:2:0x0000]: finished channel configuration
[0xa3e8] Extending timeout for 0x44 request
[0xa3e8:2:0x0702] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=64 command_id=Command.Read_Attributes_rsp>
Error calling listener.attribute_updated: unsupported operand type(s) for *: ‘uint24_t’ and ‘NoneType’
[0xa3e8] Extending timeout for 0x46 request
[0xa3e8:1:0x0006] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=66 command_id=Command.Configure_Reporting_rsp>
[0xa3e8:1:0x0006]: reporting ‘on_off’ attr on ‘on_off’ cluster: 0/900/1: Result: ‘[[]]’
[0xa3e8:2:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=68 command_id=Command.Read_Attributes_rsp>
[0xa3e8:2:0x0000]: initializing channel: from_cache: False
[0xa3e8:2:0x0000]: channel: ‘async_configure’ stage succeeded
[0xa3e8] Extending timeout for 0x48 request
[0xa3e8:1:0x0006]: finished channel configuration
[0xa3e8:1:0x0006]: channel: ‘async_configure’ stage succeeded
[0xa3e8:2:0x0702] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=70 command_id=Command.Read_Attributes_rsp>
Error calling listener.attribute_updated: unsupported operand type(s) for *: ‘uint24_t’ and ‘NoneType’
[0xa3e8] Extending timeout for 0x4a request
[0xa3e8:2:0x0b04]: bound ‘electrical_measurement’ cluster: Status.SUCCESS
[0xa3e8] Extending timeout for 0x4c request
[0xa3e8:2:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=2 command_id=Command.Report_Attributes>
[0xa3e8:2:0x0b04] ZCL request 0x000a: [[<Attribute attrid=1285 value=>, <Attribute attrid=1288 value=>, <Attribute attrid=2309 value=>, <Attribute attrid=2312 value=>, <Attribute attrid=2565 value=>, <Attribute attrid=2568 value=>]]
[0xa3e8:2:0x0b04] Attribute report received: rms_voltage=65535, rms_current=65535, rms_voltage_ph_b=65535, rms_current_ph_b=65535, rms_voltage_ph_c=65535, rms_current_ph_c=65535
[0xa3e8:2:0x0702] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=74 command_id=Command.Read_Attributes_rsp>
[0xa3e8] Extending timeout for 0x4e request
[0xa3e8:2:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=76 command_id=Command.Configure_Reporting_rsp>
[0xa3e8:2:0x0b04]: reporting ‘active_power’ attr on ‘electrical_measurement’ cluster: 30/900/1: Result: ‘[[]]’
[0xa3e8:2:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=3 command_id=Command.Report_Attributes>
[0xa3e8:2:0x0b04] ZCL request 0x000a: [[<Attribute attrid=1285 value=>, <Attribute attrid=1288 value=>, <Attribute attrid=2309 value=>, <Attribute attrid=2312 value=>, <Attribute attrid=2565 value=>, <Attribute attrid=2568 value=>]]
[0xa3e8:2:0x0b04] Attribute report received: rms_voltage=65535, rms_current=65535, rms_voltage_ph_b=65535, rms_current_ph_b=65535, rms_voltage_ph_c=65535, rms_current_ph_c=65535
[0xa3e8:2:0x0702] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=78 command_id=Command.Read_Attributes_rsp>
[0xa3e8] Extending timeout for 0x50 request
[0xa3e8:2:0x0b04]: finished channel configuration
[0xa3e8:2:0x0b04]: channel: ‘async_configure’ stage succeeded
[0xa3e8:2:0x0702]: bound ‘smartenergy_metering’ cluster: Status.SUCCESS
[0xa3e8] Extending timeout for 0x52 request
[0xa3e8:2:0x0702] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=4 command_id=Command.Report_Attributes>
[0xa3e8:2:0x0702] ZCL request 0x000a: [[<Attribute attrid=0 value=>, <Attribute attrid=1024 value=>, <Attribute attrid=512 value=>]]
[0xa3e8:2:0x0702] Attribute report received: current_summ_delivered=281474976710655, instantaneous_demand=-8388608, status=0
[0xa3e8:2:0x0702] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=82 command_id=Command.Configure_Reporting_rsp>
[0xa3e8:2:0x0702]: reporting ‘instantaneous_demand’ attr on ‘smartenergy_metering’ cluster: 30/900/1: Result: ‘[[]]’
[0xa3e8:2:0x0702] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=5 command_id=Command.Report_Attributes>
[0xa3e8:2:0x0702] ZCL request 0x000a: [[<Attribute attrid=0 value=>, <Attribute attrid=1024 value=>, <Attribute attrid=512 value=>]]
[0xa3e8:2:0x0702] Attribute report received: current_summ_delivered=281474976710655, instantaneous_demand=-8388608, status=0
[0xa3e8:2:0x0702]: finished channel configuration
[0xa3e8:2:0x0702]: channel: ‘async_configure’ stage succeeded
0xa3e8: completed configuration
0xa3e8: stored in registry: ZhaDeviceEntry(name=‘Develco Products A/S EMIZB-132’, ieee=‘00:15:bc:00:1b:02:4d:68’, last_seen=1577085700.0461383)
0xa3e8: started initialization
0xa3e8:ZDO: entry loaded from storage: ZhaDeviceEntry(name=‘Develco Products A/S EMIZB-132’, ieee=‘00:15:bc:00:1b:02:4d:68’, last_seen=1577085700.0461383)
0xa3e8:ZDO: channel: ‘async_initialize’ stage succeeded
[0xa3e8] Extending timeout for 0x54 request
[0xa3e8] Extending timeout for 0x56 request
[0xa3e8] Extending timeout for 0x58 request
[0xa3e8:1:0x0006]: attempting to update onoff state - from cache: True
[0xa3e8:2:0x0b04]: async_update
[0xa3e8] Extending timeout for 0x5a request
[0xa3e8:1:0x0006] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=84 command_id=Command.Read_Attributes_rsp>
[0xa3e8:1:0x0006]: initializing channel: from_cache: False
[0xa3e8:1:0x0006]: channel: ‘async_initialize’ stage succeeded
[0xa3e8] Extending timeout for 0x5c request
[0xa3e8:2:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=86 command_id=Command.Read_Attributes_rsp>
[0xa3e8:2:0x0000]: initializing channel: from_cache: False
[0xa3e8:2:0x0000]: channel: ‘async_initialize’ stage succeeded
[0xa3e8:2:0x0702] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=88 command_id=Command.Read_Attributes_rsp>
[0xa3e8:2:0x0702]: initializing channel: from_cache: False
[0xa3e8:2:0x0702]: channel: ‘async_initialize’ stage succeeded
[0xa3e8:2:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=90 command_id=Command.Read_Attributes_rsp>
[0xa3e8:2:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=92 command_id=Command.Read_Attributes_rsp>
[0xa3e8] Extending timeout for 0x5e request
[0xa3e8:2:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=94 command_id=Command.Read_Attributes_rsp>
[0xa3e8:2:0x0b04]: initializing channel: from_cache: False
[0xa3e8:2:0x0b04]: channel: ‘async_initialize’ stage succeeded
0xa3e8: power source: Battery or Unknown
0xa3e8: completed initialization
[0xa3e8:2:0x0b04]: async_update
[0xa3e8] Extending timeout for 0x60 request
[0xa3e8:2:0x0b04] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=96 command_id=Command.Read_Attributes_rsp>
How to add a logg file to this post ? It’s to long to copy and paste here
Tried adding the Ikea Fyrtur blinds and remote. No dice so far. They join the network, but only show the battery status. Remote also shows a binary sensor that always says closed.
1 Like
I have 4 of the old Quirky Outlink plugs. The energy monitoring on those never seemed to work correctly, but while digging through some of the “Attributes” of the switch, I noticed that one did appear to be tracking usage and updating while the plug was supplying power.
Under the Cluster:
Metering (Endpoint id: 1, Id: 0x0702, Type: in)
and Attribute:
current_summ_delivered (id: 0x0000)
Is there a way to change the default cluster attribute used for reporting energy?
A little digging online in a Smarthings forum and found:
“The Outlink reports in kWh, with a conversion factor of 1/3600000”
With the current power draw, that conversion seems about right for the rate the value increases.
Just finished up support for zigbee cover devices. Once it makes its way into the release Ikea Fyrtur will be supported (and hopefully any other zigbee cover devices)
6 Likes
Awesome, planning to get some of these blinds in a couple of months.
Curious if anyone has jumped to 0.104 and tested Zigbee groups in ZHA?
I’m trying to, but I stumbled across a problem creating ZHA groups. Further, I can’t seem to find where the ZHA groups are created (if they are created as entities, they aren’t showing up in my states list nor my entities list).
1 Like
I think these are groups in the zigbee sense, not the HA sense. Things grouped will respond to group commands, like a remote controlling grouped lights directly. Going to give it a spin now…
Yeah, that makes sense and it’s how I understand ZHA groups to work as well. However, until I can even add (or modify now) said groups, I’m dead in the water on this one. 
[Edit]: One thing I don’t understand is how we would issue a group command without a remote if there is no corresponding entity created.
you should be able to create/add devices to the groups and then issue zha.issue_zigbee_group_command service calls to issue ZCL commands to the specified group. Currently there’re no ZHA entities and no UI to bind remotes to the groups.
1 Like
Ahhh, that’s the part I was missing. Thanks! The thing that sucks is that probably only a handful of users of HA (myself included lol) are going to bother trying to properly call any service in the ZHA domain. I really hope that the devs are planning on using an entity type of approach with groups once it matures a bit.
This is correct