I bought a Home Assistant Voice Preview Edition to try out. It's surprisingly good, but still falls short when compared to Google Home speakers:
- Wake word detection isn't as good as the Google Homes (more false positives, more false negatives - so I can't just tune sensitivity).
- Mic and speakers are both of poor quality in comparison to Google Home devices.
- Flow is awkward. On a Google Home device, you can say "Okay Google, turn on the lights" with no pause. On the Voice PE, you have to say "Hey Mycroft [awkward pause while you wait for the acknowledgement noise] turn on the lights" - it seems like the Google Home devices start buffering immediately after the wake word, but the Voice PE doesn't.
- Voice fingerprints don't exist, so this prevents the device from figuring out that two separate people are talking, or who is talking to it.
- The device has poor identification of background noise, so if you talk to it while there is a TV playing speech in the background, it will continue to listen to the speech from the TV. It will eventually transcribe everything you said + everything from the TV and get confused. (This probably folds into the voice print thing as well.)
On the upside, though:
- Setting it up was really easy.
- All of the entities I want to control with it are already available, without needing to export them or set them up separately in Google Home.
- Despite all of the above complaints, the device is probably 80-90% of what I realistically need to use it day-to-day. If they throw a better speaker and mic array in, I'd likely be comfortable replacing all of my Google Homes.
Mysa thermostats - don't integrate well with Home Assistant and can't even reliably follow schedule.
Every Samsung phone I've ever owned - great hardware, but the software is a mess, especially with all of the Samsung apps that duplicate the Google apps.
Sony smart TV - was excited about running Android TV apps, but the onboard hardware is so bad that everything lags, and I actually ran out of space after installing 10-20 apps (it only has 4GB of flash storage). Also, its Ethernet adapter has a hardware bug that occasionally freezes up my entire network by spamming it with flow control frames.
I've got this running on several units and it works great. If you buy ESP32 development boards with pre-soldered pins, you can even build the boards without soldering.
I'm especially curious about which ones are earning "life-changing" money for their authors. I couldn't find an easy way to list Substack newsletters by subscriber count, though. (By revenue would be even better.)
Roblox | Senior Software Engineer | ONSITE (San Mateo, CA, USA) | Full time
We are hiring systems engineers experienced in C++ to work on the game engine that powers our platform, supporting extensive user-generated content from 2M+ developers. We have three roles we're actively hiring for:
The Engine Networking Team pulls the players together by ensuring the communication of the game state to all. You will help the players experience the game as a nearly synchronous world.
The Foundation team works on the building blocks of Roblox itself -- core C++ libraries. Your work will touch every part of the engine, from threading and memory management to physics and scripting.
The Reliability team works to ensure that the Roblox Engine is as stable, reliable, and debuggable as possible. You will work to ensure that Roblox delivers world-class user experience while also supporting internal developers to root-cause issues and prevent recurrence.
You can install the microcode driver to have Linux provide the updated microcode, if you'd like. (Depending on your distro, it might already be doing it.)
I think the big issue is the different "tuning" for each heat pump system. For example, a heat pump water heater needs a different maximum temperature than an air conditioner, and has much different cycling behavior. This leads to very different design decisions, including refrigerant choice, pressure, compressor type, whether the refrigerant loop is even serviceable, etc. (Some appliances operate at a refrigerant pressure so high that they require being fully assembled at the factory, which would be a non-starter for a manifold system like we're discussing.)
I think this might eventually become a thing once science gets us far enough that there's an "obvious" refrigerant choice for most applications, but we definitely aren't there yet. There are hundreds of different kinds that perform better or worse in different applications.
AFAIK all of the big commercial systems that do multiple different types of heat transfer use water to do it, thus bypassing the entire refrigerant selection issue. Right now the most advanced we can do is VRF ("Variable Refrigerant Flow") systems that can individually select air handlers for cooling or heating (i.e. move the heat from one room to another). These are still commercial units and not really available for residential installs.
Just because a device isn't cloud-connected doesn't mean it isn't designed for planned obsolescence. For example, the ongoing cheapening of major appliances, or the DRM applied to printer cartridges and coffee pods.
This is a legislation problem IMO: companies need to be held to reasonable expectations when they sell a product. My ink cartridge shouldn't say it's "empty" when the page counter reaches 100 [and it's still actually full]. Neither should cloud devices go to the landfill because the company selling them decided that they don't want to support them anymore.
Companies foisting negative externalities on us (like more e-waste) in exchange for more profit are a blight and should be treated (and prevented) as such.
Anything dense (e.g. lasagna, meatloaf, etc.) is good for a lower power level / more time trade-off. It will end up more evenly warm without the edges exploding. I usually use power 3 or 4 for these dense dishes.
Panasonic "inverter" microwaves actually do reduce the power output. It's one of my favorite features. On power level 1 you can actually soften butter without melting random pits into it.
Unfortunately, at least on my current model, the UX to access this feature is very bad: repeatedly pressing the "power" button until it reaches the desired level. I've had other microwaves where you just key in the desired power after pressing "power", and much prefer that method.
I don't know whether Panasonic has licensed this to any other manufacturer.
Good. Spam calls and texts are a blight, and nobody was doing anything about it until regulation kicked in.
Last year, after receiving several spam texts from numbers that were registered to Bandwidth.com (which was already difficult to discover), I sent an abuse report. I was not only told that Bandwidth.com couldn't do anything about it (other than forward the report to the reseller), but also they couldn't even tell me who they were reselling services to due to privacy reasons, and did not even know who the end customer was. They advised me to contact the police... To report text message spam.
On most (all?) carriers, you can forward spam SMS messages to 7726 ("spam" on the keypad) to report messages as spam.
That said, I've got no idea if they actually do anything actionable with this data. It certainly doesn't seem to have reduced my spam volume. Now I just let Android Messages filter the spam out.
Assuming you're using Chargepoint level 2 chargers (3.3/6.6kW AC, not DC fast chargers), they are reporting energy delivered. There is no data channel to report energy stored; only level 3 (DC fast charge) charging ports establish a data connection.
FYI, it looks like you've been shadowbanned ever since a rather uncivil comment in 2013. Most of your recent comments are dead, the rest I assume someone hit "vouch" for.
- Wake word detection isn't as good as the Google Homes (more false positives, more false negatives - so I can't just tune sensitivity).
- Mic and speakers are both of poor quality in comparison to Google Home devices.
- Flow is awkward. On a Google Home device, you can say "Okay Google, turn on the lights" with no pause. On the Voice PE, you have to say "Hey Mycroft [awkward pause while you wait for the acknowledgement noise] turn on the lights" - it seems like the Google Home devices start buffering immediately after the wake word, but the Voice PE doesn't.
- Voice fingerprints don't exist, so this prevents the device from figuring out that two separate people are talking, or who is talking to it.
- The device has poor identification of background noise, so if you talk to it while there is a TV playing speech in the background, it will continue to listen to the speech from the TV. It will eventually transcribe everything you said + everything from the TV and get confused. (This probably folds into the voice print thing as well.)
On the upside, though:
- Setting it up was really easy.
- All of the entities I want to control with it are already available, without needing to export them or set them up separately in Google Home.
- Despite all of the above complaints, the device is probably 80-90% of what I realistically need to use it day-to-day. If they throw a better speaker and mic array in, I'd likely be comfortable replacing all of my Google Homes.