What about hight memory usage?
Petro, you are aware thats exactly what has been done at Dev tools states shows friendly_name instead of entity_id · Issue #11938 · home-assistant/frontend · GitHub ?
1 Like
o right, that’s what you mean… I still see the discussion section there as the Frontend FR section…
but then again, we could consider keeping the UI consistent a FR 
No problem!
It was a blast coding it.
I have an automation that sends a notification to my Alexas when it increases by over 200 in case of a storm passing through or something. It helps me prepare for a power outage before hand.
Smart meter checking and the map alert is in the works!
2 Likes
Your issue has a ‘bug’ label, not feature request. 
As a dev, I’d skip right over that because it’s not a bug, it’s an opinion. And as a dev, it’s not a decision I’d be able to make without a discussion. And my job as a dev is to dev, not discuss stuff (that’s for the people who make decisions). Hopefully you’re starting to see the process…
discuss → reach agreement → develop
or
is-bug → develop-fix
okok, I see. otoh, there are many Frontend discussions opened with no response either, so currently it is a bit of
enduser finds inconsistent behavior → reports (maybe in the wrong section) → no reponse → gets lost (at best)
enduser tries to fit in → suggests (in the correct section) → no reponse → gets lost (at best), shrugs, or … disconnects
hope the Ha team sees that also
a simple response of recognition would be awesome
btw: Make all searches behave the same way. · Discussion #12304 · home-assistant/frontend · GitHub for starters
2 Likes
Smart Meter checking would be amazing…great work!
Is it not possible from one of the HA github mods to change type? Should be the best and easiest way in such cases. Even if someone is creating this from scratch, the history is gone otherwise.
1 Like
I’m sure it could be changed. I was just pointing out the process that is used in HA for the frontend. Whenever there is behavior changes to the frontend, we start with discussions not issues. Issues may lead to a discussion, but someone has to take that leap.
Is there anyway to edit a group / helper after it was created? Or do I have to delete the helper and recreate it?
Just asking as I want to keep adding sensors along the way for a helper that calculates and average value, but I don’t have all the sensors in hand right now…stupid supply chain issue.
Is anyone else still having the ZHA/ConBee II issue? I’ve seen a bunch of people surface this issue, but no solution that I can find.
What I’m seeing:
Since moving to 2022.4.0, my zigbee lights (all hue) are responding extremely slow (if at all) to commands. I tried to back out to the previous version (2022.3.8 I think) but the system fails to start properly. I don’t have anything that’s customized (quirks, etc). Just 46 hue lights and a couple of dimmers.
I couldn’t find anything in the forum.
2 Likes
Yes, of course. But if there is a migration click, I would suggest to use it in such cases, where something has been opened in a wrong place. You pointed out, that developers or the UI deciders will skip such issues, bucause it is not a bug or an issues. But sometimes, there is valuable content. And instead of letting this move down and let perhaps users who open such cases (in a wrong place) alone/frustrated, the migration would help both sides. In other repositories, it is a task of moderators, who are doing this.
1 Like
I agree it’s frustrating to have so many disconnected discussion environments. But this forum is where we (users) are being directed. Right on the bottom of the configuration screen, we see this:
Even right on the HA web site, if we click Need Help? we see this:
So we come here; the first item on both lists. We lurk for a while until we get the hang of it, and finally chime in with what we hope will be constructive ideas.
And then we’re told that’s wrong.
So I hope you can understand why there’s frustration on both sides.
9 Likes
The statistics editing has something very wrong with it. Every time I enter a value, the result gets worse and worse. Example:
Sensor value:
-41136026493363540
Enter: 0
New Value:
1411569038482139600
Enter: 0
New Value:
-48437521079554100000
I’m not going to talk about this again for he 10th release thread in a row. You know the answer, I’ve said it before. All I can offer as advice is:
If you partake in the current process, you’re more likely to get heard.
If you completely ignore the process, you’re less likely to get heard.
Can’t figure out why, but I had a big memory use drop from 2022.4 to 20022.4.1 
You can definitely edit it after the fact including adding devices and changing how those devices are recognized.
Thanks, It’s actually pretty confusing/cumbersome to get to. You have to go to “Configuration” > “Automations & Scenes” > “Helpers” > click on the helper you want to change > “Settings” tab > Click the “Configure State” text > Now a window is provided to update the helper and the entities assigned to this helper.
I really hope that in the future an edit button will be provided in the “Helpers” window / list that will take me to the specific helper’s “Options” window.
1 Like
Hi Jimmy,
I’ve also noticed this with my Hue bulbs and ZHA/ConBee II setup. Tried digging into the issues on Github but didn’t make it very far.
Please let me know if you find out what the issue is!
1 Like