Ok, so are you saying in 0.102 it should be fixed or is it 0.100.2? . But I didn’t see this problem previously, so why is it suddenly a problem? It can’t be 0.100.2, because I don’t see anything in the GUI that allows me to retry?
102, it was merged after the cutoff for 101, and you would not see anything in the UI.
This logic happens during the startup, and only if you configured it with the UI (not YAML).
Instead of giving up when you get a communication issue during startup, it will retry to set it up until it can.
@ggravlingen is also adding more logic to handle communication issues here https://github.com/home-assistant/home-assistant/pull/28241
It is configured with the UI. But I don’t see it come back with it, it’s been rebooted 15 mins ago, and all but the gateway is still unavailable, but could that be because I’m using @7even tradfri?
Yes and no, 102 does not exist yet, when it does it will be an updated version of a custom version you now have, so when 102 is released you need to remove the custom variant to start using the official version again.
Ok, great, thankjyou for clearing that up, so it’s still a bit away, if we are on 0.100 and it’s at 0.102 
Correct, it was merged the day after the beta for 101 was cut, my best guess is 102 will arrive in about 5,5 weeks.
As an alternative you can do what you are doing now, by copying the files directly from the dev branch of HA like @7even showed you.
Sure, but I think it will impact the waf (which is already strained because of the WLED under the bed 
) so I’ll stay on the release, and just be a bit carefull with the restarting.
Where can I find the battery status?
Just curious how Home Assistant can ‘talk’ to the Fyrtur blinds - any new hardware needed? I already run Zigbee2Mqtt but that’s a receiver not a transceiver, isn’t it?
I have the IKEA hub, and that is integrated to HA.
Dunno about zigbee2mqtt.
Que? Not sure what you are saying here?
Sorry, I’m being unclear! I’m trying to find out what hardware I would need to communicate with the blind (ie to tell it to go down or up), and if already running Zigbee2Mqtt IS that hardware. I posited that it probably isn’t, because the dongle used with Zigbee2mqtt is receive only rather than transmit?
That is nonsense
Way to go! I’m guessing you’re a teacher in your day job? Because I feel fully in the picture now.
Lol. Lawyer actually. My last answer could have been more supportive sorry.
Take a look at the devices z2m supports. Light bulbs. Smart switches. Shade motors. It sends commands to all of those.
It is likely the fyrtur blinds will work with z2m, but until someone tries, we won’t know.
Anyone got battery status for the blinds to work in .101? In the new release I see the covers in entities as
cover.. I can also see the remotes as sensors, i.e sensor.tradfri_open_close_remote.
As I understood the blids should also show up as sensors so I could monitor the battery level. That doesn’t seems to be the case.
There are currently no attribute/dedicated sensor for blind battery.
Does the tradfri integration now have the stop command for these blinds or only up and down still?