Frontend status feedback for cover component?

Configuration
21

OK I worked on this again this morning and have somehow fixed the issues.

After I bought my config files up to speed, I basically upgraded from 0.26.1 straight to 0.31.1 on my main debian server and had the issues above. Now that I had config files that worked from 0.27.0 onwards (because mine were stuck at 0.26 and 0.27 introduced some big changes in covers and other components along the way), I down graded back to 0.27.0 started to work my way up to see what happens without touching config files, just upgrading hass versions. 0.28.0 fixed the buttons on covers issue and displayed the status of the door properly and the sliders displayed properly as a bonus, but then covers broke again at 0.29.0 up to 0.31. BTW I only upgraded to major versions, not the hotfixes. At 0.31.0 I got worried but decided to upgrade to 0.31.1 and much to my surprise everything worked normal. Does this sound weird, cause it is. Anyway it’s all working but it took a long time to get there. Maybe this may provide some clues to someone more knowledgeable than me.

Anyway my Synology server is a test environment. I will stage things there before I upgrade from now on. I rely on HA so much. That’s why I was stuck at 0.26.1. It was stable and I just didn’t have the time to upgrade (and troubleshoot) even though there were some great new features on higher versions. Now I can keep going :slight_smile:

From main system. All OK

22

I’m unclear on the resolution on this problem. I have the same issue as the OP (aimc). I only have those displays on the front panel, and no indication of whether the garage door (cover) is open or closed.
The system does know that the door is open/closed as in the Logbook, it properly indicates when the door sensor indicates open/closed via mqtt.
I did upgrade to 0.31 (was previously on 0.28), but still have the same issue.

Appreciate all input!

24

To reply to my prior comment, the front end is now responding properly for me. I believe my prior issue was related to improper operation of the mqtt service.
I now see that the icon changes based on the sensor state, and if the door is closed, only the ‘open’ arrow is active (and vice versa if the door is open).