Can't add new helper

[Marc1200]

The problem

The button add helper is unresponsive, i can't add an new helper.

What version of Home Assistant Core has the issue?

core-2023.6.1

What was the last working version of Home Assistant Core?

core-2023.5.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

helper

Link to integration documentation on our website

https://www.home-assistant.io/integrations/input_boolean/

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

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (input_boolean) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of input_boolean can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign input_boolean Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

input_boolean documentation input_boolean source _{^{(message by IssueLinks)}}

[MartinHjelmare]

Please attach a screenshot.

[Marc1200]

this button is unresponsive. when i click on it, nothing happen

[MartinHjelmare]

Are you using the default_config: in configuration.yaml or have you removed that entry?

[Marc1200]

Yes i'm using default_config: , it is in the configuration.yaml

[ronald3060]

Here too, can't make a helpen since last upgrade. \Botton doesn't respond, default_config is present in configuration.yaml.

[bramkragten]

Any errors in the browser console?

[ronald3060]

No, no other errors

[Marc1200]

i have some errors in browser console when i press the button

[rjodwyer]

same issue, same error in console here when trying the button

[MartinHjelmare]

Please don't comment unless you have new information. You can react to the top post with 👍 to show that you're also affected.

[silamon]

Based on the error description: This comes from the upgrade to full calendar v6.1.8 which changes the way the styling is done. https://github.com/fullcalendar/fullcalendar/commit/8a03db7e9d7e8e6598531a5b2fd9ccc6de30716b Seems to me that it's something in the browser that doesn't allow it. What browsers are you using? I'm unable to reproduce unfortunately. All I can add is that a downgrade to v6.1.7 would fix this for now.

[daschmidt1994]

Have the problem in the App also not only in the browser. A clear from the app cache doesen't help.

[ronald3060]

Chrome, with safari on iPhone no issues.

Verstuurd vanaf 06 28422438

Op 21 jun. 2023 om 15:02 heeft daschmidt1994 @.***> het volgende geschreven:

 Have the problem in the App also not only in the browser. A clear from the app cache doesen't help.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[pcwii]

Just to add to this list. I also Have this issue running latest docker install on a debian system. The button does not work in Chrome browser on Android, the android app, or a Chrome browser on Windows 10 laptop. I have attempted reboot of the server, clearing cache and app data on the android app, as well as clearing the browser cache on android and windows 10. The only thing I can confirm does work is if HA is accessed with incognito mode on the Chrome browser, either on android or windows 10. I hope this is helpful.

[karwosts]

I actually ran into this by accident in my dev instance, so I got the full unobfuscated stack trace:

internal-common.js:46 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'cssRules')
    at appendStylesTo (internal-common.js:46:1)
    at eval (internal-common.js:10:1)
    at Map.forEach (<anonymous>)
    at injectStyles (internal-common.js:9:1)
    at eval (internal.js:6:1)
    at ./node_modules/@fullcalendar/timegrid/internal.js (vendors-node_modules_date-fns_esm_isSameDay_index_js-node_modules_date-fns_esm_isSameWeek_ind-f98b95.js:79:1)
    at __webpack_require__ (app.js:1934:41)
    at eval (index.js:6:70)
    at ./node_modules/@fullcalendar/timegrid/index.js (vendors-node_modules_date-fns_esm_isSameDay_index_js-node_modules_date-fns_esm_isSameWeek_ind-f98b95.js:69:1)
    at __webpack_require__ (app.js:1934:41)


appendStylesTo | @ | internal-common.js:46
-- | -- | --
  | eval | @ | internal-common.js:10
  | injectStyles | @ | internal-common.js:9
  | eval | @ | internal.js:6
  | ./node_modules/@fullcalendar/timegrid/internal.js | @ | vendors-node_modules…ek_ind-f98b95.js:79
  | __webpack_require__ | @ | app.js:1934
  | eval | @ | index.js:6
  | ./node_modules/@fullcalendar/timegrid/index.js | @ | vendors-node_modules…ek_ind-f98b95.js:69
  | __webpack_require__ | @ | app.js:1934
  | eval | @ | ha-schedule-form.ts:9
  | __webpack_require__.a | @ | app.js:1994
  | eval | @ | ha-schedule-form.ts:1
  | ./src/panels/config/helpers/forms/ha-schedule-form.ts | @ | src_data_counter_ts-…tetim-94c827.js:159
  | __webpack_require__ | @ | app.js:1934
  | eval | @ | dialog-helper-detail.ts:39
  | __webpack_require__.a | @ | app.js:1994
  | eval | @ | dialog-helper-detail.ts:1
  | ./src/panels/config/helpers/dialog-helper-detail.ts | @ | src_common_array_ens…alert-1c0ca1.js:169
  | __webpack_require__ | @ | app.js:1934
  | await in __webpack_require__ (async) |   |  
  | eval | @ | make-dialog-manager.ts:162
  | fireEvent | @ | fire_event.ts:76
  | showHelperDetailDialog | @ | show-dialog-helper-detail.ts:17
  | _createHelpler | @ | ha-config-helpers.ts:365
  | handleEvent | @ | lit-html.ts:2010

I'm not sure what caused it, and once I refreshed the page one time it started working again.

[dmpohlmann]

Team, just had the same issue. Would not work in Chrome, works in Firefox!

[Marc1200]

I got the errors with the Chrome browser on pc and phone and Microsoft Edge browser at desktop pc

[Boromore]

For me it works with Edge but not with Chrome on a Windows 11 PC

[Marc1200]

with Microsoft Edge i have this error, the same as with chrome

[bramkragten]

I tracked this down to an issues in full calendar used for the schedule helper. I refactored this in the beta so it doesn't impact the other helpers at least. Not sure if it completely fixes the problem.

[Turmoil1112]

Adding new helpers is working again in Supervisor 2023.07.1 Operating System 10.3 Frontend 20230705.1 On Firefox and the Android App.

[Boromore]

I can confirm that it is working on Chrome too.

Home Assistant 2023.7.1 Supervisor 2023.07.1 Operating System 10.3 Frontend-versie: 20230705.1 - latest

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[pcwii]

I missed updating this. It began working again in 2023.7.1. Confirmed it is still good in 2023.10.1

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[GeorgeBark]

Still happening to me in 2024.1.2.

[DanielHabenicht]

Still happening to me in 2024.1.2.

For me its working again after upgrading to 2024.1.3 with Frontend 20240104.0

[maddingamer]

I have a similar issue, but when klicking on the "schedule" button within the helpers list (after klicking add helper) Running Core 2024.1.5, SV 2023.12.1, OS 11.4, Frontend 20240104.0

Issue is only in chrome, firefox works just fine.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.