One Zigbee gateway to rule them all?

Hardware
1

So I’ve got a Philips Hue Hub 1 and 2, Osram Lightify Gateway and bought my self an Ikea Tradfri set this weekend with the hopes to exploit the sensors cheaply. Although this doesn’t seem to quite be there yet.

I’ve also seen Xiaomi, Samsung and Swann seem to have Zigbee smart sensors too. Having had a pretty rough time with various technologies (such as Z-wave) I’m pretty attached to Zigbee as the potential path forwards.

I wanted to know if anyone has come across something like the SmartThings Hub that behaves more like the Tradfri gateway (offline doesn’t require internet etc and preferably open source)? The ideal thing I want to achieve is to have a single hub I can attach all my Zigbee Sensors / Lights to and control them with as minimal man the middle interaction as possible (thinking MQTT would be ideal) it looks like something could be achievable with the Xbee modules however having no real experince at this level I wondered could any one shed any light on the matter for me? Thanks.

2

Next release will have native support for zigbee similar to zwave only needing a dongle.

/Robban

1 Like
3

Sounds brilliant, I’ll await the next version. Can you provide any links to the required hardware?

4

Sorry, I don’t know that. I would also like to know this so I can migrate from my Hue Bridge.

/Robban

5

Some details here:
https://github.com/home-assistant/home-assistant/pull/6263

6

I think he’s based it on the HUSBZB-1 stick. Check out this post. https://community.home-assistant.io/t/z-wave-zigbee-usb-stick/8232

7

Yeah it seems that each chipset vendor implements a totally different uart command set

8

I’ve got a EM3588 based device on the way so I’ll see how I get on with that for now. Hopefully most stuff will “just work” and at worst it will hopefully provide a good jumping off point to expand things.

2 Likes
9

Which device did you order? I suppose it’s different from the HUSBZB-1 stick?

10

Hey folks,

Do you know if the Silicon Labs ETRX358USB will work?
http://www.silabs.com/products/wireless/mesh-networking/telegesis-modules-gateways/ertx358-usb-stick

Since it’s ETRX3588 based and supports EmberZNet I am guessing yes.

@MindrustUK - Did you have a chance to test with your EM3588 device?

11

@hijinx Unfortunately Fed Ex are messing me around a bit, hoping I get the stick sooner rather than later so I can test and provide some feedback.

1 Like
12

Sure np. let us know when you are able :slight_smile:

13

Just found in the PR:

In terms of the local radio, it should support any EmberZNet device that supports the EZSP protocol.

Silicon Labs ETRX358USB seems to use an AT-command based protocol, so it’s probably not compatible.

14

Any update on this?

15

@corneyl , @hijinx - FWICT, you might be able to flash a working firmware onto the ETRX35x devices. It’s not clear whether such a firmware is even available without buying the developer kit, though.

16

I found a bunch of firmware on GitHub.
I’ll share the link.

17

Here is the link to the FW I found:


Now that I look at it again its for the em357 family, not etrx35x.
18

So latest update, FedEx after much screwing around delivered at long last!

So here’s what I’ve got: http://eu.mouser.com/search/ProductDetail.aspx?r=634-RD-0002-0201

I had to follow the out of the box guide to upload the NCP firmware to the device (which is all nicely done through python): https://www.silabs.com/documents/public/user-guides/ug129-zigbee-gateway-ref-design-guide.pdf

Unfortunately on startup of HASS it dies with an error of:

DEBUG:bellows.ezsp:Send command version
DEBUG:bellows.uart:Sending: b'\x00B!\xa8P\xed,~'
DEBUG:bellows.uart:Data frame: b'\x01B\xa1\xa8Q(\x05\xeb\xd8{~'
DEBUG:bellows.uart:Sending: b'\x81`Y~'
DEBUG:bellows.ezsp:Application frame 0 (version) received
DEBUG:bellows.ezsp:Send command setConfigurationValue
DEBUG:bellows.uart:Sending: b"}1C!\xfbX(\x15\xc3'~"
DEBUG:bellows.uart:Data frame: b'\x12C\xa1WT\xa3`~'
DEBUG:bellows.uart:Sending: b'\x82P:~'
ERROR:homeassistant.core:Error doing job: Exception in callback SerialTransport._read_ready()
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/events.py", line 120, in _run
    self._callback(*self._args)
  File "/opt/hass/.homeassistant/deps/serial_asyncio/__init__.py", line 106, in _read_ready
    self._protocol.data_received(data)
  File "/opt/hass/.homeassistant/deps/bellows/uart.py", line 54, in data_received
    self.frame_received(frame)
  File "/opt/hass/.homeassistant/deps/bellows/uart.py", line 64, in frame_received
    self.data_frame_received(data)
  File "/opt/hass/.homeassistant/deps/bellows/uart.py", line 84, in data_frame_received
    self._application.frame_received(self._randomize(data[1:-3]))
  File "/opt/hass/.homeassistant/deps/bellows/ezsp.py", line 144, in frame_received
    frame_name = self.COMMANDS_BY_ID[frame_id][0]
KeyError: 255```

Which isn't perfect but I don't think it's actually that bad either.

Cloning bellows directly the "Scan" and "Config" options both seem to work so I'm hoping this is a minor fix around the protocol. I'll carry on my investigation and see what else I can produce although I think the next topic for this might be configuration / component specific and not in hardware. Hopefully once this problem is sorted I'll post a Zigbee compatibility list as someone requested.
19

Have you got the stick working properly?

20

Not yet, I need to find some time to get a proper look into why this is happening. Maybe over the weekend if I get the chance.