Earlier quoted context omitted.
> EVERYTHING MUST FAIL NORMAL. I'm often surprised how little discussion I see of failure analysis and especially failure design is in software engineering. It is one of the most important concepts in engineering, but I guess we still operate like software can't kill you. For those unfamiliar with this type of analysis I'll give you 3 examples. 1) Imagine you are building skyscrapers in city with a bunch of other sky…
The concept of "Safety Critical" is something that I wish more software developers and engineers would have exposure to
I built an offline smart home
171–180 of 192 posts
Re: I built an offline smart home
#172Earlier quoted context omitted.
> EVERYTHING MUST FAIL NORMAL. I'm often surprised how little discussion I see of failure analysis and especially failure design is in software engineering. It is one of the most important concepts in engineering, but I guess we still operate like software can't kill you. For those unfamiliar with this type of analysis I'll give you 3 examples. 1) Imagine you are building skyscrapers in city with a bunch of other sky…
> Failing closed is typical of safes Unless it's a very large safe where people can walk inside, like a bank vault. The fire department gets very grumpy with you if they fail closed and can trap people inside. So if you want to force open a bank vault, stage a purported terrorist attack, and the FBI will cut power to the building as standard operating procedure. Voila, vault opens.
Re: I built an offline smart home
#173Earlier quoted context omitted.
The next best thing I've seen are the smart switches that are just two buttons, up and down for on and off. I just want to be able to hit up for on, the actual switch state is less of a concern. That's been my annoyance with two-ways. I've ordered some Inovelli switches which do this and have an RGB LED if I need a state status indicator.
Grew up when they were always switches... not sure I can change. I can't feel around in the dark for two buttons, and know what the hell they are.
Re: I built an offline smart home
#174Earlier quoted context omitted.
> EVERYTHING MUST FAIL NORMAL. I'm often surprised how little discussion I see of failure analysis and especially failure design is in software engineering. It is one of the most important concepts in engineering, but I guess we still operate like software can't kill you. For those unfamiliar with this type of analysis I'll give you 3 examples. 1) Imagine you are building skyscrapers in city with a bunch of other sky…
> Failing closed is typical of safes Unless it's a very large safe where people can walk inside, like a bank vault. The fire department gets very grumpy with you if they fail closed and can trap people inside. So if you want to force open a bank vault, stage a purported terrorist attack, and the FBI will cut power to the building as standard operating procedure. Voila, vault opens.
Re: I built an offline smart home
#175Earlier quoted context omitted.
But why are people surprised then that in most software the process is not as thorough as in aerospace or elsewhere with physical things. Most of the time physical devices failing will have much more severe consequences, than a website going down for an hour. In some cases there are APIs which many other critical systems use and frequently those APIs do have much more rigorous process in making sure that they are rel…
> But why are people surprised then that in most software the process is not as thorough as in aerospace or elsewhere with physical things. Outside of engineering, few people have ever even heard the phrase “risk management”, let alone understand the theory behind it. It’s really hard to argue that a developer can consider themself an engineer, when they don’t bother understanding what happens when the thing they “en…
And not to say there aren't plenty of software engineers that do failure analysis. I mean we do have exceptions, exit codes, traces, and even QA (though many hate them). But I'm not under the impression that the idea is as ingrained in the average software engineer as it is in the average engineer. Having taught CS I've been surprised at how much less time is spent on this topic and how less explicit it is usually discussed when compared to other engineering disciples. The same goes for ethics which I think go hand in hand here. My impression is that this is because when software harms it is often less tangible and less direct than in other engineering disciplines where it's obvious how a bridge failing causes substantial harm and economic impact but where a failure to protect against injection in your not mainstream platform also causes large damage because people reuse passwords and that passing the buck to user error is unacceptable given that it's expected behavior from the user (work on expected behavior and account for unexpected behavior but never rely on domain knowledge unless under special circumstances). We all know everyone reuses their Gmail and bank password on websites like Netflix or fucking neopets.
We wouldn't have as frequent front page posts about users getting accounts unlocked only due to the fact that they were able to go viral if software engineers better planned for failures in the system. Do Gmail devs really deeply think about what happens when someone loses access to their account? If there's a means of recovery if they're devices are also taken or destroyed? That this solution works in practice, not just theory? Do they audit and dogfood this process to ensure it's working properly and understand how it fails and the consequences of that? I'm assuming no because we see people locked out of these systems ("these" because I'm generalizing beyond Gmail)
Re: I built an offline smart home
#176Earlier quoted context omitted.
The concept of "Safety Critical" is something that I wish more software developers and engineers would have exposure to
100%. But I really hope that they can learn this concept and understand that it is generalizable and need but require a system that is critical nor dangerous. That the same ideas are essential for simply designing good user experiences. It's really frustrating that this isn't understood well in ML where people end up talking past one another and therefore the extreme ends of the spectrum end up dominating the convers…
Re: I built an offline smart home
#177I went with the Apple HomeKit compatible camp, because it does indeed all work locally across your local LAN without a network connection - its not foolproof, but it mostly just works, and works well at that - and more importantly works when the internet is out. The biggest thing with Apple is they get that houses have more than one person living in them, and provided everyone has an Apple device, it all just works.
I've been pretty happy with HK augmented by Homebridge. However, I'd go out of my mind if it weren't for the Controller for HomeKit app[^1] to allow backup and restore, and it's still not perfect due to Apple restrictions on how third-party apps are allowed to interact with HK. Controller also is the only way to access more advanced automation options that are impossible to do through the Home app. Just the other day…
And other Apple restrictions. I've got a lot of stuff looking really good with this combo. And then I added a Brilliant (https://www.brilliant.tech/home?tab=system) Smart "Outlet", particularly for my living room, which has six can Hue lights, and a lot of ambient stuff around the TV - it's great for driving a lot of scenes, daylight, evening warmth, media (where the front row of cans are off), etc. But it could also so a lot more that would be nice (Christmas lights, which are off a smart switch etc.) - except Apple doesn't allow external devices to initiate HomeKit actions. So a lot of potential usability is lost.
Re: I built an offline smart home
#178Earlier quoted context omitted.
> EVERYTHING MUST FAIL NORMAL This is the Mitch Hedberg Rule. "An escalator can never break: it can only become stairs. You should never see an Escalator Temporarily Out Of Order sign, just Escalator Temporarily Stairs. Sorry for the convenience. "
I hate that quote, because it's dangerously false. Even if the power is off, that doesn't mean it's safe to stand on it. One example would be if the gearing breaks so that the segments move freely: Congratulations, you and the crowd--given false confidence by a comedian's joke--just piled onto the top of a downhill treadmill... It will now accelerate until you crash into a smothering crunchy heap at the bottom.
Re: I built an offline smart home
#179Smart Home has kind of been my hobby for the last 7-8 years. I have well over 100 devices controlled by my smart home setup. Before I installed the first smart device in my home, however, I had a single requirement: EVERYTHING MUST FAIL NORMAL. By this I mean that if the internet went out or a vendor went out of business or I rage quit a vendor, then the device in question had to act like it was a normal non-smart de…
> after bedtime, the lights still come on when someone goes in the bathroom, but very dim, etc. I’d be curious to hear more about this. Most of the “smart” light solutions I’ve tried struggle to go directly to a specific lighting level without some bright flash as they activate. What brand switches/lights are you using to do this with?
I’d stay away from consumer grade stuff, it’s pretty much all garbage. Commercial controls will come with a 5 year warranty.
Most commercial lighting controls have 0-10v dimming, but you can get forward or reverse phase line voltage dimmers to use with consumer grade LED lamps (bulbs).
Re: I built an offline smart home
#180- HA have a slick UI, but it's a MONSTER, less monstrous maybe then OpenHAB but still a monster, I HATE it's YAML config, it's use of SQLite is well... And it's less horrific way to deploy, by pip in a virtual environment is meh, at best;
- wires are needed for reliability, but while ShellyPro and WaveShare seems to be reliable (in few years almost no issues) they are still limited, damn expensive and not much comfy to keep them up to date automatically and centrally. In general most IoT products are crap at best, badly documented, buggy, dysfunctional and damn expensive;
- most sound reasons for home automation lay in energy saving/automation, I normally see no sound reason to switch on the lights from a mobile phone instead of a physical switch for instance, but most appliances seems to be designed without any clue on how they can be used and integrated. A small example, I have a Daikin/Rotex heat pump for domestic hot-water, it's not really a small economic device, well: just to read water temp to makes decision I need a 300+€ extra card, my take was a far cheaper pt100 inserted via the hot-water return intake I do not use. Remote piloting can choose "do not heat", "heat full power, heat-pump if possible + classic resistive heater", "try heating with the heat pump for 15' than goes full power", "choose automatically what to do".
WHY THE HELL not offering a simple:
- try heating with ONLY the heat pump
- try heating with ONLY the resistence
- do not heat
- heat full power
leaving the extra bit for "choose internally what to do"? I still have not answer, and to heat only with the heat pump, for instance because I have just 600-800W spare from my p.v. I have to switch any 10' "do not run" for a minute, than "start with the heat pump" in a loop.
My VMC is even worse: it's only ModBUS, native, but various registers store/read different values than those documented, a small set of them are totally undocumented, some fails to read or write randomly so I need a bit of extra logic to try again few times.
IoT can be a nice addition, but so far there is simply too much crap both on electronic side and on the digital side.