Zigbee Channel?

If you are using text files, then the only way is going to be to restart the binding. Unfortunately openHAB blocks any configuration for devices that are configured through files.

I have a debug log file, and it looks like the channel is changed, but paperui does not pick it up.
I have to go out right now, will massage down the log (it is HUGE) and upload it somewhere later tonight if it is still of interest.

just to fully understand this.

via text config I can change the channel.
it will be used when I restart the binding.

or I can only set a channel once when no device is paired to the coordinator?

best

You can only set the channel when the network is first initialised. There is an “Reset Controller” option in the coordinator - you can generally only set the channel when this is set.

Thanks. I think I will try it as my current channel is 20 and I would rather go to 26 in the hope to be at the edge of wifi … and I am mostly ybluetooth free.

@chris
Do the “reset” do the same as a restart of the binding, or is it a more gentle approach?

There must be something that is out of sync somewhere as paperui say channel 11 and the logs say channel 25.

The most accessable check is in paperui, so I do not know when the cannel changed.
I better rerun some channel changes (and look for devices that did not follow)
Likewise test the autochannel thingie just to see what it put out.

Restarting the binding doesn’t really do anything other than start everything up - it assumes the network has been established already and it just continues.

Reset the network completely resets the coordinator and establishes a new network. All devices will need to join the new network.

You can only change the channel when the network is initialised - ie reset as described above.

Oh, I think I understand.
I will keep the settings in my .things file then.

Thank you for answering these questions.
I learned a lot :slight_smile:

1 Like

Paperui fooled me for many days…

@chris

since I installed the zigbee binding my openhab stalled fully 2 times in a few days
could it be related to the binding?

tons of this in the log when it stalls

2020-05-16 10:20:27.558 [WARN ] [zsmartsystems.zigbee.ZigBeeExecutors] - Uncaught exception in thread NotificationService-thread-1870
java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start0(Native Method) ~[?:1.8.0_191]
	at java.lang.Thread.start(Thread.java:717) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:957) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1025) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_191]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]
2020-05-16 10:20:27.678 [DEBUG] [converter.ZigBeeConverterSwitchOnoff] - 7CB03EAA00ACF5AF: ZigBee attribute reports ZclAttribute [cluster=On/Off, id=0, name=On Off, dataType=BOOLEAN, lastValue=false, lastReportTime=Sat May 16 10:20:27 CEST 2020, implemented=true]
2020-05-16 10:20:27.679 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 7CB03EAA00ACF5AF: Channel zigbee:device:c890ebfb:7cb03eaa00acf5af:7CB03EAA00ACF5AF_3_switch updated to OFF
2020-05-16 10:20:27.680 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA00ACF5AF: Updating ZigBee channel state zigbee:device:c890ebfb:7cb03eaa00acf5af:7CB03EAA00ACF5AF_3_switch to OFF
2020-05-16 10:20:27.682 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - Reset timeout for handler with thingUID=zigbee:device:c890ebfb:7cb03eaa00acf5af
2020-05-16 10:20:27.683 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - Scheduling timeout task for thingUID=zigbee:device:c890ebfb:7cb03eaa00acf5af in 1830 seconds
2020-05-16 10:20:27.684 [WARN ] [zsmartsystems.zigbee.ZigBeeExecutors] - Uncaught exception in thread NotificationService-thread-1867
java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start0(Native Method) ~[?:1.8.0_191]
	at java.lang.Thread.start(Thread.java:717) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:957) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1025) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_191]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]

2020-05-16 10:36:32.697 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA00ACF5AF: Polling...
2020-05-16 10:36:32.698 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA00ACF5AF: Polling zigbee:device:c890ebfb:7cb03eaa00acf5af:7CB03EAA00ACF5AF_3_activepower
2020-05-16 10:36:32.700 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: 
java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start0(Native Method) ~[?:1.8.0_191]
	at java.lang.Thread.start(Thread.java:717) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:957) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1378) ~[?:1.8.0_191]
	at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) ~[?:1.8.0_191]
	at com.zsmartsystems.zigbee.dongle.xbee.internal.XBeeFrameHandler.sendRequestAsync(XBeeFrameHandler.java:554) ~[?:?]
	at com.zsmartsystems.zigbee.dongle.xbee.ZigBeeDongleXBee.sendCommand(ZigBeeDongleXBee.java:347) ~[?:?]
	at com.zsmartsystems.zigbee.aps.ApsDataEntity.send(ApsDataEntity.java:168) ~[?:?]
	at com.zsmartsystems.zigbee.ZigBeeNetworkManager.sendCommand(ZigBeeNetworkManager.java:881) ~[?:?]
	at com.zsmartsystems.zigbee.transaction.ZigBeeTransactionManager.send(ZigBeeTransactionManager.java:444) ~[?:?]
	at com.zsmartsystems.zigbee.transaction.ZigBeeTransactionManager.sendNextTransaction(ZigBeeTransactionManager.java:670) ~[?:?]
	at com.zsmartsystems.zigbee.transaction.ZigBeeTransactionManager.queueTransaction(ZigBeeTransactionManager.java:372) ~[?:?]
	at com.zsmartsystems.zigbee.transaction.ZigBeeTransactionManager.sendTransaction(ZigBeeTransactionManager.java:356) ~[?:?]
	at com.zsmartsystems.zigbee.ZigBeeNetworkManager.sendTransaction(ZigBeeNetworkManager.java:1915) ~[?:?]
	at com.zsmartsystems.zigbee.ZigBeeNode.sendTransaction(ZigBeeNode.java:894) ~[?:?]
	at com.zsmartsystems.zigbee.ZigBeeEndpoint.sendTransaction(ZigBeeEndpoint.java:591) ~[?:?]
	at com.zsmartsystems.zigbee.zcl.ZclCluster.sendCommand(ZclCluster.java:292) ~[?:?]
	at com.zsmartsystems.zigbee.zcl.ZclCluster.readAttributes(ZclCluster.java:454) ~[?:?]
	at com.zsmartsystems.zigbee.zcl.ZclCluster.read(ZclCluster.java:1693) ~[?:?]
	at com.zsmartsystems.zigbee.zcl.ZclCluster.read(ZclCluster.java:1668) ~[?:?]
	at com.zsmartsystems.zigbee.zcl.ZclCluster.read(ZclCluster.java:1680) ~[?:?]
	at com.zsmartsystems.zigbee.zcl.ZclCluster.readSync(ZclCluster.java:1610) ~[?:?]
	at com.zsmartsystems.zigbee.zcl.clusters.ZclElectricalMeasurementCluster.getActivePower(ZclElectricalMeasurementCluster.java:3552) ~[?:?]
	at org.openhab.binding.zigbee.internal.converter.ZigBeeConverterMeasurementPower.handleRefresh(ZigBeeConverterMeasurementPower.java:118) ~[?:?]
	at org.openhab.binding.zigbee.handler.ZigBeeThingHandler$2.run(ZigBeeThingHandler.java:586) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_191]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[?:1.8.0_191]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_191]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_191]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]
2020-05-16 10:36:33.668 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.669 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.670 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.671 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.672 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.673 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.673 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.674 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.674 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.675 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.675 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.676 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.676 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.677 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.678 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:33.678 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:34.739 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:34.742 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:34.743 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.
2020-05-16 10:36:34.744 [WARN ] [me.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.eclipse.smarthome.core.internal.items.ItemUpdater@16fbe655' takes more than 5000ms.


2020-05-16 13:09:38.420 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:38.421 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:38.423 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:38.424 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:38.429 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:46.599 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: 
java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start0(Native Method) ~[?:1.8.0_191]
	at java.lang.Thread.start(Thread.java:717) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:957) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.ensurePrestart(ThreadPoolExecutor.java:1603) ~[?:1.8.0_191]
	at java.util.concurrent.ScheduledThreadPoolExecutor.reExecutePeriodic(ScheduledThreadPoolExecutor.java:350) ~[?:1.8.0_191]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:296) ~[?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_191]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]
2020-05-16 13:09:48.301 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.302 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.302 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.303 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.303 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.304 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.325 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.325 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.326 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.327 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.328 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.349 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.350 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.350 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.351 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.351 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.352 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.353 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.353 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.354 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.354 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.355 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.356 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.356 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun
2020-05-16 13:09:48.357 [WARN ] [ding.zigbee.handler.ZigBeeSerialPort] - Processing DATA_AVAILABLE event: Serial buffer overrun

edit:
it is joined by some zwave logging which I have not seen before:

2020-05-16 10:51:50.397 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling aborted due to exception
java.lang.IllegalStateException: Timer already cancelled.
	at java.util.Timer.sched(Timer.java:397) ~[?:1.8.0_191]
	at java.util.Timer.schedule(Timer.java:208) ~[?:1.8.0_191]
	at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager.startTransactionTimer(ZWaveTransactionManager.java:1005) ~[bundleFile:?]
	at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager.addTransactionToQueue(ZWaveTransactionManager.java:376) ~[bundleFile:?]
	at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager.queueTransactionForSend(ZWaveTransactionManager.java:332) ~[bundleFile:?]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.enqueue(ZWaveController.java:505) ~[bundleFile:?]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.sendData(ZWaveController.java:889) ~[bundleFile:?]
	at org.openhab.binding.zwave.handler.ZWaveControllerHandler.sendData(ZWaveControllerHandler.java:472) ~[bundleFile:?]
	at org.openhab.binding.zwave.handler.ZWaveThingHandler$1.run(ZWaveThingHandler.java:427) [bundleFile:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_191]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_191]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_191]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_191]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]

It looks like your system is running low on resources. In general, the binding tries to be a low resource user, but it does make use of a number of threads within the zigbee libraries to monitor transactions etc.

@chris what resources? :wink:
its quite a overspeced dedicated openhab server with 16gb ram. cpu Intel N3450 quad-core. OS Ubuntu

edit:
just checked it allocated 20% RAM now overall incl. whatever linux preallocates
and openhab is more or less idling on 0-2% CPU

Threads / memory. The error is about threads creation.

memory as above 20% now
threads if my linux knowledge is right

Total running: 1262
For openhab: 611
MAx possible: 125610

really unsure what happens. just can tell before I used zigbee the uptime was a couple months.
I will continure to monitor and post here if I come to a conclusion

:~$ ps -eo nlwp | tail -n +2 | awk '{ num_threads += $1 } END { print num_threads }'
1262
:~$ ps -o nlwp 1193
NLWP
 611
:~$ cat /proc/sys/kernel/threads-max
125610

If you keep using more resources though, then something will give. If you stop using some other bindings this will also help - it’s not the zigbee binding as such, but the total system. It’s like the old (english) saying - “the straw that broke the camels back” - each little bit of straw is fine, but sooner or later it’s too much :wink:

well but my threads are at 1% of the max and memory at 20%
So I am not sure if the straw is that big or the camel that small :D:D:D

I will check the metrics again when it stalls next.

Ok, I’m not sure then - sorry. It doesn’t seem to be a generic problem, and the issue seems to be thread related, unless I’m reading this wrong -:

this morning the threads for openhab went up.
in 12 hours uptime they went from ~600 to ~2200 (only reporting the threads for the openhab pid)

almost 400% increase. while my thread max cap is at 120k this should still be no issue. however if they increase so strong in the next days it fits to my observation that it stalls after only few days.

any possibility to check within openhab what is using that threads?

best

ok for my future me

shell:threads --list

this shows that almost all threads go to
Mi IO MessageSenderThread: TIMED_WAITING

I will try to get some insights from @marcel_verpaalen on this

from ~2200 threads this process is consuming ~1900

You don’t say what process is consuming the threads? Can you see the thread names? Possibly there’s an issue with the S2 driver as that hasn’t had extensive testing (although I know people are using it and haven’t reported this in the past).