Huh, I wish my town would do those corner protectors. There’s one corner especially, a block from my house, and on a major walking route to our neighborhood elementary school. After it snows, I frequently see tire tracks across the sidewalk from people who cut the corner badly. One of these days, they’re going to run over a kid on the sidewalk on their way to school.

Anyone try Rancher? Is that still a thing? When I looked into k8s a few years back, Ranchers was highly recommended to simplify managing k8s if you couldn’t automate. Supposedly friendly and free.

Tesla always had “light show” as a fun gimmick. It’s one of the first things you show friends and family.

There’s a few canned versions but apparently you can create your own on usb stick. Supposedly it was an outgrowth of qa, so it includes things like windows and trunk opening and closing, side mirrors folding and unfolding, all timed to music, etc. Even before the active matrix headlights were approved for regular use, one of the canned light shows used them to spell out “Tesla” on whatever is in front of you.

A recent update mentioned new light shows and a way to synchronize. I can certainly imagine a Tesla club having great fun with this

Step 0. Make sure your networking equipment can do vlans and subnets.

Given how much I paid for a “high end” consumer router, I just assumed ……

I got into each mesh technology for specific devices. Home Assistant supports them all and they seem to coexist just fine in my use case.

I have a small to medium setup with only a few simple automations and a focus on voice control and scheduling

Preference

• Thread - given Apple, Amazon, and Google support and the standardization work, I expect this to be the future. Eventually. But I’m getting impatient. If I’m buying a device, I prefer Thread but usually it’s not yet
• z-Wave - my first, and most devices. Basically this was what was most available at local stores when I started. No complaints
• Zigbee - by far the biggest selection of simple, cheap sensors. I need to more of those
• all too much is WiFi but I try to avoid

But it also helps that my approach is generally switches and outlets. Hard-wired, predictable network, tend to be repeaters. I have comparatively fewer leaf nodes.

This approach also fits in with my biggest challenge. While my house is small, it’s an older one with dense materials that blocks a lot of radio signals. For example I have no cell phone reception inside yet strong signal just out any door. My focus on switches and outlets overcome this with a repeater in every room

So for example a few years back I got a z-wave IR blaster to control a mini-split AC because at the time I mostly used z-wave. I already had a z-wave light switch in the same room, acting as a repeater, so no worries about connectivity. Now I have both z-wave and Zigbee light switches in that room so expect both meshes to be strong for any future devices in that room

I’ll also vote to reconsider WiFi. Home Assistant supports a variety of local mesh networks that by default can’t connect to the cloud and whose devices are cheaper and lower power.

I use all three of zwave, Zigbee, and thread; ha works with whatever you need.

I choose to pay for remote access, but it’s for convenience and to support the developers. You are free to configure it yourself in a couple ways (and there is decent documentation) or do without remote access

I don’t know how you set up remote access for OpenHab, but from a quick glance at the web site it looks similar

Wait, really? You’re telling us there are rural areas with unreliable electricity, yet are piped for gas?

Why not both? Even before I understood the indoor pollution caused by gas stoves, I never understood how it was legal to have a “vent” blowing supposedly filtered air back into the kitchen. cooking causes pollutants and should always require venting to the outside

Another warning label is a step. It will raise awareness and convince some. Most importantly it should ease the process for more significant steps.

Given that induction ranges are so hard to find and so much more expensive, I hope the warning can lead to incentive programs to convert. Maybe having a predictable and growing market will help companies with the decisions to manufacture more choices at more reasonable cost

My reading of this article shows the judge issued a temporary injunction saying the evidence suggested looks like the manufacturers will win. That is something a judge should decide.

It’s the wrong decision but we don’t know what was presented or how.

I believe it hinges on “controversial” but how do you give the controversy any credence when it is only manufacturers with a profit motive to disagree with science?

I’m not entirely sure why all the hate : Jenkins can do the most things the must ways. And yes, it’s so much nicer defining a pipeline with a fully functional language than an assortment of yaml files

Actually that was my response when my company wanted to start using Gitlab ci. It only has one way of doing things so you can probably get a faster start if you had no ci, were a small company, and had simple builds. However we’re over 4,000 builds in many languages from 12 year old monoliths to modern micro services and containers…… and way too much godawful JavaScript. Do you want the quick and simple tool great for a small startup or the all powerful kitchen sink of tools?

I’ve wondered if people’s watch lists are prioritized to be pay videos. The first time I saw this I wondered why my watch list was mostly pay videos: I must have misunderstood something. So I created it again with only free shows. A year later it was mostly pay

In the us, Tesla has a much higher reputation for chargers that actually work when you need them. Usually the credit goes to better sensors and more responsive service, but an underrated factor is larger charging stations with many more chargers. One failing of twelve is less impact than one failing of four, for example.

As yet another anecdote showing how regressive/spiteful US treatment of EVs is …… over the summer I saw an article about a new vendor winning contract for New Jersey rest areas. Part of the contract was to replace 12 charger Tesla supercharger rest areas with “equivalent” four charger that cost 20¢/KwH more

Yeah I think it’s mainly North America (us?) that’s the problem.

However the standards process worked, it created poor choices and was not effective. Twice. At least we’re finally coalescing on a de facto standard, and NACS is better than the previous two choices

But yeah the app situation is bad. While I appreciated using chargers that use my cars internal ID, and just worked, that clearly doesn’t scale. Now that we’re trying to scale out to general use so we really need credit card readers instead of a plethora of apps.

Not requiring an app was one of the prerequisites for federal incentive money, but the short-sighted administration retracted that

Sprint is an interesting example because I believe regulators did block previous merger attempts on exactly those grounds.

It’s yet another case subject to the whims of whatever administration is in charge, and we’re stuck with the fallout

Fwiw I like ll beans. It’s quite expensive but really durable

Home Assistant hs communities to share exactly that

My similar script has a very different goal: at midnight if someone is still up, it dims the family room light and announces on speaker”hey kids, it’s time for bed”

It could probably do a decent job generating those scripts, given adequate prompting and a few cycles of feedback from you. But it’s almost never a final result. It’s still on you to know what it’s doing and whether it meets requirements, whether it’s sufficiently performant and scalable, whether it’s resilient and flexible. Most importantly it’s up to you to ensure good quality that future you can read and maintain.

Complexity or “complexity”? A couple months ago I had to accept a merge from a junior developer that is now flagged as the code with the highest complexity in my code base. It was in Groovy and he must have just discovered closures. Instead of breaking up the code in nice modular testable blocks, it was massive methods hundreds of lines long, and the most egregious use of closures