Thanks, done 
1 Like
Hey @chris the pr has been in for a few days and the pressure spikes appear to have stopped. I think it did the trick. Thanks.
1 Like
I have upgraded to M4 and the latest bindings, but I am seeing some errors in the main OH log file now. I will get those figured out and then I’ll see where my zigbee stick is at.
Ok, upgraded to OH M4 and the latest zigbee libs:
openhab> bundle:list -s | grep -i g.zig
285 x Active x 80 x 2.4.0.201810032130 x org.openhab.binding.zigbee.telegesis
287 x Active x 80 x 2.4.0.201810032130 x org.openhab.binding.zigbee.ember
288 x Active x 80 x 2.4.0.201810032130 x org.openhab.binding.zigbee.xbee
293 x Active x 80 x 2.4.0.201810032130 x org.openhab.binding.zigbee
294 x Active x 80 x 2.4.0.201810032130 x org.openhab.binding.zigbee.cc2531
openhab> bundle:list -s | grep -i s.zig
286 x Active x 80 x 1.1.2 x com.zsmartsystems.zigbee.dongle.cc2531
289 x Active x 80 x 1.1.2 x com.zsmartsystems.zigbee
290 x Active x 80 x 1.1.2 x com.zsmartsystems.zigbee.dongle.xbee
291 x Active x 80 x 1.1.2 x com.zsmartsystems.zigbee.dongle.ember
292 x Active x 80 x 1.1.2 x com.zsmartsystems.zigbee.dongle.telegesis
but I am still seeing the same behavior:
- zigbee logs look good on startup
2018-10-06 17:29:32.162 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=343, service.bundleid=285, service.scope=singleton} - org.openhab.binding.zigbee.telegesis 2018-10-06 17:29:32.165 [DEBUG] [e.telegesis.handler.TelegesisHandler] - Initializing ZigBee Telegesis serial bridge handler. 2018-10-06 17:29:32.166 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_telegesis:04003E38]. 2018-10-06 17:29:32.166 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1 2018-10-06 17:29:32.167 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 49600 2018-10-06 17:29:32.167 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 785E4F0CDFD4E66B 2018-10-06 17:29:32.167 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network Key null 2018-10-06 17:29:32.167 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link Key null 2018-10-06 17:29:32.168 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network Key String 2018-10-06 17:29:32.168 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network key initialised 80C519ACEC72365F1AEF152485FCB27A 2018-10-06 17:29:32.169 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network key final array 80C519ACEC72365F1AEF152485FCB27A 2018-10-06 17:29:32.169 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link Key String 2018-10-06 17:29:32.169 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link Key String has invalid format. Revert to default key. 2018-10-06 17:29:32.169 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link key final array 5A6967426565416C6C69616E63653039 2018-10-06 17:29:32.174 [DEBUG] [e.telegesis.handler.TelegesisHandler] - ZigBee Telegesis Coordinator opening Port:'/dev/ttyUSB1' PAN:c1c0, EPAN:785E4F0CDFD4E66B, Channel:-1 2018-10-06 17:29:32.176 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
-
Yet PaperUI shows it as offline:
Status: OFFLINE Failed to startup ZigBee transport layer -
And when I start a scan it aborts right after it starts:
> 2018-10-06 17:30:37.118 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_telegesis:04003E38 > 2018-10-06 17:30:37.118 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee coordinator is offline - aborted scan for zigbee:coordinator_telegesis:04003E38
Worth noting that I see several ServiceEvent REGISTER / ServiceEvent UNREGISTERING cycles in the logs. This may have been correlated to when I check the dongle status in PaperUI, but I can’t say for sure
Full logs: openhab.log zigbee.log
Hi Scott… Thnks for your example…
My org.ops4j.pax.logging.cfg is located in /srv/openhab2-userdata/etc/
I just added this to the config file.
# Zigbee
log4j2.logger.ZSmart.name = com.zsmartsystems.zigbee
log4j2.logger.ZSmart.level = DEBUG
log4j2.logger.ZSmart.additivity = false
log4j2.logger.ZSmart.appenderRefs = ZSmart
log4j2.logger.ZSmart.appenderRef.ZSmart.ref = ZIGBEE
log4j2.logger.Zigbee.name = org.openhab.binding.zigbee
log4j2.logger.Zigbee.level = DEBUG
log4j2.logger.Zigbee.additivity = false
log4j2.logger.Zigbee.appenderRefs = Zigbee
log4j2.logger.Zigbee.appenderRef.Zigbee.ref = ZIGBEE
# Zigbee
log4j2.appender.Zigbee.name = ZIGBEE
log4j2.appender.Zigbee.type = RollingRandomAccessFile
log4j2.appender.Zigbee.fileName = /var/log/openhab2/zigbee.log
log4j2.appender.Zigbee.filePattern = /var/log/openhab2/zigbee.log.%d{yyyyMMddHHmmss}
log4j2.appender.Zigbee.immediateFlush = true
log4j2.appender.Zigbee.append = true
log4j2.appender.Zigbee.layout.type = PatternLayout
log4j2.appender.Zigbee.layout.pattern = %d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%c] - %m%n
log4j2.appender.Zigbee.policies.type = Policies
log4j2.appender.Zigbee.policies.size.type = SizeBasedTriggeringPolicy
log4j2.appender.Zigbee.policies.size.size = 10MB
log4j2.appender.Zigbee.strategy.type = DefaultRolloverStrategy
log4j2.appender.Zigbee.strategy.max = 10
I believe that should do the trick… a zigbee.log file was created in /var/log/openhab2/ but its 0 bytes in size right now… But I think the zigbee binding has stopped working again. I dont get any respons from any of my devices. Could that be the reason for this beeing a 0 byte file?
@5iver
After an reboot, and activationg DEBUG level for zigbee and Zsmart systems, the zigbee-log file is still 0 byte in size…
I guess it´s not logging to this file after all… Hmprf! 
Will continue in this thread:
That’s great - thanks for the feedback 
These are the shortest “full” logs I’ve seen . Please can you enable debug logging - there’s only INFO in here…
I suspect it will show the same issue as previously. There was a bug introduced a while back where the initialisation method returned an error and this stopped the binding starting. I’m pretty sure this was fixed in 1.1.2 though -:
This was merged on the 22nd Sept, and 1.1.2 was released on the 23rd Sept. 
Oops, forgot to enable debug for the main OH classes. Here’s another one: openhab.log Hopefully that gives you what you need
Hmm. I did a fresh M4 install which looks like it was built on Sept 25th. Here’s a full version list of what I’m running:
openhab> bundle:list
START LEVEL 100 , List Threshold: 50
ID │ State │ Lvl │ Version │ Name
────┼──────────┼─────┼────────────────────────┼─────────────────────────────────────────────
20 │ Active │ 80 │ 5.3.1.201602281253 │ OSGi JAX-RS Connector
21 │ Active │ 80 │ 2.7.0.v20170129-0911 │ Gson: Google Json Library for Java
23 │ Active │ 80 │ 3.0.0.v201312141243 │ Google Guice (No AOP)
26 │ Active │ 80 │ 3.5.4 │ JmDNS
28 │ Active │ 80 │ 1.0.0 │ Units of Measurement API
30 │ Active │ 80 │ 1.1.0.Final │ Bean Validation API
31 │ Active │ 80 │ 2.0.1 │ javax.ws.rs-api
32 │ Active │ 80 │ 3.2.0.v201101311130 │ ANTLR Runtime
35 │ Active │ 80 │ 3.2.1 │ Commons Collections
36 │ Active │ 80 │ 1.1 │ Commons Exec
37 │ Active │ 80 │ 2.2.0 │ Commons IO
38 │ Active │ 80 │ 2.6 │ Commons Lang
47 │ Active │ 80 │ 4.2.1 │ Apache Karaf :: OSGi Services :: Event
63 │ Active │ 80 │ 4.6.0 │ Apache XBean OSGI Bundle Utilities
64 │ Active │ 80 │ 4.6.0 │ Apache XBean :: Classpath Resource Finder
65 │ Active │ 80 │ 2.12.0.v20160420-0247 │ EMF Common
66 │ Active │ 80 │ 2.12.0.v20160420-0247 │ EMF Ecore
67 │ Active │ 80 │ 2.11.0.v20160420-0247 │ EMF Change Model
68 │ Active │ 80 │ 2.12.0.v20160420-0247 │ EMF XML/XMI Persistence
69 │ Active │ 80 │ 3.8.0.v20160509-1230 │ Common Eclipse Runtime
70 │ Active │ 80 │ 3.6.100.v20160223-2218 │ Extension Registry Support
80 │ Active │ 80 │ 9.4.11.v20180605 │ Jetty :: Proxy
94 │ Active │ 80 │ 0.4.1.v20180515-1321 │ org.eclipse.lsp4j
95 │ Active │ 80 │ 0.4.1.v20180515-1321 │ org.eclipse.lsp4j.jsonrpc
96 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Config Core
97 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Configuration Discovery
98 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Configuration mDNS Discov
99 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Config Dispatcher
100 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome Config XML
101 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core
102 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core Audio
103 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core Binding XML
104 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core ID
105 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core Persistence
106 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Scheduler Service
107 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core Thing
108 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core Thing XML
109 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Transformation Service
110 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core Voice
111 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Console
112 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Console for OSGi runtime
113 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome JavaSound I/O, Fragments:
114 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Monitor
115 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Net I/O Bundle
116 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome REST Interface Bundle
117 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Core REST API
118 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome REST mDNS Announcer
119 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome REST Interface JAX-RS opt
120 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Sitemap REST API
121 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome SSE REST API
122 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Voice REST API
123 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Bonjour/MDS Service Disco
124 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Web Audio Support
125 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Model Core
126 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Item Model
127 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Item Model IDE
128 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Item Model Runtime
129 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Language Server
130 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Persistence Model
131 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Persistence Model IDE
132 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Persistence Runtime
133 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Rule Model
134 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Rule Model IDE
135 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Rule Runtime
136 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Script
137 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Script Model IDE
138 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Script Runtime
139 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Sitemap Model
140 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Sitemap Model IDE
141 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Sitemap Runtime
142 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Thing Model
143 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Thing Model IDE
144 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Thing Model Runtime
145 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Json Storage Service
146 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome UI
147 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome UI Icons
148 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Classic IconSet
149 │ Active │ 80 │ 2.14.0.v20180522-1629 │ Xtend Runtime Library
150 │ Active │ 80 │ 2.14.0.v20180522-1629 │ Xtend Macro Interfaces
151 │ Active │ 80 │ 2.14.0.v20180522-1821 │ Xtext
152 │ Active │ 80 │ 2.14.0.v20180522-1833 │ Xtext Common Types
153 │ Active │ 80 │ 2.14.0.v20180522-1821 │ Xtext IDE Core
154 │ Active │ 80 │ 2.14.0.v20180522-1821 │ Xtext Utility
155 │ Active │ 80 │ 2.14.0.v20180522-1833 │ Xbase Model
156 │ Active │ 80 │ 2.14.0.v20180522-1833 │ Xbase Generic IDE Services
157 │ Active │ 80 │ 2.14.0.v20180522-1629 │ Xbase Runtime Library
172 │ Active │ 80 │ 1.9.6 │ MIME streaming extension
174 │ Active │ 80 │ 6.2.0 │ org.objectweb.asm
175 │ Active │ 80 │ 6.2.0 │ org.objectweb.asm.commons
176 │ Active │ 80 │ 6.2.0 │ org.objectweb.asm.tree
177 │ Active │ 90 │ 2.4.0.M4 │ openHAB Core
178 │ Active │ 80 │ 2.4.0.M4 │ openHAB Karaf Integration
180 │ Resolved │ 80 │ 2.4.0.M4 │ openHAB Sound Support, Hosts: 113
181 │ Active │ 80 │ 2.4.0.M4 │ openHAB Dashboard UI
186 │ Active │ 80 │ 1.0.2 │ Units of Measurement Common Library
187 │ Active │ 80 │ 1.0.8 │ Units of Measurement Implementation for Jav
199 │ Active │ 80 │ 1.6.0 │ Commons Codec
200 │ Active │ 80 │ 3.3.0 │ Commons Net
201 │ Active │ 80 │ 4.2.3 │ Apache HttpClient OSGi bundle
202 │ Active │ 80 │ 4.2.3 │ Apache HttpCore OSGi bundle
203 │ Active │ 80 │ 3.1.0.7 │ Apache ServiceMix :: Bundles :: commons-htt
204 │ Active │ 80 │ 2.4.0.M4 │ openHAB 1.x Compatibility Layer
205 │ Active │ 80 │ 1.1.1.201605111122 │ Swagger Provider
206 │ Active │ 80 │ 2.4.5 │ Jackson-annotations
207 │ Active │ 80 │ 2.4.5 │ Jackson-core
208 │ Active │ 80 │ 2.4.5 │ jackson-databind
209 │ Active │ 80 │ 2.4.5 │ Jackson-dataformat-XML
210 │ Active │ 80 │ 2.4.5 │ Jackson-dataformat-YAML
211 │ Active │ 80 │ 2.4.5 │ Jackson-module-JAXB-annotations
212 │ Active │ 80 │ 18.0.0 │ Guava: Google Core Libraries for Java
213 │ Active │ 80 │ 2.1.0 │ json-path
214 │ Active │ 80 │ 3.14.0 │ nrjavaserial
220 │ Active │ 80 │ 1.5.8 │ swagger-annotations
221 │ Active │ 80 │ 1.5.8 │ swagger-core
222 │ Active │ 80 │ 1.5.8 │ swagger-jaxrs
223 │ Active │ 80 │ 1.5.8 │ swagger-models
224 │ Active │ 80 │ 3.19.0.GA │ Javassist
225 │ Active │ 80 │ 2.2 │ json-smart
226 │ Active │ 80 │ 3.2.1 │ Apache Commons Lang
227 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Astro Binding
228 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Configuration USB-Serial
229 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Configuration USB-Serial
230 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Config Serial
231 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Serial Transport
232 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Serial Transport for RXTX
233 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Serial Transport extensio
234 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome Exec Transformation Servi
235 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome JavaScript Transformation
236 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome JSonPath Transformation S
237 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome Map Transformation Service
238 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome RegEx Transformation Serv
239 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome Scale Transformation Serv
240 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome XPath Transformation Serv
241 │ Active │ 75 │ 0.10.0.oh240M4 │ Eclipse SmartHome Xslt Transformation Servi
242 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Basic UI, Fragments: 253
243 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome WebApp UI, Fragments: 254
244 │ Active │ 80 │ 0.10.0.oh240M4 │ Eclipse SmartHome Paper UI, Fragments: 257
245 │ Active │ 80 │ 2.4.0.M4 │ DSCAlarm Binding
252 │ Active │ 80 │ 2.4.0.M4 │ openHAB REST Documentation
253 │ Resolved │ 75 │ 2.4.0.M4 │ openHAB Basic UI Fragment, Hosts: 242
254 │ Resolved │ 75 │ 2.4.0.M4 │ openHAB Classic UI Fragment, Hosts: 243
255 │ Active │ 80 │ 2.4.0.M4 │ HABmin User Interface
256 │ Active │ 80 │ 2.4.0.M4 │ HABPanel User Interface
257 │ Resolved │ 75 │ 2.4.0.M4 │ openHAB Paper UI Theme Fragment, Hosts: 244
258 │ Active │ 80 │ 0.9.10.v20160429-1435 │ reflections (wrap)
259 │ Active │ 80 │ 3.1.4 │ Stax2 API
260 │ Active │ 80 │ 1.5.8.v20160511-1038 │ swagger-jersey2-jaxrs (wrap)
274 │ Active │ 80 │ 2.4.0.201810032130 │ ZWave Binding
285 │ Active │ 80 │ 2.4.0.201810032130 │ ZigBee Telegesis Binding
286 │ Active │ 80 │ 1.1.2 │ com.zsmartsystems.zigbee.dongle.cc2531
287 │ Active │ 80 │ 2.4.0.201810032130 │ ZigBee Ember Binding
288 │ Active │ 80 │ 2.4.0.201810032130 │ ZigBee XBee Binding
289 │ Active │ 80 │ 1.1.2 │ com.zsmartsystems.zigbee
290 │ Active │ 80 │ 1.1.2 │ com.zsmartsystems.zigbee.dongle.xbee
291 │ Active │ 80 │ 1.1.2 │ com.zsmartsystems.zigbee.dongle.ember
292 │ Active │ 80 │ 1.1.2 │ com.zsmartsystems.zigbee.dongle.telegesis
293 │ Active │ 80 │ 2.4.0.201810032130 │ ZigBee Binding
294 │ Active │ 80 │ 2.4.0.201810032130 │ ZigBee CC2531 Binding
Unfortunately not (sorry). I don’t see the dongle initialising at all - in fact there’s nothing in the log that I can see from the ZigBeeCoordinatorHandler class. On top of this it’s missing the zsmartsystems library debug, but I’m not sure this is “missing” as there’s nothing from the coordinator handler, so maybe it’s not being called. I’m not really sure what is happening, but it doesn’t look like the binding is even running .
This looks ok I think - at least there’s nothing obviously wrong.
I’m not sure what to suggest at the moment, but there’s something fundamentally wrong somewhere I think.
@chris
Finally with help from @5iver I have managed to log zigbee into a seperate logfile at debug level.
Zigbee is still running fine since a few hours ago, so the logfile will not show the typical problem I´ve got.
I just scanned through the logfile untill now, and there seem to be a few errors anyway. Some not supported attributes, and some managment error… I have no idea if thats important or not.
If you want to have a look, this is the logfile. logfile
Meanwhile, I´m just waiting for the communication to stop, hopefully soone, (I´ll bet within a day).
Thanks - I’ll take a look.
I suspect that the communications issue may not show anything useful in the log, but let’s see. It depends where the problem lies - if it’s a coordinator configuration issue, then the log won’t help (probably) - although it won’t hurt. For this, we will need a sniffer log (I’m still waiting to receive the dongles, but I hope they should be here in the coming days).
If the problem is an exception in the binding, then the log will help - either way, I’m very happy to take a look, and thanks for spending the time to get this set up.
I know. I just thought that maybe this log could provide someting, cause I saw these errors. It may have nothing to do with the failing communication, though.
Look forward to start sniffing so we hopefully can get this zigbee up running for good…
Do you mind emailing me your XML file for Zigbee - it’s in the {userdata}/zigbee folder.
Thanks.
Yep - it’s interesting and useful. I don’t think there’s anything major in the log, but I think I see one thing that is wrong, so I can fix that at least.
Done…
Sound great. Look forward to whatever changes that may be
1 Like
Hi,
When I connect my Silicon lab’s WSTK board to openhabian, it shows this,
[zigbee.dongle.ember.ZigBeeDongleEzsp] - NCP requires unsupported version of EZSP (required = V7, supported = V4)
what is it and how to resolve it.
.
I am trying to install gateway on openhabian, using silicon lab’s zigbee wireless stater kit - EFR32MG12P332F1024Gl125
Please provide a debug log so we can see what is happening and also what binaries you have programmed.
From where, I can get Debug log
Please check the ZigBee binding documentation.
