mirror of
https://github.com/4IceG/luci-app-modemdata.git
synced 2026-04-26 11:16:06 +03:00
[GH-ISSUE #9] modempreview shows removed modem #4
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/luci-app-modemdata#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @giorez on GitHub (Sep 10, 2025).
Original GitHub issue: https://github.com/4IceG/luci-app-modemdata/issues/9
hello,
I have configured two modems at http://192.168.1.1/cgi-bin/luci/admin/modem/modemdata/modemdefine
Modem(s)
1 Quectel RM520N-GL serial /dev/ttyUSB2 4g: [Ethernet Adapter: "usb0"]
2 Quectel RM551E-GL serial /dev/ttyUSB2 4g: [Ethernet Adapter: "usb1"]
Than I phisycally removed the second one (RM551E-GL). But the page http://192.168.1.1/cgi-bin/luci/admin/modem/modemdata/modempreview still shows the "RM551E-GL" tab with data coming from "RM520N-GL" modem
@4IceG commented on GitHub (Sep 10, 2025):
Hi,
Clear settings to zero in the modem configuration tab.
@giorez commented on GitHub (Sep 10, 2025):
modem configuration tab doesn't show any CLEAR function. On my zbt z8102ax, I just have this theme (material).
@4IceG commented on GitHub (Sep 10, 2025):
There is no “magic button”, you simply need to adjust the configuration to your hardware.
Another thing is that package does not check modems, because why would it.. The entire configuration is performed by the user.
Quectel has several ports for reading data, and the ones you currently have set up may be assigned to modem 1 and 2. The system should set this up and iterate the ports when modems are detected. It's not a package bug, you haven't changed the configuration.
By the way, I found a bug, but without another modem I can't check it and fix it.
@giorez commented on GitHub (Sep 11, 2025):
@4IceG great, thanks!