add tasmota blueprint

[SoloJan]

This is a generic blue print to connect with any Tasmota device. Tasmota is very generic firmware, and is used in relays, sensors, powermeters, ledstrips and even MP3 players, and we also use it to control the water purifier. I was therefore not sure in which category to put it.

I tested it on a couple of our Tasmota devices.

I read the contributting_guidelines, and I think that I comply to them, but its my first contribution. So feel free to comment

[nkrasko]

Please find logo here!

[nikitug]

Jan, thank you for the contribution! Also feel free to add Tasmota as a new vendor into vendors.yml.

[SoloJan]

I also added a device in the device.yml i put the status to ready_for_testing, i did test the behavior of the blueprint on several physical devices, but was not sure if you require aditional testing by a third party

[nikitug]

@SoloJan, we have the following verification levels:

Name	Description
verified	Tested on a real device and quality-checked by Enapter or certified partners.
community_tested	Tested by a community member on a real device. Proof of performance was provided to Enapter (screenshots, temporary site access).
ready_for_testing	This blueprint has yet to be tested. It may not work as expected.

Please upload the latest version of the blueprint to the real device in Enapter Cloud and send us the link to developers@enapter.com, we will confirm it's tested.

Feel free to change to community_tested level. I think it's good to merge 👍

[SoloJan]

@nikitug sorry for late reply had some other things on my mind this week. Our live setup is at a customer location, we do use some tasmota devices for example to switch on our waterpurifier when we start the electrolyser but we use a slightly different setup, and I dont want to modify them at this stage just to get this generic blue print to a different state. I can upload it, and test it and then switch back to the old settings, but I dont want to leave it out there in a way that you can check it with a link at a time convenient for you.

I'd say we leave it to ready_for_testing and I might do a nother pull request once I get arround testing it. And feel free to merge it, I dont have the rights to do so