Setup HUSBZB-1 (EMBER EM35x Coordinator) Help Please

[wormuths (Wormuth Household)]

@chris

ls /dev/tty*

/dev/tty /dev/tty13 /dev/tty19 /dev/tty24 /dev/tty3 /dev/tty35 /dev/tty40 /dev/tty46 /dev/tty51 /dev/tty57 /dev/tty62 /dev/ttyS0 /dev/ttyS14 /dev/ttyS2 /dev/ttyS25 /dev/ttyS30 /dev/ttyS8
/dev/tty0 /dev/tty14 /dev/tty2 /dev/tty25 /dev/tty30 /dev/tty36 /dev/tty41 /dev/tty47 /dev/tty52 /dev/tty58 /dev/tty63 /dev/ttyS1 /dev/ttyS15 /dev/ttyS20 /dev/ttyS26 /dev/ttyS31 /dev/ttyS9
/dev/tty1 /dev/tty15 /dev/tty20 /dev/tty26 /dev/tty31 /dev/tty37 /dev/tty42 /dev/tty48 /dev/tty53 /dev/tty59 /dev/tty7 /dev/ttyS10 /dev/ttyS16 /dev/ttyS21 /dev/ttyS27 /dev/ttyS4 /dev/ttyUSB0
/dev/tty10 /dev/tty16 /dev/tty21 /dev/tty27 /dev/tty32 /dev/tty38 /dev/tty43 /dev/tty49 /dev/tty54 /dev/tty6 /dev/tty8 /dev/ttyS11 /dev/ttyS17 /dev/ttyS22 /dev/ttyS28 /dev/ttyS5 /dev/ttyUSB1
/dev/tty11 /dev/tty17 /dev/tty22 /dev/tty28 /dev/tty33 /dev/tty39 /dev/tty44 /dev/tty5 /dev/tty55 /dev/tty60 /dev/tty9 /dev/ttyS12 /dev/ttyS18 /dev/ttyS23 /dev/ttyS29 /dev/ttyS6
/dev/tty12 /dev/tty18 /dev/tty23 /dev/tty29 /dev/tty34 /dev/tty4 /dev/tty45 /dev/tty50 /dev/tty56 /dev/tty61 /dev/ttyprintk /dev/ttyS13 /dev/ttyS19 /dev/ttyS24 /dev/ttyS3 /dev/ttyS7

Sorry, but there it is. LOL

[chris (Chris Jackson)]

So now I would suggest to change the ports to /dev/ttyUSB0 (etc) - it’s highly likely to solve your problem based on this.

[wormuths (Wormuth Household)]

I did, might have to restart the PC… Let me try that and let you know.

[chris (Chris Jackson)]

You shouldn’t need to restart the PC - it won’t change the port - just restart the binding.

[wormuths (Wormuth Household)]

Tried deleting and recreating the coordinator things. My z-wave is online, but the zigbee portion stuck at initializing, even after restarting the PC.

[5iver (Scott Rushworth)]

Try setting up the logging for zigbee to get more details in the log…

Zigbee binding

It doesn’t look like you’ve enabled any debugging in the log? I can only see INFO messages. http://docs.openhab.org/administration/logging.html log.set DEBUG org.openhab.binding.zigbee and log.set DEBUG com.zsmartsystems.zigbee should help. What are the “sensors” you are talking about?

[wormuths (Wormuth Household)]

Tried to recreate the zigbee controller with debugging on, and this is what it shows…

==> /var/log/openhab2/openhab.log <==
2017-09-18 19:21:48.460 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1
2017-09-18 19:21:48.460 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 0
2017-09-18 19:21:48.460 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 0000000000000000
2017-09-18 19:21:48.460 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2017-09-18 19:21:48.461 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising network
2017-09-18 19:21:48.461 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee PAN ID [93C0].
2017-09-18 19:21:53.456 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing 'zigbee:coordinator_ember:30f50753' takes more than 5000ms.
2017-09-18 19:21:53.458 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee extended PAN ID [21F8E993428602C5].
2017-09-18 19:21:53.464 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2017-09-18 19:21:53.465 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key array [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
2017-09-18 19:21:53.466 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Creating random ZigBee network key.
2017-09-18 19:21:53.469 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee network key.

==> /var/log/openhab2/events.log <==
2017-09-18 19:21:53.463 [ThingUpdatedEvent         ] - Thing 'zigbee:coordinator_ember:30f50753' has been updated.

==> /var/log/openhab2/openhab.log <==
2017-09-18 19:21:53.470 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised String 8A 11 44 5E A1 90 53 D7 CA A9 46 C7 EE F2 1E D9
2017-09-18 19:21:53.473 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised array [138, 17, 68, 94, 161, 144, 83, 215, 202, 169, 70, 199, 238, 242, 30, 217]
2017-09-18 19:21:53.473 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array [138, 17, 68, 94, 161, 144, 83, 215, 202, 169, 70, 199, 238, 242, 30, 217]
2017-09-18 19:21:53.473 [DEBUG] [andler.ZigBeeCoordinatorEmberHandler] - ZigBee Coordinator Ember opening Port:'/dev/ttyUSB1' PAN:93c0, EPAN:21F8E993428602C5, Channel:-1
2017-09-18 19:21:53.473 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start

==> /var/log/openhab2/events.log <==
2017-09-18 19:21:53.475 [ThingUpdatedEvent         ] - Thing 'zigbee:coordinator_ember:30f50753' has been updated.
2017-09-18 19:21:53.476 [ThingUpdatedEvent         ] - Thing 'zigbee:coordinator_ember:30f50753' has been updated.
2017-09-18 19:21:53.483 [ThingUpdatedEvent         ] - Thing 'zigbee:coordinator_ember:30f50753' has been updated.

==> /var/log/openhab2/openhab.log <==
2017-09-18 19:21:54.473 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2017-09-18 19:21:54.474 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2017-09-18 19:21:54.474 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_ember:30f50753
2017-09-18 19:21:54.474 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_ember:30f50753
2017-09-18 19:21:54.476 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=298, service.bundleid=184, service.scope=singleton} - org.openhab.binding.zigbee
2017-09-18 19:21:54.476 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise [138, 17, 68, 94, 161, 144, 83, 215, 202, 169, 70, 199, 238, 242, 30, 217]
2017-09-18 19:21:54.477 [INFO ] [andler.ZigBeeCoordinatorEmberHandler] - Connecting to serial port [/dev/ttyUSB1] at 57600
2017-09-18 19:21:54.493 [INFO ] [andler.ZigBeeCoordinatorEmberHandler] - Serial port [/dev/ttyUSB1] is initialized.
2017-09-18 19:21:54.494 [WARN ] [bee.dongle.ember.ash.AshFrameHandler] - Trying to send when not connected.
2017-09-18 19:21:55.872 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initResponse is NOT_JOINED
2017-09-18 19:21:55.872 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initializeNetwork is true
2017-09-18 19:21:57.551 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialise done....... 21  65535  21F8E993428602C5

==> /var/log/openhab2/events.log <==
2017-09-18 19:21:57.554 [ThingUpdatedEvent         ] - Thing 'zigbee:coordinator_ember:30f50753' has been updated.

==> /var/log/openhab2/openhab.log <==
2017-09-18 19:22:09.064 [ERROR] [bee.dongle.ember.ash.AshFrameHandler] - <-- RX ASH frame: BAD PACKET 11 11 57 4E A1 9C C5 26 54 9A

[5iver (Scott Rushworth)]

@wormuths

Added openHAB to the dialout and tty groups

Did you set the EXTRA_JAVA_OPTS for both ports?

EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyUSB1"

[wormuths (Wormuth Household)]

Ahhh, nope.

Some of this is a little unclear in the documentation. When running through the steps, it seems that some of this implies that it was only necessary during a manual installation, and I installed from the repository so didn’t do most of this. Hopefully, this thread will serve as a reference for others who buy this stick.

So this…

EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyUSB1"

I just enter this command in the standard linux terminal, or the Karaf console?

[5iver (Scott Rushworth)]

@wormuths

Hopefully, this thread will serve as a reference for others who buy this stick.

There have been a few threads where people were trying to get this stick going… but they’ve mainly been about learning OH! And yes, hopefully they can all be used as a reference for others! I learn something new every time I go through the forum, and there are a lot of helpful people here who made my initial OH setup so much easier than going at it alone!

Which version of OH are you running? You can find it on the bottom of the home page/welcome screen or Karaf console after a startup. When I first setup this stick, I was stuck about where you are! It looks like after the controller was first setup, it stayed in Initializing until the binding was restarted. After creating/configuring the coordinator, what happens when you restart OH?

Zigbee binding

You got it! I can report that an OOTB HUSBZB-1 is controlling both my zwave and zigbee networks. The Ember EM35x Coordinator needs the baud rate set to 57600 when it is first created. I tested the others, but the binding would hang and Java would do a core dump when the binding was stopped. The coordinator would need to be deleted at this point. The coordinator stayed in Initializing after it was created, but after a restart it went Online. I have only tested GE Link bulbs. Changing the name …

@wormuths

I just enter this command in the standard linux terminal, or the Karaf console?

It was in the link with the permissions setup…
http://docs.openhab.org/installation/linux.html#privileges-for-common-peripherals

… so I thought you might have only half set it up, and was hoping that would explain why only the zwave was working. If you didn’t set it for the zwave side, then this is likely not the issue. It’s more for non-standard port names setup through udev rules. To answer your question though, you would put that line in a text file named openhab2 in /etc/default. You could try it… I don’t think it could hurt anything. Maybe try running OH as root to eliminate the possibility of a permissions issue? You said zwave was online. Have you included anything and is everything functional?

[wormuths (Wormuth Household)]

I have no z-wave things to try. I have all kinds of zigbee devices connected to my existing alarm system though. And that’s the one that will not work at this point. I did do a lot of the steps in that document anyhow as part of troubleshooting, figuring they couldn’t hurt. Like adding the openhab user to the groups mentioned. No such luck though.

At this point, all openhab will do is zwave.

[5iver (Scott Rushworth)]

@5iver

It looks like after the controller was first setup, it stayed in Initializing until the binding was restarted. After creating/configuring the coordinator, what happens when you restart OH?

What about this?

[wormuths (Wormuth Household)]

Same thing. It just stays at initializing. I’ve rebooted the entire PC, open OpenHAB, and it’s initializing…

[wormuths (Wormuth Household)]

Wondering how the hardware on this stick works… Wouldn’t the fact that the z-wave portion is currently online rule out that there was a permission or install problem? Is there a way to test the z-wave portion of the stick short of buying things? Is zigbee passing through the same circuitry?

Seems that if the software can access ttyUSB0, then it should be able to access ttyUSB1?

[wormuths (Wormuth Household)]

OMFG!!

Keeping it family friendly… So last night I removed the controllers… Both. Restarted the PC and left it running after I’d essentially given up for the night. Just now I re-installed the z-wave portion, and it’s online. Re-installed the zigbee portion, and it went online too…!!!

Damned if I know, unless it was holding onto a configuration on the backend somewhere which has since been removed? I had initially installed with the 2.1 zigbee binding, and don’t think I ever restarted after removing the stuck controller… I put in 2.2 of the binding and tried again… Maybe something was stuck and since cleared out?

I’ll leave it alone for a day and report back if it still stays online after a restart?

[5iver (Scott Rushworth)]

@wormuths

Seems that if the software can access ttyUSB0, then it should be able to access ttyUSB1?

I would think so. But, based on your log, it looks like the binding is talking to the stick. Before the baud rate setting was configurable, my log only got to ‘Trying to send when not connected’.

Zigbee binding

OH2.1, zigbee binding 2.2.0.201706290942, HUSBZB-1 (Silicon Labs EM3581, EmberZNet Pro 5.4) The Coordinator is stuck at Initializing: 2017-06-30 07:30:55.602 [zigbee ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee 2017-06-30 07:30:55.617 [zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=8, service.id=115, ser…

OH! You just got it working! Wahoo!

@wormuths

I had initially installed with the 2.1 zigbee binding, and don’t think I ever restarted after removing the stuck controller… I put in 2.2 of the binding and tried again

I remember having to restart a bunch of times to clear out the 2.1 binding. You can do a bundle:list in the Karaf console to see what bindings are installed. Maybe they were both installed and the restarts finally cleared the older one. Now the fun begins!

[wormuths (Wormuth Household)]

Ah, yes! Fun! I’ll be in here a million times being told to do other things I should have done before asking in the first place. LOL

Thanks for the help to both you and Chris!

I’ll keep the thread updated if anything develops. In the meantime, I want to say that I have made the switch to open source over the last few years, and this is why… I find the community to always help out, and I always appreciate it. In regards to this project, although I know nothing about how the software works yet, I completely support the efforts everyone is making in developing it. OpenHAB is EXACTLY what home automation needs, and open source is the only way it can happen. Google has no interest in making samsung or apple products work. Samsung doesn’t care to integrate with Ecobee, etc…

This project enables some miracles to happen, and no other community is positioned to do that. Keep up the awesome work!!

Now, I’m off to break some sh*^%$…

[5iver (Scott Rushworth)]

@wormuths

OpenHAB is EXACTLY what home automation needs, and open source is the only way it can happen

True!

Moving forward, get familiar with Habmin. It has some advantages over PaperUI. And if you run into trouble with zigbee, don’t be afraid to pop into the other thread. Once you’ve run discovery, you will likely find some devices that the binding is not ready for. Yet. We just need to be really nice to Chris… and be patient. Or, better yet, contribute to the development!

[wormuths (Wormuth Household)]

Quick Question…

Does it matter what these coordinator things are named? Documentation says spaces aren’t allowed when naming things, but these have spaces in the name. “Ember EM35x Coordinator”. Any issues? Or should I rename them. Afraid to mess with them at this point… LOL

[5iver (Scott Rushworth)]

All of my Things have spaces in their names and I’ve renamed most of them, including my Zigbee coordinator. It would help to see a link to the documentation you referenced, in case it needs to be updated.