Thanks. Can you replace the one on the panel with this one?
Just posting this in case it helps some others. I found out my HACS integration failed after the 0.108.0 upgrade due to some stray integration files in the custom_components directory. Moved them to their proper place, and everything runs fine.
With the new ZigBee group entity will it know those light have been turned on for example lights that don’t support attribute reporting before if turned on in group would turn the lights on but the UI would so them all off still.
Can it not be made to know it turned on those say 3 lights to then turn them on in the UI?
Hello, I had the same problem, I updated to 108 and hacs broke along with many custom components, I also could not uninstall the integration or appear in the menu of new integrations, I had a backup of 107.7 and it was still broken, luckily, I had a copy of 106.6 and it returned to normal, finally I updated it again to 108 and everything working
Hi,
How can i assign entities to a new Area Configuration ?
Thanks in advance
For everyone having troubles with HACS and/or custom components:
I don’t know why or when this happened but many files from /config/custom_components/hacs got copied to /config/custom_components, which resulted in many very strange error messages and as well as HACS & some components not working at all. Simply check for duplicates and delete them in /config/custom_components and then restart HA.
2 Likes
Yes… Currently it requires Home Assistant to be running on port 443; unless, you’re using Home Assistant Cloud with Remote UI/Control.
The Camera Capability checks your base_url to make sure Home Assistant is configured with HTTPS on port 443. Your base_url must also match the URL that is used on your SSL/TLS certificate.
For this particular function, your ISP should not be involved. The echo device makes the request from your LAN to the camera stream URL. As long as domain in that URL resolves to your HA instance either local IP of HA or external IP of your router (using Hairpin-NAT), the request should not leave your network.
Also, If you’re using a custom Alexa skill with your own Lambda function you should be sending requests externally to Home Assistant on port 443 already; assuming you’re port forwarding from 443 to 8123 in your router.
If you’re using Home Assistant Cloud, you will need to enable Remote Control/Remote UI and the connection will be made using that URL.
It is also possible to use a reverse-proxy in front of HA, but HA still needs to run on port 443 to pass the check, with a base_url that resolves to the reverse proxy.
Let me know if your need any more help, helping you helps me improve the documentation and the implementation.
Oh that makes a ton more sense, and yeah if that’s in the documentation that would help a ton. I dont use remote ui but can toggle it to test. Cheers mate!
i had the same issue with HACS not working, but after another reboot, everything worked.
Another fantastic job by the Home Assistant “A” TEAM! Keep the good stuff coming and everyone don’t forget to support them through Nabu Casa Subscription!!!
1 Like
Wow love the icons in the integration section now. I really liked the Roku integration better than the old way but only suggestion would be to have them all under one integration section vise having to input each one and have separate entries, just a thought.
Totally agree, the icons make everything look really professional.
Nexia integration keeps throwing an unexpected error. Can’t find away around it even editing the configuration.yaml file manually.
I nominate for most incomplete post of this release thread. Please see How to help us help you - or How to ask a good question
Thanks for the update! I’m excited about all the ZHA improvements in the changelog; I’ve got something to experiment with this upcoming weekend 
Upgrade on Hassio went smooth as usual; HACS and all it’s plugins and integrations worked just fine for me. Everything was up to date before this update, though. Not sure if that is the cause of some of the problems others are having.
Hello,
I’ve just used the “Check Home Assitant Configuration” tool to check the new Home Assistant version.
I get the following reported error :
"Component error: sonoff - No module named ‘zeroconf’"
I checked that default_config is in my configuration file (for zeroconf integration).
The current system is Home Assistant 107.4 on HassOS.
If I remove my sonoff configuration lines, I pass the check without error.
Here are the config lines for my sonoff devices (S26 Smart Socket). The smartplug works fine on HA 107.4
sonoff:
devices:
1000b8XXXX:
devicekey: 6c34XXXX-YYYY-ZZZZ-3b95cdUUUUUU
1000b1YYYY:
devicekey: 593fXXXX-YYYY-ZZZZ-8284f0UUUUUU
Thank you.
thanks, I was looking for an example how to use the new Hue device triggers. How did you find the device id for your specific remote?
myStrom WiFi-Switches Update:
All automations calling myStrom Switch Entites are working just fine.
Strangely enough, after a myStrom entity was called by a script or an automation, this paticular entity is visible in Home Assistant again!
Apparently myStrom Entities are available somehow in Home Assistant, but not visible to Lovelace.
1 Like
20-04-09 08:42:10 ERROR (SyncWorker_0) [supervisor.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:0.108.0 -> 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.108.0: No such image: homeassistant/qemux86-64-homeassistant:0.108.0”).
Same here