There is a new version V6.8-Beta released on 27-01-2021
Bug fixes and improvements. No major impact ie. No re config required.
Did you change speed via MQTT message or via Config portal.
If retain is set to true in the ymal and speed was changed via MQTT then the command will remain forever in the MQTT datadase.
There have been similar issues with blinds randomnly moving usually after a auto restart etc.
On reboot the device subscribs to all topics including cmd, SPEED etc. and acts on last message in MQTT database. And if there is a ghost Retain messages then thats the current one. and action happens.
You need to change retain in ymal to false is blind section, restart home assistant.
Stop MQTT and remove MQTT database, MQTT will create a new one.
(or Delete all retain messages in database). The only retain message should be LWT.
After others and myself did this all running smoother.
Retain messages caused me a lot of late nights trying to strip code appart as I had no problems using OPENHAB until I setup a basic Home assistant server and implement the ymal problems were happening.
retain is not necessary as telementry in now implemented reporting STATE’s etc back to MQTT.
This was not a feature in V2.
Try this let me know outcome.
Also I am not very farmilar with Home Assistant , still getting head around this one.
As I use OPENHAB 3.
I am trying to put a ymal together to cover all functions of V6, such as speed control, tilt, siginal, battery monitor etc.
So if there is a home assistant YMAL’ er that can help would be great.