How reliable are the Tasmota'ed Sonoffs in the long run? (Share your experience and/or configuration please)

Codec303 · October 26, 2019, 4:40pm

All my devices are now on 6.7.1 and so far so good, no wifi issues to note of.

However my HA is showing lots of new errors, for example this one:

2019-10-26 04:40:56 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: Garage Light 1 Button4 with state_topic: garage_lights_xx06xx/stat/RESULT

And buttons now appear in the integrations page. I am using HA auto discovery over MQTT, and I have kept all the settings the same, as in flashing new firmware does not overwrite settings.

Anyone else getting this?

francisp · October 26, 2019, 4:55pm

I don’t see any difference with before. No extra errors in the log.

Codec303 · October 26, 2019, 5:00pm

Are you using Auto discovery? I have a feeling that may be the issue.

I’ll try setting SetOption19 Off and On again and see if that fixes things.

francisp · October 26, 2019, 5:10pm

All my tasmota devices are auto discovered.

Crhass · October 26, 2019, 7:58pm

Most of mine are on 6.7.1 now, had a couple that needed power cycling following upgrade before they would respond and 1 that needed reset 5 and then a reflash as it kept dropping WiFi every minute or so. They seem faster in the web interface and are staying connected.

Codec303 · October 26, 2019, 11:12pm

How odd, it looks like it’s a known issue, others are gettings the ‘No matching payload found for entity’ error also here:

and here:

github.com/home-assistant/core

Component mqtt binary_sensor log warning “No matching payload found for entity”

opened 11:40AM - 19 Mar 19 UTC

closed 03:00AM - 09 Sep 19 UTC

wmrato

integration: mqtt stale

**Home Assistant release with the issue:** 0.89.2 **Last working Home Assistant release (if known):** unsure maybe (0.89.0+); Whichever made custom-components require all component files. **Operating environment (Hass.io/Docker/Windows/etc.):** Hass.io **Component/platform:** https://www.home-assistant.io/components/binary_sensor.mqtt/ **Description of problem:** When using multiple Sonoff_RF components, Error log outputs multiple "[homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: " - Used to add Custom_component for mqtt/binary_sensor.py which would disable output. -- Now since 8.9.0 having to add all mqtt files via Configurator IS UN-WORKABLE. -- also monitoring release updates to all mqtt component files against custom-components IS UN-WORKABLE. - Hass.io runs slow when issue outputs to log. - Hass.io takes 15-35 minutes to reboot. - MariadB is locking up due to too many of these errors recorded. -- Snapshot takes 90 mins, as MariaDB takes ages. -- this is eating up my SD Card's life expectancy. -- Don't like losing my house data. Please revert pull request (https://github.com/home-assistant/home-assistant/pull/11836) or update code from components/mqtt/binary_sensor.py #Line: 147 To comment out LOGGER warning Example of change: ``` @callback def state_message_received(_topic, payload, _qos): """Handle a new received MQTT state message.""" value_template = self._config.get(CONF_VALUE_TEMPLATE) if value_template is not None: payload = value_template.async_render_with_possible_json_value( payload, variables={'entity_id': self.entity_id}) if payload == self._config.get(CONF_PAYLOAD_ON): self._state = True elif payload == self._config.get(CONF_PAYLOAD_OFF): self._state = False else: # Payload is not for this entity # _LOGGER.warning('No matching payload found' # ' for entity: %s with state_topic: %s', # self._config.get(CONF_NAME), # self._config.get(CONF_STATE_TOPIC)) return ``` Example Error log (1 entry below, but logs this 19 times): ``` 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir a hall with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir b bathroom with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: kitchen smoke with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: livingroom window r with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: kitchen window with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: bedroom window with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: livingroom window l with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: front door with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: kitchen fridge door with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 ab with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 c with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 cd with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 d with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 a with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 b with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir e bedroom with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir d livingroom with state_topic: tele/sonoff-RF/RESULT 2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir c kitchen with state_topic: tele/sonoff-RF/RESULT ``` **Problem-relevant `configuration.yaml` entries and (fill out even if it seems unimportant):** ``` binary_sensor: # Door - platform: mqtt name: 'front door' payload_on: 'SECRET_RF_CODE_ON' payload_off: 'SECRET_RF_CODE_OFF' device_class: door qos: 1 state_topic: 'tele/sonoff-RF/RESULT' value_template: "{{ value_json.RfReceived.Data }}" - platform: mqtt name: kitchen fridge door payload_on: 'SECRET_RF_CODE_ON' payload_off: 'SECRET_RF_CODE_OFF' device_class: door qos: 1 state_topic: 'tele/sonoff-RF/RESULT' value_template: "{{ value_json.RfReceived.Data }}" # Window - platform: mqtt name: bedroom window payload_on: 'SECRET_RF_CODE_ON' payload_off: 'SECRET_RF_CODE_OFF' device_class: window qos: 1 state_topic: 'tele/sonoff-RF/RESULT' value_template: "{{ value_json.RfReceived.Data }}" - platform: mqtt name: livingroom window l payload_on: 'SECRET_RF_CODE_ON' payload_off: 'SECRET_RF_CODE_OFF' device_class: window qos: 1 state_topic: 'tele/sonoff-RF/RESULT' value_template: "{{ value_json.RfReceived.Data }}" - platform: mqtt name: livingroom window r payload_on: 'SECRET_RF_CODE_ON' payload_off: 'SECRET_RF_CODE_OFF' device_class: window qos: 1 state_topic: 'tele/sonoff-RF/RESULT' value_template: "{{ value_json.RfReceived.Data }}" - platform: mqtt name: kitchen window payload_on: 'SECRET_RF_CODE_ON' payload_off: 'SECRET_RF_CODE_OFF' device_class: window qos: 1 state_topic: 'tele/sonoff-RF/RESULT' value_template: "{{ value_json.RfReceived.Data }}" ``` **Traceback (if applicable):** ``` ``` **Additional information:** This is related to this change https://github.com/home-assistant/home-assistant/pull/11836 plus referenced in https://community.home-assistant.io/t/mqtt-py-log-warning-no-matching-payload-found-for-entity/42995/5 I really need this fixed, please let me know what I can do to fix this, am I required to push a commit to fix / add configuration option to allow for Sonoff_RF or other devices acting on different codes.

So I’ll have to see why they have only started to appear in v6.7.

SteveDinn · October 26, 2019, 11:27pm

I copied the code for the MQTT binary_sensor and am using a custom component for this now just to eliminate that ridiculous error.

DavidFW1960 · October 27, 2019, 1:04am

I flash my own bin (around 450kb in size so don’t need minimal)

DavidFW1960 · October 27, 2019, 1:08am

Yes I am. seems a binary_sensor is now created in the integration… you can probably disable it. I have not tried.

OK I’m disabling them here and will restart. That should fix it as the entity is disappearing

EDIT: I am not getting the errors now after disabling the binary_sensor.*_btn’s It MAY be that this function is only in HA 0.101.0 (currently running b2 of that)

ALSO note core pre-2.6 is the ONLY supported core now.

Codec303 · October 27, 2019, 2:32am

Glad to know I’m not the only one with the errors.

I should have said earlier that I’m running HA v0.100.3, and the binary sensor buttons only appeared after flashing Tasmota v6.7, with Tasmota v6.6 there is no binary sensor button.

I don’t think this is a HA change, more a Tasmota change that is causing the binary sensor buttons to appear. I think it’s probably a HA bug that is throwing the errors however.

Thanks for the tip about disabling the entities, I’ve tried it on a few devices and so far so good, no errors from that device then HA is restarted.

Also I’ve used core pre-2.6 and so far so good, my binaries are a little larger now, but using the minimal firmware I was able to update OK.

galv83 · October 27, 2019, 2:46am

I have 8 gen1 Sonoff Basics, 3 S20’s & 3 TH16’s. running for about 2 years & (touch wood) for the most part no issues.

there was one issue with a Sonoff basic, it thought the relay had failed, trying to contolr it via HA didn’t make a difference & the same with the push button. so I bought another (ready to replace it) - in the process, I turned the device off the at the wall. Tunred it back on a day or so later & its worked fine ever since.

When I restart my WiFi, there is one in a hard to reach place that need a bit of help to find the WiFi signal. but the than that, they have been rock-solid for the past 24 months.

francisp · October 27, 2019, 5:14am

My Qia is configured as a Tuya MCU Module, no binary button, but the Sonoff Basic I flashed with 6.7.1 does indeed show a binary button.

DavidFW1960 · October 27, 2019, 5:30am

Yeah my nodemcu same thing. Only my Sonoff S22’s and SV’s have it.

Philip_Embleton · October 27, 2019, 8:03am

I have 3 MagicHome / Arilux RGB controllers.

I tried flashing 6.7.1 but having constant wifi disconnects.

I’ve tried doind reset 5 but no luck.

Philip_Embleton · October 27, 2019, 10:03am

In case anyone has the same issue as me above I managed to fix it.

Setting option “sleep 0” in the console has fixed it.

klogg · October 28, 2019, 12:57pm

I think I can confirm this as I have a mix of v6.6 and v6.7. Only those on v6.7 have the binary sensor button.

Jokerigno · October 29, 2019, 10:33pm

I have 5 r2 and 12 shelly 1. After a reboot 1 r2 stopped to be reacheble. I had to hard reset using phisical button to restore connection. Since then it instable. I tried reset 5 and upgrating to 6.7.1 but nothing happens.

Moreover starting from few days some other device become unreachable. Those are shellies and are quite difficult to reach so I don’t know what to do because previous mentioned action didn’t work. Any ideas?

Fury1SOG · October 30, 2019, 12:11am

Perhaps interference on the Wifi channel?

Recently, I tracked down some Sonoff wifi problems to an USB-C hub that I purchased for use with a Mac that was nearby the wifi router. It seems that USB-C can cause interference in the 2.4GHz frequency. The problem went away after replacing the hub.

jik849 · October 30, 2019, 8:58am

You can use a external watchdog timer to increase reliability

Philip_Embleton · October 30, 2019, 9:22am

Not one disconnect on my devices for a few days now.

I do have good WiFi coverage via a TP-Link Deco mesh which no doubt helps.