Not running Tasmota?
Nice! Yeah I guess this is just a quirk of Tasmota.
Iām not so sure about that. In particular if you happen to think that autodiscover is a convenient way to find all your devices and then you turn it off.
Youāre David, it sounds more like turning off auto-discovery caused the confusion.
Statements to the the effect of āyou never needā some aspect of a system remind me of BIll Gatesā in/famous "ā640K is more memory than anyone will ever need on a computer,ā - which he may not have actually said.
I donāt know HA well enough to understand the reasons why the change was made. I asked in Discord and no has anwered me. (They owe me nothing - I get it.) I do know that large organizations that plan for wide ranges of use of MQTT donāt flip fields in MQTT this way.
An interesting read if you care about this stuff might be: āhttps://d1.awsstatic.com/whitepapers/Designing_MQTT_Topics_for_AWS_IoT_Core.pdfā
I think tasmota is in cahoots to some extent here too. I noticed that the Full Topic field has an config option to switch the order of the fields in the 6.4.1 release. Thatās why Iām personally interested in this because I went through exactly what CancunManny did as I switched on auto-discover in some new devices that I deployed and noticed that the fields were the reverse of what I was seeing for my initial non-autodisovered devices.
I assume that someone was trying to fix a real problem, but like many open source things they fixed their problem and didnāt consider the side effects. Itās a hobby not a job for most.
It was pointed out on the Tasmota Wiki that there were changes related to home assistant. I think thereās collaboration between HA and Tasmota - we donāt know why they switched it but I canāt imagine they enjoy the heat of breaking changes like this so I think there must be a good reasonā¦