Paired Zigbee2MQTT device not discoverable in Home Assistant Devices/Entities?

temmyn · June 13, 2025, 3:50am

Hi,

I have several of those Tuya TS011F plugs. Haven’t had issues so far. They work great.
With the latest I have the issue, that it has been paired successfully and shows all values (see screenshot), but when searching e.g. “NAS2” in devices or entities in Home Assistant it doesn’t find anything. The same for the developer tools/states.

Any clue/idea, why that is/could be?

I already removed the device and paired it again. Also changed the device name and restarted HA. But nothing has helped so far.

francisp · June 13, 2025, 4:10am

Try restarting Zigbee2MQTT

LiQuid_cOOled · June 13, 2025, 4:28am

Do you see a new entity in MQTT? There can be a disconnect with the Z2M name and the HA entity name.

Follow the suggestion by @francisp first.

temmyn · June 13, 2025, 4:31am

Restart of Z2M Addon didn’t help.

The Zigbee device is listed in Z2M addon (online), but not in MQTT Addon
Hence cannot be found in HA devices.

tom_l · June 13, 2025, 4:40am

Use the blue edit button bottom left of that page or on the main devices list to rename the device (to something easily searchable) and make sure you have the update home assistant switch on:

See if that updates Home Assistant. If it does then change the name back - making sure you have the switch on again.

LiQuid_cOOled · June 13, 2025, 4:43am

You can also check the Mosquitto Broker logs to ensure the broker is communicating to MQTT

temmyn · June 13, 2025, 4:55am

I had the option tagged, when renaming when device. Didn’t solve the issue.

Regarding the Mosquito Broker Log. All my Zigbee → Z2M → HA automations are working, so I guess, the communication must be ok/working.

LiQuid_cOOled · June 13, 2025, 5:05am

You are on a troubled device firmware(v1.0.5). Using Z2M, see if the OTA update works.

tom_l · June 13, 2025, 5:06am

Do it again.

temmyn · June 13, 2025, 5:10am

I did, here is the Z2M log of the renaming process. According to Z2M it was ok:


info 2025-06-13 07:04:51z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/rename', payload '{"data":{"from":"Buero NAS2","homeassistant_rename":true,"to":"AAAAA"},"status":"ok","transaction":"4bpij-1"}'
info 2025-06-13 07:04:51z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/AAAAA/availability', payload '{"state":"online"}'

Regarding the firmware. The other (working) devices show the same firmware version 1.0.5. On the OTA check Firmware Version installed and available is shown: 1.0.01-3.6.07 (for the other devices of the same type as well). So I think the firmware version should be fine.

Still device is not beeing found under “AAAAA”. The device count in mqtt does not go up. Also, since this is a new device, it should not be assigned to any area, so in the mqtt list, there should be a device without area assigment, but it isn’t. All are assigned to an area.

Is there any further “deep” debugging I can do?

francisp · June 13, 2025, 5:15am

What version of HA are you running, and what version of Zigbee2MQTT ?

temmyn · June 13, 2025, 5:18am

This is my version:

Installation method Home Assistant OS
Core 2025.5.3
Supervisor 2025.05.5
Operating System 15.2
Frontend 20250516.0

Z2M: 2.4.0 commit: unknown

francisp · June 13, 2025, 5:20am

Ok, that is not the problem then.

Just a question, the home assistant checkbox did not get unchecked by accident ?

LiQuid_cOOled · June 13, 2025, 5:27am

The disconnect appears to be between the broker and MQTT.

What server settings do you have in your z2m config?

An example…

mqtt:
  server: mqtt://core-mosquitto:1883

LiQuid_cOOled · June 13, 2025, 5:39am

Broken attribute reporting functionality

Starting with firmware version 1.0.5 (which comes pre-flashed on plugs produced since Q4 2021) core functionality on this plug is broken. TuYa has disabled the automatic reporting of power, voltage and current values meaning they need to be polled instead. The poll interval can be controlled through the measurement_poll_interval option.

If your plug is affected, it will be detected as TS011F_plug_3 instead of TS011F_plug_1

Directly from Z2M

francisp · June 13, 2025, 5:56am

Even if measurement_poll_interval not set, it should be discovered.

LiQuid_cOOled · June 13, 2025, 6:00am

I do agree, but it is a Tuya device. If the Tuya bridge was used, I suspect it would be discovered by HA.

temmyn · June 13, 2025, 6:17am

So here is the HA integration setting. It’s enabled. Not sure why there is “homeassistant2”. However, Z2M/HA integration is working, I added yesterday three other devices (one was the exact the same socket which came with the same delivery) without a problem.

Here you can see the other devices I have. They are working fine. So I still believe it’s not a problem with the firmware?

Here is my Z2M config:

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt:
  server: mqtt://core-mosquitto:1883
serial:
  port: >-
    /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_82d45144336cef11825197adc169b110-if00-port0
  adapter: zstack

francisp · June 13, 2025, 6:19am

Change discovery topic to homeassistant. It should work

temmyn · June 13, 2025, 6:22am

i tried but get this error:


<small>2025-06-13 08:21:14</small>`z2m: Request 'zigbee2mqtt/bridge/request/options' failed with error: 'Extension with name HomeAssistant already present'`