nielsfaber / scheduler-component

Custom component for HA that enables the creation of scheduler entities
GNU General Public License v3.0
631 stars 41 forks source link

Unable to save new changes #227

Closed MS-Turbo closed 1 year ago

MS-Turbo commented 1 year ago

Running latest version of everything

When trying to change any setting, the scheduler "jumps back" to old settings. This issue happens to all type of schedules, temperatur changes, time changes, name changes and so on.

Any thoughts on why this is happening?

Skjermbilde 2022-11-27 kl  19 02 27
nielsfaber commented 1 year ago

This is a problem of 2 versions before, it’s fixed in the latest release. You should clear your browser cache or something.

MS-Turbo commented 1 year ago

This is a problem of 2 versions before, it’s fixed in the latest release. You should clear your browser cache or something.

Still not working here.

  1. Deleted all cache (tried the same both in crome and brawe)
  2. Reinstalled HACS scheduler addon v3.2.12
  3. Restarted Home Assistent

When trying to change temperature in a schedule, it just jumps back before beeing able to save changes

Any other soulutions I can try?

nielsfaber commented 1 year ago

Please check your browser console logs (under developer tools or similar). There should be a badge displayed there with the version of the card which is running.

I’m still convinced this is a problem due to old version. If you can prove otherwise, I’m willing to dive into it.

MS-Turbo commented 1 year ago

Hi. Not sure what to look for but here is a screenshot. One interesting find...this issue is only occurring when accessing HA through nabucasa. When connected by local ip, everything works fine. So maybe the fix was not solved other then local?

Skjermbilde 2022-11-30 kl  23 58 57
nielsfaber commented 1 year ago

Not sure what to look for

This: image

In the release notes for v2.3.7 of the card you can read:

Fixed a bug introduced in HA 2022.9 causing settings in the card to be reverted every few seconds while making changes.

You need to erase your browser cache to solve the issue. It is still holding an older version of the code of the card.

omarantelmi commented 1 year ago

The problem seems to persist for me too, even when accessing from a device that has never been used

nielsfaber commented 1 year ago

@omarantelmi update to v2.3.7 or newer to solve the problem. If the problem persists after the update, follow https://github.com/nielsfaber/scheduler-component/issues/227#issuecomment-1329000471 If the browser logs show v2.3.6 or beforel, while you installed v.2.3.7 or newer -> browser cache issue.

MS-Turbo commented 1 year ago

Update on my rookie mistake on this issue. Deleting cache did not work and I also tried different browsers, but the problem was an old version of the scheduler card in HACS that needed update. My mistake was looking NOT at the scheduler card, but at the scheduler component in HACS witch has the similar software version series.

Skjermbilde 2022-12-02 kl  16 10 25 Skjermbilde 2022-12-02 kl  16 10 35
catalinbordan commented 1 year ago

Here I had the same issues; did not revaluate the conditions on update of states and the issues described here. I was thinking something broke the updates of new versions of homeassistant and then said to check if other have same issues here open on github. Investigating, I have found that my scheduler card was almost having same version format like scheduler integration 3.1.xx witch is > 2.4.1, so HACS did not let me know that I have new update and off course problems because different version. I redownloaded and now I have version 2.4.1 listed on HACS + make a small modification on my schedulers to fix it. I suppose something gone wrong with versioning on scheduler card on HACS and a lot o people don't know because HACS did not trigger anymore an notification of a new update because of bad version number. Thanks!

nielsfaber commented 1 year ago

@catalinbordan All releases of scheduler-card can be found in the releases page. There is no 3.x.x yet, latest is 2.4.1. It would be helpful if someone experiencing this problem could (before redownloading) check the actual version which is running. I have no idea what is causing this issue. I'm not sure if the problem is on the side of scheduler or HACS either.