state_topic: is working for me.
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.
I don’t don’t think so. I think it may be a documentation error. state_topic: is working for me.
Also working fine for me too with state_topic. I’m however missing the reload option. But I think that’s a general bug
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
Oh, hang on, topic: is only for the availability section. The docs are ok.
1 Like
Ah ha
topic works, state_topic doesn’t
Wait what?
Really?
It shouldn’t.
topic: is only for availability configuration.
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'
For me, state_topic works.
Everything works except reloading from YAML panel. Just restarting HA works.
Like with IgorZg, state_topic is working just fine for my mqtt selects, switches and sensors. Only groups stopped working
I wouldn’t use topic: for the sensor value. It’s not documented and may break.
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
Reload will be in the future via reload of mqtt-integration and not in developer tools anymore. But is not implemented yet.
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.
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.
Because you have the field sensor twice, remove the second one.
Thanks
Shame it doesn’t fail config check…
Things like that have never shown in configuration check because it’s valid Yaml.
I’m also confused. The release blog states, API becomes local but links to an integration page with a cloud API. Please people a more clear explanation helps. I would love to use a local API instead of a cloud API, where to find the info about it?