I didn't mean to imply that Services actually broke. Only that they didn't come back after a reboot. A clean reboot may have caused some of the same issues because, I'm learning as I go. Some services are restarted by systemctl, some by cron, some....manual. This is certainly a wake up call that I need standardize and simplify the way the services are started.
padook
joined 2 years ago
Slaps forehead I know I read that guide too....whether I forgot about it or thought that would do something else... Thank You!
Me: Hovering mouse over the update button Click it!!
Also me: No no, it says right in the changelog that this is one of biggest releases ever, wait for a point release
Me again: but you can make the "sleep time" automation say Goodnight after it runs!!!!!!
click
The problem with a good running automation is you end up used to them, I forget they're even there most if the time.
I end up appreciating my once-in-awhile automations more. A couple times a month I need to get up extra early, skip my normal routine and go straight to work. But I'm American, this can't be done without coffee. The night before I prepare the coffee maker and scan an NFC on the top that turns off the plug and waits for my next alarm, then turns it back on. Once it runs it disables the automation, so I dont accidently burn the house down. Worth a million bucks
In the summer in the northeast US most evenings are cool enough to sleep with just a fan in the window. For the nights that stay too warm past bedtime I scan an NFC on my AC that triggers an automation to shutoff the AC and turn on the window fan at a specified outdoor temp. Saves on electricity and who doesn't love fresh air??
Yes! Especially automations! I would rather have tags than folders, so an automation could fit into more than one category (eg. Location, action) but I'd take anything over alphabetical!!
Maybe click on that lux entity in the dashboard and see if it has been consistently transmitting its data (on the history graph)? I'm pretty sure you'll get this warning if the state reads "unavailable" which could be a reception issue or a dying sensor.
I recently saw this happen to an animation of mine and I think this was the cause
I would spend the money on smart switches before smart outlets. I personally find that I want smart control over almost all of my lights/ fans but only some of my outlets.
Another reason for my avoidance of smart outlets is they are much more expensive than smart plugs and it's rare that you want to control both plugs in an outlet anyways.
As far as wiring if you want window/ door sensors or motion sensors you might consider running power to those locations. Much better than changing button batteries constantly.
Use conduit to future proof any network cables you run....
That's all that comes to mind at the moment
Should be able to just do it with automations and include "choose" action. 2024.1 looks like it makes it easier building blocks.
I've been pretty happy with paperless-ngx, it should tick all your boxes
This thought came to me this morning. I have 4 machines both because the BEAST grows organically, and because we're always trying to avoid that single point of failure. Then a scenario comes along that makes you question your whole way of thinking, diversifying may actually create more problems