271–280 of 324 posts
Earlier quoted context omitted.
fwiw, I got us booting on GCE years ago, and the scripts may still work. https://cs.opensource.google/fuchsia/fuchsia/+/main:scripts/...
"permission denied"
Earlier quoted context omitted.
Rhasspy is an easy to use open source, fully offline, suite for this with wake word detection and integration with home assistant.
I've never understood the desire to control systems by speaking to them in code words. Speaking monopolizes a shared channel, requires diverting your conversation, and is really slow. For practically anything that involves using code words to tell the computer what to do there are better input methods, like physical switches, or purely automated. This is slightly off-topic, but in your opinion what are some of the re…
When the light is off, the switch is invisible and you have to guess at where it is, or where you need to be walking (hitting your shins on things, or stepping on lego)
Using a non-light based interface means it works just as well when the light is on and off, vs being a broken experience for half of the usecases
Earlier quoted context omitted.
If I'm curled up comfortably with my SO, and don't want to take ten minutes of unwinding, doing whatever, then tucking back up together...
It seems like in that case a remote control could be placed nearby -- are you also using voice activated code words to control the television ?
Earlier quoted context omitted.
You don’t want a remote-controlled smart (actually: dumb) home. You want a fully local solution, then you can add remote, internet-dependent functionality like alexa to it. That way your primary mode of control will always work.
And get some motion detectors. Your lights should come on when someone enters the room and the light is below a threshold. I usually hit the off switch by the door when I leave, otherwise if no one is present the lack of movement will dim and then turn the lights off. It's 2021 people!
Earlier quoted context omitted.
The key concepts are documented here: https://fuchsia.dev/fuchsia-src/concepts Some things that Fuchsia was able to do thanks to starting from scratch: - The system is based on capabilities, a security model which is based on explicit tracking of permissions. It wouldn't be possible to change Linux to be capability-based because the ambiant-authority model has been used pervasively since it was conceived 30 years ago…
> Fuchsia provides a stable binary interface (like Windows, but unlike Linux). Linux does provide a stable binary interface, to userspace . > eg. binary drivers from a hardware manufacturer that wouldn't provide updates for them anymore That can be seen as much as a downside as an upside, because it makes life a lot easier for hardware manufacturers to ship more binary blobs
Which is essentially the point of this approach for Google, to exert greater control.
Would this solve the extreme UI lag and make google hub finally useable?
It really depends on the polish of Fuchsia for Nest Hubs. Getting a few more FPS out of the 1st gen hardware is something I'm actually hoping for because it's gotten really slow and I rarily touch the screen anymore because of the lag.
10 years ago I would be really excited, as I could expect some groundbreaking tech like search engine or revolutionary approach to something, like Gmail (no ads sent to users, great UI, hige disk space). Today, instead of excitement, I am wondering how this thing is going to push me in some walled garden, how I will be tracked, how my data will be fetched and sold, what will be the trick used to move people away from…
I've been worried about it since they announced it which feels like it was 10 years ago.
Earlier quoted context omitted.
I never bought in to the premise of the "smart home." It sounds like endless minor annoyances and aggravation more than anything.
In my experience it brings minor conveniences: yelling at Google or Alexa to turn on the kitchen lights when your hands are greasy, or dimming the lights with your phone when you're sitting on the couch with a cat on your lap. None of these are huge selling points, but once in place they're nice. If done right, though, the system just degrades gracefully to a normal set of switches.
I'm in a rental, so instead of smart switches I just use smart bulbs. For like Most are configured so turning them on turns them on full brightness and pleasantly warm. The one in the bedroom and the baby's room are configured to turn on dim and warm, and if you do another quick off-on flick of the switch they'll come on at full brightness.
So they... work like normal light bulbs. Except they're all remote controllable from your phone. So if the baby falls asleep on top of you and the light's on you can turn it off without getting up and waking her up.
From there, I added some basic z-wave sensors in a few spots in the house. If you get up in the middle of the night to use the bathroom, as soon as you step in the hall the motion sensor picks up that (1) someone is moving in the hallway and (2) the hallway is currently really dark; and it turns the hall light on a really dim red. Enough you can see where you're going without killing your night vision. Then a minute after it stops sensing motion it turns off.
If you walk into the one end of the basement where the washer/dryer/workshop/storage/etc are, all of the lights will come on for you, and a couple minutes after it stops sensing motion they all turn back off. If you want them to stay on you can just flip the switch off-on to turn them all on and keep them on. So now if you just wander over to let the dog out, grab a tool from the shop, throw a load of laundry in, etc, the lights are just automatic. No need to try and balance a laundry basket while you screw around with light switches.
The room my office is in does the same thing except uses my computer's lock state for presence detection. So when I walk in the lights come on, when my computer unlocks it keeps them on. When I lock my computer it goes back to the regular program. At any point I can pull my phone out and flip them over to the super bright, super harsh light when I need it for doing fine work instead of working at my computer.
Just a lot of little, basic conveniences. And it's amazing how futuristic it feels to just wander around the house and have lights turn on and off for you as you do.
It all runs locally in a VM on my server, with all the smart devices entirely isolated from the internet. If the internet's out... nothing changes. If my server/WAP/whatever dies, then my house just goes back to working like a normal house.
Earlier quoted context omitted.
> Fuchsia provides a stable binary interface (like Windows, but unlike Linux). Linux does provide a stable binary interface, to userspace . > eg. binary drivers from a hardware manufacturer that wouldn't provide updates for them anymore That can be seen as much as a downside as an upside, because it makes life a lot easier for hardware manufacturers to ship more binary blobs
> That can be seen as much as a downside as an upside, because it makes life a lot easier for hardware manufacturers to ship more binary blobs Which is essentially the point of this approach for Google, to exert greater control.
When the goal is, to support a broad range of devices - and the vast majority of hardware manufactors are not into open hardware - it is probably easier, to convince them of supporting Fuchsia by writing firmware and drivers - if they do not have to deal with the GPL and the kernel driver integration, like it is the case with linux. They just write their driver once against a stable API.
That makes things easier.
And google are not driven by free software ideals - but rather buisness pragmatism. But I don't see this design choice as an attack on free software.