There was a related thread about this issue that I’ve since seen more persistently with my own install of Sonoff (Tasmota flashed) units.
EDIT: just saw you posted in that thread as well.
I’ve been digging into it a bit more tonight and it looks like it’s to do with how the homeassistant binding handles the forced update value.
If you have a look at the MQTT home assistant config data using MQTT explorer or similar, it looks like Tasmota flags frc_upd as true for the switch state sensor - which the openhab home assistant binding doesn’t support.
ie: MQTT /homeassistant/sensor/_status/config
{
“name”:“Dining Room Light status”,
“stat_t”:“~HASS_STATE”,
“avty_t”:“~LWT”,
“frc_upd”:true,
“pl_avail”:“Online”,
“pl_not_avail”:“Offline”,
“json_attributes_topic”:“~HASS_STATE”,
“unit_of_meas”:" “,
“val_tpl”:”{{value_json[‘RSSI’]}}“,
“ic”:“mdi:information-outline”,
“uniq_id”:”_status",
“device”:{“identifiers”:[“”],
“connections”:[[“mac”,]],
“name”:“Dining Room Light”,
“model”:“Sonoff Mini”,
“sw_version”:“8.1.0(tasmota)”,
“manufacturer”:“Tasmota”},
“~”:“tasmota-/tele/”
}
Tasmota source is setting it to true - lines 45 & 67.
OpenHAB HomeAssistant Binding - ComponentSensor class:
Line 50
if (channelConfiguration.force_update) {
throw new UnsupportedOperationException(“Component:Sensor does not support forced updates”);
}
I believe I’ve seen some comments that the old v6 something release of tasmota didn’t have the issue and it was probably prior to them changing it to forced_update = true, but I suspect the OH homeassistant binding probably needs updating.