• chevron_right

    Samsung will shut down the v1 SmartThings hub this month / ArsTechnica · Thursday, 3 June - 18:29 · 1 minute

A featureless, white electronic device.

Enlarge / The v1 SmartThings Hub from 2013. It's dying at the end of the month. (credit: Samsung )

Samsung has spent the last year or so upending its SmartThings ecosystem . SmartThings was born as an independent company in 2012 when it launched one of the largest Kickstarter campaigns ever: a $1.2 million funding program for the company's first smart home hub. Samsung bought SmartThings in 2014, and in June 2020, the Korean giant announced a plan that would basically shut down all of that acquired stuff, forcing everyone over to in-house Samsung infrastructure. A big part of that plan is happening at the end of the month, when Samsung will kill the first-generation SmartThings Hub.

The SmartThings Hub is basically a Wi-Fi access point—but for your smart home stuff instead of your phones and laptops. Instead of Wi-Fi, SmartThings is the access point for a Zigbee and Z-Wave network, two ultra low-power mesh networks used by smart home devices. Wi-Fi is great for loading webpages and videos, but it's extreme overkill for something like a light switch or door sensor, which just needs to send a few bits for "on or off" or "open or closed." Zigbee and Z-Wave are so low-power that you can run these devices on AA or coin cell batteries for months. The Hub connected your smart home network to the Internet, giving you access to a control app and connecting to other services like your favorite voice assistant.

You might imagine that killing the old hub could be seen as a ploy to sell more hardware, but Samsung—a hardware company—is actually no longer interested in making SmartThings hardware. The company passed off hub manufacturing for the latest "SmartThings Hub (v3)" to German Internet-of-things company Aeotec. The new hub is normally $125, but Samsung has been generous enough to offer existing users a dirt-cheat $35 upgrade price.

Read 3 remaining paragraphs | Comments

  • chevron_right

    XMPP for IoT: Visualisation of Meteorological Live Data for Renewable Energy

    debacle · / berlin-xmpp-meetup · Tuesday, 11 May - 15:29 edit

Dan and Tim will present a beautiful web application based on Strophe.js and Flot.js to visualise live measuremen data transmitted via XMPP PubSub/PEP. This is not about instant messaging at all, this is IoT, but security included.

When? Wednesday, 2021-05-12 18:00 CEST (always 2ⁿᵈ Wednesday of every month)

Where? Online, via our MUC ( A Jitsi video conference will be announced there.

See you then!

#jabber #berlin #meetup #community #xmpp #iot #webapplication #javascript #strophejs #flotjs #pubsub #pep #security #renewableenergy

  • favorite

    3 Like

    Holger Weiß , Timothée Jaussoin , debacle

  • chevron_right

    They hacked McDonald’s ice cream machines—and started a cold war / ArsTechnica · Wednesday, 21 April - 17:45

The lure of frozen deliciousness that led to uncovering insane techno craziness.

Enlarge / The lure of frozen deliciousness that led to uncovering insane techno craziness. (credit: NurPhoto | Getty Images)

Of all the mysteries and injustices of the McDonald’s ice cream machine, the one that Jeremy O’Sullivan insists you understand first is its secret passcode.

Press the cone icon on the screen of the Taylor C602 digital ice cream machine, he explains, then tap the buttons that show a snowflake and a milkshake to set the digits on the screen to 5, then 2, then 3, then 1. After that precise series of no fewer than 16 button presses, a menu magically unlocks. Only with this cheat code can you access the machine’s vital signs: everything from the viscosity setting for its milk and sugar ingredients to the temperature of the glycol flowing through its heating element to the meanings of its many sphinxlike error messages.

“No one at McDonald’s or Taylor will explain why there’s a secret, undisclosed menu," O’Sullivan wrote in one of the first, cryptic text messages I received from him earlier this year.

Read 81 remaining paragraphs | Comments

  • chevron_right

    100 million more IoT devices are exposed—and they won’t be the last / ArsTechnica · Wednesday, 14 April - 14:04 · 1 minute

100 million more IoT devices are exposed—and they won’t be the last

Enlarge (credit: Elena Lacey)

Over the last few years, researchers have found a shocking number of vulnerabilities in seemingly basic code that underpins how devices communicate with the Internet. Now a new set of nine such vulnerabilities are exposing an estimated 100 million devices worldwide, including an array of Internet-of-things products and IT management servers. The larger question researchers are scrambling to answer, though, is how to spur substantive changes—and implement effective defenses—as more and more of these types of vulnerabilities pile up.

Dubbed Name:Wreck , the newly disclosed flaws are in four ubiquitous TCP/IP stacks, code that integrates network communication protocols to establish connections between devices and the Internet. The vulnerabilities, present in operating systems like the open source project FreeBSD, as well as Nucleus NET from the industrial control firm Siemens, all relate to how these stacks implement the “Domain Name System” Internet phone book. They all would allow an attacker to either crash a device and take it offline or gain control of it remotely. Both of these attacks could potentially wreak havoc in a network, especially in critical infrastructure, health care, or manufacturing settings where infiltrating a connected device or IT server can disrupt a whole system or serve as a valuable jumping-off point for burrowing deeper into a victim's network.

Read 12 remaining paragraphs | Comments

  • chevron_right

    Ubiquiti breach puts countless cloud-based devices at risk of takeover / ArsTechnica · Wednesday, 31 March - 19:50

Stylized image of rows of padlocks.

Enlarge (credit: Getty Images )

Network devices maker Ubiquiti has been covering up the severity of a data breach that puts customers’ hardware at risk of unauthorized access, KrebsOnSecurity has reported , citing an unnamed whistleblower inside the company.

In January, the maker of routers, Internet-connected cameras, and other networked devices, disclosed what it said was “unauthorized access to certain of our information technology systems hosted by a third-party cloud provider.” The notice said that, while there was no evidence the intruders accessed user data, the company couldn’t rule out the possibility that they obtained users’ names, email addresses, cryptographically hashed passwords, addresses, and phone numbers. Ubiquiti recommended users change their passwords and enable two-factor authentication.

Device passwords stored in the cloud

Tuesday’s report from KrebsOnSecurity cited a security professional at Ubiquiti who helped the company respond to the two-month breach beginning in December 2020. The individual said the breach was much worse than Ubiquiti let on and that executives were minimizing the severity to protect the company’s stock price.

Read 7 remaining paragraphs | Comments

  • On chevron_right

    MQTT Broker on Orange Pi Zero (Armbian) / onetransistor · Saturday, 20 March - 17:17 edit

Some time ago I was attempting to install the Mosquitto MQTT broker software on an old router with OpenWrt firmware. I no longer think that is the best option for a self-hosted MQTT broker with the advent of single board computers (SBC) like Raspberry Pi and Orange Pi. To my surprise, the Orange Pi Zero board (with quad core 1 GHz CPU and 256 MB RAM) requires less power to run than an old router (300 MHz single core CPU and 64 MB RAM).

With sufficient processing capabilities, the SBC can run more than the MQTT broker. I’m thinking of turning this Orange Pi board into a Home Automation Gateway which manages local devices and makes data available in a web interface. There is plenty of software support for what I want (I’m thinking of Node-RED with a web-based dashboard). Another good candidate is Raspberry Pi, but because it does not have wired network port (Zero version), I chose Orange Pi.

MQTT Broker on Orange Pi Zero (Armbian)

Read more

Značky: #MQTT, #IoT, #Elektro, #Armbian