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.
What about this?
Same thing. It just stays at initializing. I’ve rebooted the entire PC, open OpenHAB, and it’s initializing…
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?
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?
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’.
OH! You just got it working! Wahoo!
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!
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*^%$… 
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!
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
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.
Okay, ITEMS can’t have spaces in the names. Sorry, been reading too much. Glad I’m in the beginners forum. LOL
So it doesn’t survive a restart.
I restarted, and both the z-wave and zigbee controllers are OFFLINE. Gotta run out tonight, but I wanted to update. What is the Karaf command to restart the bindings? I’ll try later.
That’s odd. Did you happen to unplug the stick and then plug it back in again? If so, it could have come up on different ports. A system restart should put them back, or you could look into udev rules to make them static. If not, I don’t know what could cause this, but you could do a bundle:list in Karaf console and you’ll see something like this:
openhab> bundle:list
START LEVEL 100 , List Threshold: 50
ID │ State │ Lvl │ Version │ Name
────┼──────────┼─────┼────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
15 │ Active │ 80 │ 2.1.0.201709182108 │ ZWave Binding
16 │ Active │ 80 │ 2.2.0.201709152241 │ ZigBee Binding
17 │ Active │ 80 │ 5.3.1.201602281253 │ OSGi JAX-RS Connector
18 │ Active │ 80 │ 2.4.5 │ Jackson-annotations
19 │ Active │ 80 │ 2.4.5 │ Jackson-core
20 │ Active │ 80 │ 2.4.5 │ jackson-databind
21 │ Active │ 80 │ 2.4.5 │ Jackson-dataformat-XML
If the binding state is Resolved, then it is not started. Do a bundle:start X, where X is the ID listed from the bundle:list results. Here I have zwave on ID 15 and zigbee on ID 16. Did you see anything in the logs?
Bindings show as active. Z-Wave on /dev/ttyUSB0 shows “OFFLINE - COMMUNICATION_ERROR zwave.thingstate.serial_notfound” and ZigBee controller shows “OFFLINE - COMMUNICATION_ERROR Serial Error: Port/dev/ttyUSB1 does not exist”.
Looks like this is now a port issue…
dmesg | grep tty
[ 0.000000] console [tty0] enabled
[ 23.773896] usb 8-1.1: cp210x converter now attached to ttyUSB0
[ 23.781596] usb 8-1.1: cp210x converter now attached to ttyUSB1
[ 24.046497] cp210x ttyUSB1: failed set req 0x1e size 4 status: -32
[ 24.046503] cp210x ttyUSB1: failed to set baud rate to 300
[ 184.798996] cp210x ttyUSB1: failed get req 0x1d size 4 status: -110
[ 184.799006] cp210x ttyUSB1: failed get req 0x4 size 2 status: -19
[ 184.799019] cp210x ttyUSB1: failed set request 0x3 status: -19
[ 184.799035] cp210x ttyUSB1: failed set request 0x3 status: -19
[ 184.799047] cp210x ttyUSB1: failed set request 0x3 status: -19
[ 184.799052] cp210x ttyUSB1: failed get req 0x14 size 16 status: -19
[ 184.799059] cp210x ttyUSB1: failed set req 0x1e size 4 status: -19
[ 184.799063] cp210x ttyUSB1: failed to set baud rate to 300
[ 184.799255] cp210x ttyUSB0: failed set request 0x0 status: -19
[ 184.799260] cp210x ttyUSB0: cp210x_open - Unable to enable UART
[ 184.803084] cp210x ttyUSB1: failed set request 0x0 status: -19
[ 184.803091] cp210x ttyUSB1: cp210x_open - Unable to enable UART
[ 184.803158] cp210x ttyUSB0: failed set request 0x0 status: -19
[ 184.803162] cp210x ttyUSB0: cp210x_open - Unable to enable UART
[ 199.110051] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 199.110401] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
ttyUSB0 or ttyUSB1 dont show in ls /dev/tty*. Tried unplugging and reinserting the stick.
Is there any power management enabled on your USB ports? Also, are you unplugging the stick while OH is running (best not to)? What happens after rebooting the system?
No. I left it running for a day when they were online and they stayed that way. I didn’t do anything except reboot and the port situation occurred. I have a request out in the Mint forum looking for answers to that issue.
Another restart and up they came. Strange.
I’m eliminating my frustration by playing with some other things in here for a while. Got the Hue lights installed, got a stereo that’s supported, plex, etc… I’ll play with those things for a while instead of frustrating myself to the point of quitting over zigbee. 
I’ll keep this thread posted if they go offline again.
Hi All, I recently bought a HUBBZB-1 dongle, zwave binding works perfectly but not the zigbee.
The thing keep saying zigbee.status.offline_startupfail
Someone had a similar problem?
/dev/ttyUSB1, Baud is on 57600
here part of the final log on debug,
2017-12-03 22:22:55.150 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - --> TX ASH frame: AshFrameData [frmNum=0, ackNum=0, reTx=false, data=31 00 02 01 04 01 00 00 00 01 01 00 00 00 00]
2017-12-03 22:22:55.262 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=0, ackNum=1, reTx=false, data=31 80 02 00]
2017-12-03 22:22:55.264 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - RX EZSP: EzspAddEndpointResponse [status=EZSP_SUCCESS]
2017-12-03 22:22:55.264 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=1]
2017-12-03 22:22:55.264 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EzspAddEndpointResponse [status=EZSP_SUCCESS]
2017-12-03 22:22:55.265 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - TX EZSP queue: 1
2017-12-03 22:22:55.266 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - TX EZSP: EzspGetNetworkParametersRequest []
2017-12-03 22:22:55.267 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - --> TX ASH frame: AshFrameData [frmNum=1, ackNum=1, reTx=false, data=32 00 28]
2017-12-03 22:22:55.385 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=1, ackNum=2, reTx=false, data=32 80 28 93 00 00 00 00 00 00 00 00 00 FF FF FF 00 00 FF FF 00 00 00 00 00]
2017-12-03 22:22:55.386 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - RX EZSP: EzspGetNetworkParametersResponse [status=EMBER_NOT_JOINED, nodeType=EMBER_UNKNOWN_DEVICE, parameters=EmberNetworkParameters [extendedPanId={00 00 00 00 00 00 00 00}, panId=65535, radioTxPower=255, radioChannel=0, joinMethod=EMBER_USE_MAC_ASSOCIATION, nwkManagerId=65535, nwkUpdateId=0, channels=00000000]]
2017-12-03 22:22:55.387 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=2]
2017-12-03 22:22:55.391 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EzspGetNetworkParametersResponse [status=EMBER_NOT_JOINED, nodeType=EMBER_UNKNOWN_DEVICE, parameters=EmberNetworkParameters [extendedPanId={00 00 00 00 00 00 00 00}, panId=65535, radioTxPower=255, radioChannel=0, joinMethod=EMBER_USE_MAC_ASSOCIATION, nwkManagerId=65535, nwkUpdateId=0, channels=00000000]]
2017-12-03 22:22:55.393 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - TX EZSP queue: 1
2017-12-03 22:22:55.394 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - TX EZSP: EzspGetCurrentSecurityStateRequest []
2017-12-03 22:22:55.394 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - --> TX ASH frame: AshFrameData [frmNum=2, ackNum=2, reTx=false, data=33 00 69]
2017-12-03 22:22:55.506 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=2, ackNum=3, reTx=false, data=33 80 69 93 00 05 11 41 03 00 00 00 03 00]
2017-12-03 22:22:55.513 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - RX EZSP: EzspGetCurrentSecurityStateResponse [status=EMBER_NOT_JOINED, state=EmberCurrentSecurityState [bitmask=[], trustCenterLongAddress=0003000000034111]]
2017-12-03 22:22:55.513 [DEBUG] [bee.dongle.ember.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=3]
2017-12-03 22:22:55.514 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EzspGetCurrentSecurityStateResponse [status=EMBER_NOT_JOINED, state=EmberCurrentSecurityState [bitmask=[], trustCenterLongAddress=0003000000034111]]
2017-12-03 22:22:55.515 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Error during retrieval of security parameters: EzspGetCurrentSecurityStateResponse [status=EMBER_NOT_JOINED, state=EmberCurrentSecurityState [bitmask=[], trustCenterLongAddress=0003000000034111]]
2017-12-03 22:22:55.516 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize done: Initialised true
2017-12-03 22:22:55.523 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - null: Node 0 is added to the network
I have this device and am trying to use it for the first time.
Paper UI is showing online, yet the log’s last few things about zigbee say:
/var/log/openhab2/events.log:9797:2018-06-24 10:30:35.781 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:0844a8aa' changed from UNINITIALIZED to INITIALIZING
/var/log/openhab2/events.log:9798:2018-06-24 10:30:35.825 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:0844a8aa' changed from INITIALIZING to UNKNOWN
/var/log/openhab2/events.log:9804:2018-06-24 10:30:38.522 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:0844a8aa' changed from UNKNOWN to OFFLINE: Failed to startup ZigBee transport layer
/var/log/openhab2/events.log:9942:2018-06-24 10:30:49.518 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:0844a8aa' changed from OFFLINE: Failed to startup ZigBee transport layer to ONLINE
/var/log/openhab2/events.log:9943:2018-06-24 10:30:49.559 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_ember:0844a8aa changed to UNKNOWN.
/var/log/openhab2/events.log:9944:2018-06-24 10:30:49.956 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:0844a8aa' has been updated.
Last one to me looks like it failed to start up. How come it says online? Is it really online or does it have a problem?
Another zipbee-beginner question: How do you pair devices with this? With the Z-Stick 5 for ZWave, there’s a button for that. But here, I don’t see anything in the paperUI to put it into inclusion mode.
The last line is fine - it just says the thing was updated - probably the properties were updated (just guessing as the events log doesn’t really provide much information).
Before that there is an OFFLINE, then 10 seconds later it shows ONLINE. Maybe it’s started ok? I’d suggest to put the binding into debug and checking the log to see what’s happening - this doesn’t really provide a lot to go on.