Home Network Community > Deco > Connection Error with Magic Home Pro
< Deco

Connection Error with Magic Home Pro

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Connection Error with Magic Home Pro

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Connection Error with Magic Home Pro
Connection Error with Magic Home Pro
2020-09-29 08:38:02 - last edited 2020-09-29 08:48:19
Model: Deco M4  
Hardware Version: V2
Firmware Version: 1.4.2 Build 20200727 Rel. 37987

I boutgth a led strip that works with Magic Home Pro

 

I've paired the device with my network but always gives connection failed. I've found this in te log. The device IP is 192.168.68.119

 

Tue Sep 29 10:36:24 2020 daemon.err udhcpd[5808]: Sending OFFER of 192.168.68.119

Tue Sep 29 10:37:25 2020 daemon.err udhcpd[5808]: clear ip c0a84477

Tue Sep 29 10:37:25 2020 daemon.err udhcpd[5808]: Sending OFFER of 192.168.68.119

Tue Sep 29 10:38:26 2020 daemon.err udhcpd[5808]: clear ip c0a84477

Tue Sep 29 10:38:26 2020 daemon.err udhcpd[5808]: Sending OFFER of 192.168.68.119

Tue Sep 29 10:39:28 2020 daemon.err udhcpd[5808]: clear ip c0a84477

Tue Sep 29 10:39:28 2020 daemon.err udhcpd[5808]: Sending OFFER of 192.168.68.119

Tue Sep 29 10:40:07 2020 daemon.err udhcpd[5808]: clear ip c0a84477

Tue Sep 29 10:40:07 2020 daemon.err udhcpd[5808]: Sending OFFER of 192.168.68.119

Tue Sep 29 10:40:11 2020 daemon.err udhcpd[5808]: clear ip c0a84477

Tue Sep 29 10:40:11 2020 daemon.err udhcpd[5808]: Sending OFFER of 192.168.68.119

 

I've tried a lot of thinks. My network it's in 2.4GHz. Fast Roaming & Beamforming disable, etc.

 

Can you help me, please?

 

Thanks in advance

  0      
 
  0      
 
#1
Options
10 Reply
Re:Connection Error with Magic Home Pro
2020-10-13 01:36:24 - last edited 2020-10-13 01:38:15

@toniki 

 

Hello, thanks for the detailed info.

 

Firstly, please update the Deco M4 firmware to the latest 1.4.3 Build 20200918 Rel. 74289, then reconfigure the Magic Home Pro strip from scratch.

 

As per the log you provided, the Magic Home Pro is constantly sending requests every minute to the gateway asking for an IP address but failed to respond. Can you kindly take a short video showing the connection failed error on your app when controlling the strip?

 

Just to confirm, are you sure this 192.168.68.119 is the IP address assigned to the Magic Home Pro strip? Can I have a screenshot of it on its app?

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! Deco BE85_1.1.1 Supports WireGuard VPN,Channel Selection and Matter Deco BE65_V2_1.1.0 Supports WireGuard VPN, Channel Selection and More ▶Deco APP 3.8.102/3.8.112-Ready for A New Deco Onboarding Experience! Try to leave a Message if urgent help is required.
  0  
  0  
#2
Options
Re:Connection Error with Magic Home Pro
2020-10-15 14:54:05

@TP-Link_Deco 

 

  
I have the same problem, and with the most updated Firmware.

I already have an open case at TP-Link Internacional and TP-Link Local, both are not giving the correct assistance to the client. I do not recommend nor buy TP-Link ever again.

Unfortunately, instead of TP-Link acquiring a Magic Home WiFi Controller and taking it to its laboratory in order to carry out tests and identify the problem, it is asking several nonsensical questions.

I can't choose the Network and Sub-netmask that I want to use on my WiFi Network at the time of Setup? I'm starting to suspect this and IPv6 (but I have already disabled it and it didn't change the error scenario).

 

  0  
  0  
#3
Options
Re:Connection Error with Magic Home Pro
2020-10-16 01:46:29

@xXxRichxXx34 

 

Hello, thanks for reporting again. It is suggested to keep in touch with the engineers since you have already get in touch with them and have a ticket opened. This issue may need further analysis, hope you could understand and cooperate.

 

Have a nice day~

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! Deco BE85_1.1.1 Supports WireGuard VPN,Channel Selection and Matter Deco BE65_V2_1.1.0 Supports WireGuard VPN, Channel Selection and More ▶Deco APP 3.8.102/3.8.112-Ready for A New Deco Onboarding Experience! Try to leave a Message if urgent help is required.
  0  
  0  
#4
Options
Re:Connection Error with Magic Home Pro
2020-10-16 11:16:14

@TP-Link_Deco, I've update and the problem is the same.

 

The IP is the same in the log than the APP. I've re paired again and the issue persist.

 

In the APP que error persist. OFF LINE.

  0  
  0  
#5
Options
Re:Connection Error with Magic Home Pro
2020-10-17 05:04:13

@TP-Link_Deco 

 

  
I checked the Deco M4 Log and found these suspicious lines:

 

IP filter:

 

Fri Oct 16 20:44:52 2020 daemon.err udhcpd[4108]: Sending OFFER of 192.168.68.100
Fri Oct 16 20:44:52 2020 daemon.err udhcpd[4108]: Sending ACK to 192.168.68.100
Fri Oct 16 20:44:54 2020 authpriv.warn dropbear[16904]: Login attempt for nonexistent user from 192.168.68.100:47506
Fri Oct 16 20:44:54 2020 authpriv.warn dropbear[16904]: Login attempt for nonexistent user from 192.168.68.100:47506
Fri Oct 16 20:44:54 2020 authpriv.notice dropbear[16904]: Password auth succeeded from 192.168.68.100:47506
Fri Oct 16 20:45:22 2020 daemon.err udhcpd[4108]: Sending ACK to 192.168.68.100
Fri Oct 16 20:45:52 2020 daemon.err udhcpd[4108]: Sending ACK to 192.168.68.100
Fri Oct 16 20:46:22 2020 daemon.err udhcpd[4108]: Sending ACK to 192.168.68.100
Fri Oct 16 20:46:52 2020 daemon.err udhcpd[26574]: Sending ACK to 192.168.68.100
Fri Oct 16 20:53:30 2020 daemon.err udhcpd[32166]: Sending OFFER of 192.168.68.100
Fri Oct 16 20:53:30 2020 daemon.err udhcpd[32166]: Sending ACK to 192.168.68.100

 

MAC Address filter:

 

Fri Oct 16 20:53:29 2020 daemon.err client_mgmt: wireless client associate or disassociate.
Fri Oct 16 20:53:29 2020 daemon.err client_mgmt: client_mac:10-52-1C-CD-E7-BF, client_ifname:ath0, client_action:associate
Fri Oct 16 20:53:29 2020 daemon.err client_mgmt: client(10-52-1C-CD-E7-BF) assocaite by if(ath0).
Fri Oct 16 21:10:20 2020 daemon.err client_mgmt: client(10-52-1C-CD-E7-BF) not found in arp table disconnect_counter=0

  
It seems that the problem is very clear, but TP-Link is having trouble solving it.
  0  
  0  
#6
Options
Re:Connection Error with Magic Home Pro
2020-10-19 01:12:13

@xXxRichxXx34 

 

Thank you very much for the log attached, we will ask the engineers to confirm again. Please check your email box and they will contact you via email directly.

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! Deco BE85_1.1.1 Supports WireGuard VPN,Channel Selection and Matter Deco BE65_V2_1.1.0 Supports WireGuard VPN, Channel Selection and More ▶Deco APP 3.8.102/3.8.112-Ready for A New Deco Onboarding Experience! Try to leave a Message if urgent help is required.
  0  
  0  
#7
Options
Re:Connection Error with Magic Home Pro
2020-10-19 01:25:57

@toniki 

 

Hello, thanks for the update. We would like to follow it up via email as well, please check your email box and respond, thanks.

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! Deco BE85_1.1.1 Supports WireGuard VPN,Channel Selection and Matter Deco BE65_V2_1.1.0 Supports WireGuard VPN, Channel Selection and More ▶Deco APP 3.8.102/3.8.112-Ready for A New Deco Onboarding Experience! Try to leave a Message if urgent help is required.
  0  
  0  
#8
Options
Re:Connection Error with Magic Home Pro
2020-10-22 19:44:35
Hi, I recently purchased a 3 x Deco M4 setup and I'm experiencing the same issue with connections from MagicHome Pro devices (specifically the Arilux AL-LC01 controller). They will connect initially during the pairing process and successfully work for 1-2 minutes, then disconnect and never successfully connect again unless reset and repaired. As a temporary workaround I noticed that if I went into that device in the Deco app and disabled the device from using mesh networking it would then remain connected. 2 hours afterwards and I'm still seeing the MagicHome device connected!
  0  
  0  
#9
Options
Re:Connection Error with Magic Home Pro
2020-10-22 21:15:13

@TP-Link_Deco 

 

The 2 MagicHome devices (with IPs 192.168.0.122, 192.168.0.123) eventually disconnected at around 22:00 this evening. Now they won't reconnect in the MagicHome app and show disconnected in Deco app also.

 

Below are the logs.

 

Thu Oct 22 21:36:55 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:37:12 2020 daemon.err udhcpd[18743]: Sending ACK to 192.168.0.123
Thu Oct 22 21:37:12 2020 daemon.err udhcpd[18743]: clear ip c0a8007b
Thu Oct 22 21:37:35 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:37:35 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:37:48 2020 daemon.err udhcpd[18743]: Sending ACK to 192.168.0.121
Thu Oct 22 21:37:48 2020 daemon.err udhcpd[18743]: clear ip c0a80079
Thu Oct 22 21:37:53 2020 daemon.err udhcpd[18743]: Sending ACK to 192.168.0.105
Thu Oct 22 21:37:53 2020 daemon.err udhcpd[18743]: clear ip c0a80069
Thu Oct 22 21:39:00 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:39:40 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:39:40 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:41:06 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:41:45 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:41:45 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:43:11 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:43:46 2020 daemon.err udhcpd[18743]: Sending ACK to 192.168.0.109
Thu Oct 22 21:43:46 2020 daemon.err udhcpd[18743]: clear ip c0a8006d
Thu Oct 22 21:43:50 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:43:50 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:45:17 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:45:55 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:45:55 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:47:22 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:48:00 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:48:00 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:49:27 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:49:41 2020 daemon.warn radvd[2203]: RDNSS address fe80::12fe:edff:fec1:9fc2 received on br-lan from fe80::12fe:edff:fec1:9fc2 is not advertised by us
Thu Oct 22 21:49:41 2020 daemon.warn radvd[2203]: DNSSL suffix lan received on br-lan from fe80::12fe:edff:fec1:9fc2 is not advertised by us
Thu Oct 22 21:50:05 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:50:05 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:50:45 2020 daemon.err udhcpd[18743]: Sending ACK to 192.168.0.111
Thu Oct 22 21:50:45 2020 daemon.err udhcpd[18743]: clear ip c0a8006f
Thu Oct 22 21:50:46 2020 daemon.err udhcpd[18743]: Sending ACK to 192.168.0.111
Thu Oct 22 21:50:46 2020 daemon.err udhcpd[18743]: clear ip c0a8006f
Thu Oct 22 21:51:33 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:52:10 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:52:10 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:53:38 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:54:15 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:54:15 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:55:44 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:56:20 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:56:20 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:56:37 2020 daemon.err udhcpd[18743]: Sending ACK to 192.168.0.106
Thu Oct 22 21:56:37 2020 daemon.err udhcpd[18743]: clear ip c0a8006a
Thu Oct 22 21:57:49 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 21:58:25 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:58:25 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:58:37 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:58:37 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:58:38 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:58:38 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 21:59:55 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 22:00:30 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:00:30 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:02:00 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 22:02:35 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:02:35 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:04:06 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 22:04:40 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:04:40 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:06:11 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 22:06:45 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:06:45 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:07:55 2020 daemon.err uhttpd[7503]: iptables: No chain/target/match by that name.
Thu Oct 22 22:07:55 2020 daemon.err uhttpd[7503]: iptables v1.4.21: Couldn't load target `domain_login_rule':No such file or directory
Thu Oct 22 22:07:55 2020 daemon.err uhttpd[7503]: 
Thu Oct 22 22:07:55 2020 daemon.err uhttpd[7503]: Try `iptables -h' or 'iptables --help' for more information.
Thu Oct 22 22:07:55 2020 daemon.err uhttpd[7503]: iptables: No chain/target/match by that name.
Thu Oct 22 22:07:55 2020 daemon.err uhttpd[7503]: iptables: No chain/target/match by that name.
Thu Oct 22 22:07:55 2020 user.emerg syslog: tp215,22[5458]:
Thu Oct 22 22:07:57 2020 daemon.err uhttpd[7503]: ath22     no frequency information.
Thu Oct 22 22:07:57 2020 daemon.err uhttpd[7503]: 
Thu Oct 22 22:08:05 2020 daemon.err uhttpd[7503]: ath22     no frequency information.
Thu Oct 22 22:08:05 2020 daemon.err uhttpd[7503]: 
Thu Oct 22 22:08:05 2020 daemon.err uhttpd[7503]: sh: write error: Broken pipe
Thu Oct 22 22:08:12 2020 daemon.err uhttpd[7503]: ath22     no frequency information.
Thu Oct 22 22:08:12 2020 daemon.err uhttpd[7503]: 
Thu Oct 22 22:08:16 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Thu Oct 22 22:08:41 2020 daemon.err udhcpd[18743]: Found static lease: c0a80075
Thu Oct 22 22:08:41 2020 daemon.err udhcpd[18743]: Sending ACK to 192.168.0.117
Thu Oct 22 22:08:41 2020 daemon.err udhcpd[18743]: clear ip c0a80075
Thu Oct 22 22:08:50 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:08:50 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@808]: unknown igmp type 0x11
Thu Oct 22 22:10:22 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF

  0  
  0  
#10
Options
Re:Connection Error with Magic Home Pro
2020-10-23 12:09:58

@WreckBar 

 

Hi, thank you again for all the detailed info. Our engineers are working on this case, and we will try our best to find a solution ASAP.

 

While we are investigating this, can you please try to enable the guest network on the Deco M4 and leave it open without security, then try to connect these Magic Home devices to the guest network and see how it goes, thanks a lot.

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! Deco BE85_1.1.1 Supports WireGuard VPN,Channel Selection and Matter Deco BE65_V2_1.1.0 Supports WireGuard VPN, Channel Selection and More ▶Deco APP 3.8.102/3.8.112-Ready for A New Deco Onboarding Experience! Try to leave a Message if urgent help is required.
  0  
  0  
#12
Options

Information

Helpful: 0

Views: 2718

Replies: 10

Related Articles
BE230 and Honor Magic 6 Pro - dropping from wifi7 to wifi6 when connect
1331 0
 Deco M4 connection error
1824 0
WAN connection error!
5325 0
Wan connection error
912 0
Wireless connection error
451 0
 Connection error
472 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.