News for hackers. Stuff that matters.
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by madjam002 on Tuesday November 24, 2020 @05:58AM (#25197317)
The Xiaomi stuff is great, I have a lot of Aqara devices around the house.

A nice alternative to the temperature + humidity sensor is this Xiaomi Mijia one which uses BLE instead of Zigbee and has a little screen which shows the temperature as well: https://www.aliexpress.com/item/1005001355746608.html

It's also much cheaper at $3-$4 each instead of ~$11 each. I've been scattering them around and they're great, the display is also nice.

They can easily be added to Home Assistant with a Raspberry Pi or ESP32 ($3-4) using ESPHome: https://esphome.io/components/sensor/xiaomi_ble.html

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by retSava on Tuesday November 24, 2020 @09:12AM (#25198546)
I have a couple of Yeelights, ie their RGBW-led light in common E27 socket. Very nice, you can "unlock" developer mode so you can control it over the local network. Super nice. Scripted up a simple thing running on a Raspberry pi + telegram bot for simple commands like "movie", "night" etc without needing to switch apps or be on wifi.

Then my daughter said that it was so cool when it blinked in all colors and I realized she had flipped it on/off till it factory reset itself.

Now I can't commission them. At all. Both apps provided by Yeelight fail with timeouts, neither server works (you have to pick one, eg china, germany), and none of the troubleshooting steps help. Changing DNS server, wifi hotspot, etc etc. None works. They even have a bug where if your account number is large enough, it will fail since it can fit in the apparently int32_t they seem to store it in.

They are cheap, but I'm beyond frustrated that I can't get them online again. The light was nice and bright, but the sw quality is apparently not on par.

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @09:15AM (#25198581)
I've had the timeout happen to me. The bulb does connect to your wifi, just connect your phone to your wifi manually near the end of the pairing and it will continue where it left off. Afterwards, enable LAN mode control and uninstall the app, you never need to use it again. You can use the YeeLight Python library (which I wrote!) and yee (or HA) to do anything you want.
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by gempir on Tuesday November 24, 2020 @09:37AM (#25198761)
I wish there was a way to completely avoid the app. I have a bunch of Aqara devices that are Zigbee and they never even talked to Xiaomi because I only connected them to my Conbee without ever installing any Xiaomi App or whatever.

I wonder how hard it is to add an ESP8266 to the lamps and just control via the ESP.

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @10:02AM (#25199041)
You can do that with Zigbee? That sounds fantastic, but the Conbee is a bit pricy still.

Look at the Sonoff line of devices, they're all ESP8266-based and extremely hackable (all mine run custom firmware, Espurna).

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by gempir on Tuesday November 24, 2020 @10:08AM (#25199101)
Yeah you can. You can get something like a CC2531 which works great aswell. Not sure If it's supported by ZHA yet but https://www.zigbee2mqtt.io/ worked very good with my CC2531. I just switched to the Conbee because it was supported by ZHA and I wanted my lights etc to directly connect to Home Assistant with ZHA.
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @11:00AM (#25199584)
The CC2531 looks dirt-cheap, Ali stocks it for $2. What's ZHA? I saw it mentioned in the article but don't understand why the CC2531 doesn't work with it. I was thinking of buying an ITEAD Zigbee bridge, but I don't know whether that will work with ZHA or why I'd want it to...
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by gempir on Tuesday November 24, 2020 @11:11AM (#25199721)
ZHA is Zigbee Home Automation. It's basically the part of Home Assitant that deals with zigbee devices. So it's like first party vs something like zigbee2mqtt which then hooks into Home Assitant.

Makes a little less work configuring etc, but not all Zigbee sticks are supported. Check support here

https://www.home-assistant.io/integrations/zha/#known-workin...

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @11:15AM (#25199771)
Ahh, so it's a HA thing. The ITEAD gateway is explicitly listed as supported, so that seals it. Their stuff has always been stellar, thank you for the info.
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by retSava on Wednesday November 25, 2020 @05:44AM (#25207831)
Yeah, it's really cheap, but 8051 which is quite cumbersome to work with imho.
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Wednesday November 25, 2020 @06:00AM (#25207954)
Oh, what's the difference? Also what's the alternative?
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by retSava on Wednesday November 25, 2020 @05:45AM (#25207836)
Oh nice! Hope this works, trying it out later!
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by tda on Tuesday November 24, 2020 @06:05AM (#25197360)
How long do they last on a battery? I have the older version https://www.aliexpress.com/item/32845863956.html which runs on a about 9 months on a rechargeable AAA penlite. But I could use a few more and these new ones are a lot cheaper.
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by madjam002 on Tuesday November 24, 2020 @06:21AM (#25197451)
To be fair, I only got them around a month ago :) So I'm not sure, although in the specs they say it's supposed to last around a year. My battery levels are still at 100% although I know that is not a reliable indication.

One thing to note with the new model, the Bluetooth messages are encrypted and a device bindkey is needed to read the temperature values. Fortunately there is a great project over at https://atc1441.github.io/TelinkFlasher.html which can pair with the device and retrieve a bindkey from within the web browser. Then you just need to plug the bind key and MAC address into ESPhome and you're good to go.

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @09:16AM (#25198590)
What do they talk to? Do you need to get a Xiaomi hub? Are they hackable? I really don't want my devices talking to the internet, I even jailbroke my vacuum so I could control it locally (what a brave new world).
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by tga on Tuesday November 24, 2020 @09:37AM (#25198760)
This is the great part about Zigbee/BLE/433MHz devices, they do _not_ go on your wifi (and the internet), but instead talk to a dedicated gateway. As long as you find a way to talk to them, you can mix and match sensors from the shadiest of vendors.

You can ignore the gateways offered by each manufacturer and instead go with something (more) open like zigbee2mqtt or deConz.

Zigbee: https://www.zigbee2mqtt.io https://www.phoscon.de/en/conbee2/software

BLE: RPi or ESP32 running https://esphome.io

433MHz: https://sonoff.tech/product/accessories/433-rf-bridge running https://esphome.io or https://tasmota.github.io

Of course, this way you lose the (more or less) polished apps that come with each system and need to set up something like Home Assistant or openHAB for control and automation.

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @10:04AM (#25199056)
That's great, thanks! I already run Espurna on everything, so that's fine, I just wanted to confirm that all Zigbee devices are interoperable. It's unlikely that I'll get a device that will only want to talk to its specific vendor's gateway, then?
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by comfydragon on Tuesday November 24, 2020 @12:49PM (#25200906)
> I just wanted to confirm that all Zigbee devices are interoperable.

At the RF protocol level, yes they should be. Speaking as someone who works at a company with a few Zigbee-certified products, I can say that there are a LOT of "optional" features in the Zigbee specification, and even implementations of mandatory features can have differences that lead to incompatibility.

Manufacturer-specific profiles are also a big thing. So just be aware that manufacturer A's Zigbee "hub"/coordinator may or may not be inherently compatible with manufacturer B's sensors. But I would imagine that open-source systems like HomeAssistant deal with that.

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @12:52PM (#25200939)
How can HA deal with it? Is the incompatibility not at the protocol level? Does HA even see the messages at all? Or are the messages compatible, and then HA has to decode them somehow?
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by comfydragon on Tuesday November 24, 2020 @06:35PM (#25204289)
Messaging in Zigbee (i.e. sending data back and forth) is all about two things: addressing (endpoint, profile and cluster... kind of like port + URI for HTTP, where endpoint=port and profile+cluster=URI), and the payload itself. The Zigbee specification defines a variety of standard profiles that devices may choose to implement. Things like device temperature, on/off switch, metering, time, lighting, etc.

But nothing says that any given device, say a Zigbee light controller (on/off) from manufacturer X, MUST implement the standard on/off cluster for that. They could have their own manufacturer-specific profile+cluster for controlling the light, where a payload of 0x11 turns it on, 0x22 turns it off, and 0xF7 toggles the light. Or maybe you send the ASCII string "on".

Suppose that HA has implemented the functionality needed to interact with the standard on/off cluster. That functionality would work with devices that implement the standard cluster, but not with manufacturer X's device that needs the string "on". But then, HA could be updated to recognize such devices and implement the required functionality.

Assuming you're familiar with HTTP: just because two services both consume and produce JSON, doesn't mean the message bodies are interchangeable.

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @06:59PM (#25204457)
That clarifies things perfectly, thanks. As long as the wire format is compatible (which it is, from your description), then compatibility is only a matter of software updates, which is great.
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by madjam002 on Tuesday November 24, 2020 @10:34AM (#25199366)
They display temperature and humidity on the LCD display, but also transmit the temp + humidity every 10 minutes or so via Bluetooth Low Energy.

Battery lasts around a year (on paper) so they make for cheap alternatives to the Zigbee temperature + humidity sensor in the OP article (although that one is pretty cheap as well!)

No internet needed if you set up a Raspberry Pi or ESP32 and run some software which can e.g decode the BLE messages and publish them to MQTT. ESPHome has a component for this which can get you up and running in a few minutes if you have an ESP32 lying around (needs to be ESP32 as ESP8266 doesn't have Bluetooth).

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @10:57AM (#25199552)
That's pretty cool, though my WiFi is already pretty crowded, so rather than have an ESP32 in every room and on WiFi, I think I'll get an ITEAD ZigBee hub and go that route instead, thanks!
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by madjam002 on Tuesday November 24, 2020 @05:28PM (#25203748)
Yeah fair enough the Zigbee ones will last longer with one battery anyway.

I only have one ESP32 for the 4 BLE sensors, it handles them all fine across different corners of my flat (the furthest one is around 10m through 2 walls). The same ESP32 is also in my utility cupboard with a photoresistor attached taped to my electric meter which counts the LED pulses so I can see how much electricity I’ve used in Home Assistant as well. Esphome makes it easy to configure multiple use cases for one device like that

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @05:33PM (#25203804)
Hmm, that's interesting. I've never tried ESPhome, but I should. I rolled my own five years ago and it's been working fine so far, but ESPhome + Home Assistant might be easier to configure and update than Espurna.
Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by madjam002 on Tuesday November 24, 2020 @06:40PM (#25204328)
Yeah I was using Espurna on my lightbulbs that I replaced the firmware with (they were Tuya-based bulbs so I swapped them for Espurna). It was rock solid but I decided to move to Esphome as I liked the YAML based config, makes for a more "infra-as-code" style for IoT devices :)

Since then I'm using it on all kinds now, my own ESP32 dev board like I mentioned for the BLE sensors, and a variety of Shelly 1 devices and random brands of WiFi smart plugs from Amazon.

Re:IoT Unravelled Part 2: IP Addresses, Network, Zigbee, Cus... by StavrosK on Tuesday November 24, 2020 @06:57PM (#25204444)
That sounds great, I like Espurna for the web interface and general quality but I really hate the C-style header file configuration, it's very hard to update your code.

With YAML, I at least know that the file I have will continue to work across updates. Seems much more usable.