You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! After upgrade Mikrotik CAP AC to 7.17 integration stopped to work. There is no system/health section at all on CAP AC and it prevents integration from working. Debug logs: 2025-01-21 12:03:03.176 ERROR (SyncWorker_10) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix 2025-01-21 12:04:24.449 ERROR (SyncWorker_0) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix 2025-01-21 12:04:24.593 ERROR (SyncWorker_9) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix 2025-01-21 12:05:46.027 ERROR (SyncWorker_6) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix 2025-01-21 12:05:46.066 ERROR (SyncWorker_10) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
How to reproduce the issue
For Mikrotiks CAP AC integration showing "failed to setup", logs provided above.
Expected behavior
Integration should work even with system/health missing on a router, because not all Mikrotiks have this functionality.
Screenshots
Software versions
All fields in this sections are required.
Home Assistant version: core 2025.1.3, supervisor 2024.12.3, operating system 14.1
Mikrotik Router integration version: 0.0.0
Mikrotik Hardware: CAP AC
RouterOS version: 7.17
Traceback/Error logs
2025-01-21 11:27:45.914 ERROR (SyncWorker_3) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:29:06.267 ERROR (SyncWorker_6) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:29:07.343 ERROR (SyncWorker_3) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:30:27.927 ERROR (SyncWorker_1) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:30:28.728 ERROR (SyncWorker_5) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:31:49.303 ERROR (SyncWorker_4) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:31:50.113 ERROR (SyncWorker_5) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:33:10.553 ERROR (SyncWorker_5) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:33:11.640 ERROR (SyncWorker_5) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:34:31.788 ERROR (SyncWorker_0) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:34:33.014 ERROR (SyncWorker_10) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:35:53.005 ERROR (SyncWorker_6) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:35:54.425 ERROR (SyncWorker_5) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:37:14.298 ERROR (SyncWorker_8) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:37:15.749 ERROR (SyncWorker_6) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:38:35.699 ERROR (SyncWorker_0) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:38:37.312 ERROR (SyncWorker_4) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:39:57.286 ERROR (SyncWorker_3) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
2025-01-21 11:39:58.751 ERROR (SyncWorker_8) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix
The text was updated successfully, but these errors were encountered:
Same problem:
2025-01-23 02:06:06.724 ERROR (SyncWorker_3) [custom_components.mikrotik_router.mikrotikapi] Mikrotik X.X.X.X error while building list for path /caps-man/registration-table : no such command or directory (caps-man), no such command prefix
Describe the issue
Hello! After upgrade Mikrotik CAP AC to 7.17 integration stopped to work. There is no system/health section at all on CAP AC and it prevents integration from working. Debug logs:
2025-01-21 12:03:03.176 ERROR (SyncWorker_10) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix 2025-01-21 12:04:24.449 ERROR (SyncWorker_0) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix 2025-01-21 12:04:24.593 ERROR (SyncWorker_9) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix 2025-01-21 12:05:46.027 ERROR (SyncWorker_6) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.2 error while building list for path /system/health : no such command or directory (health), no such command prefix 2025-01-21 12:05:46.066 ERROR (SyncWorker_10) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.1.254 error while building list for path /system/health : no such command or directory (health), no such command prefix
How to reproduce the issue
For Mikrotiks CAP AC integration showing "failed to setup", logs provided above.
Expected behavior
Integration should work even with system/health missing on a router, because not all Mikrotiks have this functionality.
Screenshots
Software versions
All fields in this sections are required.
Traceback/Error logs
The text was updated successfully, but these errors were encountered: