New MQTT config (json_attributes_topic)

Configuration
4

But, I don’t know how to call to a list of attributes… In my case, this is my actual config:

  - platform: mqtt
    name: Cell BT
    state_topic: "homeassistant/sensor/android_bluetooth/state"
    value_template: "{{ value_json.enabled }}"
    json_attributes:
      - name
      - mac
      - discovered_devices

So, I think I should have this config:

  - platform: mqtt
    name: Cell BT
    state_topic: "homeassistant/sensor/android_bluetooth/state"
    value_template: "{{ value_json.enabled }}"
    json_attributes_topic: "homeassistant/sensor/android_bluetooth/discovered_devices"

But this config doesn’t work…

5

Does

json_attributes_topic: "homeassistant/sensor/android_bluetooth/state"

work?

6

I had the same thing following the .85 upgrade. The above change worked for me, but now I get all the states in the json string, rather than simply the one specified in the value_template. Not an issue, just shows them all (~16).

7

I have the same issue.

Coming from here:

To get the attributes I simple copied the state_topic to the json_attributes_topic.
But as mentioned before this will show all of the attributes, which is not as smart as before (picking the right ones).

8

I wonder if an issue should be created to keep also the old configuration style because it is smarter for setups where you cannot change MQTT message payloads.

1 Like
9

Found this in another thread

10

I’m receviing the configuration variable "json_attributes" is deprecated, replace with "json_attributes_topic" error in my logs but for the life of me I can’t find any references to json_attributes anywhere in my config files.

Is there something hidden I should be looking at?

I used zigbee2mqtt amongst other things such as MQTT sensor templates. Below is a snippet from one of my MQTT sensors, would that cause any issues?

  - platform: mqtt
    state_topic: "zigbee2mqtt/Cube"
    name: "Cube Battery"
    unit_of_measurement: "%"
    value_template: '{{ value_json.battery }}'
    icon: mdi:battery-bluetooth-variant
11

Do you have any devices created by discovery?

12

Excuse my ignorance but how would I tell? And if I did surely they would be created as part of the core HA functionality not effected by this issue?

13

I have the same issue as apt… I use zigbee2mqtt. I originally had it all set up pairing devices through that component and then managed to break it all. All the data files were still in tact but I was trying to rebuild the MQTT integration (under config). I ended up deleting it and Hassio ‘auto discovered’ my old config and it started working again. Below is the integration (apt: it is under configuration -> integrations).

59%20am

Interestingly, I do have the same number of json_attributes errors as I have sensors under that integration, but I can’t find the text “json_attributes” anywhere in my files either.

Do you know where the files may have been stored? I checked the /share/zigbee2mqtt files.

Thanks,
Matthew

1 Like
14

This appears fixed by today’s zigbee2mqtt component update. Thanks for the update guys.

1 Like
15

That seems to have fixed it for me too plus my random restarts every few hours. :slight_smile:

16

Can someone, post your Before and After code? I still don’t get it…

17

@mattat My “json_attributes” was hidden in a package…

18

Have you updated the zigbee2mqtt component under the Hass.io menu? It should be version 1.1.1, which made the error go away for me. I didn’t have to change any of my code.

19

Having manually configured all my YAML to use to new json_attributes_topic I am still getting warnings in the HA log about /mqtt/sensor.py and using json_attributes

I am running 1.1.1 and 0.87.0

Someone suggested maybe auto discovered devices? I have a bunch I don’t use that I manually added and HA added as well (I’d love to get rid of them)

20

@stratplayer I was having these error messages as well, turned out I had retained messages from old devices in my mqtt database. Check this out: https://github.com/Koenkk/zigbee2mqtt/issues/713
It mentions hass.io but that’s besides the issue. I have a separate mqtt container so i just removed my mosquitto.db. If you’re using the HA integrated mqtt you should see if you can clear the retained messages as mentioned in the url i mentioned.
Good luck.

edit:
I think I had json_attributes in “homeassistant/light/+/+/config” and “homeassistant/sensor/+/+/config”. be sure to check out both.

21

Nice one!

Seems like I have about a million retained messages from my sensors etc… Good spot on this thanks

22

Got rid of all but 1 now… oddly not showing in MQTT.fx under Sensor even though the message states its a sensor

23

Hmm, odd indeed.
There’s a couple more things you could try.

  1. Perhaps there’s a package still using json_attributes. I was using the package battery_alert.yaml which had a few json_attributes references. FYI this package isn’t needed anymore because recent versions of zigbee2mqtt add a battery component for each sensor.
  2. I was having issues with mqtt-fx and mqtt-spy, so i installed mqtt snooper on my android phone. I subscribed to homeassistant/# which showed all messages. Cool thing about this app is you can use filters, so I filtered on “json_attributes” (including quotes so it doesn’t include json_attributes_topic).
  3. I don’t know if a) you use the integrated HA mqtt and b) the integrated HA mqtt stores mqtt messages into homeassistant.db, but if you don’t care about your sensors’ history, you could stop HA, remove (or rename) homeassistant.db and start HA. The database will be regenerated and you’ll only have lost your history.
    Hope this helps. Good luck!
1 Like