If you're referring to the water sensor, it's definitely not parent-friendly, but I sometimes have to bail water during power outages from thunderstorms. It has to work during a power outage and an old Chromebook was cheaper than a UPS.
I kind of ran out of time for messing around with the sensor, but I did think of either dumping the Winbond chip on my reader, or using a .bin file that was used for OTA updates and pushing a modified version down locally.
That likely would have been "cleaner" vs. a 23-hour reboot cycle. I likely would have wanted a dump first in case I borked the firmware. The Python monitoring script just uses standard HNAP to read status codes from the sensor in 30 second intervals - I think there's some way to push updates via HNAP as well.
Thanks for the reminder - may be a good project for winter, when there's no chance of needing the sump.
Anyone made any progress on rooting it?
You can then flash new firmware over USB.
https://github.com/morluto/rea
Do we just need to establish bounties per cloud service target to reverse engineer and publish a spec, copyleft code, and reference architecture? Maybe https://www.fulu.org/ could host the results?
but isn't the alternative to have some third party on the Internet sitting between you and knowing that your cellar is flooding? third party services in the cloud have downtimes (not necessarily less than your Chromebook), tend to shut down entirely over time, tend to give up on you if you're not on a premium plan, tend to stop supporting the version of your device, etc
Contactors are built to run giant industrial motors for years, nevermind my little 1/4hp pump.
The way I built it lets my mother bypass it by unplugging the pump from the control box and plugging it right into the wall outlet.
So, hopefully it lasts years. If it doesnt, anyone can bypass it
My rules for home automation are largely the same as the article, first and foremost the existing physical UX of switches and stuff should always work, and ideally automations should be nearly invisible: They should subtly be convenient and monitoring should be useful, but nobody should be confronted with a weird change of lifestyle because a house has automation. And nobody should ever need an app to use their house.
Reminds me of a possible apocryphal anecdote I heard about Alan Turing. He loved going on long bike rides, but one day his bike developed a distressing habit of slipping the chain. After the third time it happened, he realized it was due to a broken tooth on both the front and the back gear. He went back home and calculated how many revolutions of the pedals it would take for both broken teeth to line up when they were at the critical part of the rotation, and he built a little mechanical counter that would click on each link in the bike chain, and at the calculated time, a little arm would reach down and clasp the chain, holding it in place long enough for the teeth to re-engage.
He showed the device to his friend, who said "Why didn't you just buy new gears? You could have gotten both for a dime." And Alan replied "Oh, that's clever, I didn't think of that."
In a moment of weakness, I bought a D-Link wireless (wifi) water detector for the sump pit (it was on clearance for $30); it relied on a D-Link Home cloud service (free) that was closed down a few years ago.
Not wanting to toss it, I repurposed a spare Chromebook 14 that I was going to recycle and turned it into a Alpine monitor for the water detector, which I'm powering from the Chromebook's USB port (if power is lost in a rainstorm, I need to know about it before the sump pit fills up).
An immediate issue was that the D-Link firmware tried to "phone home" every 24 hours and would drop from the local network, since the server was kaput, and I had no clue what response it was expecting from the server to keep it alive. Solution; "reboot" the unit by interrupting USB power (with a Pico and MOSFET) every 23 hours. There's no question that home automation should work without the internet.