LTE7480-M804 loses connection and stays disconnected until next reboot

nicosemp
nicosemp Posts: 10
First Anniversary Friend Collector First Comment
edited January 4 in Mobile Broadband
Hi,
as per the title, my LTE7480-M804 has a SIM card with many GBs left and great connection.
It works very well for a couple of days, then it loses connection for some reason. The only way to get the connection back is to reboot the device!

I tried setting the automatic reboot on Sundays, but it's no use because the signal drops by Tuesday, and since it's at a remote location I cannot communicate with it until the next Sunday when it reboots.
If I am at the location I can just reboot it by hand, but I'm not always there and internet needs to keep working.

I understand that the signal might drop once in a while, but it should reconnect automatically without waiting for a reboot.

I updated to the latest firmware found here: https://community.zyxel.com/en/discussion/comment/42923 but that didn't solve anything.

This is the last chance to save what is otherwise a good product. Either I find a solution here or I have to return it.
«1

All Replies

  • Lolo
    Lolo Posts: 1
    First Comment
    Hello Nicosemp,

    Do you have foud a solution as I have the same issue.

    Thanks
  • @Lolo not yet, I am waiting for an official reply hopefully. I'll wait another month to give them plenty of time to answer.
  • No way to solve this? The connection keeps dropping every 2-4 days.
  • SELBERG
    SELBERG Posts: 266  Master Member
    First Anniversary 10 Comments Friend Collector First Answer
    I think your provider is the problem.....
  • Hi @SELBERG
    I already tried different SIM cards from different providers that use a separate infrastructure (not providers who rent the same 4G antennas), and the problem persists.
    Also, when the connection drops I just restart the router and it reconnects, so it can't be on the provider: it should reconnect without needing a reboot.
  • @nicosemp Did you find a solution to this? I have exactly the same problem. I get even get into the GUI and it shows a good signal strength etc but the only way of getting it back is to reboot the connection.  
  • @nicosemp Did you find a solution to this? I have exactly the same problem. I get even get into the GUI and it shows a good signal strength etc but the only way of getting it back is to reboot the connection.  
  • @jdawg69 no solution yet.
    So many routers have a fail check, where you can reboot the device if X pings fail one after the other. It's a shame this one has no solution.
    I wish I had root access to the router to make a script and solve this myself.
    It looks like returning the product is the only way, will do that after the holidays.
  • @nicosemp It's amazing that it has SSH access but doesn't support a simple reboot command. I'm trying the firmware relased a few days ago on the hope that it will sort the problem.

    Log before reboot showing the drop and reconnect and it all looked good in the GUI with the globe etc.

    Dec 15 21:44:36 daemon.debug dnsmasq-dhcp: sendLeaseMessageToESMD send to esmd buf = {"ac":"add","expire":"129627","mac":"f4:92:bf:ab:bf:8c","ip":"192.168.1.96","host":"XYZ","vendor":"ubnt","moui":"*","serial":"*","pclass":"*","cid":"01:f4:92:bf:ab:bf:8c","ifname":"br0"}
    Dec 15 21:44:36 daemon.debug dnsmasq-dhcp: sendLeaseMessageToESMD esmd ret=1
    Dec 15 22:04:00 user.notice RILCMD: set_LTE_connection_status: Down 
    Dec 15 22:04:00 user.notice RILCMD: Attached to schema shared memory
    Dec 15 22:04:00 user.notice RILCMD: Attached to object name shared memory
    Dec 15 22:04:00 user.notice RILCMD: Attached to parameter name shared memory
    Dec 15 22:04:00 user.notice RILCMD: 
    Dec 15 22:04:00 kern.info ZTR69: [DB    ] cwmp_cmd_proc(): ipcCmd=1, data={  }
    Dec 15 22:04:00 kern.info ZTR69: [STATUS] cwmp_main_proc(): ***current state=1, cmd=1***
    Dec 15 22:04:00 kern.info ZTR69: [STATUS] cwmp_main_proc(): ***state change to 1***
    Dec 15 22:04:01 user.notice RILCMD: LTE7480 with EG12 module
    Dec 15 22:04:13 user.notice RILCMD: RILCMD_AUTO_APN flag enable.
    Dec 15 22:04:17 user.notice RILCMD: SIM card ready after initialization
    Dec 15 22:04:23 user.notice RILCMD: Change state from RS_INIT to RS_UPDATE.
    Dec 15 22:04:33 user.notice RILCMD: Device UP in quectel_eg12_update()
    Dec 15 22:04:33 user.notice RILCMD: set_LTE_connection_status: Up 
    Dec 15 22:04:33 kern.info udhcpc: udhcp client (v0.9.8) started
    Dec 15 22:04:33 kern.notice udhcpc: Attached to schema shared memory
    Dec 15 22:04:33 kern.notice udhcpc: Attached to object name shared memory
    Dec 15 22:04:33 kern.notice udhcpc: Attached to parameter name shared memory
    Dec 15 22:04:33 kern.notice udhcpc: 
    Dec 15 22:04:34 kern.debug udhcpc: Sending discover...
    Dec 15 22:04:34 kern.debug udhcpc: Sending select for 10.10.15.235...
    Dec 15 22:04:34 kern.info udhcpc: Lease of 10.10.15.235 obtained, lease time 7200
    Dec 15 22:04:34 kern.info udhcpc: dhcpMsgSend: msgType[-2147483432]
    Dec 15 22:04:37 kern.info ZTR69: [STATUS] cwmp_main_proc(): ***current state=1, cmd=1***
    Dec 15 22:04:37 kern.info ZTR69: [STATUS] cwmp_main_proc(): ***state change to 1***
    Dec 15 22:04:38 kern.info ZTR69: [DB    ] cwmp_cm_msg_proc(): cwmp receive ZCFG_MSG_NTP_SYNC_SUCCESS
    Dec 15 22:04:38 kern.info ZTR69: [DB    ] cwmp_cm_msg_proc(): cwmp receive ZCFG_MSG_NTP_SYNC_SUCCESS

  • MargoH
    MargoH Posts: 1
    First Comment
    I have same problem as you described with Zyxel LTE7480-M804 4G outdoor modem.
    It disconnects from network and only way to restore the connection is to reboot the device. I also tried different ISP-s and problem remains. I had similar problem after six months when that device was installed. Then after firmware update and inserting special configuration from backup/restore section which i got from my ISP, it worked very nicely 1,5 year. The problem is back again starting november 2022. Updating the firmware to version 5.0 didnt help. I havent tried the 6.0 version yet. Did the latest V1.00(ABRA.6)C0 firmware resolved the issue for you?

Consumer Product Help Center