limelight79

Hi, all. Finally migrated from Kubuntu to Debian 12 over the weekend. It's working great, as I figured it would, with one exception: The system isn't turning the monitors off after 10 minutes. It's blanking them, but they're clearly still on.

One monitor is on an AMD graphics card, the other is on the motherboard Intel adapter.

Debian 12 with KDE Plasma running on Wayland with sddm login. It previously worked fine on Kubuntu (which I believe was running X11). It's a fresh Debian install on a different drive; I didn't overwrite the Kubuntu installation.

In the Energy Saving settings, I have "Screen energy saving" checked with a delay of 10 minutes. (I have "suspend session" turned off - one, because I don't want the computer to sleep or suspend, and two, because when I woke it up again, the graphics were garbled and I had to reboot.) As I said, it does blank the screens, but they're still clearly on. I want them to go into power save mode.

I've tried running dpkg-reconfigure and selecting sddm, no change. In KDE's background services, I tried turning off KScreen 2, but that didn't help (though I'm not sure if I rebooted after turning it off, now that I think about it).

I found advice somewhere that suggested deleting .config/powermanagementprofilesrc and rebooting; I did that, no change.

I did notice yesterday that the monitors had shut off...after a very long time of being idle. I'm not sure how long, but more than overnight, for certain.

Any advice or suggestions? Unfortunately, searching is difficult, because I get a lot of results where the screen blanks when it shouldn't. I haven't found much for this problem.

I used the same installer on my laptop to do the same migration (also with KDE Plasma and sddm) and it works fine there.

No major question here, just thought you might find this interesting. It's an example of the kind of (off-the-wall) things you can do with HA that aren't immediately obvious. When I was starting out with HA, I enjoyed reading these examples, because it gave me ideas for my own setup. And, I wrote many automations that should really be scripts, so hopefully this will help someone avoid that and recognize the power of scripts early.

At home, my laptop from work sits (closed) on a stand under the monitors. I have a docking station for it, but the docking station doesn't have a power button to start the laptop (the official Dell docking stations have a power button, but other brand of docking stations don't). So, since I got that stand a few weeks ago, I've been pulling the laptop out and opening juuuuuuust enough that I could reach the power button, then closing it and sliding it back into the stand. There had to be a better way that didn't involve buying an expensive Dell docking station.

The docking station power is on a Sonoff S31 outlet (flashed with Tasmota, not that that's important here) that is remotely controllable. Long ago, I set up HA automations that turned on the S31 when the laptop was detected on the network, and shut off the S31 after the laptop dropped off the network at the end of the day (leaving in a time delay so it didn't shut off if there was a momentary network glitch). So, I'd boot the laptop, and a moment later the docking station would kick on and connect the mouse and monitors to it. And the end of the day, I shut down the laptop, and a few minutes later the docking station shuts off automatically.

I recently discovered the Wake on LAN integration. So, after setting that up, I wrote a script that turns on the S31, waits a while*, then triggers the Wake-on-LAN for the laptop...and it boots up! With HA, I can start the boot process while I'm still relaxing in the living room before starting work; in theory I'll go into the office and it'll be ready for me to log in.

Heck, if HA knew for certain it was a workday, it could boot the laptop for me.....hmmm. Maybe something to think about for the future.

*How long? Well, 30 seconds seems to be too short; the laptop doesn't respond to the WoL command after just 30 seconds with power applied. It did work this morning when I waited several minutes to try it again. I just changed the delay to 1 minute and will see how that works tomorrow.

I also added a repeat loop (starting after that 1 minute timer) with three components:

• A condition that looks for the laptop being "Away" on the network. (If it is "Home" on the network, the condition will end the script.)
• If it is, then it tries the WoL command again.
• Then waits 30 seconds and repeat.

The repeat loop counter is set to 3, for a total of 4 attempts to start the laptop. I'll check the traces and see when it starts working, and set the initial delay accordingly, so that in general it shouldn't need the repeat loop.

If people want, I can post (sanitized) YAML. But I do like explaining the process rather than just posting code.

This is not the first time I've ranted about the previous owner's wiring jobs, though I think they were on the other site (and I had a different username there).

His greatest hits include:

• Above a drop ceiling in the basement, a wire that went into a metal box without a strain relief, so it eventually wore through (for whatever reason) and started shorting out. Since it was above the drop ceiling I had no idea why that breaker would occasionally trip, then reset without complaint. Also, there are other things on that circuit, but the offending wire was only live when the light switch in the room was on, so it was harder to diagnose. It wasn't until we demolished the room that we found the problem...black marks on the box and wires and all.

• A duct fan to route heat from the pellet stove into the master bedroom...with the wiring completely enclosed in the ceiling, with no access to the box. Said duct fan has started making noise, so I'm going to have to cut that ceiling open and replace it, and I'll probably install one of those spring-loaded covers so there is access in the future.

• A fascinating wiring job in the shed that is unnecessarily complicated and certainly a violation of the code on how many conductors can be in a box. I'm going to fix that some time this spring. This is actually a REALLY great one, so maybe I'll post it as a comment.

On to today's hilarity. A few weeks ago I noticed the UPS for my computer in the basement had a red light on the back warning of a wiring fault. I never noticed it before, or I did and forgot, and it's not very bright, so you almost have to be looking for it to see it. Well, I got out one of those testers that you plug in, with three lights that diagnose the issue, and it showed no ground. Odd.

I checked the other two outlets on the same wall, the one closer to the panel tested fine, but the one on the other side of the outlet in question also showed an open ground.

Today I dug in to find out what was up. It turns out the ground was cut on both wires in the outlet the computer was using (supply from the previous outlet and the wire to the next outlet). It was not connected to the metal box or the outlet.

WHY WHY WHY? Why did he do this? I can't fathom why you'd do this.

I replaced all three outlets on that wall with new ones and made sure the grounds were connected. Nothing really wrong with the original outlets and covers, but they were old and beige, and I like white.

Years ago I found an outlet in our closet that only had two prongs, no ground. The house was built in 1987, well after three prongs were standard. With some trepidation - what am I going to find here? - I opened it up and found that...there was a good ground there (to my relief) but he apparently just decided to use a two prong outlet. WHY? He had to have gone to special effort to find a two prong outlet to install. (Actually it is theoretically possible that was done by the builders, but everything else in the house is three prongs, and I can't believe it would have passed inspection.)

Hi, all. My wife and I recently got new phones, and it got me thinking again about how notifications work.

Currently I have several automations (maybe 10) that send notifications to my phone, her phone, both, and possibly other devices.

But when we get a new phone, or replace a tablet, etc., I have to update every single one of those automations. And I inevitably forget some or introduce errors.

Is there a better way to do this? For example, it'd be nice if I could abstract the concept of "my phone" out in those automations, then I'd only have to change the device "my phone" in one place, rather than a bunch of places.

Any thoughts on this? Maybe I'm missing a way to do it. Thanks.

https://lemmy.world/post/10554910

Running on a Lenovo Yoga Tab 13, Android 13, version 1.0.4 of Boost.

First impressions, anyone?

The change isn't a big deal for me, because I ride Zwift for exercise when I can't ride outside, and the achievements are secondary. But I know, for a lot of people, chasing those badges or next level is huge.

I especially think how they're handling the transition to the new level is interesting. I'm not sure I totally understood it, but I think any amount of XP you have over the new level you're on will be applied to reduce the amount of XP you need to level up, reducing it by 20%. The amount of "extra" XP you start with determines how many levels will get that 20% bonus. At least, that's how I read it.

Despite what I said above, I sometimes feel like I'm sitting on a level forever. It doesn't really bother me, but it's also like, wow, still level 35, eh? And I would like to get the doughnut jersey, so that seemed like forever away. So requiring less XP to level up will be nice.

I think I'm the only subscriber to this community, but I thought I'd post this in the hopes to get some responses...

I know no one has subbed to this Airstream community, but I'm posting this anyway. We're currently in Fort Collins, Colorado, and heading to Rock Springs tomorrow!

In light of the issues going on the other site, I thought it would be a good idea to create an Airstream group here.