Just wanted to provide an update that I had recently gotten a new SD card and decided to fresh install everything and moved over my entire config directory. Things are pretty stable now and I don’t need to restart home assistant to regain control of zigbee.
What is the DeviceType that it reports as? If it’s REMOTE_CONTROL, then there doesn’t appear to be a Clusters entry for that type in the profiles. (Which is probably one of the problems I’m having with the Iris Key Fob)
what configuration were you using? zha?
@gohassgo what zha configuration are you using? i am seeing the same lock up problem as noted by others- curious if its a setup or configuration issue
@dexrex this is what my config looks like:
zha:
usb_path: /dev/zigbee
database_path: zigbee.db
for the record the issue came back a few days later. I am starting to wonder if maybe its a faulty usb stick
there is another thread on this, which highlights some specifics on the configuration definition. I still have not got this to work, but perhaps there’s a hint in there
ok. i got it to work, at it seems reliable.
the format of the configuration is very specific, my indentation was wrong and i was missing a space, and i had to remove all other USB devices (not sure why yet)
here’s the configuration, you seem to also need to include zwave, or zha gives an error and hangs hassio.
(indent usb_path, database_path attributes)
zwave:
usb_path: /dev/ttyUSB0zha:
usb_path: /dev/ttyUSB1
database_path: zigbee.db
will report back on device testing.
Yea mine is also indented properly and it works. I have my USB paths mapped out too. You will probably see the lock up show up in a few days or so is my guess. Again its a HASS restart required not a computer restart which means something is happening between the communication of hass and the USB stick as the computer still recognizes it. Just stops responding to zigbee.
The device_type from the database is 2080, which when converted to hex becomes 0x820. I had a look at the ZLL profile definitions and 0x820 looks to be defined as CONTROLLER
Here’s my config (looks like you settled on something similar for zha):
# Z-Wave
zwave:
usb_path: /dev/ttyUSB0
network_key: "0x00,0x11,0x22,0x33,0x00,0x11,0x22,0x33,0x00,0x11,0x22,0x33,0x00,0x11,0x22,0x33"
# Zigbee
zha:
usb_path: /dev/ttyUSB1
database_path: /config/zha.db
Confirming the newest Samsung SmartThings Outlet works great, at least for on/off. Using the HUSBZB-1.
Through my HUSBZB-1, I have:
Sensors:
- 2 CentraLite 3321S contact switches (Samsung SmartThings). Both work for open/close and temperature sensing.
- 1 CentraLite 3325S motion sensor (Samsung SmartThings). Works for motion and temperature sensing
- 1 CentraLite 3326L motion sensor (Iris). Works for motion and temperature sensing.
Plugs:
- 1 CentraLite 4257050 RZHAC smart plug (Samsung SmartThings). Works as expected, though it is detected as a
light
and not aswitch
. - 3 CentraLite 3210L smart plugs (Iris). These are great, though 1 continues to detect as a
light
instead of as aswitch
. These smart plugs also have a Z-Wave repeater in them that you must add as Z-Wave nodes separately.
Lights:
- 1 Cree Connected A19 60w equivalent, dimmable. This works great, and I plan on buying more.
All of these work well. I have them integrated with Alexa via Home Assistant Cloud, and Siri through the homebridge home-assistant plugin.
The following is the itemized output of:
bellows -d /dev/ttyUSB1 devices -D ./zigbee.db
Iris Motion Sensor
Device:
NWK: 0xbf6d
IEEE: 00:0d:6f:00:04:b9:34:c8
Endpoints:
1: profile=0x104, device_type=DeviceType.IAS_ZONE
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Poll Control (32)
Temperature Measurement (1026)
IAS Zone (1280)
Diagnostic (2821)
Output Clusters:
Ota (25)
2: profile=0xc2df, device_type=263
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Diagnostic (2821)
Manufacturer Specific (64582)
Output Clusters:
Identify (3)
SmartThings Motion Sensor
Device:
NWK: 0x2446
IEEE: 00:0d:6f:00:0b:13:f6:1e
Endpoints:
1: profile=0x104, device_type=DeviceType.IAS_ZONE
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Poll Control (32)
Temperature Measurement (1026)
IAS Zone (1280)
Diagnostic (2821)
Output Clusters:
Ota (25)
%s: Uninitialized
Cree Connected Bulb
Device:
NWK: 0x6bc3
IEEE: e2:0d:b9:ff:fe:06:ac:ba
Endpoints:
10: profile=0xc05e, device_type=DeviceType.DIMMABLE_LIGHT
Input Clusters:
Basic (0)
Identify (3)
Groups (4)
Scenes (5)
On/Off (6)
Level control (8)
LightLink (4096)
Output Clusters:
Basic (0)
Ota (25)
Iris 3210L Smart Plug
Device:
NWK: 0x9a47
IEEE: 00:0d:6f:00:05:97:89:45
Endpoints:
1: profile=0x104, device_type=DeviceType.ON_OFF_LIGHT
Input Clusters:
Basic (0)
Identify (3)
Groups (4)
Scenes (5)
On/Off (6)
Electrical Measurement (2820)
Diagnostic (2821)
Manufacturer Specific (64515)
Output Clusters:
Ota (25)
Note that this is anomalously flagged as an ON_OFF_LIGHT
where the other 3210Ls are SMART_PLUG
SmartThings Contact Switch
Device:
NWK: 0x6fd3
IEEE: 00:0d:6f:00:05:65:a2:13
Endpoints:
1: profile=0x104, device_type=DeviceType.IAS_ZONE
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Poll Control (32)
Temperature Measurement (1026)
IAS Zone (1280)
Diagnostic (2821)
Manufacturer Specific (64514)
Output Clusters:
Ota (25)
2: profile=0xc2df, device_type=12
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Diagnostic (2821)
Manufacturer Specific (64527)
Output Clusters:
Identify (3)
SmartThings Contact Switch
Device:
NWK: 0xce38
IEEE: 00:0d:6f:00:05:76:89:fd
Endpoints:
1: profile=0x104, device_type=DeviceType.IAS_ZONE
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Poll Control (32)
Temperature Measurement (1026)
IAS Zone (1280)
Diagnostic (2821)
Manufacturer Specific (64514)
Output Clusters:
Ota (25)
2: profile=0xc2df, device_type=12
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Diagnostic (2821)
Manufacturer Specific (64527)
Output Clusters:
Identify (3)
Iris 3210L Smart Plug
Device:
NWK: 0x7086
IEEE: 00:0d:6f:00:0b:2d:4f:30
Endpoints:
1: profile=0x104, device_type=DeviceType.SMART_PLUG
Input Clusters:
Basic (0)
Identify (3)
Groups (4)
Scenes (5)
On/Off (6)
Metering (1794)
Electrical Measurement (2820)
Diagnostic (2821)
Manufacturer Specific (64515)
Output Clusters:
Ota (25)
SmartThings Plug
Device:
NWK: 0xac6c
IEEE: 00:0d:6f:00:05:8f:ed:d6
Endpoints:
1: profile=0x104, device_type=DeviceType.ON_OFF_LIGHT
Input Clusters:
Basic (0)
Identify (3)
Groups (4)
Scenes (5)
On/Off (6)
Electrical Measurement (2820)
Diagnostic (2821)
Output Clusters:
Ota (25)
Note that this is anomalously flagged as an ON_OFF_LIGHT
even though it is a SMART_PLUG
.
Iris 3210L Smart Plug
Device:
NWK: 0x2744
IEEE: 00:0d:6f:00:0b:2c:f3:13
Endpoints:
1: profile=0x104, device_type=DeviceType.SMART_PLUG
Input Clusters:
Basic (0)
Identify (3)
Groups (4)
Scenes (5)
On/Off (6)
Metering (1794)
Electrical Measurement (2820)
Diagnostic (2821)
Manufacturer Specific (64515)
Output Clusters:
Ota (25)
I’m having this same issue. All zigbee devices just stop communicating with HASS. If I restart HASS then everything is back, but after a few hours it goes back down again. All other devices continue operating normally - it’s just the zigbee devices that stop working. Don’t see anything in the error logs to indicate what might be wrong.
Not sure if there’s another thread or Github issue tracking this?
I had originally opened up an issue but I had reinstalled home assistant on an ubuntu server and so far have been up and running for 5 days straight without issue. I don’t know if the issue will come back or not but since reinstalling it has been fine.
I just got a Iris 3210L Smart Plug and it works great. I see references to it being able to measure current (in amps or watts), and I see “Electrical Measurement (2820)” in your bellows output. Have you been able to get that to work in Home Assistant?
Someone is actually working on this already. Hopefully we will see the PR come by soon, personally looking forward to the battery and energy reporting
Awesome, that’s great to see.
As an aside does anyone know of a way to see zigbee signal strength? I bought the smart plug mainly to strengthen my zigbee mesh network and I’d like to be able to test different locations for it. Ideally something in HA would be great, but even just a command line tool on the Pi would work.
I have no idea, but I get the idea that it might be in the Diagnostic
cluster data.
Have you got these working again?
Also do they look as ugly as they do online?
I’ll try to get back to that PR this week. I have metering and battery reporting mostly working. I’m still trying to find a stable way to set up the entity id’s. I have something working but I’m going to try to clean it up a bit. My PR will include a breaking change and that’s why I closed it for now.