2022.6: Gaining new insights!

Blog
126

Quick questions regarding groups.

In my switch file (all mqtt switches) I had included a group. After I transferred all my mqtt-entities to the file mqtt.yaml Homeassistant can no longer find that group.
I tried putting it in the switch file, I tried putting it in the mqtt file and even in the template file but nothing works.

From what I understand in the documentation I cannot just put it unter the tag group.
Any advice here?

127

Hmm I hadn’t seen that. I’ve had/have state_topic since forever. Is this a change part of the migration to the mqtt key?

128

state_topic: is working for me.

129

Well, it looks to me buggy also. I have lot of manually configured binary sensors and sensors, so I will wait a little bit before I start to change my configuration.

130

I don’t don’t think so. I think it may be a documentation error. state_topic: is working for me.

131

Also working fine for me too with state_topic. I’m however missing the reload option. But I think that’s a general bug

132

But this reason is only the half way.

The reason was in my point of yiew, that the check and reloads has been moved last release from system to developer tools.
→ complains from the user, that a. it is at a new position and b. for those, who are using this (and not other parts of developer tools that often), thay a. have to click once more to go to another tab and b. habe to wait until first tab is loaded.

Only to mitigate this, now the recently new page has been moved to first place.

No benefit for those, who want to use developer tools for let’s say 90% state checks and manipulations as before.

And yes, it is remembered, but only per browser session, but not for the user. This is, what I still would propose. Then everyone is happy/happier than currently.

Didn’t even survive a page refresh or new tab.

1 Like
133

Oh, hang on, topic: is only for the availability section. The docs are ok.

1 Like
134

Ah ha
topic works, state_topic doesn’t

135

Wait what?

Really?

It shouldn’t.

topic: is only for availability configuration.

136

Yes, topic OK, state_topic is ignored
[edit]
Is it possible that I have both

mqtt:
  sensor:
    - name: 'Test MQTT'
      topic: 'test/test'

and

sensor:
  - platform: mqtt
    name: 'Enviro PM1.0'
    state_topic: 'enviro/particulate/1.0'
137

For me, state_topic works.
Everything works except reloading from YAML panel. Just restarting HA works.

138

Like with IgorZg, state_topic is working just fine for my mqtt selects, switches and sensors. Only groups stopped working

139

I wouldn’t use topic: for the sensor value. It’s not documented and may break.

Screenshot 2022-06-02 at 19-22-43 MQTT Sensor

Screenshot 2022-06-02 at 19-22-27 MQTT Sensor

140

Oh man…
state_topic is now working (with a restart NOT with a reload manual mqtt entities)
[edit]
I don’t know what’s going on now

mqtt:
  sensor:
    - name: 'Test MQTT1'
      state_topic: 'test/test'
  sensor:
    - name: 'Enviro PM1.0'
      state_topic: 'enviro/particulate/1.0'
      unit_of_measurement: 'Îźg/mÂł'
      value_template: '{{ value | round(1) }}'
      expire_after: 600
      device_class: PM1

Test MQTT1 does NOT show but Enviro PM1.0 does.

I’m leaving it as it was for now

141

Reload will be in the future via reload of mqtt-integration and not in developer tools anymore. But is not implemented yet.

142

Whole story about manually configured MQTT sensors is step back from my point of view.
Just al little bit different yaml format, but loosed ability to reload without restart.

143

So what do we do if init is automatically being set in the entrypoint on portainer?
What ever I do to remove it, when I create the container it will be there.

144

Because you have the field sensor twice, remove the second one.

145

Thanks
Shame it doesn’t fail config check…