Hello everyone,
I wanted to start a continuation of the problem here:
Unfortunately, the error still seems to be present.
I have an RB5009 router and a LoRaWAN-GW.
RB5009 runs on Firmware 7.18 and the LoRaWAN Gateway on 7.19.
Both have the problem that a core of the Raspberry Pi 4 always runs at 100%.
The debug log also spits out such great things with some queries:
2025-06-09 13:54:09.440 [DEBUG] [krotik.internal.model.RouterosDevice] - Attempting login to 192.168.178.1 ...
2025-06-09 13:54:09.465 [DEBUG] [krotik.internal.model.RouterosDevice] - Logged in to RouterOS at 192.168.178.1 !
2025-06-09 13:54:09.472 [DEBUG] [krotik.internal.model.RouterosDevice] - RouterOS Version = 7.18.2
2025-06-09 13:54:11.392 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Cancelling refresh job
2025-06-09 13:54:11.393 [DEBUG] [krotik.internal.model.RouterosDevice] - Logging out of 192.168.178.1
2025-06-09 13:54:11.394 [DEBUG] [krotik.internal.model.RouterosDevice] - Closing connection to 192.168.178.1
2025-06-09 13:54:11.396 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Initializing MikrotikRouterosBridgeHandler with config = RouterosThingConfig{host=192.168.178.1, port=8728, login=openhab, password=*****, refresh=10s}
2025-06-09 13:54:11.398 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Scheduling refresh job every 10s
2025-06-09 13:54:11.399 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Starting routeros model
2025-06-09 13:54:11.401 [DEBUG] [krotik.internal.model.RouterosDevice] - Attempting login to 192.168.178.1 ...
2025-06-09 13:54:11.427 [DEBUG] [krotik.internal.model.RouterosDevice] - Logged in to RouterOS at 192.168.178.1 !
2025-06-09 13:54:11.433 [DEBUG] [krotik.internal.model.RouterosDevice] - RouterOS Version = 7.18.2
2025-06-09 13:54:21.435 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Refreshing RouterOS caches for mikrotik:routeros:MikrotikRB5009Router
2025-06-09 13:54:21.486 [DEBUG] [krotik.internal.model.RouterosDevice] - Command used for updating the interfaces is:/interface/ethernet/print
2025-06-09 13:54:21.544 [DEBUG] [krotik.internal.model.RouterosDevice] - Found the following SSID's:{}
2025-06-09 13:55:21.546 [DEBUG] [krotik.internal.model.RouterosDevice] - MikrotikApiException: Device may have the CAPsMAN feature for wireless management disabled.
2025-06-09 13:56:21.549 [DEBUG] [krotik.internal.model.RouterosDevice] - MikrotikApiException: Device does not appear to have any built in CAPsMAN wireless devices.
2025-06-09 13:57:21.553 [DEBUG] [krotik.internal.model.RouterosDevice] - MikrotikApiException: Device does not appear to have any built in wifi.
2025-06-09 13:57:31.584 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Refreshing RouterOS caches for mikrotik:routeros:MikrotikRB5009Router
2025-06-09 13:58:31.588 [ERROR] [andler.MikrotikRouterosBridgeHandler] - RouterOS cache refresh failed in mikrotik:routeros:MikrotikRB5009Router due to Mikrotik API error
me.legrange.mikrotik.MikrotikApiException: Command timed out after 60000 ms
at me.legrange.mikrotik.impl.ApiConnectionImpl$SyncListener.getResults(ApiConnectionImpl.java:482) ~[?:?]
at me.legrange.mikrotik.impl.ApiConnectionImpl$SyncListener.access$100(ApiConnectionImpl.java:436) ~[?:?]
at me.legrange.mikrotik.impl.ApiConnectionImpl.execute(ApiConnectionImpl.java:117) ~[?:?]
at me.legrange.mikrotik.impl.ApiConnectionImpl.execute(ApiConnectionImpl.java:75) ~[?:?]
at org.openhab.binding.mikrotik.internal.model.RouterosDevice.updateResources(RouterosDevice.java:347) ~[?:?]
at org.openhab.binding.mikrotik.internal.model.RouterosDevice.refresh(RouterosDevice.java:167) ~[?:?]
at org.openhab.binding.mikrotik.internal.handler.MikrotikRouterosBridgeHandler.performRefresh(MikrotikRouterosBridgeHandler.java:202) ~[?:?]
at org.openhab.binding.mikrotik.internal.handler.MikrotikRouterosBridgeHandler.scheduledRun(MikrotikRouterosBridgeHandler.java:190) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1583) [?:?]
Caused by: me.legrange.mikrotik.ApiConnectionException: Command timed out after 60000 ms
at me.legrange.mikrotik.impl.ApiConnectionImpl$SyncListener.getResults(ApiConnectionImpl.java:474) ~[?:?]
... 13 more
2025-06-09 13:58:31.599 [DEBUG] [krotik.internal.model.RouterosDevice] - Logging out of 192.168.178.1
2025-06-09 13:58:31.602 [DEBUG] [krotik.internal.model.RouterosDevice] - Closing connection to 192.168.178.1
2025-06-09 13:58:41.606 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Starting routeros model
2025-06-09 13:58:41.608 [DEBUG] [krotik.internal.model.RouterosDevice] - Attempting login to 192.168.178.1 ...
2025-06-09 13:58:41.626 [DEBUG] [krotik.internal.model.RouterosDevice] - Logged in to RouterOS at 192.168.178.1 !
2025-06-09 13:58:41.632 [DEBUG] [krotik.internal.model.RouterosDevice] - RouterOS Version = 7.18.2
2025-06-09 13:58:51.633 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Refreshing RouterOS caches for mikrotik:routeros:MikrotikRB5009Router
2025-06-09 13:58:51.689 [DEBUG] [krotik.internal.model.RouterosDevice] - Command used for updating the interfaces is:/interface/ethernet/print
2025-06-09 13:58:51.742 [DEBUG] [krotik.internal.model.RouterosDevice] - Found the following SSID's:{}
2025-06-09 13:59:51.744 [DEBUG] [krotik.internal.model.RouterosDevice] - MikrotikApiException: Device may have the CAPsMAN feature for wireless management disabled.
2025-06-09 14:00:51.760 [DEBUG] [krotik.internal.model.RouterosDevice] - MikrotikApiException: Device does not appear to have any built in CAPsMAN wireless devices.
2025-06-09 14:01:51.763 [DEBUG] [krotik.internal.model.RouterosDevice] - MikrotikApiException: Device does not appear to have any built in wifi.
2025-06-09 14:02:01.773 [DEBUG] [andler.MikrotikRouterosBridgeHandler] - Refreshing RouterOS caches for mikrotik:routeros:MikrotikRB5009Router
Unfortunately, I can’t use the binding in this state.
I have the feeling that the Pi sometimes hangs and I have to restart it manually.
