spongebue

As a parent of a toddler in this program (one who is getting 4 provider visits per week, was going to be cut to 4 per month) I'm glad to have gotten an email late Friday saying that there will be no changes to services at this time. Still, this week has been a clusterfuck for us and especially our providers!

In the past I've gotten around this by printing on the left side of the bed, but some things need the space so here I am.

I've got an Ender 3 V2 with some tasteful mods: OctoPrint, BLTouch, a magnetic flexible bed surface, and a few other things people are bound to do with an entry-level printer they got for $100 with a Micro Center coupon. One issue I'm having with it is that any printing done on the right side of the bed seems to have a pretty big gap. I have the G28 and G29 commands in to run the bed level, I try to get it leveled properly with the springs (with help of the bed visualizer plugin for OctoPrint) and no matter what I do, the nozzle drifts just a little farther from the bed on the right side, so the filament does not stick.

I'm open to more mods, but before I spend more time and money on this for what I think is the problem, does anyone actually have a good idea of what's wrong here?

Thanks much!

Solved!

Solution was to create a group and perform an action on that:

action: light.turn_on
target:
  entity_id: light.kitchen_cabinet_sink
data_template:
  brightness_pct: "{{100*state_attr('light.kitchen_sink_ceiling','brightness')/255}}"

Original:

Trying to run an automation to match one light's state (on/off/dim) to another's. Have this currently:

alias: Sync cabinet lights with sink light
if:
  - condition: device
    type: is_on
    device_id: [something]5710
    entity_id: [something]a438
    domain: light
then:
  - type: turn_on
    device_id: [something]b447
    entity_id: [something]470f
    domain: light
    brightness_pct: 100
else:
  - type: turn_off
    device_id: [something]b447
    entity_id: [something]470f
    domain: light

That works fine to turn the lights on or off, and I have triggers in the automation for that and changes in brightness. But using a non-static number for brightness_pct (yes, I know I'll probably have to math the 0-100 scale instead of 0-255) is giving me trouble. When I try something like this:

alias: Sync cabinet lights with sink light
if:
  - condition: device
    type: is_on
    device_id: [something]5710
    entity_id: [something]a438
    domain: light
then:
  - type: turn_on
    device_id: [something]b447
    entity_id: [something]470f
    domain: light
    brightness_pct: {{state_attr("light.kitchen_sink_ceiling", "brightness")}}
else:
  - type: turn_off
    device_id: [something]b447
    entity_id: [something]470f
    domain: light

I have also tried {{states.light.kitchen_sink_ceiling.attributes.brightness}} instead. Both seem to have the correct value when I play around in the developer tools. But when I put it in the automation, I get an error that a float value was expected. I see some similar issues online, but it always seems to be in a different context and people fix it by changing some value I never had.****

My, how the tables have returned!

Year and a half old. It may feel silly, but she's always been in the single-digit percentile, usually low-single-digits at that. She was born about 3 months premature, and after her weight gain stalling, they prescribed a medication with a side effect of increased appetite to give things a jump start. I think it's going to work 🙂

So many instructions to cut an onion are essentially

1. Cut off the top
2. Peel
3. Cut in half
4. Cut horizontally (in parallel to the cut you just made)
5. Cut vertically into strips from just shy of the bottom to top, with the bottom holding things together
6. Cut vertically perpendicular to your last cuts to get little squares

On something like a potato, I'd understand it. You'll be cutting a 3-dimensional object along all 3 axes to get cubes. But as Shrek taught me, onions have layers. Why make that first set of horizontal cuts when the onion's natural layers do the same thing already, albeit a little bit curved?

Running on a Raspberry Pi 400

Lately my home has been dumb and unassisted at random times, and the HA app can't connect to my HA rpi server. Ditto when I go to homeassistant:8123 in a browser. I'm trying to see what's causing this, but the logs in app only show since last restart. Tried plugging my Pi into a monitor and getting something from the command line but not sure how to do the equivalent of a Linux tail or whatever. Searching was surprisingly unhelpful. Any advice?

Thanks much!

I get that some instances use the domain + TLD to make a word, like lemm.ee or to an extent, sh.itjust.works. But I've seen so many TLDs I had no idea existed, like .world, .zone, .social, and yes .works as well.

Is there any real reason for that? Trying to look cool or kinda underground-y? Cheaper and more varied domain options? Something actually kinda functional?

Interestingly, I started on vlemmy.net because I was a scared Reddit refugee and the .net TLD gave me comfort. Then it vanished a few days later without a trace. So here I am on lemmy.world

I originally created this community to post a few of my own projects and get a few others, but found retrolemmy before I could post anything. I'll still keep my lemmy.world account and all, but in the interest of keeping themes within instances, I think retrolemmy is a better fit. Admin, feel free to nuke this community if you wish! I don't see a way to on my end.

[email protected]