When you’re hooking up hardware to a network, it can sometimes be a pain to figure out what IP address the device has ended up with. [Bas Pijls] often saw this problem occurring in the classroom, and set about creating a simple method for small devices to communicate their IP address and other data with a minimum of fuss.
[Bas] specifically wanted a way to do this without adding a display to the hardware, as this would add a lot of complexity and expense to simple IoT devices. Instead, RGBeacon was created, wherin a microcontroller flashes out network information with the aid of a single RGB WS2812B LED.
In fact, all three colors of the RGB LED are used to send information to a computer via a webcam. The red channel flashes out a clock signal, the green channel represents the beginning of a byte, and the blue channel flashes to indicate bits that are high. With a little signal processing, a computer running a Javascript app in a web browser can receive information from a microcontroller flashing its LEDs via a webcam.
It’s a neat hack that should make setting up devices in [Bas]’s classes much easier. It needn’t be limited to network info, either; the code could be repurposed to let a microcontroller flash out other messages, too. It’s not dissimilar from the old Timex Datalink watches which used monitor flashes to communicate!
In today’s “predictable things that happened before and definitely will happen again”, Insteon, a smart home company boasting the Insteon ecosystem of devices built around their proprietary communication standards, has shut down their servers without a warning. For almost two decades, Insteon used to offer products like smart light switches, dimmers, relays, various sensors, thermostats – the usual home automation offerings, all linked into a cozy system. Looking through the Insteon subreddit’s history, there were signs of the company’s decline for good half a year now, but things were mostly stable – until about a week ago, when users woke up and noticed that parts of their smart home network stopped working, the mobile app would no longer respond, and the company’s resources and infrastructure went down. What’s more – the C-rank management has scrubbed their LinkedIn profiles from mentioning Insteon and SmartLabs (Insteon’s parent company).
Instantly, the Insteon subreddit has livened up. People, rightfully angry about being literally left in the dark, were looking for answers – as if mocking them, Insteon’s homepage claimed that all services were operational. Others, having expected the shutdown to eventually happen, started collecting and rehosting rapidly disappearing documentation, helping each other keep their tech up in the meantime, and looking into alternative platforms. It turned out to be imperative that users don’t factory reset their Insteon hubs, since those have to communicate with the currently Inste-Gone servers as part of initial configuration, diligently verifying the SSL certificates. Sadly, quite a few users, unaware and going through the usual solutions to make their network function again, are now left with hubs that are essentially bricked, save for a few lucky ones. Continue reading “Insteon Abruptly Shuts Down, Users Left Smart-Home-Less”→
Wait, what? Is it possible that a tech company just killed off a product with a huge installed base of hardware and a community of dedicated users, and it wasn’t Google? Apparently not, if the stories of the sudden demise of Insteon are to be believed. The cloud-based home automation concern seems to have just disappeared — users report the service went offline at the end of last week, and hasn’t been back since. What’s more, the company’s executives removed Insteon from their LinkedIn profiles, and the CEO himself went so far as to remove his entire page from LinkedIn. The reasons behind the sudden disappearance remained a mystery until today, when The Register reported that Smartlabs, Inc., the parent company of Insteon, had become financially insolvent after an expected sale of the company failed in March. The fact that the company apparently knew this was going to happen weeks ago and never bothered to give the community a heads up before pulling the switches has led to a lot of hard feelings among the estimated 100,000 Insteonhub users.
Then again, with a comet the size of Rhode Island heading our way, a bunch of bricked smart bulbs might just be a moot point. The comet, known as C/2014 UN271, has a nucleus that is far larger than any previously discovered comet, which makes it a bit of an oddball and an exciting object to study. For those not familiar with the United States, Rhode Island is said to be a state wedged between Connecticut and Massachusetts, but even having lived in both those states, we couldn’t vouch for that. For scale, it’s about 80 miles (128 km) across, or a little bit bigger than Luxembourg, which we’re pretty sure is mythical, too. The comet is a couple of billion miles away at this point; it may never get closer than a billion miles from the Sun, and that in 2031. But given the way things have been going these last few years, we’re not banking on anything.
From the “Answering the Important Questions” file, news this week of the Massachusetts Institute of Technology’s breakthrough development of the “Oreometer,” a device to characterize the physical properties of Oreo cookies. The 3D printed device is capable of clamping onto the wafer parts of the popular sandwich cookie while applying axial torque. The yield strength of the tasty goop gluing the two wafers together can be analyzed, with particular emphasis on elucidating why it always seems to stay primarily on one wafer. Thoughtfully, the MIT folks made the Oreometer models available to one and all, so you can print one up and start your own line of cookie-related research. As a starting point, maybe take a look at the shear strength of the different flavors of Oreo, which might answer why the world needs Carrot Cake Oreos.
And finally, since we mentioned the word “skiving” last week in this space, it seems like the all-knowing algorithm has taken it upon itself to throw this fascinating look at bookbinding into our feed. We’re not complaining, mind you; the look inside Dublin’s J.E. Newman and Sons bookbinding shop, circa 1981, was worth every second of the 23-minute video. Absolutely everything was done by hand back then, and we’d imagine that very little has changed in the shop over the ensuing decades. The detail work is incredible, especially considering that very few jigs or fixtures are used to ensure that everything lines up. By the way, “skiving” in this case refers to the process of thinning out leather using a razor-sharp knife held on a bias to the material. It’s similar to the just-as-fascinating process used to make heat sinks that we happened upon last week.
It’s fair to say that many of us will have at some time inadvertently bricked a device by applying the wrong firmware by mistake. If we’re lucky then firing up some low-level reflashing tools can save the day and return the item in question to health, but we’re guessing that among you will be plenty of people who’ve had to discard a PCB or replace an inaccessible microcontroller chip as a result.
Spare a thought then for the consumer appliance manufacturer Electrolux, whose AEG subsidiary has bricked combi microwave ovens acrosss a swathe of Western Europe (Dutch, Google Translate link). They managed this improbable feat by distributing an over-the-air update that contains the firmware for a steam oven instead. Worse still, the update has disabled over-the-air updates, meaning that any fix requires physical access to the oven.
We can’t help sympathising with whichever poor AEG engineer has had the ultimate in bad days at work, but at the same time we should perhaps consider the difference between a computer and an appliance, and whether there should be a need for an oven to phone home in the first place. Sure, such devices have been computer-controlled for decades, but should a microcontroller doing a control task need constant updates?
We’re guessing this oven has some kind of cloud aspect to it which allows AEG to slurp customer data the user to control it via their app, but even so it should serve as a warning to anyone tempted by an internet-connected kitchen appliance. If the internet isn’t necessary for the food to be cooked, don’t connect it.
We feel sorry for anyone who might have put a pizza in the oven just before it was bricked, and watched in disappointment as their tasty meal remained uncooked.
First of all, there are definitely simpler ways to monitor remote temperatures, but [Mike]’s remote MQTT temperature sensor and display project is useful in a few ways. Not only does it lay out how to roll such a system from scratch, but it also showcases system features like solar power.
After all, if one simply wants to monitor temperature that’s easily done, but once one wishes to log those temperatures and use them to trigger other things, then rolling one’s own solution starts to get more attractive. That’s where using someone else’s project as a design reference can come in handy.
[Mike’s] solution uses two Wemos D1 boards: one with a DS18B20 temperature sensor for outdoors, and one with a small OLED screen for an interior display. The external sensor relies on a rechargeable 18650 cell and a solar panel for a hassle-free power supply, and the internal sensor (of which there can be many) has a cute enclosure and is powered by USB. On the back end, a Raspberry Pi running an MQTT gateway and Node Red takes care of the operational side of things. The whole system has been happily running for over two years.
Whether you live in an apartment downtown or in a detached house in the suburbs, if your mailbox is not built into your home you’ll have to go outside to see if anything’s there. But how do you prevent that dreadful feeling of disappointment when you find your mailbox empty? Well, we’re living in 2022, so today your mailbox is just another Thing to connect to the Internet of Things. And that’s exactly what [fhuable] did when he made a solar powered IoT mailbox.
The basic idea was to equip a mailbox with a camera and have it send over pictures of its contents. An ESP32-Cam module could do just that: with a 1600 x 1200 camera sensor, a 160 MHz CPU and an integrated WiFi adapter, [fhuable] just needed to write an Arduino sketch to have it take a picture every few hours and upload it to an FTP server.
The components inside: a solar cell, battery, power controller, LDO and ESP32-Cam module with WiFi antenna
But since running a long cable all the way from the house was not an attractive option, the whole module had to be completely wireless. [fhuable] decided to power it using a single 18650 lithium ion cell, which gets topped up continuously thanks to a 1.5 W solar panel mounted on the roof of the mailbox. The other parts are housed in a 3D-printed enclosure that’s completely sealed to keep out moisture.
The enclosure had to be made from a material that does not degrade in direct sunlight, which is why [fhuable] decided to try ASA filament; this should be very resistant against UV rays, but proved tricky to process. It warped so much during cooling that the only way to get a solid piece out of the printer was to enclose the entire machine in a cardboard box to keep it warm inside.
The end result was worth it though: a neat little extension on the back of the mailbox that should keep sending photos of its insides for as long as the Sun keeps shining. The camera should also give a good indication as to the contents of the mailbox, allowing the user to ignore any junk mail; this is a useful improvement over previous IoT-enabled mailboxes that use proximity sensors, microswitches or optical sensors.
There’s a fine line between simple feature creep and going over the top when it comes to project design. It’s hard to say exactly where that line is, but we’re pretty sure that this filament dry box has at least stepped over it, and might even have erased it entirely.
Sure, we all know the value of storing 3D printer filament under controlled conditions, to prevent the hygroscopic plastics from picking up atmospheric moisture. But [Sasa Karanovic] must really, REALLY hate the printing artifacts that result. Starting with a commercially available dry box that already had a built-in heating element, [Sasa] took it to the next level by replacing the controller and display with an ESP32. He added a fan to improve air circulation inside the enclosure and prevent stratification, as well as temperature and humidity sensors. Not satisfied with simply switching the heating element on and off at specific setpoints, he also implemented a PID loop to maintain a constant temperature. And of course, there’s a web UI and an API available for third-party control and monitoring.
The video below details [Sasa]’s design thoughts and goes into some detail on construction and performance. And while we may kid that this design is over-the-top, what really comes through is that this is a showcase for design ideas not only for one application, but for hardware projects in general. There are certainly simpler heated dry box designs, and zero-cost solutions as well, but sometimes going overboard has its own value too.
Instantly, the Insteon subreddit has livened up. People, rightfully angry about being literally left in the dark, were looking for answers – as if mocking them, Insteon’s homepage claimed that all services were operational. Others, having expected the shutdown to eventually happen, started 
