Zigbee2MQTT throwing errors in HA Core logs

[jakeshbazi]

Hi Folks,

I’m just about at the end of my ropes and not sure what is going on. When I change the name of a device with in zigbee2mqtt interface, i get the following errors and warnings in my HA Core logs. I have posted the screenshots of the errros and my version of HA. For record I am using a brand new SLZB-06 coordinator. I had the same issues with my Sonoff dongle as well. At this point willing to pay someone for helping me fix this. I completely uninstalled both the mqtt broker add on in HA and z2m add on. I’m still getting these warnings and errors . The device works, i just dont know why this happens

[tom_l]

@jakeshbazi

When I change the name of a device

Which device?

Looks like it has a poorly written device converter.

[jakeshbazi]

when you ask which device, what info and from where can i give you to effectively answer it. Its a zigbee plug. This is happening with any device, even my aqara contact sensor. Doesnt matter which device.

[tom_l]

@jakeshbazi

This is happening with any device,

Then it is unlikely to be a converter issue.

When you change the name in Z2M are you making sure you turn this on?

[jakeshbazi]

What is a converter ?

Yes I do checks that box. The issue isn’t that the name doesn’t change in HA. It does. It’s that those errors show up. Also whether I check that box or not , the error show up.

[d921 (dominic)]

Do you have any MQTT triggers that you wrote (for automations or trigger-based template sensors) that listen to the zigbee2mqtt topic?

[jakeshbazi]

I have no written any Mqtt triggers . I don’t have any trigger based template sensors .

To make sure where would I find such things ? @d921

[d921 (dominic)]

Have you imported any blueprints?

The errors seem to suggest that some script, automation, or other thing that can use Jinja templates is assuming that messages from a particular device have those value_json fields.

I could be wrong, but I think errors like that, which reference Jinja syntax (the {{ and }} delimiters) are due to something that you would have yourself created or imported into HA.

[jakeshbazi]

I believe these are what HA came with

[jakeshbazi]

I have created this automation , saw the {{}} in it

alias: Entry Lights - Auto On
triggers:
  - alias: Presence detected
    trigger: state
    entity_id: binary_sensor.entrance_presence_sensor_occupancy
    to: "on"
  - alias: Front door opened
    trigger: state
    entity_id: binary_sensor.front_door_sensor_contact
    to: "on"
  - alias: Rear door opened
    trigger: state
    entity_id: binary_sensor.rear_door_sensor_contact
    to: "on"
conditions:
  - condition: state
    entity_id: binary_sensor.entrance_presence_sensor_occupancy
    state: "on"
  - condition: template
    value_template: |
      {{ states('sensor.entrance_presence_sensor_illuminance') | float(0)
         < states('input_number.entry_lux_threshold') | float(50) }}
  - condition: not
    conditions:
      - condition: state
        entity_id:
          - light.front_entry_light
          - light.rear_entry_light
        state: "on"
actions:
  - action: light.turn_on
    target:
      entity_id:
        - light.front_entry_light
        - light.rear_entry_light
mode: single

[jakeshbazi]

I deleted that part of the automation code, went to rename in z2m and still got the errors

[d921 (dominic)]

I don’t think that code would directly cause those errors.

[jakeshbazi]

Figured as much , and def didn’t . Any other ideas ?

[d921 (dominic)]

Did the errors start happening right when you integrated Z2M with HA, or was there another event they correlated with?

[jakeshbazi]

I only see them when I rename a device

[d921 (dominic)]

If there aren’t other suggestions, and if you aren’t going to cause yourself destruction (hopefully Z2M is new to your system), I’d try removing and re-adding the MQTT integration. And if that doesn’t work, reinstalling Z2M. But especially as to the Z2M part, if you’ve already got a bunch of devices paired, I’d do that as a last resort.

[jakeshbazi]

Ahead of you brother. Fully removed MQTT, and removed z2m . Reinstalled , via add ons. Restarted HA

[reste_narquois (Chris Warne)]

To be clear, are your devices working properly after the rename? Are you seeing these errors continuously, or only once straight after the rename?

I think I’ve seen similar on adding new devices, or more specifically enabling device sensors that are disabled by defaullt, such as link quality. But I just ignore them assuming they are only momentary errors which happen before sensor values are actually populated with data.

If your devices are actually working fine, I wouldn’t worry about it.

[jakeshbazi]

As far as I can tell the devices do work fine. It’s when I rename them in z2m, I see these warnings and errors in the HA core log

[reste_narquois (Chris Warne)]

The I definitely think you’ve got nothing to worry about.