Zigbee2MqttAssistant
Zigbee2MqttAssistant copied to clipboard
yllibed
lot of "no components" devices ...
Quite a strange topic I know ....
And it's not defined as BUG either, as I'm not sure if it's a bug. Just asking for help. I got about 20 of these devices:
Could all be true, that those are not supported, but I don't believe it. I don't even have that many devices. How can I find out what devices are? Is there something like the MAC Address Database where you can lookup the manufaturer or something? How can I get rid of those entries? Or better: What can I do to make them work in case they really are there ....?
Possibly a duplicate of or at least related to #130, #129, #176, and #170.
I think these might be devices that are listed in the zigbee2mqtt database.db, but are not properly paired (this sometimes happens when pairing fails). Stop zigbee2mqtt, search for the item in the database.db file, delete it (make a backup first) and restart zigbee2mqtt.
I think these might be devices that are listed in the zigbee2mqtt database.db, but are not properly paired (this sometimes happens when pairing fails). Stop zigbee2mqtt, search for the item in the database.db file, delete it (make a backup first) and restart zigbee2mqtt.
At least for me, I did that already and my db is 'clean' but thanks for the hint.
Anyway, I am starting to believe that all these issues are related to Home Assistant's device / integration / entity registry and how MQTT discovery works. Can you check if such devices are listed in HA's registry?
Mine were listed there and after removal (which was a pain), such phantoms are / seem to be (fingers crossed) gone in Z2MA as well. :sunglasses:
I read the other open issues, and it seems like a common, but unsolved issue. I checked the database.db file, and DIDN'T find MOST of those ID in the file. No idea where they come from. Then I started deleting some of the IDs that I DID find. Unfortunately those IDs were duplicates, that also showed up somewhere down the list as connected and properly working devices. Of course they were unfunctional after removing them from the db file. But still showed up like before in the unknown list. Good that I had a backup of the db file.
Have you checked the device registry? See my previous post...
Sorry, not checked. If you say HA's registry what file are you referring to exactly? Thanks!
No files, at least in v0.105 there's a web UI for that (something like Settings / Configuration > Integration / Devices / Entities).
The devices that show "no components" don't show up in this entities screen. No idea WHERE in the system they are buried. But I'd really like to get rid of them.
I also have a 3 of these, however in my case they are all groups (https://www.zigbee2mqtt.io/information/groups.html) that I configured within Z2M.
Would be great if these could show a group badge or something.
I also have this. When I restart z2m it looks good again, but after a couple of days this issue appears again in Z2Massistant
Same problem here. I have all my devices "NO COMPONENTS". But if i restart z2m, it's fine for next 24 hours.
I got the same issue. All my devices have "no components". Restarting Z2M does not change anything. My devices are on the Z2M compatibility list.
Is it possible that showing components requires MQTT discovery? In my case this is deactivated in Z2M, since I prefer to configure my devices in HA manually.
I found out why this problem happened to me. It was because i used external MQTT broker. If i use local mqtt, no problems....
Related: I have been trying to get 2 Hue bulbs to connect to my zigbee network for the last few nights and have the same experience. At first it was because the devices were not supported in devices.js (new model, off by 1 digit). Now that has been corrected but they show as no components either way. I have tried removing their entries from database.db but the entry gets recreated upon launch.
Use "MQTT Explorer" connect to your MQTT (such as Mosquitto), navigate to the zigbee2mqtt root topic, under that you'll find both the hex and the friendly name where the hex name is supposed to be superseded by the friendly name, so just remove the hex name. Then do a "Reset local state" in zigbee2mqttassistant. This worked for me. Apparently when you rename a device to assign a friendly name, the device will start appearing with its friendly name on the MQTT server, but the hex name also remains/stuck.
Edit: I see this is covered here: https://github.com/yllibed/Zigbee2MqttAssistant/issues/130
@fdaemon can you kindly add a print screen? I am unable to find the hex name in MQTT Explorer. All my zigbee end devices are marked with "NO COMPONENTS Maybe this device is not (yet) supported by Zigbee2Mqtt?":
Thank you
Any news about this issue? I did'nt found any hex name in MQTT Explorer but I still have all of my devices with "NO COMPONENTS" Thanks
