The old HA discovery method is removed from Tasmota. It was to unflexibel, had errors and was too resource hungry. We decided to implement how it is done now. HA uses this plugin GitHub - emontnemery/hatasmota to “translate” for HA needs.
Sorry to hear there is no interest from OH to support the millions of Tasmota users to make the use of OH easy for them.
It’s not that we aren’t interested–it’s that someone has to volunteer to do the work. Would you perhaps be interested in contributing to OH? I can’t imagine that anyone would be better suited since you’re on the Tasmota dev team.
I’m not being sarcastic. We really would appreciate it and I’m sure many people would take advantage of Tasmota auto-discovery. I’d certainly be happy to test it.
@Johann_Obermeier: is there any clear documentation on the structure of Tasmota’s discovery topics? Looking through both the Tasmota and hatasmota source I wasn’t able to find anything, and the code isn’t exactly easy to follow.
Heh, famous last words. I said the same thing, several years ago. Until I was frustrated enough to want to fix something I depended on in openHAB. I also have no desire to learn JavaScript, TypeScript, or Python, and yet I’ve contributed to several projects in those languages :).
It seems there are a few more payload objects in the discovery message depending on Tasmota settings, most importantly shutter configuration and buttons. I have a shutters-enabled device in a remote location, I’ll try to gain access to it to update the schema with whatever I can find.