how can i resolve it ? thanks
YES
Read the post from francisp
effectively, i have deconz in my integrations(supervisor) …
so i have to uninstall it but how can i do that ? thanks
ok i have seen it…
if i understood correctly, it is not possible to use zha and zigbee2mqtt together …
if you uninstall deconz, the zigbee devices in zha no longer work
so how to use zigbee2mqtt? thanks
sorry but i am a beginner in ha
confronted with the identical issue I added the 'serial" entry in configuration.yaml, which leads to the following error:
2021-09-14 12:41:25 ERROR (MainThread) [homeassistant.setup] Setup failed for serial: No setup or config entry setup function defined.
… how to proceed please? only connected the Deconz stick, no other add-on configured
would I need a port forward maybe (since I am not on the default ports with my HA instance )?
The part of configuration.yaml containing serial should at least contain the port the adapter is attached to.
serial:
port: /dev/ttyACM0
adapter: deconz
And we are talking about the configuation.yaml of zigbee2mqtt, not about the configuration.yaml of home assistant.
8 Likes
thank you! I completely missed that, (probably because there is no configuration.yaml for the zigbee2mqtt add-on, but a configuration panel). Duh. But there is… in the zigbee2mqtt folder. no wonder it is all so confusing. Never use an identical name for different files ;-(
it was immediately successful, how cool is that!
now how to get it to not show under ‘homeassistant’ in mqtt explorer, but under its own login name?
1 Like
by default it uses mqtt discovery (which imo is also enabled by default in HA). So the entity should appear immediately (check developer HA page).
If you don’t have discovery enabled or don’t want to use it, you can add entities on your own. usually you can find needed yaml code on zigbee2mqtt portal on page dedicated to particular device.
I suggest however to change the name of device to something more friendly first (use blue edit icon shown on your screenshot)
thanks, and yes, ive changed the friendly name.
Also I set homeassistant: false ( have 3 HA instances, which makes the moniker somewhat useless 
)
it now is found under:
with as you can see all relevant values in the 1 payload. Before with the homeassisant: true it shows like this:
why I dont get that now is still bit unclear to me. shouldn’t I see that, but under the zigbee2mqtt base topic?
I have 3 HA instances too, but still homeassistant: true 
This is the actual payload, independent if homeassistant true or false
These are the mqtt auto-discovery messages, only when homeassistant: true :
yeah, figured as much so we cant rename the homeassistant there?
maybe more importantly: we dont need those discovery messages for eg creating an mqtt switch? seems a bit of a hassle, where I would have hoped the sensors and switches on the device to be available in the HA entities…
off-topic:
maybe I should explore the ZHA integration too, and see if that does create the entities. Wonder if we can configure that to use the Conbee on another HA instance, just like we can do with the zwaveJS server and integration.
No. That is the topic HA listens on for auto-discovery messages
If not using discovery, you have to enter everything manual in .yaml (and you won’t have devices, since devices are only created through discovery)
if using discovery everything appears in entities.
thanks. I checked once more, but I dont see any Frient entity, even having clicked the ‘change homeassistant friendly_name’ checkbox.
not a single sensor or switch from the Z2M server is created, only mqtt topics? maybe I need an extra setting somewhere?
Set homeassistant: true and restart zigbee2mqtt
yes, thats what I have done… few times, and still no entities in sight.
Did manage to set the discovery topic though:
advanced:
homeassistant_discovery_topic: zigbee2mqtt
nicely adds all under the 1 key in mqtt explorer:
and the user: and password: options allow to separate the logins on the broker easily, I feel that is a much underestimated option.
for now I remain in quest for the entities…
Does not change the fact that homeassistant itself still listens on homeassistant to discover devices.
Homeassistant configuration.yaml :
mqtt:
broker: x.x.x.x
port: 1883
discovery: true
discovery_prefix: homeassistant
yeah well, I dont use discovery , because way too many topics this simply cleans the mqtt explorer window for me.
which now makes it all clear: thats why there are no entities…? duh. 
indeed. Entities are created through mqtt auto-discovery.
1 Like