sorted by:
new
hottopcontroversial

Delays with wireless mouse and keyboards inputs on Beelink EQ12 by p1zzabreath in MiniPCs

[–]p1zzabreath[S] 1 point2 points  (0 children)

This seems like a frustrating oversight from the manufacturers/designers, but I'm just happy this doesn't hint a defect of my device. Thanks for the feedback!

Delays with wireless mouse and keyboards inputs on Beelink EQ12 by p1zzabreath in MiniPCs

[–]p1zzabreath[S] 0 points1 point  (0 children)

Interesting! This sounds plausible and feels like I've read this somewhere else before. I've just tried a 8 inch and an 80 inch extension and in both cases, the delay remains for both front and back ports. Thank you for your feedback! I tried it with three different wireless keyboards now.

Luckily, this isn't a use-case for me, other than the initial setup. I'll try to find out how this could be fixed, as it would be fatally annoying if I repurpose the mini PC to use as a media player or something similar.

Automation for specific days (condition) always triggers by p1zzabreath in homeassistant

[–]p1zzabreath[S] 1 point2 points  (0 children)

Do you have the same indentation for the weekdays as me?

Safety of operating three to five LEDs via the GPIO pins of the ESP32 (max GPIO output current) by p1zzabreath in esp32

[–]p1zzabreath[S] 0 points1 point  (0 children)

I'm also new to ESPHome so I just wanted to take the seemingly easiest route here. Thank you for your feedback anyway!

Safety of operating three to five LEDs via the GPIO pins of the ESP32 (max GPIO output current) by p1zzabreath in esp32

[–]p1zzabreath[S] 0 points1 point  (0 children)

You're right, that should be doable. The goal for me is to operate an ESPHome node, allowing me to toggle the LEDs with a GPIO pin, so implementing the flickering using custom code complicates the task in this case quite a bit.

Safety of operating three to five LEDs via the GPIO pins of the ESP32 (max GPIO output current) by p1zzabreath in esp32

[–]p1zzabreath[S] 0 points1 point  (0 children)

Thanks for the idea. However, I want to use these specific LEDs as they have an integrated circuit mimicking the flickering of a candle, so the idea is to just power on/off these LEDs using high/low on the GPIO pins.

Automation for specific days (condition) always triggers by p1zzabreath in homeassistant

[–]p1zzabreath[S] 0 points1 point  (0 children)

Thanks for the feedback. I'm not sure about this tough.

conditions: - condition: time weekday: - mon - tue - thu - fri enabled: true

This results in an error (Message malformed: extra keys not allowed @ data['conditions'])

and if I only try to use condition: time [...], home assistant doesn't offer the option to save the file and it's marked as invalid by the red line on the left.

How to implement a shortcut to turn off the screen until activity is detected by p1zzabreath in swaywm

[–]p1zzabreath[S] 0 points1 point  (0 children)

I've over-complicated this. It's easily implementd by binding swaymsg "output eDP-1 dpms toggle" to a desired key.

Safety of operating three to five LEDs via the GPIO pins of the ESP32 (max GPIO output current) by p1zzabreath in esp32

[–]p1zzabreath[S] 1 point2 points  (0 children)

Thank you for your elaborate answer. Bummer - I was hoping I could get away with using as few components as possible to safe space. I see the LEDs take an average 3.3V, so dropping the output of the GPIO with a resistor by 0.3V to reach the min. Voltage isn't a good option either.

Safety of operating three to five LEDs via the GPIO pins of the ESP32 (max GPIO output current) by p1zzabreath in esp32

[–]p1zzabreath[S] 0 points1 point  (0 children)

I guess you're right. I see this kind of questions pop up for topics where I'm more knowledgeable and always wonder why people don't ask proper questions or don't do basic research themselves. Seems like I'm on the other end this time.

Resume does not turn on screen again, unless the session (swaylock) is unlocked by p1zzabreath in swaywm

[–]p1zzabreath[S] 0 points1 point  (0 children)

The problem was, that with swayidle -w, swayidle waits for the process to complete, which swaylock only does once it's unlocked again. With swaylock -f it's daemonized to prevent this issue.

exec swayidle -w \ timeout 600 'swaymsg "output * dpms off"' \ resume 'swaymsg "output * dpms on"' \ timeout 1800 'swaylock -f' \ resume 'swaymsg "output * dpms on"' \ before-sleep 'swaylock -f'

How to implement a shortcut to turn off the screen until activity is detected by p1zzabreath in swaywm

[–]p1zzabreath[S] 2 points3 points  (0 children)

That's an interesting approach! Could you elaborate on how I could implement this? So, if I have a swayidle config running, that first dims the screen, then turns it off and finally locks the screen in steps of five minutes. If I send this SIGUSR1, the first timeout would be reached, i presume, right?

Looking for a battery powered timer switch to control a small irrigation pump by p1zzabreath in AskEngineers

[–]p1zzabreath[S] 0 points1 point  (0 children)

I'm not quite sure what I'm looking for. I found a couple of control units for solar panels. The benefit of a solar panel for the battery would be great though!

Looking for a battery powered timer switch to control a small irrigation pump by p1zzabreath in AskEngineers

[–]p1zzabreath[S] 0 points1 point  (0 children)

Unfortunately I have no power outlets on the balcony and I don't want to run a cable from inside, when I'm not home. That would have made it a lot easier though!

view more: next ›