One monitored device schedule bleeds into another

[timgoldrein-lgtm]

I'm systematically adding TRV entities to the scheduler, one room at a time. The first two go fine, but by the third, the data in the third seem to get copied into the second or first, or sometimes both. Sometimes it takes up to the fourth for it to go all wrong.
It was working just fine when I only had two rooms in there, but now I'm trying to roll it out around the house, it's all going pear shaped. It's such a shame, because it seems to be a very wonderful integration, if only I could get it to work.
I'm sure I've corrupted something, but I can't seem to get a clean install any more. Even if I've done a "factory reset" and then deleted the whole of everything as far as I can tell (including the files in /files/custom_components/climate_scheduler), when I reinstall everything, things don't work quite as I expect.

1. I can't for the life of me get the card to appear. I have to paste it in manually. No obvious reason why, and the diagnostics say all is good.
2. When I click "monitor" on a thermostat entity, it says "This entity will be managed by the scheduler again." This makes me think that somehow, it has remembered that it was monitoring it before.

Maybe I've hit a bug, or maybe I've broken something somehow. I'm out of ideas. I've deleted all the thermostat settings that I used to have (except the entities), cleaned up everything I can find, installed and run Spook and still not found anything that points to anything broken here. I'm very keen to help make this work, because it absolutely nails my requirements for my heating. Spot on. I loved it when I had it working. I just wish I could make it work again!

I do hope someone has some ideas for me.

The diagnostics dump starts as follows:

integration:
version: 1.15.1
domain: climate_scheduler
name: Climate Scheduler
ha_version: 2026.5.1
card_registration:
status: registered
count: 1
resources:
- url: /climate_scheduler/static/climate-scheduler-card.js?v=1.15.1
type: module
id: c5001871078c4a7187412b63fcca49c9
card_accessibility:
url: /climate_scheduler/static/climate-scheduler-card.js
full_url: http://localhost:8123/climate_scheduler/static/climate-scheduler-card.js
status: accessible
http_status: 200
content_length: 27315
total_lines: 312
first_10_lines:
- >-
/******************************************************************************
- Copyright (c) Microsoft Corporation.
- ""
- Permission to use, copy, modify, and/or distribute this software for any
- purpose with or without fee is hereby granted.
- ""
- >-
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH
- >-
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY
- >-
AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL,
DIRECT,
- >-
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
FROM
appears_valid: true
storage:
status: @loaded//

[kneave]

Regarding pasting in the card, I've no idea why automated registration works for most people but not others, if I could figure it out I'd solve it for sure.

For 2, there's a hidden folder in config called ".storage", it's where data is stored by default for all addins. If you have a look in there and delete (or backup first) the climate_scheduler_data file it should nuke the configuration for Climate Scheduler and put you back to an install state.

[timgoldrein-lgtm]

Thank you so much! Well, I tried, but this didn't seem to work out, but the good news is I've found a workaround.
• I factory-reset the integration, then uninstalled the card then the integration, then the HACS download and finally restarted.
• I deleted the file in .storage. This was very short, presumably because the of the factory reset.
• I deleted the folder in /root/config/custom_components/climate_scheduler
I use the Terminal and bash to do all this – I'm more at home with Unix commands! I also searched for any other files with climate_scheduler in their names, and I deleted anything I found.
I reinstalled the integration completely with restarts and cache-flushes along the way. Still, it somehow knew that it had once managed each TRV entity, so it was monitoring them "again", and still the confusions started happening. Add an extra entity to the list being monitored somewhere along the way, and suddenly, well-behaved schedules are being lost, overwritten by another. Sometimes the next one along, or sometimes the one I was working on. Very odd indeed.

It did work if I added all the devices to be monitored to the list before editing any schedules at all. Maybe each time a device is added, the file is read in, edited and then re-written. Maybe somewhere in that process something is getting mixed up?

Anyway, I now a happy bunny again because I have my long list of schedules set up and it seems to be remembering each of them and keeping it all organised. Woo hoo! And thank you! If you want me to do any further testing for you, please ask.

Update: I thought it had stuck and when I went to bed, so far as I could see, all the different profiles were working. When I got up this morning, I was surprised to see a number of TRVs at a particular temperature which I didn't expect. When I looked this morning, all the profiles are the same – all copies of one particular room. So still no clues!

[kneave]

Are they all using the same profile?

[timgoldrein-lgtm]

Yes. Initially, I had made two profiles, but as I've rebuilt it block by block, I have not invented anything new there. Just the one default profile for everything at the moment.

[timgoldrein-lgtm]

Any thoughts, Keegan? Any more diagnostics I can look up for you? Obviously, the weather is such that I'm not using the heating much at the moment(!), but I'm keen to sort this while at least some of it is still in my head. Thanks in advance.

[kneave]

Apologies Tim, I've been a bit burned out and not able to look at this for a while. Regarding the card issue, I've sadly no idea as it only seems to occur on some folks servers and copying and pasting in to the yaml manually is the only way to do it.

For the other bits are you creating an individual schedule for each trv or adding them all to the same group? The whole "monitored again" wording is probably a UI bug more than anything so I'd ignore that for now

[timgoldrein-lgtm]

Thanks, Keegan! You are a volunteer – you are allowed to be burned out. Trust me – I know how you feel! Don't worry at all.

If you could point me to the yaml to copy, I can do that. I guess if I set them up, there will be the times and temperatures stored there somewhere in a scrutable way that I can mess with. I hope I'll be able to get my head round it easily enough. I don't see why I shouldn't, but it's fair to say I haven't yet.

Cheers, Keegan.