tydom2mqtt icon indicating copy to clipboard operation
tydom2mqtt copied to clipboard

tydom2mqtt 2.4.0 Cover status not saved after ha reboot

Open cob94440 opened this issue 2 years ago • 5 comments

Hello since 2.4.0 each time i have to reload or reboot HA, i need to close open my cover because their state is not good. Some says that they are closed even if they're open, some says they're at 60% open even if all are open.The log seems to tell they're all open.maybe it doesn't update well mqtt.

cob94440 avatar Sep 21 '22 09:09 cob94440

Same issue here: cover state is good only if I control them for HA. If I open them from the physical switch, state is not updated. HA restart, HA reboot, MQTT restart, mqtt2addon restart: none of this fixes the problem.

jerry34ha avatar Oct 01 '22 11:10 jerry34ha

Hello, I think we should probably listen to event from the websocket of Tydom in order to update the values on MQTT... So they may be replicate on Home Assistant.

mopi1402 avatar Oct 03 '22 22:10 mopi1402

On my side a restart of tydom2mqtt fixes the problem.

So I added the following automation:

image

alias: Restart tydom2mqtt on HA startup
description: ""
trigger:
  - platform: homeassistant
    event: start
condition: []
action:
  - service: hassio.addon_restart
    data:
      addon: 6b64d821_tydom2mqtt
mode: single

jrlacharnay avatar Dec 09 '22 23:12 jrlacharnay

Hello, same behavior on my side, as you can see in below history: Shutters were closed in the night, they opened by automation at around 08:25 and their status were good From 8h30 I may have restarted HA and did it several times during the day at 15:13 I decided to restart the tydom2mqtt docker and the status went up again

image

In the docker logfiles I can see tydom2mqtt trying to refresh the status to the Tydom but doesn't update anything back to mqtt / HA image

EDIT 04.01: maybe the attribute "retain" should be set to true: image

As per HA doc in MQTT Cover page: image

ThibaultRT avatar Jan 03 '23 14:01 ThibaultRT

A year later I tried again. I'm now on mqtt2tydom 3.4.2 and I do not experience this problem anymore.

jerry34ha avatar Jan 17 '24 13:01 jerry34ha