Why so negative? That sounds so unneeded.
Everything goes in steps. We now gain experience with this part, and expanding slowly to add more features and enable those things.
Making small steps and doing MVPs, keep things moving.
As a matter of fact, this is being worked on.
Tado Integration is completely broken since 0.108. Cannot use the new interface to add component. YAML isn’t working either.
@Filip that is a fairly limited description, which makes it hard to help.
Have you checked our issue tracker for similar reports? If there is none, maybe you could raise an issue? Thanks!
After few more retries I noticed, that configuring Synology DSM a
- platform: synologydsm
host: 192.168.0.21
port: 5001
username: Synology
password: xxxxxxxxx
name: Lewiston NAS
do not work, these entries are ignored - I removed one from my configuration.yaml and still see one unit configured properly and the other one awaiting to be configured, but never succeeding. So the questions are:
As per the breaking change the name key is also no longer valid fysa.
Ah! Got it, I’ll have a go with that and see how I get on. many thanks, I’ll work on this over the weekend!
I have the same issues with D-Link sensors all show unavailable in my zwave network
I think it is time someone thanked @frenck for responding on this forum.
Whether you agree with or like his answers it is nice that we finally have someone form the ‘inner circle’ prepared to respond directly to the masses.
It’s like the patient who gets better just because they have seen a caring doctor; it feels good to know that we at least have a crack in the door to speak to those who are in control.
Thank you, I retract my comment. Very good to hear. The new integrations page is a bit “blotchy” with custom component integrations having no logo.
PS undoubtedly th fact that 500 brand images have been processed is down to mainly you and a few others, congrats.
Sadly many of the new integration icons work only on light themes.
Looks awful.
I wish that some devs would listen and not bluntly think that everything looks awesome. One of the compromises could be something suggested here:
I’ve got the same issue. Raspberry Pi 4 and MQTT covers here. All buttons are greyed out except the stop buttons that do nothing.
Interestingly, I have a few covers grouped and the groups are available and working. And once the group has been activated, the blinds in that group become available and work. A restart of Home Assistant will deactivate the individual MQTT blinds once more.
20-05-01 10:53:05 ERROR (SyncWorker_0) [supervisor.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:0.109.2 -> 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.109.2: No such image: homeassistant/qemux86-64-homeassistant:0.109.2”)
The answer as usual : you ran out of disk space. Remember, during the upgrade there need to be space for 2 HA images.
2.5 - 3 actually. As while the original image is running, the new gets downloaded, which needs to be extracted and installed as well. 
I chimed in on the issue. Seems like it’s fixed and merged 
