Some cool examples there, I’m going to think about them. I particularly like the walking ones.

I want to love dashboards. I love the idea of a control centre in each room but I just can’t get to the point of winning with them

I totally understand mission critical motivations, but I reached a different conclusion from you. I’ve been HA’ing for a long time and everything dies eventually.

Do you have a backup HA green in the cupboard? my wife would murder me if I couldn’t get the house back in 24 hours. I want to use hardware that you can buy literally anywhere so I don’t need to keep a backup.

I’m not there yet, but I havve moved to running HA on a proxmox server and have used my HA backup to recover from a software failure. I’m now thinking about what the same would look like for a hardware failure, either the mini pc or the zigbee dongle.

I like this, but I don’t like that rooms are cold unless I hang out in them. I live in an old stone house and I’d rather have a room schedule than a room presence sensor.

I’ve done something similar. I use the excellent scheduler from Niels Faber. I have room radiator TRVs. I have a helper entity that counts the number of radiators that have an open valve, and an automation that triggers when this changes to/from zero. This automation adjusts the central nest thermostat, converting it to more or less a posh switch.

My radiator valves use Better Thermostat and external temperature sensors, and the whole thing keeps my house warm in every room. I need to write a GH blog post about it, but happy to answer questions/share bits of config

Big shout out to Adaptive Lighting. Absolutely love this integration

I feel like almost everyone with ADHD could have told them that.

I can’t exactly solve your problem, but when I wanted to get HA running on proxmox I used these scripts

Tteck

Completely painless and running in almost as little time as it took to download the files.

If you’ve got access to the file system I think you could remove the custom component there - can’t exhausted resources if there’s no code!

I did wonder if that was the one that did it. That’ll teach me to update multiple things at once.

The only thing I lost was a day of recorder data and since I repaired it before bed I guess if I went and recovered the previous build I’d lose what I had overnight in the switch back.

Thanks for letting me know though, I’ll warn my friends before they update.

This happened to me, I’m running HAOS on proxmox. Ended up restoring from backup. Rollback from the CLI didn’t fix it either.

It’s hard to not make them sound trivial, but you’ll see some of them in the memes that pass through here. Off the top of my head though:

• the importance of routine/consistency. He got up at the same time almost every day for 50 years. He went to the gym before anything got in the way, that sort of thing.
• he pushes conscious decision making, of following through on things and being definite. Do not let yourself be guided by what you want in the moment, be guided by what you plan and intend.
• put things in the same place. Put things back where you got them from. Don’t rely on your memory, rely on your habits.

When I write these they seem silly and trivial, but they help me a lot.

It’s hard though. A key criteria (at least in the UK) how much it affects you day-to-day. My father probably has it and passed along a lot of guidance that I now recognise as coping mechanisms/symptom management strategies. Day to day I’ve got it in hand, it’s only when the big storms come that I struggle, and that doesn’t fit with the diagnostic approach.

I don’t know how tech savvy you are, but I’m assuming since your on lemmy it’s pretty good :)

The way we’ve solved this sort of problem in the office is by using the LLM’s JSON response, and a prompt that essentially keeps a set of JSON objects alongside the actual chat response.

In the DND example, this would be a set character sheets that get returned every response but only changed when the narrative changes them. More expensive, and needing a larger context window, but reasonably effective.

It’s got a nice component to go with it, so setting up is easier. I particularly use it for scheduling thermostats, and find it much more user friendly. Sure I could do it with automations, but I’d either have one, massively unwieldy one with lots of states and triggers, or lots of individual ones.

This custom component is what I use and love - https://github.com/nielsfaber/scheduler-component

I have this battle - I am great at routine but terrible at habit. My wife asks me why I do the same thing every day, and I can’t really explain that I have to do it every day or i’ll stop doing it completely.

These are a great example that I might use in the office. Everything makes sense in isolation, but the unity the wind, waves and sails don’t quite match in a way I couldn’t put my finger on.

Listen. Well done. Just because it’s simple, doesn’t mean it’s easy.

Now go and put away your laundry. /s

I can’t decide if I want this to have been written by an AI or not.

This looks great, in no small part because the weathering on the rest of the leg looks great too. Show us the rest of the model!

Part of the problem here I think relates to scale.

If I invite a load of friends over to my house for a party, they might be in different rooms having different conversations but they’re all my friends in my house. No one cares who I let in or kick out, certainly not either of the next groups.

Let’s say I’m part of the committee for the local community hall. We let our halls out to clubs. Some of the committee go to some of the clubs. I might not be interested in what it is, but if someone I trust says they are OK, I’m OK.

At the local University they have a lot of spaces, each managed by the respective school. Each school has a slightly different ethos. Some of them might let their space to groups that other schools wouldn’t, but it’s not their call. They share some resources but not decision making.

We’ve got this problem emerging. The decisions made by lemmyworld or other large instances are generally in service to their communities, whereas on smaller or more focused instances the instance level decisions are the same as community level decisions.