The syntax for include and exclude is different in auto entities so you’ll need some adjustment to your filters. But all options history supports are supported by this card. Then drop the card in a new dashboard in single-card panel mode and you’ve got your history dashboard back.
The only thing I’m not sure about is whether the history graph card works like the history panel and automatically excludes entities you listed which were excluded from recorder. If not then that would be a bummer since you’d have to move recorders filters over too and duplicate them.
But maybe a better workaround then listing 156 entities in the meantime?
I did check the dock and I tested it out as well as best as I could also looked at int and float as well that’s why I made the educated guess that when bool is used as a filter the value inside the parenthesis is maybe the default value but I don’t see it explicitly written out so hence why I came here to asked. I did do my due diligence.
Hi, that is not correct unless you’ve disabled “my home assistant”? See discussion in Nest - Home Assistant – but i assume there you mean that you replace with your real hostname.
Just want to clarify that this advice is not correct in general, and most everyone should be using https://my.home-assistant.io/redirect/oauth as their redirect url.
press yes and youll see itll ask for the update file location on your pc… clicking yes wont do anything to your zwave device this is not an auto update you need to manually find the files online to flash over zwave.
the zwave updater works great, i updated my 6 aeotec multisensor 6’s to latest 1.15 version as i have never updated them since i had them over 5 years ago. i used homeseer update files for them not the .exe that come in the downloads file extension type .hec
Where did you read this? I too own some leviton devices, but I looked through the breaking changes for 2022.7 and didn’t see anything related to leviton there.
this actually a nice idea, and Ive tried to make a start, not really sure if it gets the ordering from before though, auto-entities has its own logic n that regard. But maybe we can manipulate it to be close to what is was, or maybe even more useful, based on state etc etc.
I personally don’t like the idea, that a feature is removed and then the user has to rebuild it on their own or to open a feature request to get what was there before. Esp. in this case.
But if I’m remembering correctly from the beta channel, at least there was a 90% commitment to have the ALL come (back) in the next release. Esp. as it is not influencing those user, who will never press it.
sure, I do feel that way too.
Having great suggestions is something we need every now and then, and Mike has a way with those
Ive just added all single included entities under the entities key in the auto-entities panel mode card, and yes can confirm that to show.
Tip: pre-edit the card config in a standalone editor, which makes it very easy to move from the recorder filter syntax to the auto-entities syntax using replace -all…
ah well in that case it might be beneficial to re-word that pop-up, as I wasn’t sure what’ll actually happen once I press “Yes”. I assumed it a point of no return and it’ll just straight update the firmware
After upgrading to 2022.7.0, TP Link ‘Tapo Integration’ for P110 stopped working. Couldn’t figure out what was happening since the entity became unavailable. I had to restore it back to Home Assistant Core: 2022.6.7 from 2022.7.0 and it just started working again without any modifications. Not sure what changes are breaking this integration.
Now my HA version is,
Home Assistant Core: 2022.6.7
Home Assistant Supervisor: 2022.7.0