and Netgear, and pretty much all the IoT companies.This should be the standard for all devices, not the exception.
Hey, Google, Western Digital and others, are you listening?
If you don't control the sources of your assembly/product, you are proven to fail or go under. Just like now, its still hard to get a RaspberryPi4... all vendors I trust are "out of stock" unless a prohibitively expensive ($150-$200) kit. The point was a sub$50US board, and another $50US for power, storage, case, etc. Which I am wondering, what are the guts inside this Monitor-IO? Anyone have one opened? Or alternative that could be like a color status, emoji indicator with info scroll?Seems like it was a well-engineered solution in search of a problem (anyone who would really need this could probably also quickly rig up some other way to get notified of network issues via existing resources/channels), but I applaud them for wrapping things up well before they go.
They were, but then... SQUIRREL! and they forgot everything you said.When reading about the demise of Dropcams the other day I kept thinking that companies that truly cared about their customers would release updated firmware that would allow users to disentangle their devices from the cloud services rather than just bricking them. Kudos to these guys for doing exactly that. Are you paying attention Google??
It didn't just change the color of the display. They collected the stats from the device and emailed you a regular summary that listed your outages and slowdowns in some pretty tables.Wow, this missed my radar in 2018. I would have found it super useful last year, there was something wonky with my ISP. I probably would not have paid $100 for something that just shoots out some pings for me and has a color coded display, but I would have thought about it. I've already thought about cobbling something together to turn on a light when the internet goes down as the wife and I work from home. In the meantime my music streaming is a pretty good canary for that. But still... knowing how much care they put into it and their customers to go so far as to give it this end of life support is something that if you had the ability to see the future would have made an impact when deciding to buy. Top marks folks. If they ever release another product I'll absolutely be thinking about this when looking at it.
As problematic as Microsoft can be, they also retired their Harman Kardon Cortana speaker similarly to this company and that’s just great, it still works as a Bluetooth speaker.When reading about the demise of Dropcams the other day I kept thinking that companies that truly cared about their customers would release updated firmware that would allow users to disentangle their devices from the cloud services rather than just bricking them. Kudos to these guys for doing exactly that. Are you paying attention Google??
Seems like it was a well-engineered solution in search of a problem (anyone who would really need this could probably also quickly rig up some other way to get notified of network issues via existing resources/channels), but I applaud them for wrapping things up well before they go.
This should be the standard for all devices, not the exception.
Hey, Google, Western Digital and others, are you listening?
They were, but then... SQUIRREL! and they forgot everything you said.
This makes it sound like a passive occurrence. For big players, planned obsolescence is usually part of a corporate strategy to drive new sales. If all your old stuff stops working every 5 years, you have to buy new stuff every 5 years. Corporate economics 101.I fully agree, but the trouble is it's not hurting their business enough for them to care. If all the major players are doing the same thing, they'll just continue their bad behavior.
So far I've been addressing this by not buying IoT devices, but large companies won't notice that either.
Yeah. Super-easy. Get back to us when you have that firmware written and debugged.Totally agree it's a good way to go out, kudos to them!
A mini linux server doing this seems total overkill, though, just to periodically ping a remote IP and show the results... could do the same with an arduino/ethernet shield/LCD display (lots of examples on google in various forms/pieces). Or some esp32 module with a build-in LCD , running over wifi (which could then be left on a coffee table)
Barely an inconvenience.Yeah. Super-easy.
Right, this is the problem. If you're an ongoing concern, then it benefits you to brick old products and require updates. And of course, with everything becoming cloud-connected, we're going to iPhone-ify cars, washers, dryers, HVAC systems, TVs, etc. Stuff that used to last thirty years will last five because of software-implemented planned obsolescence.They didn't forget, they just couldn't care less. Some analyst probably crunched the numbers showing that they can provide better shareholder value in the long-run by bricking those devices versus providing them with a cloud-free option during discontinuation.
Well, the colored lights is one little reason for that to exist as a hardware device, in case you have a need to check whether your Internet is up when you're not working at your computer. Other than that it's just software that could run on any computer, so it's not surprising if there wasn't enough demand to make their business plan take off. Maybe they thought users would be more willing to pay for a tangible gadget than for a program to install on their computers?It did this both with detailed reports you could access from the local network and with a screen that glowed one of three colors: green for good, purple for problems, and red for dead.
Journalling filesystems have been the norm in Linux for many years. Perhaps this gadget used a simple non-journalling filesystem, but in that case the cause of its vulnerability to power outages was their choice of filesystem, not the fact that it ran Linux.It's a "standard Linux operating system," so you should consider keeping it on an uninterruptible power supply to avoid file corruption during power outages.
If the gadget required a subscription, then the centralized service was the justification for the subscription fees that were meant to make the company profitable. Otherwise it's a mystery.But why do the graphs and data presentation rely on an external service?
It didn't require a subscription (at least when I bought one). The price included lifetime* data collection and generation of reports.If the gadget required a subscription, then the centralized service was the justification for the subscription fees that were meant to make the company profitable. Otherwise it's a mystery.
Oh, it was anything but. The key to this was the nuanced understanding of networking enlisted by the system along with clear color-coded feedback about the testing.Seems like it was a well-engineered solution in search of a problem (anyone who would really need this could probably also quickly rig up some other way to get notified of network issues via existing resources/channels), but I applaud them for wrapping things up well before they go.
I have asked the owner repeatedly in support tickets for some point of community focus--a GitHub, Discord, or something. The response was "it's just a bash script and a binary to change the screen color". Which, yeah. But the bash script and the binary have no license attached to them that I can find.I really wish that it would be a common upfront promise of IoT device makers (and especially crowdfunded ones) that if they were ever winding down, they'd hand over the reins to the user community. I would probably be willing to pay more for that sort of assurance, and it would definitely be a significant selling point when choosing between competing providers/ecosystems.
The original device wasn't just doing ICMP/TCP pings. There were two sides to the UDP datagrams that were being sent and received, so both sides (especially the server) could analyze the data received, show differences between Eastern US and Western US latency, etc. I don't understand it all, but it was more than just the simple ping it is now.I have to wonder why it wasn't designed this way to begin with.
Partly the above. And partly because the service provider can update the graphs and data presentation without having to push code to the device. And partly so the service could be configured to alert you via email or app if the Monitor-io device went off the Internet.But why do the graphs and data presentation rely on an external service?
One issue with this is that the owner has not provided an open source license for the components of the new image so we can't modify them.The Monitor-IO fan community