Home Network Community > All Threads > DECO network forgetting constantly customized name
< All Threads

DECO network forgetting constantly customized name

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

DECO network forgetting constantly customized name

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
DECO network forgetting constantly customized name
DECO network forgetting constantly customized name
2023-11-15 18:34:33
Model: Deco X50-Outdoor   Deco M5  
Hardware Version: V2
Firmware Version: 1.2.4

I have a DECO network of 2 x X50-outdoor (1 is main) and 6 x M5.

The M5 constantly forget their customized name and rermturn to M5. Almoat daily I have to rechange the name of 1 or 2 DECOs. Why so many issuea with them?

Could be a solution to keep them more stable?

  1      
 
  1      
 
#1
Options
4 Reply
Re:DECO network forgetting constantly customized name
2023-11-16 03:30:42

  @CCDan 

Hi, Thank you very much for your feedback. I am really sorry for the inconvenience.

Could you please refer to this link to help me submit the Deco APP log:

How to submit Deco APP log

Wait for your reply and best regards.

 

Check What's Currently Going on With Deco Deco Early Access Firmware Open for Test! 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:DECO network forgetting constantly customized name
2023-11-16 07:05:55

  @CCDan In the picture, all Decos have their customized names, right?

  0  
  0  
#3
Options
Re:DECO network forgetting constantly customized name
2023-11-16 09:45:57
Yes, and sometimes they loose them and return to M5 default name.
  1  
  1  
#4
Options
Re: DECO network log flooded
2024-01-05 11:40:08 - last edited 2024-01-05 12:10:40

  @CCDan 
I am struggeling with my DECO since many months now. Main DECO is X50 outdoor. DECO-Mesh-Curte is same X50 Outdoor (both 1.2.5) while the others are M5 (all 1.7.3). They are in AP mode managed by Omada ER7206 (2.1.0). Except X50 Deco-Mesh-Curte, all are conected with the router by cable through TPlink unamanaged switch.

The log of each DECO is full at maximum, each minute happening a lot of events (similar on each sattelite, 192.168.1.246 is the IP of the Main DECO):

 

Fri Jan 5 04:09:44 2024 authpriv.notice dropbear[2629]: Pubkey auth succeeded for 'root' with key sha1!! c3:54:65:6c:1a:1e:4e:29:f9:ce:a7:4d:b0:0a:8b:01:07:a9:7c:9f from 192.168.1.246:51698

Fri Jan 5 04:10:01 2024 authpriv.notice dropbear[2655]: Pubkey auth succeeded for 'root' with key sha1!! c3:54:65:6c:1a:1e:4e:29:f9:ce:a7:4d:b0:0a:8b:01:07:a9:7c:9f from 192.168.1.246:51712

Fri Jan 5 04:10:18 2024 authpriv.notice dropbear[2695]: Pubkey auth succeeded for 'root' with key sha1!! c3:54:65:6c:1a:1e:4e:29:f9:ce:a7:4d:b0:0a:8b:01:07:a9:7c:9f from 192.168.1.246:51728

Fri Jan 5 04:10:19 2024 authpriv.notice dropbear[2719]: Pubkey auth succeeded for 'root' with key sha1!! c3:54:65:6c:1a:1e:4e:29:f9:ce:a7:4d:b0:0a:8b:01:07:a9:7c:9f from 192.168.1.246:51746

Fri Jan 5 04:10:35 2024 authpriv.notice dropbear[2733]: Pubkey auth succeeded for 'root' with key sha1!! c3:54:65:6c:1a:1e:4e:29:f9:ce:a7:4d:b0:0a:8b:01:07:a9:7c:9f from 192.168.1.246:51756

Fri Jan 5 04:10:52 2024 authpriv.notice dropbear[2771]: Pubkey auth succeeded for 'root' with key sha1!! c3:54:65:6c:1a:1e:4e:29:f9:ce:a7:4d:b0:0a:8b:01:07:a9:7c:9f from 192.168.1.246:51770

 

 

DECO

Please help to stabilized the DECO as because of these incidents many devices are thrown out or appear connected but cannot be accessed.

 

  0  
  0  
#5
Options

Information

Helpful: 1

Views: 1014

Replies: 4

Related Articles
Device keeps forgetting new name
292 1
Problem with multiple deco`s network with same network name ssid
1114 0
Changing Network Name
698 0
Network displayed name
465 0
Change Network Name
1167 0
Edit network name in Deco app
238 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.