• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle
    • Separate batteries. Using a device for music and a standard phone drains from the same battery. You could carry a power brick, but then you’re carrying two bricks for worse audio.
    • No camera. Certain work assignments won’t allow me to bring a device with a camera into those zones. Or, if I do, the transition process is so intrusive that it’s not worth it.

    Those are the only unique characteristics. You can compensate other differences on a phone like adding an additional DAC and/or amp.











  • In 2016, the first known fatality linked to a self-driving car took place when a Tesla Model S failed to stop and crashed into a semitrailer truck.

    Ah, this one is hard to forget. I remember this one vividly because it sparked all sorts of philosophical discussions around the use of self-driving cars. Hypothetical scenarios like “Between a family of 5 with children, should the car choose to kill the driver to save the family” and the different variations of the trolley problem.

    Determining the responsible party was always a puzzle to me. The current state of auto-pilot requires hands-on attention from the driver, so the accountable party is arguably the driver. But with a fully autonomous vehicle, where the steering wheel isn’t installed, is the car manufacturer accountable for deaths and accidents?


  • I use the Ecowitt moisture sensors for potted plants. Given their size, I wouldn’t recommend using them for your lawn because you have to be sure to not hit them when mowing.

    Automated irrigation systems are reasonably consistent. I moved from my lawnless apartment to a house with a backyard of grass. I left out a few empty containers across the lawn, waited for the first watering cycle, and adjusted the timings based on the distribution.






  • From reading only the article and none of its cited sources: the change requires a $.50/minute increase while the driver is in the middle of a gig, or $17.96 (which is the rounded $18 in the headline). Assuming the driver is literally doing a job every minute (i.e. no gaps in-between deliveries), then that’s a $30 for an entire hour. So the cost-effective alternative is to have the employee on an hourly wage and just pay them $18/hr for x hours that they’re scheduled for. The quotes in the article explained how the switching from a per-job model to a “do as many jobs in the hours we schedule you for” means they’ll lose the benefit of flexible work schedules.

    That said, I think the economy will speak for itself. Given the number of times I see companies complain in the media about “nobody wants to work”, they’ll need to pony up the money in order to maintain their share in the market.



  • I’m a few versions behind, but I’m using the add-on without issue. A few things I would check if my setup failed:

    1. The wrapper has 2 major components. Make sure you’re running both of them.
    2. Slim down your config.
    3. You mentioned you have your own decoders. Double check the rtl_433 version that’s being used in the add-on to ensure everything is compatible.

    From the /r/homeassistant lurking days, I know that some other people skip the add-on in favor of using a script or another machine that proxies the data into HA. So there are a few other options in case the add-on approach doesn’t seem to be working quite right.


  • Overall, not surprised.

    Couple of points I noticed were missing:

    1. No race-related data was reported regarding the Model 3.
    2. No data at all from the Model Y.

    These are their most affordable models, so I’m reading this article in terms of the Model X & Model S, and not every owner. The data did say that the Model 3 was predominantly male-owned, and I expected nothing less from a car marketed as a sports car.

    A state that was once identified as “Camry California”, the Model Y exceeding Camry sales in the state is a big enough deal to include that data to qualify an article that describes all Tesla owners.