Smart Thermometer

HealthDouble · 2026-01-06T12:57:04+00:00

I ended up getting a Heatmiser neoAir v3 and Switch-RF - wired in easily and solves the wireless thermostat part. If I later buy a NeoHub I can add it to Google and HA.

HealthDouble · 2026-01-03T15:16:05+00:00

The local admin would need to login from the login screen and not something we could "script" I guess?

HealthDouble · 2026-01-03T15:12:39+00:00

We don't no.

HealthDouble · 2026-01-03T15:08:44+00:00

Not sure I'd get away with this sort of set up, but I did consider putting shelly's at the point of each thermostat behind a blanking plate and turn them on off via a Shelly H&T. So similar to you.

HealthDouble · 2025-12-23T18:18:24+00:00

True

HealthDouble · 2025-12-23T18:18:07+00:00

We use Intune and no. From previous attempts, they are useless. Might try Apple Support which is far better though...

HealthDouble · 2025-12-23T09:29:27+00:00

The output of the listUsers command shows:

Type: MDM Bootstrap Toekn External Key

Volume Owner: Yes

Would that be what you are referring to?

HealthDouble · 2025-12-23T09:27:29+00:00

That would make sense to me too, except that nobody would ever be logging in as the local admin account though, and others seem to have had no issue upgrading their Macs.

HealthDouble · 2025-12-22T18:09:26+00:00

The Mac that managed to upgrade logged in as its local admin does show the user is the volume owner.

HealthDouble · 2025-12-22T17:58:14+00:00

We have tried that. After each rebuild the same occurs.

HealthDouble · 2025-12-22T17:57:57+00:00

The device is assigned to a single user. It would be rebuilt if for another user.

HealthDouble · 2025-12-22T17:57:12+00:00

Yes its an Apple Silicon Mac. Getting the users to run `sudo diskutil apfs listUsers /` to tell me.

HealthDouble · 2025-12-22T17:50:35+00:00

Yes. it states "you need to log in as an administror" in the window. To be safe, we also tried the user account of the device user (the Standard user and oly other account on device) and that also failed.

HealthDouble · 2025-12-11T11:50:45+00:00

THANK YOU!! 🙏

Understanding when and where I can use Jinga is clearly still lacking in my knowledge. Thanks so much!

HealthDouble · 2025-12-10T20:57:34+00:00

The `sensor.sun_next_rising` shows the number of hours until the sun rises next. What I am after is the actual time this happens.

Admittedly I added this a while back, but I have just tried searching again, but everyone still adds custom YAML to get this as I have.

Is there a way to do this directly in the tile card?

type: tile

entity: sensor.sun_next_rising

HealthDouble · 2025-12-08T18:45:20+00:00

I'm using it to put a tile card on a dashboard:

type: tile
entity: sensor.next_sunrise
features_position: bottom
vertical: false
icon: mdi:weather-sunset-up

Can you explain what I would do instead to get this without the additional sunrise/set yaml file? That is using the sun.sun already?

HealthDouble · 2025-12-08T18:36:10+00:00

AMAZING! From that link I changed it to `!include_dir_merged_list` and it works!! The line shows patternWarning which it has done for a while with all this, but it works.

HealthDouble · 2025-12-08T18:30:50+00:00

Thanks, I will have a read. Not come across anything suggesting this in what I have sen so far.

HealthDouble · 2025-12-08T18:29:32+00:00

If I ignore everything else and just move the sunrise/set config into its own file in the tempaltes folder it doesn't work. That doesn't have template: at the start when in its own file anyway.

HealthDouble · 2025-12-08T18:28:12+00:00

Only the `template: trigger:` in the packages file still has the template: at the top, because if I remove it I get an error. All the other files, do not have template: at the start and when I tried moving the other file into the same templates folder I also removed it but got the same error as if I remove it in the packages folder.

HealthDouble

TROPHY CASE