Official Release Deco X50(V1) 1.1.0
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi All and @JoaoRamos, @knittl79 @macroth72
Hi All,
Good news! Apart from the 1.6.0 firmware for Deco M5, the official firmware 1.1.0 for Deco X55/Deco X50 has been released recently,
They would be the first batch of HomeShield models to have customized signal source and connection preference as well as other features available on 1.6.0 of M5.
Deco X55(EU/US/JP/CA)_V1_1.2.0
Deco X50(EU/US/JP/CA)_V1_1.1.0
More details about New Features/Enhancement:
1. Added Reboot Schedule for every day/week under Deco App > More > Reboot Schedule.
2. Added support for customizing Satellite Deco Signal Source under Deco App > Internet > Select the Satellite Deco > Signal Source.
3. Added support for customizing clients Connection Preference under Deco App > CLIENTS > Select the client > Click the gear icon on the right-up corner > Connection Preference.
4. Added No-IP and DynDNS to the DDNS settings under Deco App > More > Advanced > DDNS.
5. Added Smart DHCP on/off switch in Access Point mode under Deco App > More > Advanced > Smart DHCP.
6. Added a prompt notification when the Ethernet link rate goes down to 100Mbps.
7. Added schedule and bandwidth limit to guest network under Deco App > More > Wi-Fi > Guest Network.
Notes:
1. Please update your Deco APP to the latest version for the new features.
2. If there are non-1.6.0/1.1.0 models in the Mesh network, you may miss some new features but this feature will be supported via firmware update in the future.
3. You may miss some new features when Deco is set to Access Point mode.
As usual, the 1.6.0/1.1.0 firmware version is a leap forward and any feedback after the firmware upgrade will be highly valued. If you have any confusion about the firmware upgrade, please feel free to comment below.
Related Articles:
Deco M5 1.6.1
Deco M9 Plus 1.6.0
Deco M4(V4) 1.1.0
Deco X55(V1) 1.1.0
Frequently Asked Questions on Deco Firmware Update
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@David-TP As with others I'm seeing this in the error logs
Tue Dec 20 15:53:44 2022 daemon.err client_mgmt: update_history_wire_type:exit failed.
Tue Dec 20 15:53:44 2022 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Tue Dec 20 15:53:45 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:53:46 2022 daemon.err client_mgmt: client(xxxx) not found in arp table disconnect_counter=1
Tue Dec 20 15:53:46 2022 daemon.err client_mgmt: client(xxxx) not found in arp table disconnect_counter=0
Tue Dec 20 15:53:55 2022 daemon.err nrd[16644]: wlanifMapToBandwidth: Invalid bandwidth from driver: 3
Tue Dec 20 15:53:55 2022 daemon.err nrd[16644]: wlanifMapToBandwidth: Invalid bandwidth from driver: 3
Tue Dec 20 15:53:55 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:53:56 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:53:57 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:01 2022 daemon.err client_mgmt: can not parse json_obj
Tue Dec 20 15:54:01 2022 daemon.err client_mgmt: update_history_wire_type:exit failed.
Tue Dec 20 15:54:01 2022 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Tue Dec 20 15:54:04 2022 daemon.err client_mgmt: client(xxxx) not found in arp table disconnect_counter=2
Tue Dec 20 15:54:04 2022 daemon.err nrd[16644]: send ioctl failed
Tue Dec 20 15:54:05 2022 daemon.err bandwidth_contr: get mode: 11AHE160
Tue Dec 20 15:54:07 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:08 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:09 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:19 2022 daemon.err client_mgmt: can not parse json_obj
Tue Dec 20 15:54:19 2022 daemon.err client_mgmt: update_history_wire_type:exit failed.
Tue Dec 20 15:54:19 2022 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Tue Dec 20 15:54:19 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:21 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:25 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:26 2022 daemon.err nrd[16644]: wlanifMapToBandwidth: Invalid bandwidth from driver: 3
Tue Dec 20 15:54:26 2022 daemon.err nrd[16644]: wlanifMapToBandwidth: Invalid bandwidth from driver: 3
Tue Dec 20 15:54:29 2022 daemon.err nrd[16644]: send ioctl failed
Tue Dec 20 15:54:31 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:33 2022 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1105: Error: can't find ifname[eth1.591] in eth_ifname
Tue Dec 20 15:54:33 2022 daemon.err udhcpd[28257]: Found static lease: d44a8c0
Tue Dec 20 15:54:33 2022 daemon.err udhcpd[28257]: Sending ACK to 192.168.68.13
Tue Dec 20 15:54:33 2022 daemon.err udhcpd[28257]: clear ip d44a8c0
Tue Dec 20 15:54:35 2022 daemon.err bandwidth_contr: get mode: 11AHE160
Tue Dec 20 15:54:36 2022 daemon.err client_mgmt: can not parse json_obj
Tue Dec 20 15:54:36 2022 daemon.err client_mgmt: update_history_wire_type:exit failed.
Tue Dec 20 15:54:36 2022 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
looking at ifname[eth1.591] that is to do with the guest network, so why is it constantly throwing the error, especially if not in use but enabled.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@mirdragon work!
- Copy Link
- Report Inappropriate Content
@David-TP the bandwidth error I believe is to do with the QOS setting, not sure why it is filling the logs even though the setting is disabled
- Copy Link
- Report Inappropriate Content
@David-TP
Windows 10, generic Intel AX210 card disconnecting several times throughout the day, the card then connects to an isolated router several rooms away.
When I try to manually connect to the Deco network using the network icon in the tray, I see the router I'm connected to with weak signal, but there is a very strong hidden network. After 1-3 seconds the Deco network shows up and then I can connect to it.
Deco in AP mode, the Deco is about 1 m away from the notebook, signal is very strong.
Network card driver is always the most recent, two days ago Intel released the latest driver and the problem continues.
The error log is always huge, showing that other devices also have issues
- Copy Link
- Report Inappropriate Content
Have you tried to turn off "Mesh Technology" on the Intel AX210 laptop to see whether it could improve the network stability?
It is also suggested to enable the guest network for 2.4ghz only with a different SSID to see whether it would be more stable over 2.4ghz.
Wait for your reply.
Best regards.
- Copy Link
- Report Inappropriate Content
Thanks for the feedback.
Would restarting the main Deco X50 be able to get the satellite Deco X50 units back?
And will you reproduce this issue most of the time?
At the same time, I would like to follow up on your case via email. Please check later whether you could get an email from me later.
Best regards.
- Copy Link
- Report Inappropriate Content
Hi David,
Yes, turning off Mesh for this device in the Deco App improves reliability.
But it shouldn't be this way, right?
I couldn't find any "Mesh Technology"setting in the AX210 card settings, also not in the Device Manager.
There is no guest network here, just an isolated router a couple of rooms away that is not part of the Deco AP Network
Thanks
- Copy Link
- Report Inappropriate Content
@David-TP another bug spotted on this firmware - nest thermostat keeps going offline and also one my smarthome lights. never had this issue with the deco m5 setup in the same positions using wired backhaul.
seems you need to optimise the network to get it all working again, surely this could be automated. is there a reason why it isn't?
- Copy Link
- Report Inappropriate Content
@David-TP Another bug found with the latest firmware/app
Devices are being renamed
ie: set nest protect smoke detector names for each of the devices, these are being renamed in the app to something else. also done the same for some other devices
please can you sort this out as this deco setup is no good running as router, etc in the current condition it is at.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 17755
Replies: 67
Voters 0
No one has voted for it yet.