core: tasmota beta - sonoff 4chpro unavailable

The problem

After upgrading my Sonoff 4CHProR2 to Tasmota 9.0.0.2 and switch Setoption19 0 tried to use the new tasmota integration without success. The integration includes four switches and one deactivated status binary sensor for the new device but they are all unavailable. The log doesn’t show any warnings or errors related to that. I have deleted the integration and added it again (discovery topic: tasmota/discovery) My fulltopic follows not the tasmota default. Its turned around %topic%/%prefix%/ The hostname and the %topic% is default

I read the currently unpublished documentation: Perhaps it should be stated that setoption 19 should be disabled and the firmware should be newer that 9.0.x.x… (if not updated meanwhile)

Before i have used the existing method with setoption19 1 and MQTT discovery - it worked (without the tasmota integration).

Environment

• Home Assistant Core release with the issue: 0.118.0.dev20201025
• Last working Home Assistant Core release (if known): -
• Operating environment (OS/Container/Supervised/Core): HA Container - Docker on RASPI 4
• Integration causing this issue: tasmota
• Link to integration documentation on our website: - currently not visible / not published so far

Problem-relevant configuration.yaml

automatic discovery through integration tasmota used

Traceback/Error logs

MQTT:
tasmota/discovery/<mac>/config
{"ip":"10.10.x.y","dn":"Sonoff4CHProR2","fn":["Tasmota","Tasmota2","Tasmota3","Tasmota4",null,null,null,null],"hn":"tasmota_xxxxxx-zzzz","mac":"xxxxxx","md":"Sonoff 4CH Pro","ty":0,"ofln":"Offline","onln":"Online","state":["OFF","ON","TOGGLE","HOLD"],"sw":"9.0.0.2","t":"tasmota_xxxxxx","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,1,1,1,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"btn":[0,0,0,0],"so":{"11":0,"13":0,"17":1,"20":0,"30":0,"68":0,"73":0,"80":0,"82":0},"lk":1,"lt_st":0,"ver":1}

tasmota/discovery/yyyyyyxxxxxx/sensors
{"sn":{"Time":"2020-10-25T12:45:58"},"ver":1}

tasmota_xxxxxx/tele/LWT
Online

tasmota_xxxxxx/tele/STATE
{"Time":"2020-10-25T13:25:01","Uptime":"0T00:39:27","UptimeSec":2367,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"OFF","POWER2":"ON","POWER3":"ON","POWER4":"ON","Wifi":{"AP":1,"SSId":"ssid","BSSId":"xx:xx:xx:xx:xx:xx","Channel":1,"RSSI":100,"Signal":-50,"LinkCount":1,"Downtime":"0T00:00:21"}}

HA Log: nothing!

Additional information

Note: This is not relevant for the current problem! Before upgrading to 9.0.0.2 (running 8.5.1) and disabling setoption19 (to 0) i sometimes got an error message from this integration within HA. It seems that the integration doesn’t filter (block) discoveries with an version less than 9.x.x.x. The integration doesn’t show any device…:

2020-10-25 12:05:08 ERROR (MainThread) [homeassistant.util.logging] Exception in discovery_message_received when handling msg on 'tasmota/discovery/<mac>/config': '{"ip":"10.10.x.y","dn":"Sonoff4CHProR2","fn":["Tasmota","Tasmota2","Tasmota3","Tasmota4",null,null,null,null],"hn":"tasmota_xxxxxx-xxxx","mac":"<mac>","md":"Sonoff 4CH Pro","ofln":"Offline","onln":"Online","state":["OFF","ON","TOGGLE","HOLD"],"sw":"8.5.1","t":"tasmota_xxxxxx","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,1,1,1,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"btn":[0,0,0,0],"so":{"11":0,"13":0,"17":1,"20":0,"30":0,"68":0,"73":0,"80":0},"lk":1,"lt_st":0,"ver":1}'
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/hatasmota/discovery.py", line 158, in discovery_message_received
payload = TasmotaDiscoveryMsg(json.loads(payload))
File "/usr/local/lib/python3.8/site-packages/hatasmota/discovery.py", line 117, in __init__
config = TASMOTA_DISCOVERY_SCHEMA(config)
File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
return self._compiled([], data)
File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
return base_validate(path, iteritems(data), out)
File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: required key not provided @ data['so']['82']