@tom_l Thanks for the hint. Float(0) was the solution for unknown devices.
All these moves of configuration from YAML to UI is turning HA into a nightmare to maintain.
Donât know how long it will be worth spending time on 
For most of my integrations, I now canât even change an api-key without having to first delete it and click through the whole stupid âconfiguration wizardâ again.
9 Likes
My sensors and switches fail to load history/logbook on the entity. Hints on db changes are somewhat affecting queries here and there. logbook without entity filter is fast, but on 1 entity, it just keeps loading
a nice âedit configurationâ interface for existing integrations would be awsome in that case.
It is always a bit difficult, if a setup for a specific configuration will change (IP addresses, or just other, similar things that should be configured when the integration will be added)âŚ
Honestly speaking - I think, getting everything within the UI will add value for users that arenât familiar with YAML, and all the manual configuration stepsâŚ
I like the energy compare feature, but I still really would like to be able to separate energy usage according to Area or some other way to split by location.
Some of us have more than one location under control of a single HA instance and all the energy meters get grouped together in the energy dashboard.
Well, Iâm not trying to state that âYAML good, UI badâ.
But we are moving from a well working, changeable and maintainable Yaml based config, to a UI based that is quite the opposite.
The mindset seems to be âset it up once and it will magically work perfectly foreverâ.
Which is a tempting promise for the newcomers. Until reality catches up 
But I agree that an âedit configurationâ would go a long way.
Even the option to âsee current configâ would be helpful, removing some guesswork from the âdelete and re-addâ process
17 Likes
I tried the new configuration for mqtt but it is not working for me at the moment so I left it as it is.
Should the changed configuration work already?
Thanks for the energy dashboard improvement. @frenck It will be great to add as a legend the total expected production of the day nearby the dashed white line. Maybe also the current cumsum of the real production.
yes 
I would like to see those features in the editor. Then likely I will stop using mentioned config page so intensively.
I just updated and changed my MQTT configuration. Almost everything is working except for my 2 fans, if I use the old configuration, both come up nicely:
fan:
- platform: mqtt
device:
identifiers: nrg-itho-achter
model: ITHO Wifi Add-on
name: ITHO-Achter
availability_topic: itho_achter/lwt
unique_id: nrg-itho-achter
name: nrg-itho-achter_fan
state_topic: itho_achter/lwt
state_value_template: '{% if value == ''online'' %}ON{% else %}OFF{% endif %}'
json_attributes_topic: itho_achter/ithostatus
command_topic: itho_achter/cmd/not_used/but_needed_for_HA
percentage_command_topic: itho_achter/cmd
percentage_command_template: '{{ value * 2.54 }}'
percentage_state_topic: itho_achter/state
percentage_value_template: '{{ ((value | int) / 2.54) | round}}'
- platform: mqtt
device:
identifiers: nrg-itho-voor
model: ITHO Wifi Add-on
name: ITHO-Voor
availability_topic: itho_voor/lwt
unique_id: nrg-itho-voor
name: nrg-itho-voor_fan
state_topic: itho_voor/lwt
state_value_template: '{% if value == ''online'' %}ON{% else %}OFF{% endif %}'
json_attributes_topic: itho_voor/ithostatus
command_topic: itho_voor/cmd/not_used/but_needed_for_HA
percentage_command_topic: itho_voor/cmd
percentage_command_template: '{{ value * 2.54 }}'
percentage_state_topic: itho_voor/state
percentage_value_template: '{{ ((value | int) / 2.54) | round}}'
But when I use the new configuration, only the last fan shows up:
mqtt:
fan:
device:
identifiers: nrg-itho-achter
model: ITHO Wifi Add-on
name: ITHO-Achter
availability_topic: itho_achter/lwt
unique_id: nrg-itho-achter
name: nrg-itho-achter_fan
state_topic: itho_achter/lwt
state_value_template: '{% if value == ''online'' %}ON{% else %}OFF{% endif %}'
json_attributes_topic: itho_achter/ithostatus
command_topic: itho_achter/cmd/not_used/but_needed_for_HA
percentage_command_topic: itho_achter/cmd
percentage_command_template: '{{ value * 2.54 }}'
percentage_state_topic: itho_achter/state
percentage_value_template: '{{ ((value | int) / 2.54) | round}}'
fan:
device:
identifiers: nrg-itho-voor
model: ITHO Wifi Add-on
name: ITHO-Voor
availability_topic: itho_voor/lwt
unique_id: nrg-itho-voor
name: nrg-itho-voor_fan
state_topic: itho_voor/lwt
state_value_template: '{% if value == ''online'' %}ON{% else %}OFF{% endif %}'
json_attributes_topic: itho_voor/ithostatus
command_topic: itho_voor/cmd/not_used/but_needed_for_HA
percentage_command_topic: itho_voor/cmd
percentage_command_template: '{{ value * 2.54 }}'
percentage_state_topic: itho_voor/state
percentage_value_template: '{{ ((value | int) / 2.54) | round}}'
Any idea if this is a bug or a configuration issue?
Your config is incorrect. The fans need to be a list, like this:
mqtt:
fan:
- device:
identifiers: nrg-itho-achter
model: ITHO Wifi Add-on
name: ITHO-Achter
availability_topic: itho_achter/lwt
unique_id: nrg-itho-achter
name: nrg-itho-achter_fan
state_topic: itho_achter/lwt
state_value_template: '{% if value == ''online'' %}ON{% else %}OFF{% endif %}'
json_attributes_topic: itho_achter/ithostatus
command_topic: itho_achter/cmd/not_used/but_needed_for_HA
percentage_command_topic: itho_achter/cmd
percentage_command_template: '{{ value * 2.54 }}'
percentage_state_topic: itho_achter/state
percentage_value_template: '{{ ((value | int) / 2.54) | round}}'
- device:
identifiers: nrg-itho-voor
model: ITHO Wifi Add-on
name: ITHO-Voor
availability_topic: itho_voor/lwt
unique_id: nrg-itho-voor
name: nrg-itho-voor_fan
state_topic: itho_voor/lwt
state_value_template: '{% if value == ''online'' %}ON{% else %}OFF{% endif %}'
json_attributes_topic: itho_voor/ithostatus
command_topic: itho_voor/cmd/not_used/but_needed_for_HA
percentage_command_topic: itho_voor/cmd
percentage_command_template: '{{ value * 2.54 }}'
percentage_state_topic: itho_voor/state
percentage_value_template: '{{ ((value | int) / 2.54) | round}}'
2 Likes
Breaking change MQTT, new yaml format for MQTT sensors, binary_sensors, etc. is impossible reload configuration via DEVELOPER TOOLS > YAML > MANUALLY CONFIGURED MQTT ENTITIES like before with platform: mqtt format.
Re: mqtt breaking changes:
Config checks OK but this does not get loaded either by restart or manually configured mqtt entities, what am I missing?
mqtt:
sensor:
- name: 'Test MQTT'
state_topic: 'test/test'
Only if you have not configured it correctly.
What else do you have under mqtt?
Nope,
I placed following:
mqtt:
sensor:
- name: "test_mqtt_sensor"
state_topic: "test_mqtt_sensor_topic"
After reloading, nothing happened, no entity visible, but after restarting HA, entity showed.
Thanks, beginners mistake 
1 Like
Ugh. The documented example is wrong. Use topic: not state_topic:
Iâll submit a fix now.
I think itâs a bug actually. Itâs missing for me too. I seem to remeber Nick saying it will be fixed in 2022.6.1
