Zigbee binding

Kim_Andersen · August 24, 2018, 10:37am

You´l talkning about the ZPIR-8000 (Trust Zigbee motion sensor) right?
According to it´s documentation, it should be Zigbee certified. (I have no idea if that means it´s fully standard Zigbee supported… I would say it is).

If thats all you need, I´m willing to donate the money if there is an easy way, (paypal perhaps).

chris · August 24, 2018, 10:41am

Unfortunately, that doesn’t mean toooo much in this instance. There are different certifications - the commons ones are HAP, SEP, ZLL, but there are a bunch of others. ZigBee 3 tries to unify the different profiles, but there are very few ZB3 devices currently on the market.

If the device is only designed to work with ZLL (ie lighting) then it might be difficult to get it to work with a controller.

Kim_Andersen · August 24, 2018, 10:44am

Great!, so much for certifications. I really love standards!

Kim_Andersen · August 24, 2018, 11:06am

I have the device. I have a Zigbee controller, (Ember EM35x Coordinator, ie Elelabs Zigbee shield). I have OpenHab2…
I did send you a XML file, but for some reason it did not include what you were searching for…
Now… How to go from there:

Why didn´t the xml file contain the information you´re looking for?
Donating the device/money/whatever.
Wait untill you have found a cheap device?
Is there any other way I can provide information?

Anything I can do?.. Remove my zigbee devices, (though this seems to be a problem as well… At least one device got stuck, (Xiaomi device). Reset my controller and remove the devices, then try again… running a sniffer… Whatever, Kill the binding and go back to the stable, throw my Rpi into the wall (I do have a spare one ), stop yelling? . Anything!

Just suggestions to get going.

IvanKujundzic · August 24, 2018, 11:17am

Thanks for info. I bought Zigbee bulb from Trust and it seems that it is working allright. The rest of Trust’s sensors are priced relatively ok, so I was thinking to keep buying…

The more that I read, the more I think that I should not invested in ZigBee controller?

Kim_Andersen · August 24, 2018, 11:30am

I trust Chris will fix it. It´s just a matter of time and providing whatever he needs.

Wavemaker · August 25, 2018, 10:40pm

I just purchased a Telegesis ETRX3USB-LRS, but I have trouble using it in openhab. It remains offline. The debug log is as follows. It seems to me that the final log entry “Telegesis dongle is not the coordinator.” is the real culprit? When googling I only come across the statement in the binding code here. But it’s not quite clear to me what’s the real problem. Can anybody help?

2018-08-26 00:18:51.249 [DEBUG] [e.telegesis.handler.TelegesisHandler] - Initializing ZigBee Telegesis serial bridge handler.
2018-08-26 00:18:51.251 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_telegesis:04000B50].
2018-08-26 00:18:51.263 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 11
2018-08-26 00:18:51.265 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 61066
2018-08-26 00:18:51.267 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID B5739E73BB270CCA
2018-08-26 00:18:51.271 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key null
2018-08-26 00:18:51.275 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 
2018-08-26 00:18:51.292 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 51C0B56BCD7B16989AD92F467C7837D5
2018-08-26 00:18:51.296 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 51C0B56BCD7B16989AD92F467C7837D5
2018-08-26 00:18:51.400 [DEBUG] [e.telegesis.handler.TelegesisHandler] - ZigBee Telegesis Coordinator opening Port:'/dev/ttyUSB0' PAN:ee8a, EPAN:B5739E73BB270CCA, Channel:11
2018-08-26 00:18:51.604 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-08-26 00:18:52.634 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-08-26 00:18:52.636 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-08-26 00:18:52.685 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 51C0B56BCD7B16989AD92F467C7837D5
2018-08-26 00:18:52.691 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle initialize.
2018-08-26 00:18:52.714 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB0] at 19200 baud, flow control FLOWCONTROL_OUT_NONE.
2018-08-26 00:18:52.812 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyUSB0] is initialized.
2018-08-26 00:18:53.909 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Start.
2018-08-26 00:18:54.213 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 000D6F0011139FFA: Node 0 added to the network
2018-08-26 00:18:54.215 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Done.
2018-08-26 00:18:54.218 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task starting
2018-08-26 00:18:54.222 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initResponse is NOT_JOINED
2018-08-26 00:18:54.223 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initializeNetwork is true
2018-08-26 00:18:54.614 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Setting Telegesis trust centre link mode: TC_JOIN_SECURE
2018-08-26 00:18:54.876 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle startup.
2018-08-26 00:18:54.878 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Reinitialising Telegesis dongle and forming network.
2018-08-26 00:18:56.381 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle is not the coordinator.

chris · August 26, 2018, 9:27am

Can you enable debug logging on the driver please log:set debug com.zsmartsystems.zigbee.

You could try a factory reset of the dongle if you can get a serial terminal at 19200bd and type AT&F. The Telegesis driver now works a little differently and does perform a hard reset under some circumstances, and all I can think of at the moment is your dongle has been previously used and is not reconfiguring with the old driver.

Wavemaker · August 26, 2018, 10:01pm

Chris, Thanks for helping

Can you enable debug logging on the driver please log:set debug com.zsmartsystems.zigbee .

Done.

You could try a factory reset of the dongle if you can get a serial terminal at 19200bd and type AT&F .

How to do that exactly? When googling I see there’s a Telegesis development kit to interact with the firmware. I don’t have it. I tried just opening a serial connection to /dev/ttyUSB0 and sending the command. But all I get back is “OK”. But I think that’s the default you get back when sending after connecting with “cu -l /dev/ttyUSB0 -s 19200” (on linux). I doubt something really happened.

Anyway, this is the log, still the same result:

    2018-08-26 23:28:42.769 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_telegesis:04000B50
    2018-08-26 23:28:42.771 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_telegesis:04000B50
    2018-08-26 23:28:42.775 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=402, service.bundleid=260, service.scope=singleton} - org.openhab.binding.zigbee.telegesis
    2018-08-26 23:28:42.784 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=403, service.bundleid=260, service.scope=singleton} - org.openhab.binding.zigbee.telegesis
    2018-08-26 23:28:42.823 [DEBUG] [e.telegesis.handler.TelegesisHandler] - Initializing ZigBee Telegesis serial bridge handler.
    2018-08-26 23:28:42.824 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_telegesis:04000B50].
    2018-08-26 23:28:42.826 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1
    2018-08-26 23:28:42.827 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 0
    2018-08-26 23:28:42.828 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 0000000000000000
    2018-08-26 23:28:42.830 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key null
    2018-08-26 23:28:42.831 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising network
    2018-08-26 23:28:42.832 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee PAN ID [0680].
    2018-08-26 23:28:42.843 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee extended PAN ID [71659DEB20EC5CB6].
    2018-08-26 23:28:42.886 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 
    2018-08-26 23:28:42.888 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 0854C0CE56C3B5156F25EF97C4AB67C6
    2018-08-26 23:28:42.889 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 0854C0CE56C3B5156F25EF97C4AB67C6
    2018-08-26 23:28:42.890 [DEBUG] [e.telegesis.handler.TelegesisHandler] - ZigBee Telegesis Coordinator opening Port:'/dev/ttyUSB0' PAN:680, EPAN:71659DEB20EC5CB6, Channel:-1
    2018-08-26 23:28:42.891 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
    2018-08-26 23:28:43.376 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - ZigBee coordinator is offline - aborted scan for zigbee:coordinator_telegesis:04000B50
    2018-08-26 23:28:43.893 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
    2018-08-26 23:28:43.895 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
    2018-08-26 23:28:43.898 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 0854C0CE56C3B5156F25EF97C4AB67C6
    2018-08-26 23:28:43.902 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle initialize.
    2018-08-26 23:28:43.903 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB0] at 19200 baud, flow control FLOWCONTROL_OUT_NONE.
    2018-08-26 23:28:43.915 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyUSB0] is initialized.
    2018-08-26 23:28:44.812 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Start.
    2018-08-26 23:28:44.831 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 000D6F0011139FFA: Node 0 added to the network
    2018-08-26 23:28:44.832 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Done.
    2018-08-26 23:28:44.832 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task starting
    2018-08-26 23:28:44.832 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initResponse is NOT_JOINED
    2018-08-26 23:28:44.833 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initializeNetwork is true
    2018-08-26 23:28:44.833 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - Can't set channel to -1
    2018-08-26 23:28:44.954 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Setting Telegesis trust centre link mode: TC_JOIN_SECURE
    2018-08-26 23:28:45.203 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle startup.
    2018-08-26 23:28:45.203 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Reinitialising Telegesis dongle and forming network.
    2018-08-26 23:28:46.975 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Error creating Telegesis PAN
    2018-08-26 23:28:47.979 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Error setting Telegesis trust center
    2018-08-26 23:28:48.771 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle is not the coordinator.

I note the error about not being able to set channel -1. When I set that manually in openhab I can get rid of that particular error, but the dongle still ends up as offline:

2018-08-26 23:56:18.377 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration received (Coordinator).
2018-08-26 23:56:18.382 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_initialise >> false.
2018-08-26 23:56:18.385 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_channel >> 11.
2018-08-26 23:56:18.388 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_password >> password.
2018-08-26 23:56:18.390 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_panid >> 1664.
2018-08-26 23:56:18.393 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_extendedpanid >> 71659DEB20EC5CB6.
2018-08-26 23:56:18.402 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Setting Telegesis trust centre link mode: TC_JOIN_SECURE
2018-08-26 23:56:18.711 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Start.
2018-08-26 23:56:18.769 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Done.
2018-08-26 23:56:18.771 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task shutdown
2018-08-26 23:56:18.811 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port '/dev/ttyUSB0' closed.
2018-08-26 23:56:18.821 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle shutdown.
2018-08-26 23:56:18.823 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network [zigbee:coordinator_telegesis:04000B50] closed.
2018-08-26 23:56:18.825 [DEBUG] [e.telegesis.handler.TelegesisHandler] - Initializing ZigBee Telegesis serial bridge handler.
2018-08-26 23:56:18.828 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_telegesis:04000B50].
2018-08-26 23:56:18.830 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 11
2018-08-26 23:56:18.836 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 1664
2018-08-26 23:56:18.839 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 71659DEB20EC5CB6
2018-08-26 23:56:18.841 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key null
2018-08-26 23:56:18.843 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 
2018-08-26 23:56:18.846 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 48F075B032B449E417007CEB9E0668DD
2018-08-26 23:56:18.848 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 48F075B032B449E417007CEB9E0668DD
2018-08-26 23:56:18.851 [DEBUG] [e.telegesis.handler.TelegesisHandler] - ZigBee Telegesis Coordinator opening Port:'/dev/ttyUSB0' PAN:680, EPAN:71659DEB20EC5CB6, Channel:11
2018-08-26 23:56:18.861 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-08-26 23:56:19.867 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-08-26 23:56:19.870 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-08-26 23:56:19.874 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 48F075B032B449E417007CEB9E0668DD
2018-08-26 23:56:19.876 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle initialize.
2018-08-26 23:56:19.878 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB0] at 19200 baud, flow control FLOWCONTROL_OUT_NONE.
2018-08-26 23:56:19.887 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyUSB0] is initialized.
2018-08-26 23:56:20.799 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Start.
2018-08-26 23:56:20.819 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 000D6F0011139FFA: Node 0 added to the network
2018-08-26 23:56:20.820 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Done.
2018-08-26 23:56:20.821 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task starting
2018-08-26 23:56:20.822 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initResponse is NOT_JOINED
2018-08-26 23:56:20.823 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initializeNetwork is true
2018-08-26 23:56:21.077 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Setting Telegesis trust centre link mode: TC_JOIN_SECURE
2018-08-26 23:56:21.447 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle startup.
2018-08-26 23:56:21.449 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Reinitialising Telegesis dongle and forming network.
2018-08-26 23:56:22.917 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle is not the coordinator.

chris · August 26, 2018, 10:07pm

You need to use a terminal program, set to 19200bd, and type in AT&F - this should reset it. I see a number of errors in the log, and I think this might resolve them.

The next version of the binding will do this automatically once the libraries are merged…

Wavemaker · August 26, 2018, 10:20pm

Well that’s what I did. And I did again. I am quite sure that I correctly applied the factory reset. I can also get the device information using the “ATI” command (happens to be “Telegesis ETRX357-LRS”). So I am sure the serial connection works.

But the result is identical to the first log in my latest message above.

Anything else I can try?

chris · August 26, 2018, 10:29pm

I think we’ll need to set up trace logging on com.zsmartsystems.zigbee.dongle.telegesis to see what is happening. I’m not sure if it will give us much more information, but we need to find out why there’s all these errors. It’s as though this dongle is in a mode that doesn’t allow it to be configured as a coordinator (can’t set PAN, can’t set TC and not the coordinator). It’s not something I’ve seen before anyway…

I should add that not every command is giving an error so general communications must be working.

Wavemaker · August 26, 2018, 10:37pm

In the second log (when I manually set a channel), I see no errors until it concludes that that stick is not the coordinator. If I am correct on that it seems to all come to this line in the code.
I have no knowledge on this code/technology really, but could it simpy be commented out…? Or could the binding be fooled there by making a wrong comparison? I tried a cc2531 stick before without succes. It’s not physically connected and not present as think in openhab, but could it possibly be still lingering around and messing things up?

chris · August 26, 2018, 10:41pm

Firstly, this line of code is gone in the new version, but please consider that this is telling you something is wrong. Sure, we can comment this line out, but the device still won’t be a coordinator, so it still won’t work.

We need to understand what is happening. I’ve not come across this sort of error before and we have tested this with dozens of installations with this stick.

amarpulli · August 27, 2018, 9:38am

Hello,

I have few CC2538 modules. i am new to zigbee environment.

Please provide the setup and configuration of CC2538 modules with openhab2.

Thanks and Regards,
Amar.

chris · August 27, 2018, 9:42am

This is not supported at the moment - or at least not tested. The 2531 is supported and I’ve never tried to run the 2538.

You can find the 2531 drivers at the link below if you want to try and modify them. If you want more support, please contact me off list (chris -at- cd-jackson.com).

amarpulli · August 27, 2018, 10:19am

Thanks for response @chris

I successfully cloned your repo. But how to proceed further step.
Can please explain steps.

chris · August 27, 2018, 10:57am

You need to debug the driver. I would suggest to first check to see if the 2538 ZNP is the same protocol as the 2531 (I assume it is close, but I have not looked). If it is, then you need to find any differences and update the driver to work around them.

Kim_Andersen · August 27, 2018, 8:14pm

@chris

I´m not sure what I have messed up now. I was playing around with my Philips Hue deviced, to try to somehow get them inclued again. All tries failed… So I deleted the controller (Thing) and thought I could re-add it again. But the binding could no longer find it…
Well, when things aren´t working, shut down Openhab, clear the cache/tmp, and restart (reboot). So I did…
Now I end up with this error, and OpenHab still cant find the controller.

2018-08-27 22:05:35.075 [ERROR] [org.openhab.binding.zigbee          ] - FrameworkEvent ERROR - org.openhab.binding.zigbee

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zigbee [250]

  Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.4.0.201808020834"; osgi.identity="org.openhab.binding.zigbee"; singleton:="true"

	at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1614) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) [?:?]

	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [?:?]

	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [?:?]

2018-08-27 22:05:35.113 [ERROR] [org.openhab.binding.zigbee.ember    ] - FrameworkEvent ERROR - org.openhab.binding.zigbee.ember

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zigbee.ember [252]

  Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.4.0.201808020834"; osgi.identity="org.openhab.binding.zigbee.ember"; singleton:="true"

	at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1614) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528) [?:?]

	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) [?:?]

	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [?:?]

	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [?:?]

Any reason why it all of a sudden wont work at all??

chris · August 27, 2018, 8:24pm

You probably have 2 ember bindings running - the error means that it can’t start the binding as another bundle with the same name is already running.