I’m tinkering with a separate instance of OH, running 4.2.1. My ‘production’ version is 3.4, but I’m looking to get Zigbee up and running before I migrate and make the switch.
I have an Aeotec Zigbee stick and manage to get it online - briefly. After around 10 seconds I get the following error in my logs:
This cycles a few times over before eventually staying offline with the following then reported in the logs:
2024-08-23 08:31:42.407 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: Cannot invoke “com.zsmartsystems.zigbee.dongle.ember.internal.transaction.EzspTransaction.getResponse()” because “transaction” is null
at com.zsmartsystems.zigbee.dongle.ember.EmberNcp.getConfiguration(EmberNcp.java:507) ~[?:?]
at com.zsmartsystems.zigbee.dongle.ember.internal.EmberStackConfiguration.getConfiguration(EmberStackConfiguration.java:72) ~[?:?]
at com.zsmartsystems.zigbee.dongle.ember.ZigBeeDongleEzsp.initialize(ZigBeeDongleEzsp.java:439) ~[?:?]
at com.zsmartsystems.zigbee.ZigBeeNetworkManager.initialize(ZigBeeNetworkManager.java:418) ~[?:?]
at org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler.initialiseZigBee(ZigBeeCoordinatorHandler.java:431) ~[?:?]
at org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler.lambda$2(ZigBeeCoordinatorHandler.java:557) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
Quite simply, I’m at a loss as to where to begin. I’d considered ditching the dongle altogether in favour of a Tubesz ethernet controller, but it seems unreasonable that the one I have should be so problematic. I’ve tried flashing with the latest firmware to no avail.
Reading the threads I see I’m not the only one that’s had trouble getting Zigbee up and running. I’m prepared to ditch what I have and start again if there’s a “known good” suggestion, but for the moment I’m clean out of ideas. Anyone?
I’m not familiar with the Aotec controller, but before ditching it, I’d suggest to enable debug logging so we can see what is going on. If it’s using a standard Silabs chipset, then it should work fine, and it’s used extensively by some commercial companies… The logs are important though as without this it’s a guess as to what’s wrong with your system.
If you’re looking for an ethernet system, then personally I’m using an SLZB06M which is an Ethernet based controller and supported natively by the binding.
Sensible enough that I should have done that earlier … setting it to debug via the UI in Settings seemed to introduce an error in the format of my log4j2.xml file which took a bit of figuring out. Tried again via console and just went straight to Trace level instead:
2024-08-25 13:30:22.027 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : dm ZigBeeCoordinatorHandler tracking 8 MultipleDynamic added {org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler}={service.id=700, service.bundleid=306, service.scope=singleton} (enter)
2024-08-25 13:30:22.029 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : dm ZigBeeCoordinatorHandler tracking 8 MultipleDynamic already active, binding {org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler}={service.id=700, service.bundleid=306, service.scope=singleton}
2024-08-25 13:30:22.030 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : invoking bind: addZigBeeCoordinatorHandler: parameters [org.openhab.binding.zigbee.ember.handler.EmberHandler]
2024-08-25 13:30:22.031 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : invoked bind: addZigBeeCoordinatorHandler
2024-08-25 13:30:22.033 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : dm ZigBeeCoordinatorHandler tracking 8 MultipleDynamic added {org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler}={service.id=700, service.bundleid=306, service.scope=singleton} (exit)
2024-08-25 13:30:22.086 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:89bea9b33c].
2024-08-25 13:30:22.087 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 11
2024-08-25 13:30:22.088 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 99999
2024-08-25 13:30:22.089 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 999997ABD0877C5F
2024-08-25 13:30:22.089 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network Key 99999282A9E4A53C0169F47A1FE38EEA
2024-08-25 13:30:22.090 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link Key 999997426565416C6C69616E63653039
2024-08-25 13:30:22.091 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Config: zigbee_initialise found, initializeNetwork=false
2024-08-25 13:30:22.092 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network Key String 99999282A9E4A53C0169F47A1FE38EEA
2024-08-25 13:30:22.094 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network key final array 99999282A9E4A53C0169F47A1FE38EEA
2024-08-25 13:30:22.095 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link Key String 999997426565416C6C69616E63653039
2024-08-25 13:30:22.096 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link key final array 999997426565416C6C69616E63653039
2024-08-25 13:30:22.097 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.
2024-08-25 13:30:22.098 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'/dev/ttyUSB0' PAN:5192, EPAN:999997ABD0877C5F, Channel:11
2024-08-25 13:30:22.100 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Ember end device poll timeout set to (169 * 2^9) = 86528 seconds
2024-08-25 13:30:22.101 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2024-08-25 13:30:23.102 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2024-08-25 13:30:23.103 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2024-08-25 13:30:23.104 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=INITIALISING
2024-08-25 13:30:23.117 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 943469FFFE16A42C: ZigBee reading network state complete.
2024-08-25 13:30:23.118 [DEBUG] [nding.zigbee.serial.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB0] at 115200 baud, flow control FLOWCONTROL_OUT_RTSCTS.
2024-08-25 13:30:23.139 [DEBUG] [nding.zigbee.serial.ZigBeeSerialPort] - Serial port [/dev/ttyUSB0] is initialized.
2024-08-25 13:30:24.238 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: have 7 bytes available
2024-08-25 13:30:24.239 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: try read 7 at offset 0
2024-08-25 13:30:24.340 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: did read 0 of 7 at offset 0
2024-08-25 13:30:24.341 [WARN ] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: received IOException in serial port event
java.io.IOException: Expected to be able to read 7 bytes, but saw error after 0
at org.openhab.binding.zigbee.serial.ZigBeeSerialPort.serialEvent(ZigBeeSerialPort.java:345) [bundleFile:?]
at org.openhab.core.io.transport.serial.rxtx.RxTxSerialPort$1.serialEvent(RxTxSerialPort.java:82) [bundleFile:?]
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:834) ~[bundleFile:5.2.1.OH1]
at gnu.io.RXTXPort.eventLoop(Native Method) [bundleFile:5.2.1.OH1]
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:108) [bundleFile:5.2.1.OH1]
2024-08-25 13:30:33.143 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=OFFLINE
2024-08-25 13:30:34.170 [INFO ] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee dongle inactivity timer. Reinitializing ZigBee
2024-08-25 13:30:34.171 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=SHUTDOWN
2024-08-25 13:30:34.181 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 943469FFFE16A42C: ZigBee saving network state complete.
2024-08-25 13:30:34.284 [DEBUG] [nding.zigbee.serial.ZigBeeSerialPort] - Serial port '/dev/ttyUSB0' closed.
2024-08-25 13:30:34.285 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.
2024-08-25 13:30:34.286 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'/dev/ttyUSB0' PAN:5192, EPAN:999997ABD0877C5F, Channel:11
2024-08-25 13:30:34.287 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Ember end device poll timeout set to (169 * 2^9) = 86528 seconds
2024-08-25 13:30:34.288 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2024-08-25 13:30:35.288 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2024-08-25 13:30:35.289 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2024-08-25 13:30:35.290 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=INITIALISING
2024-08-25 13:30:35.301 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 943469FFFE16A42C: ZigBee reading network state complete.
2024-08-25 13:30:35.303 [DEBUG] [nding.zigbee.serial.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB0] at 115200 baud, flow control FLOWCONTROL_OUT_RTSCTS.
2024-08-25 13:30:35.325 [DEBUG] [nding.zigbee.serial.ZigBeeSerialPort] - Serial port [/dev/ttyUSB0] is initialized.
2024-08-25 13:30:36.424 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: have 7 bytes available
2024-08-25 13:30:36.425 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: try read 7 at offset 0
2024-08-25 13:30:36.525 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: did read 0 of 7 at offset 0
2024-08-25 13:30:36.526 [WARN ] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: received IOException in serial port event
java.io.IOException: Expected to be able to read 7 bytes, but saw error after 0
at org.openhab.binding.zigbee.serial.ZigBeeSerialPort.serialEvent(ZigBeeSerialPort.java:345) [bundleFile:?]
at org.openhab.core.io.transport.serial.rxtx.RxTxSerialPort$1.serialEvent(RxTxSerialPort.java:82) [bundleFile:?]
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:834) ~[bundleFile:5.2.1.OH1]
at gnu.io.RXTXPort.eventLoop(Native Method) [bundleFile:5.2.1.OH1]
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:108) [bundleFile:5.2.1.OH1]
2024-08-25 13:30:39.624 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: have 7 bytes available
2024-08-25 13:30:39.625 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: try read 7 at offset 0
2024-08-25 13:30:39.626 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: did read 7 of 7 at offset 0
2024-08-25 13:30:40.884 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: have 13 bytes available
2024-08-25 13:30:40.885 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: try read 13 at offset 0
2024-08-25 13:30:40.986 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: did read 0 of 13 at offset 0
2024-08-25 13:30:40.986 [WARN ] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: received IOException in serial port event
java.io.IOException: Expected to be able to read 13 bytes, but saw error after 0
at org.openhab.binding.zigbee.serial.ZigBeeSerialPort.serialEvent(ZigBeeSerialPort.java:345) [bundleFile:?]
at org.openhab.core.io.transport.serial.rxtx.RxTxSerialPort$1.serialEvent(RxTxSerialPort.java:82) [bundleFile:?]
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:834) ~[bundleFile:5.2.1.OH1]
at gnu.io.RXTXPort.eventLoop(Native Method) [bundleFile:5.2.1.OH1]
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:108) [bundleFile:5.2.1.OH1]
2024-08-25 13:30:42.475 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: have 13 bytes available
2024-08-25 13:30:42.476 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: try read 13 at offset 0
2024-08-25 13:30:42.482 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: did read 1 of 13 at offset 0
2024-08-25 13:30:42.483 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: try read 12 at offset 1
2024-08-25 13:30:42.584 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: did read 0 of 12 at offset 1
2024-08-25 13:30:42.584 [WARN ] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: received IOException in serial port event
java.io.IOException: Expected to be able to read 13 bytes, but saw error after 1
at org.openhab.binding.zigbee.serial.ZigBeeSerialPort.serialEvent(ZigBeeSerialPort.java:345) [bundleFile:?]
at org.openhab.core.io.transport.serial.rxtx.RxTxSerialPort$1.serialEvent(RxTxSerialPort.java:82) [bundleFile:?]
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:834) ~[bundleFile:5.2.1.OH1]
at gnu.io.RXTXPort.eventLoop(Native Method) [bundleFile:5.2.1.OH1]
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:108) [bundleFile:5.2.1.OH1]
2024-08-25 13:30:45.328 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=OFFLINE
2024-08-25 13:30:45.658 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: have 10 bytes available
2024-08-25 13:30:45.659 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: try read 10 at offset 0
2024-08-25 13:30:45.659 [TRACE] [nding.zigbee.serial.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: did read 10 of 10 at offset 0
2024-08-25 13:30:47.713 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=SHUTDOWN
2024-08-25 13:30:47.726 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 943469FFFE16A42C: ZigBee saving network state complete.
2024-08-25 13:30:47.798 [DEBUG] [nding.zigbee.serial.ZigBeeSerialPort] - Serial port '/dev/ttyUSB0' closed.
2024-08-25 13:30:47.800 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network [zigbee:coordinator_ember:89bea9b33c] closed.
2024-08-25 13:30:47.805 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : dm ZigBeeCoordinatorHandler tracking 9 MultipleDynamic removed {org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler}={service.id=700, service.bundleid=306, service.scope=singleton} (enter)
2024-08-25 13:30:47.806 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : invoking unbind: removeZigBeeCoordinatorHandler: parameters [org.openhab.binding.zigbee.ember.handler.EmberHandler]
2024-08-25 13:30:47.807 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : invoked unbind: removeZigBeeCoordinatorHandler
2024-08-25 13:30:47.808 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - bundle org.openhab.binding.zigbee:4.2.1 (301)[org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService(407)] : dm ZigBeeCoordinatorHandler tracking 9 MultipleDynamic removed (unbind) {org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler}={service.id=700, service.bundleid=306, service.scope=singleton}
Pardon my ignorance - but the SLZB06M would not require MQTT, is that correct? If my problems appear more related to the Aeotec than anything else, I’d definitely give an ethernet approach a shot.
Thanks for the log. Trace in this case might have turned out to be useful as it seems to indicate some sort of error reading the USB serial port. It shows the binding is notified that there are bytes to be read, but when it reads the data, nothing is returned. I’m not sure if this is running off a hub - problems like this can be caused by unpowered hubs, but otherwise I’m not really sure why this would be happening.
That’s correct - it’s using a TCP socket in a similar way to the way the serial port is used, so no MQTT. Just to note that there was a bug fixed a couple of months back that is possibly only in the snapshot so I’d recommend using this as it resolves an issue with network reconnection if there’s any error…
No hub, straight into the Pi USB port, and it’s powered with a ‘proper’ power supply. I’ll try a different port to be sure. I also spotted the error in reading the port and that did catch my interest. Short of trying another device I’m not sure how to troubleshoot it further. I’ll try the snapshot build as well just in case - it’s my test environment, so plenty of room to break it if need be.
Ooh, I should also point out … not relevant to the read error (I don’t think), but openHab docs specify hardware flow control for the Aeotec, whereas Aeotec KB article specifies ‘none’. I’ve tried all three options and had the same result.
I’ll look at the ethernet option as well, that may end up being more suitable as I could obviously place it nearly anywhere, and potentially have a second one to give greater coverage. I was about to ask for some tips on config, but I see (as you indicated) there’s a SLZB06-specific option when adding a new Thing.
did you try a powered usb hub instead? sometimes pi just cannot give enough power to the usb regardless of what power supply PI is using. Unless this dongle has its own separate power
I’m starting to think you might be right. I’m running it on USB-connected SSD, too, so that might be sucking just a little more juice at times and tipping it over the threshold.
I’ve just given it a try, but the dongle isn’t being detected through the hub I have on hand. Plug it back into the Pi and check dmesg, it’s detected immediately. (Oh, I also tried a much beefier power supply with it directly plugged into the Pi and it was the same result as earlier).
The powered hub approach wouldn’t have been my preference simply because I like the small footprint of a Pi, but I was interested to try it from a troubleshooting standpoint.
I think it’s time to cut my losses. If I get my hands on another powered hub I’ll try again out of interest sake, but for the moment I’ll keep checking the shipment tracking on the SLZB06.
I’ve had my fair share of bizzare issues that got magically resolved by using powered hub instead of direct usb connection. I feel even usb stick with too many led lights can create power surge for this tiny pi thing
Plugged it in, acquired an IP and I thought I’ll come to this later when I have time.
“Later”, I couldn’t connect to it - took me a while to figure out it was no longer on the network. No problem … unplug / re-plug / etc. Lights up with power from POE, but no longer connects; Unifi switch also shows the port it’s plugged into is disconnected. Tried reset and other options from the seller, his conclusion is that it’s fried somehow and he’s sending another. I’ll keep this one in case I use it for USB one day.
He advised that it only runs at 100Mbps and I should manually tune the switch port to that speed - I’m wondering if it messed up during the first connection
The instructions for the SLZB specify using MQTT, but the HA instructions don’t seem reliant upon this. I’m guessing with OH I can just configure the Thing with an IP and the same port as specified for HA and I should be good to go?
I don’t recall changing too much when I set mine up. I set the network mode to Ethernet (since I use the PoE for power), and I configured the device name to zigbee (then I can address it with zigbee.local).
Below are a bunch of screenshots of what I think are all the relevant pages in the SLZB and also the relevant network configuration for the OH thing. It should be easy, but if you have any probs, just shout. This is relatively new functionality in openHAB so it’s always possible there’s bugs when setting it up…
), so another one is on the way!
)
