mountain_peak
an hour ago
Bought our home almost 20 years ago, and the former owner (apparently) owned a now-defunct home automation business. The upside was 100% X10/Insteon power and light controls, top alarm panel, environmental controls and so on running off of a wall-mounted "SmartLinc" touch panel. I expanded the system with Axis cameras and a Mac Server running Indigo and SecuritySpy (non-subscription), which enabled remote monitoring and control, but it all operates locally.
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.
lakeviewterrace
16 minutes ago
I don't like the idea of a Chromebook sitting between me and knowing my cellar is flooding.
jandrese
26 minutes ago
Every cloud service will eventually get shut down. The problem is that nobody wants to put the effort into reverse engineering the product to fake out the cloud service until after the cloud service is gone and the reverse engineering is much more difficult.
toomuchtodo
21 minutes ago
Reverse engineer anything with agents, from app behavior down to native binaries - https://news.ycombinator.com/item?id=50058850 - October 2026
https://github.com/morluto/rea
https://github.com/AI4AIResearch/Awesome-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? Like OpenAI and Anthropic brute forcing math proofs, we can brute force interoperability (imho).
https://bounties.fulu.org/bounties
(think in systems)
mmmlinux
36 minutes ago
Here's what you do. Skip the detector, Just put the whole laptop in there. when it goes offline, You have water in the sump.
JoshTriplett
28 minutes ago
Very much in the spirit of the "weather stone": https://en.wikipedia.org/wiki/Weather_rock
goodmythical
9 minutes ago
I haven't figured out how to recieve pings from my weather stone, I've always got to get up and look out the window, which, then I can just see the weather.
Anyone made any progress on rooting it?
Uncle_Brumpus
3 minutes ago
"...And so that's how I ended up with a $14,000 basement repair. Yup, those damn chromebooks are more waterproof than you'd think! I mean it makes sense, they're designed to be vomited on by children all day at school."
nekooooo
an hour ago
every single sentence was a level of jank that i could never imagine subjecting my parents to. could you code custom firmware for the dlink btw? your fix sounds like good ol' redneck engineering but for the smart home :p
mountain_peak
a minute ago
The neat thing about X10 and Insteon is that everything acts "normally" at the device level, but you can program everything (remotely?) via the Indigo server. Your parents wouldn't even have to know that their house was running schedules (except for lights turning on an off).
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.