I love my e-bike. It sounds like you bought an electric dirt-bike. I'm not going to call you an idiot: the market is confusing and not well regulated, manufacturers are taking advantage of this. There have been some improvements with regulation to promote safety (both for you, as the unaware rider and for others). It's possible where you live it's not legal to take your new e-bike on the road without a motorcycle license OR on bike paths. Be safe, double check your local laws. If it's not legal: return it.

Having switched to zigbee devices recently I regret trying to start with WiFi. While I'm not sure how it looks under the hood, adding devices with home assistant was miles easier.

I've helped lots of people with home automation Network build outs l; the biggest factor is the RF environment.

If you're fortunate enough to not be battery constrained at most endpoints and can put a high quality Wi-Fi access point in an optimal location than Wi-Fi is incredibly reliable.

The tooling for inspecting all layers of a Wi-Fi network is infinitely more accessible and mature and that certainly helps; I can't go to My local big box store and get a USB thread dongle for 20 bucks that will just work on a Lennox computer and integrate nicely with Wireshark out of the box...

No, you have to order it from Mouser for $16 instead.

Fixed link: https://www.mouser.com/en/ProductDetail/Nordic-Semiconductor...

And there’s a little configuration: https://wiki.makerdiary.com/nrf52840-mdk-usb-dongle/guides/n...

Dead product link

Sorry I thought I was removing tracking bits from the URL. It’s fixed now.

I have a Unifi home network with two Wifi 7 access points and gigabit ethernet. For home automation, I went with ZWave and do not regret it at all. It's been rock solid and I've never felt the need to get a dongle to debug the traffic. I don't want to be working through all of the WiFi baggage with my home automation devices. I recently introduced some Zigbee bulbs (hue and cheapos from Amazon) and they've been mostly "fine", albeit with lower range.

> For home automation, I went with ZWave and do not regret it at all. It's been rock solid and I've never felt the need to get a dongle to debug the traffic.

That's because zwave requires everything go through certification process. You pay more for this, but things generally just work.

It's an entirely different situation in zigbee land though.

I stick with ESPHome and MQTT because I can inspect and modify the behaviors of everything with free and open tools.

Wi-Fi was never unreliable. The devices that used WiFi were much worse to work with and setup.

Thread is fairly similar to Zigbee, just standardized and doesn't require brand specific hubs. You can actually control thread devices direct from an iphone with no hub at all.

Wifi for anything but cameras is a mistake, it only exists for maximum compatibility since everyone has wifi already.

My matter over thread devices (inovelli) for light switches work faster and better then my old wifi devices (cync)

Wifi for cameras is arguably also a mistake

Cameras that require internet to connect to are a mistake, but cameras that use Wifi for local link are fine (wifi is perfect for this). And, having some way to connect remotely is a requirement, for most everyone.

I took their point to be about wifi being jammable

And be sure your outdoor cameras are on an isolated VLAN so people can't just plug in to your home network.

Yeah, not sure why people are downvoting you. I suspect because most people run wifi cameras and don't see the reason to run a ethernet cable.

If you are halfway serious about your home security, you should use ethernet. It's trivial for thieves to jam wifi now.

I read this as sarcastic but it's a thing. Simplisafe, for example, is trivially jammed.

Security system that can be jammed is a terrible idea. Cameras should be wired. Ideally on separate network and with battery backup.

Can you elaborate?

Location and time

They already have that from your cellphone

That's known as Transmitter Hunting (aka Fox Hunting).

It's a fundamental flaw of most wireless communication. Are you referring to something more specific?

I think that is more of a directional antenna approach? I’m more talking about triangulation, we used to be able to do it with cell towers and if you had 3 or more in range we could get pretty accurate location (now that seems to be locked down).

There something amazing about that. Thanks for pointing it out!

On a recent project we joked "developers can't read". Occasionally we'd ask for help and be pointed to the docs "I can't read".

I suspect there's two big parts to this:

1. Users expect batteries included and that everything "just works" the first time.

2. The language you used differs match your audience. E.g they search "gray" and find no results, however you've spelt it "grey"

Profiling[1] your own repository and tweaking as necessary (possibly disabling auto-status refresh) will likely yield significant performance improvements.

I use magit with a very large repository (100k files, millions of commits) it's still not lightning fast like it is with smaller repositories, I'm still finding it an improvement over the CLI.

My config notes this saves me ~13 seconds in git-status

  (remove-hook 'magit-status-headers-hook 'magit-insert-tags-header)

[1]: https://docs.magit.vc/devel/magit/Performance.html

Bikes typically have a weight rating. Mine has 150lbs of cargo capacity (is a cargo bike).

I don't know if this figures into the engineering formulas, but an e-bike needs to be stronger due to the higher speeds and power levels. On a human powered bike, if you're hauling 150 pounds, you're probably going pretty slow.

My friends who have e-bikes go through a lot more "consumable" parts such as chains, tires, brakes, cogs, and bearings.

Context switching like that is exhausting

It's a different kind of fatigue, but it's something a felt I got stronger at over time. Beats waiting IMHO, but be sure to give yourself a chance to rest.

really interested in what the brain does when it "loads" the context for something it's familiar with but is currently unloaded from the working memory. Does it mostly try to align some internal state? or more just load memories into fast access

The next step is running an LLM that tries to figure out parts of the project that you aren't working on so it automatically starts coding that while letting you code in peace other stuff manually.

Depends on the person I guess