No longer able to edit or delete multiple helper types
The problem
When going to the helpers page an opening a counter, I'm presented with the pop-up as normal, but when I click on the gear icon to edit the settings the pop-up shrinks with no editable information. The only option is <- back to the initial pop=up page.
Trying to edit in Developer Tools | states isn't persistent. I created a new counter in case it was an upgrade issue, but I got the same results.
Ones affected: Button Counter Date/Time Number Text Timer Toggle
Not affected: Change device type of a switch (light) Group Min/Max Threshold
All our helpers were created via GUI.
1 - helper page (filtered)
2 - click on counter
3 - click on settings
4 - Trying to remove via Entities page
What version of Home Assistant Core has the issue?
core-2023.8.3
What was the last working version of Home Assistant Core?
2023.7.*
What type of installation are you running?
Home Assistant OS
Integration causing the issue
counter
Link to integration documentation on our website
https://www.home-assistant.io/integrations/counter/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @fabaff, mind taking a look at this issue as it has been labeled with an integration (counter) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of counter can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign counterRemoves the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
counter documentation counter source (message by IssueLinks)
I have the same issue, but with Helpers Text, input_number, input_button I also can't delete those helpers, I always get the popup, that I can't delete the entity as it is used by an integration, although the one I want to delete is not used by anything I am on 2023.8.2
I have also the same issue with helpers ( Text, input_button, ....) even if i create a "test" TEXT helper, and trey to remove this helper without using it, is is not possible anymore .. i am on 2023.8.2
add input_select and input_datetime to the list of helpers that do not show settings. I'm also on 2023.8.2. On second instance on 2023.7.1 it is still working as expected.
More of mine are no longer functioning (mirroring the posts above) Edited the op with revised working/not working
For me, counter, input_datetime, input_boolean, input_select, and input_number are not changeable. Binary_sensor does still work though.
Can confirm the same with counter helper. Made one as a test and tried to delete. Get the blank screen.
Latest and running docker.
confirm this with helper buttons and toggles having HA 2023.8.4 using standard theme everything configured within the UI
Same here. Found this by Googling why I can't delete old helpers that I no longer need...I actually wanted to update them but that wasn't possible either....the helpers work in that they do what they do, but they're all "MC Hammer - Can't touch this....." for everything else...no edits, no deletes, nothing.... :-(
same here with every helper having HA 2023.8.4 using standard theme everything configured within the UI
Same here, cant delete helpers. Home Assistant 2023.8.3 Frontend-versie: 20230802.1 - latest Using standard theme Configured within the UI
Just upgraded to 2023.9.0 - problem persists..... :-(
After one month since this issue was first reported: Anyone working on it?
Is there a way to delete them manualy?
downgrading solved it for me, from 2023.8.4 to 2023.7.1 (based on the above information)
manually make a backup, then in a terminal (add-on):
ha core update --version 2023.7.1
Not possible to delete them in the config files instead of downgrading?
You can find the helpers in the config/.storage directory in files input_boolean, input_number, etc. You might be able to delete them by editing the files. I haven't done this yet, so no guarantee it will work.
You can find the helpers in the config/.storage directory in files input_boolean, input_number, etc. You might be able to delete them by editing the files. I haven't done this yet, so no guarantee it will work.
This worked for me. Edited the file, saved, restarted HA and then had to go into Entities and was able to delete it from that page. Everything is latest ver, core 9.1, os 10.5, supervisor 8.3.
Same Issue. Just that I don't even get the gear icon shown after an entity had been deleted a helper was based on I have no way of deleting or restoring it. It does show me a dialog where I can change the underlaying entity. But after saving the new entity is still does not work. Nore can I delete the helper afterwards.
I had the same problem, I upgraded to Home Assistant 2023.9.2 and it works now for me
Wish I could say the same....for me it is still borken....
I do have the cog:
But clicking it gives me nothing....
So still stuck..... :-(
Same. Counter types can not be deleted
This is still broken for me as well.
I can edit the following Helper types: Group, Sensor.
I cannot edit any of the following: Toggle, Timer, Dropdown, Date and/or Time, Number.
I am still able to edit them by going into the config folder /.storage and editing the appropriate helper filer, then restart HA.
Home Assistant 2023.9.2 Frontend 20230911.0 - latest Default Theme
Same. Issue still persists.
Home Assistant 2023.9.2
Supervisor 2023.09.2
Operating System 10.5
Frontend 20230911.0 - latest
Tested by creating a VM with a fresh install (method) and all helpers worked without error. Seems like it's only affecting "legacy" helpers that have been through updates or perhaps conflict with an add-on/HACS?
In case it's a conflict, my add-ons:
Advanced SSH & Web Terminal
chrony
Cloudflared
Home Assistant Google Drive Backup
Log Viewer
MariaDB
Mosquitto broker
RPC Shutdown
SQLite Web
Studio Code Server
DHCP server (not running)
Tailscale (not running)
Uptime Kuma (not running)
ZeroTier One (not running)
HACS Integrations:
HACS
Meross LAN
Media player template
Govee LAN Control
Watchman
Xiaomi Cloud Map Extractor
Midea Air Appliances (LAN)
ZHA Toolkit
jokes
Presence Simulation
Sonoff LAN
Better Thermostat
Powercalc
Unifi Counter Sensor
Miele
HACS Frontend:
auto-entities
Better Thermostat UI
button-card
card-mod
Energy Flow Card Plus
Energy Period Selector Plus
Home Assistant Swipe Navigation
Kiosk Mode
layout-card
mini-graph-card
Mushroom
Mushroom Themes
Number Box
Simple Clock Card
sixdegrees-card
slider-entity-row
Slider Button Card
Stack In Card
state-switch
Sun Card
Swipe Card
Xiaomi Vacuum Map Card
Same. Issue still persists.
Home Assistant 2023.9.2 Supervisor 2023.09.2 Operating System 10.5 Frontend 20230911.0 - latestTested by creating a VM with a fresh install (method) and all helpers worked without error. Seems like it's only affecting "legacy" helpers that have been through updates or perhaps conflict with an add-on/HACS?
In case it's a conflict, my add-ons:
Advanced SSH & Web Terminal Cloudflared Home Assistant Google Drive Backup Log Viewer MariaDB Mosquitto broker RPC Shutdown SQLite Web Studio Code Server DHCP server (not running) Tailscale (not running) Uptime Kuma (not running) ZeroTier One (not running)HACS Integrations:
HACS Meross LAN Media player template Govee LAN Control Watchman Xiaomi Cloud Map Extractor Midea Air Appliances (LAN) ZHA Toolkit Zigbee Home Assistant Toolkit jokes Presence Simulation Sonoff LAN Better Thermostat Powercalc Unifi Counter Sensor MieleHACS Frontend:
auto-entities Better Thermostat UI button-card card-mod Energy Flow Card Plus Energy Period Selector Plus Home Assistant Swipe Navigation Kiosk Mode layout-card Lovelace mini-graph-card Mushroom Mushroom Themes Number Box Simple Clock Card sixdegrees-card slider-entity-row Slider Button Card state-switch Sun Card Swipe Card Xiaomi Vacuum Map CardHACS Automation:
Watchman
Interesting. I'll have to look in developer console in browser see if there is anything. Wonder if starting ha in safe mode will help
These are all working for me now.
I'm not 100% sure why, but I did this: While going through the process of installing all the Add-Ons and HACS integrations+frontend in the VM, I noticed a slight anomaly in my live setup. In (live) HACS I still had Watchman and Sun Card as custom repositories. They're archived as they've moved into HA core, so in the HACS Custom repositories area I removed them.
Then a restart
I was also poking about looking in /config/.storage at a couple of the files used by helpers (e.g. input_boolean), but I didn't edit anything there. I only viewed. The only other thing I did today was update a blueprint card, but I can't see how that would affect anything
But I just checked and all the helpers I'd listed in the original post are available to edit and delete again 😲
Can someone else check to see if they have the same and if it resolves the issue?
Custom Repos are in the 3 dot menu in the top right of HACS' sub-screens
Wait ... now they've stopped working again. I am so confused
Aha .. that's it Closed my browser, reopened and looked at helpers - failed I went back into the Terminal side-bar (launch new session) as I did earlier and tried to view helpers - success
Something to do with launching the add-on allowing access to the helpers, but blocking it until then. Anyone else using Advanced SSH & Web Terminal in their setup?
Anyone else using Advanced SSH & Web Terminal in their setup?
Nope. I run HA Container with no HACS and no internal add ons. All my services are ran in other containers.
See my comment above for which helpers do and don't work.
Ok, so I just saw that it's not specific to SSH. Can someone follow these steps to see if it also works for them as it does for me?
- Close browser
- Open browser and navigate to HA
- Settings | Devices and Services | Helpers
- Test editing one (it fails for me)
- Right click Settings to open in a new tab
- Devices and Services | Helpers
- Test editing one (it works for me)
I don't see why opening it in a new tab should be any different, but that's the current workaround for me atm