[Bug] Integration doesn't work with RouterOS 7.13 Beta #328
Comments
|
Did you tried to install "wireless" package as a workaround? |
wireless package will confilict with new wifi-qcom package. |
|
So in wifi-qcom CAPsMAN renamed to CAPsMAX? |
wifi-qcom is just a driver for wifi hardware and does not add any interfaces. So, as I understand "wireless" package was renamed to "wifi", so now CAPsMAN can be found on 
|
|
For ROS < 7.13: Is it correct? |
|
Yes. But also it was totally rewritten. So there is no more Edit: also we do not need to install additional |
|
I'm glad that I decided to stay on 7.12.1 😅 |
|
I have this exact issue also. 2023-11-25 19:17:10.751 WARNING (SyncWorker_3) [homeassistant.components.mikrotik.hub] Mikrotik 192.168.88.1 failed to retrieve data. cmd=[/caps-man/interface/print] Error: no such command or directory (caps-man), no such command prefix 2023-11-25 19:25:42.635 ERROR (SyncWorker_7) [custom_components.mikrotik_router.mikrotikapi] Mikrotik 192.168.88.1 error while building list for path /caps-man/registration-table : no such command or directory (caps-man), no such command prefix |
|
yea, I never touch betas. specially with mikrotik, they often change major things mid betas. |
|
Hi Tomaae, |
|
I added a PR to fix this. (Fix for ros 7.13 wireless #332) |
|
7.13 stable was released today. |
|
The wireless package is now optional. Integration setup should be possible without wireless/capsman, but that is not so. Setup fails to initialize the device...: |
|
I'm waiting for update |
|
I have the same issue. Upgraded to ROS 7.13 and the integration does not work. |
|
Hi, After ugraded to 7.13 integration not connect to router. My router C53UiG+5HPaxD2HPaxD (Mikrotik AX3), We wait for update integration. Thenks for Your great job. |
|
Why does it take so long to fix this issue? I can't use this integration for about two months now. |
|
Same here. Maybe it's a difficult problem to solve? It looks pretty embedded in Mikrotik's roadmap as 7.14 beta is using the same structure now. |
|
It Works even at 7.14 ! With this file, added manualy from (you need to replace file) and this changes (you need to add 2 lines) Работает даже в 7.14 ! Скачать и заменить файл Добавить две строчки в другой файл |
Which coordinator.py do I need to download/replace 1st or 2nd one? TIA |
|
Actually you have 2 more options to install version from #332 Option 1 - Like HACS manual installJust follow HACS manual install instruction, except steps 2 and 3 download zip file from this specific branch on repo short link via "Code" -> "Download zip" Option 2 - Install via Shell~/config$ cd custom_components/
~/config/custom_components$ rm -Rf mikrotik_router
~/config/custom_components$ curl https://codeload.github.com/slackr31337/homeassistant-mikrotik_router/zip/refs/heads/ros-7.13 -o master.zip
~/config/custom_components$ unzip master.zip
~/config/custom_components$ mv homeassistant-mikrotik_router-ros-7.13/custom_components/mikrotik_router/ .
~/config/custom_components$ rm -Rf homeassistant-mikrotik_router-ros-7.13/
~/config/custom_components$ rm -Rf master.zip
~/config/custom_components$ ls -l
total 4
drwxrwxr-x 3 user user 4096 Dec 27 14:28 mikrotik_router |
|
After using @M0DDer 's fix, integration is working again, however number of wired clients is not working, it always reports 0. |
|
Yes, I have the same issue - 3 wired clients but the integration says 0 |
|
Is there any working solution for this issue? I have two MikroTik machines, one "RB5009UG+S+" an one "hAP ax lite LTE6". But the integration of RB5009 seems to works. But the integration of the hAP doesn't. Both routers are running on RouterOS v7.13.5 |
|
I haven't added any wireless packages (the router doesn't have wireless anyways) |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
Not stale! |
|
A major problem is with the new HACS 2.x you cannot select master any longer. So impossible to get the integration to work on new HA installations. It is now 326 days since 1st reported, wish there was something we could do to help advance the resolution. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
That issue won't be closeable until a new version is released. |
|
+1 |
|
+1 running ROS 7.16.1 stable. Tried the fix suggested by Onepamopa but that did not get me up and running. I am on an |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
This issue is Not stale |
|
I am getting the error error while building list for path /caps-man/registration-table : no such command or directory |
|
I believe this project is now dead. It's broken since over one year and last commit was almost 6 months ago. |
|
Probably he just needs to create a new release. I'll try to test the latest version manually in HA when I get some free time. |
|
Maybe we can try to contact him via his website and ask him if he can assist us all. Will give it a go. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
Still not solved |
|
still not solved |
|
@tomaae do you need a Co-Maintainer? I'd be glad to contribute! Cheers! |
Are you ready to tackle the workload? With bugs like #386 that are also still outstanding, would you realistically have any idea how to troubleshoot & resolve these, and have the time to do so? The developer (@tomaae) is still active (they responded to my issue #386 today in fact) - so the project isn't totally abandoned. There's just a lack of community support to fix bugs. Whoever takes ownership of this project must be capable of doing some catch-up otherwise there's no point transferring the rights, surely? It's an open-source project after all, so nothing is stopping anyone from fixing any of the existing bugs. With that said, resolution of this specific issue (#328) is long overdue now, with a community patch already provided (the patch provided by @Onepamopa works). Would be nice if that could be committed, at least. |
I would say "alive", not "active". The last significant commit is almost one year ago, then only a couple really minor ones. |
|
Let's be patient, I am sure @tomaae will be back when they have time. |
|
+1 |
and others
Describe the issue
Integration doesn't work
How to reproduce the issue
Steps to reproduce the behavior:
Expected behavior
It should work like on Router OS <7.13
Software versions
Diagnostics data
No
Traceback/Error logs
Logger: custom_components.mikrotik_router.mikrotikapi
Source: custom_components/mikrotik_router/mikrotikapi.py:95
Integration: Mikrotik Router (documentation, issues)
First occurred: 14 листопада 2023 р. о 21:42:42 (660 occurrences)
Last logged: 12:16:05
Mikrotik 192.168.86.2 error while building list for path /caps-man/registration-table : no such command or directory (caps-man), no such command prefix
The text was updated successfully, but these errors were encountered: