Awwww yeahhh! Lets get this party started!
This has to be one of the updates I am most excided / yet terrified to update to in a long time.
Going to wait for a .2 or .3 release for sure with how many changes are in it but I am excited about native compact header, the YAML editor ETC!
1 reply
This never stops making us happy… By the time 3 weeks pass testing new stuff in current release… BOOM!! New one is already there to play with… Amazing work guys!! 
Great work! It’s a pleasure of being a user of such an amazing flexible and active community! Thank you all!
Is there a way to launch the ‘quick bar’ on devices that don’t have keyboards (like phones), or is there a plan to add this do you know?
2 replies
You guys keep adding things i didn’t know i wanted, awesome work! looking forward to try this bad boy
You can keep track of it here:
https://github.com/home-assistant/frontend/discussions/7484
Looking forward to the update! Any idea if we’ll see the ability to use broadcast messages over TTS to Google home speakers soon/ever? I use mine for notifications around the house but it’s a bit annoying when the doorbell sounds and disables all audio that was previously playing. Also would be useful to set/reset the volume on broadcasts. Fingers crossed!
2 replies
I saw similar errors, but the update worked.
/me impatiently waits for possibility to update to pop up in supervisor…
(I know it takes time, but I am impatient!)
Why?
It was a very stable beta test.
Thanks to joogs for improving the Panasonic Viera integration. I have power control! Also looking forward to the future release of Viera remote.
If you still find the header height to be too big you can theme the size. header-height: 48px works for me (instead of the default 56px 64px).
For the Aussies, David has cloned the old BoM integration and you can install it as a custom component until Brendan’s replacement (uses the new BoM API) is released: Customising the BOM Weather and lovelace - now in HACS - #564 by DavidFW1960
4 replies
About using TTS for notification, the link to the documentation is https://www.home-assistant.io/integrations/notify.tts/
Ooo I wasn’t aware. Is there a third party custom component that does this easily? The broadcast that is. RE the volume I guess I could use helpers to get the volume before, change it, broadcast then set back but something built in would make that a lot smoother!
The new API version has been released yesterday. It’s working here. I did update the docs however I’m going to tweak them a bit today so it is more coherent and less rushed…
1 reply
I am really excited that work has started for the new Google Nest API.
Cannot wait to ditch HOOBS for the Nest integration.
Again a great update!
only a minor issue… Since this update my Axis camera integration has stopped working! (devices are unavailable)
Try making a new thread for this.
Yeah nope. A new custom component that replaces BOM core and also the FTP custom component I had forked… so just the one custom component needed now.
Well header-height is
No. Not yet. Options are being considered for mobile.
I would also be very grateful if the new header was more configurable, I had it defined in the theme with car_mod theme and now many settings have been misplaced
On my system, Power Wheel Card and RPi Monitor Card no longer worked. However, just doing a Re-Install in HACS solved it
If I’m already using the existing MQTT integration to control Tasmota devices in HA, is there any advantage to switching to this new native Tasmota integration? The only thing that seems to be different is that SetOption19 is set to 0 instead of 1 on the devices.
OMG, the Entities quick search bar is FANTASTIC. Thank you, thank you!!! Been wanting something like that for quite some time.
For Compact Header, I would love a couple more Theme options, in addition to header-height:
Those would free up enough Horizontal space for all my tabs to fit on my phone just perfectly.
2 replies
You can create a different user for your phone, and hide enough tabs for that user to remove the carats.
oh no! can you tell me more about what you’re seeing? that would 100% prevent me from updating.
This is a great update!
Favorite feature so far is the entity picker, very helpful when having multiple of the same ZWave Devices!
Thanks Devs!
thanks for fixing Efergy ! love it love it love it 
Looks like there’s an undocumented breaking change for Daikin units that use an API Key rather than password (BRP072Cxx and Skyfi devices)
I had to delete and recreate them and they’re working again. The breaking change is noted on the PR but didn’t make it into the release notes.
Thanks. I missed the issues section.
If you are looking for an alternative to the BOM platform, please add my repo to HACS, it is using the new BOM API and avoids FTP and webscraping.
Looks like the Xbox gamer score is missing a unit_of_measurement.
Legend! thanks mate 
Quick Bar. It can be launched anywhere in Home Assistant; with the keyboard shortcuts
efor entities andcfor commands. You can switch between the entities and command modes by removing or adding the>at the start of the search input.
This is very nice but I’m not sure if one-letter shortcuts are great. I would think a shortcut like cmd+k (or equivalent on non-Mac platforms) might be more reasonable. It’s pretty standard in various communication apps like Slack or Discord.
I see that it was changed in https://github.com/home-assistant/frontend/pull/7496 but I don’t see why.
Also, single-letter shortcuts seem to be causing issue https://github.com/home-assistant/frontend/issues/7517 which was the kind of thing I was concerned about.
1 reply
Anyone tried to install manually the xbox integration? It gives me error immediatly
1 reply
Use a separate lovelace dashboards for desktop/mobile.
https://www.home-assistant.io/lovelace/dashboards-and-views/
Did you add any xbox entries into your configuration.yaml? You don’t need them.
Yeah, it’s already reported by others as well.
Looks like a nice update, I’m looking forward to trying the Tasmota integration.
I can’t seem to find Tasmota 9 however, I can only find 8.5.1 on the releases page.
The docs for the tasmota integration state that v9.0.0.3 is needed.
2 replies
- Tasmota devices flashed with 9.0.0.3 or later
Same. Not sure what I should change here or just stick to current…
I guess I have one I can play with… so I turn discovery off and then add the Tasmota integration after flashing 9.0.0.3… BRB…
Well that seems pointless.
As soon as I setoption19 0, the Tasmota automatically was discovered in integrations. Add Tasmota and it has the device in Tasmota integration as well as MQTT.
But it doesn’t have the status sensor available with all these goodies:
@pashdown, Something has gotten messed up with the 0.117.0 Blog post above. The details on Breaking Changes and other times have disappeared. I am sure someone will get that fixed.
As for the ISY, the main breaking change is the new support for decimal precision for Variables. If you had a variable being brought from the ISY into HA, and that variable had a precision (as in 2 decimal places) set, it would in the past not display correctly. Before, you had to manually do the precision conversion. Those manual conversions must now be removed so that they are not converted twice.
For example, if the variable was 1.45, before it used to come over as 145, and you had to divide by 100. Now, it will come over as 1.45.
This is a really good one! Doesn’t seem to close if the last dismissed item was done as an individual item though.
This is not the blog, it is the forum post about the blog item. If you go to the blog, they are clickable: https://www.home-assistant.io/blog/2020/10/28/release-117/#breaking-changes
1 reply
I am very excited about the automation and script editor! There was recently a script posted for status led notifications that I deemed “not worth it” to implement but that is no longer the case. 
I was under the impression that adaptive lighting would be included in this release. I tried to check github to get the status of it, but my github navigating ability only got me so far. Does anyone know when/if it is going to join core?
ummmmm
On firefox the arrow on the left doesn’t appear for me, but the heading is clickable and the text appears
Oh, now I see. It pops up “All Changes” at the bottom of the scroll down before comments. Clear as mud.
Having an issue after the update where my camera streams from Synology are not functioning. When I click on the entities in the UI I see the following:
This entity is currently unavailable and is an orphan to a removed, changed or dysfunctional integration or device.
There are no messages in the logs indicating an issue with the synology component at startup or run time.
How do i remove custom-header before upgrading?
EDIT:
Here are tge instructions from Mayker:
https://community.home-assistant.io/t/custom-header/155399/1121?u=mcarty
I can ping the TV even when it’s off… Who manages the integration now? joogs is not on the project anymore I think? Should I just create a new issue?
Not his full name. See: https://github.com/joogps
But you should open an issue in the core repository. https://github.com/home-assistant/core/issues He’s usually pretty quick to respond.
2 replies
Reading the whole blog post helps alot.
And the hamburger menu. Useless when swipe from left works as well…
Have I missed a breaking change in Lovelace were custom types does not work anymore? All my custom cards does not work after the update. Mini-graph, vacuum…
Hello, I have stupidly updated without removing the custom header. Currently, I can’t get the Lovelace screen. Anyway to solve this? I have access to IDE at least…
1 reply
