Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GreenBay42]

Firmware v1.07B09 released.  You can update through the web UI or D-Link Wi-Fi app.

Download - ftp://FTP2.DLINK.COM/PRODUCTS/COVR-C1203-US/REVA/COVR-C1203_REVA_FIRMWARE_v1.07B09.zip


Release Notes:

Problems Resolved:
1. Fix IPv6 PPPoE/DSlite connecting issue.
2. Fix parental control setting issue.
3. Fix app time zone sync up issue.

Enhancements:
1. Support Bridge/AP mode.
2. Support COVR series product reunion.(COVR-C1210, COVR-2200, COVR-P2502 with specific F/W version.)
3. Improve firmware auto upgrade process.
4. Improve guest network on extended COVR points.
5. Support new country code: TH and ID.
6. Support Windows 10 EDGE.
7. Improve potential security vulnerability.
8. Edit few strings on management page.

[FurryNutz]

Wow, Finally. 

I suppose DFS wasn't addressed with this version? I'll check it out though. 

[FurryNutz]

So updated to v1.07. Did the remote Points first then the router. First attempt with 1 point with IE11x32 didn't work right so I changed to FF browser with updating the remote points first then the main router lastly. All is now updated. No factory resets yet.

• I see the following new feature:

I presume this is wireless bridge mode? 
Kewl new feature.

• Also D-Link implemented onboard setup of the router with a wired PC and web browser. Thank you for including this. Now we have both flexible ways to setup the system, mobile app or wired PC and browser.

Thank you D-Link. 

Schedule is not working still to disable WiFi. 

Regarding DFS, it's choosing a lower 5Ghz channel even though my main wifi is using it. I'll set this up as the main wireless and see if I can get legacy wifi bridges to connect to it. I'm hopeful.

I'll be putting this online in the next day or two and see how it does with the NEST controllers.

[FurryNutz]

Ok, just completed getting the 1203 online. Wire connected remote points.
Took a bit longer than expected however I forgot to give the remote Points about 3-4 minutes to come to ready when setting up wire connection for them.

Legacy wireless bridges are working with it.

Getting to spec speeds on my iphone and galaxy tab S2: 230/9. Should be 10 for the UP. 

NEST controllers are connected however the PINGS on the controllers are TOO high so my mobile app for them can't connect to them. The one right next to the router is reading 28778ms. I see this is still an on going issue. 

Will let'r run over the weeken and see how it goes.

[FurryNutz]

So I need to take down the 1203 system until the NEST issue gets fixed. People are complaining that they can control the NEST from the mobile app.
Other than this and scheduling not working to disable WIFI, I believe the system is stable on this version of FW.

I do want to do one factory reset and setup from scratch to see if anything changes. I'll give this a try over the weekend when I have the system and Internet alone. 

[FurryNutz]

I ran a factory reset today to see if setting up 1203 with the new FW would maybe fix or help with the NEST app connection. Unfortunately no. It's still fails to connect. I removed the 1203 system and put a different D-Link router online and the NEST controllers were seen in the app soon after that router was online.

Hope D-Link and NEST an figure this out. This only seems to happen on the COVR 1203 system.

[FurryNutz]

FYI, users should be aware that the new feature introduced in v1.07 maybe incorrectly stated and worded. I've tried this "bridge" mode out and is not actually "wireless bridge", rather Access Point (AP) mode. For users who want to try this, you can configure the 1203 in AP Mode and LAN connect port #1 of the A point to your main network or behind a router. Look at the main host routers connected client table to find the IP address of the 1203 after you've selected the Operation mode: Bridge. Once it's reboots  and you find the new IP address it gets from the main host router, then you can access the 1203's web page to configure the WiFi settings while in "AP" mode. You can set a static IP address on the 1203 so you know it has the same IP address that doesn't change. I set mine to 192.168.0.12.

I've passed this on to D-LInk for review to see if they can better explain the new operation mode and maybe make some UI changes. I would be nice to have a default IP address for the AP mode setup so users don't have to go fishing for it.  192.168.0.50 is a default setup IP address seen on some D-Link DAP models. Maybe D-Link can add this for this mode.

[FurryNutz]

I this this is happening now:
https://arstechnica.com/gadgets/2019/05/nest-the-company-died-at-google-io-2019

I ran a factory reset today to see if setting up 1203 with the new FW would maybe fix or help with the NEST app connection. Unfortunately no. It's still fails to connect. I removed the 1203 system and put a different D-Link router online and the NEST controllers were seen in the app soon after that router was online.

Hope D-Link and NEST an figure this out. This only seems to happen on the COVR 1203 system.

[FurryNutz]

I put a DIR-882 online Sunday and all is well with NEST. No issues connecting. I checked the Pings on the NESTs and there down in the double digits. Not like the pings seen when they are connected to the 1203 system. 

Ok, just completed getting the 1203 online. Wire connected remote points.
Took a bit longer than expected however I forgot to give the remote Points about 3-4 minutes to come to ready when setting up wire connection for them.

Legacy wireless bridges are working with it.

Getting to spec speeds on my iphone and galaxy tab S2: 230/9. Should be 10 for the UP. 

NEST controllers are connected however the PINGS on the controllers are TOO high so my mobile app for them can't connect to them. The one right next to the router is reading 28778ms. I see this is still an on going issue. 

Will let'r run over the weeken and see how it goes.

[GreenBay42]

It's an issue I do not see getting fixed since Nest (gen 1) has several incompatibility issues with wireless routers and access points. 

[FurryNutz]

The 1203 would be the only wireless router that the NEST 1st gen seems to have issue with. Have tested many other routers. MANY. 

Has the wireless capture done on 2.4ghz of the 1203 been looked at?

[GreenBay42]

https://nest.com/support/article/Some-routers-may-cause-issues-with-adding-a-Nest-product-or-Wi-Fi-connections#routers-thermostat

[FurryNutz]

"Incompatible routers"
"Even if your router is not on this list, you may be using a router that is incompatible with Nest Products. The list of symptoms below can help you to identify routers that may be incompatible or are using incompatible settings."
So I presume this means that NEST and or D-Link will not attempt any such fixes? The NEST works with COVR 2202 and 3902.  Why is the 1203 so different? I presume maybe wifi chipset drivers.

Symptoms of an incompatible router or incompatible router settings include:
Nest thermostat being offline in the Nest app
Nest thermostat disconnecting frequently
Excessive battery drain
Frequent restarts
Being unable to add your Nest thermostat to the app
Higher than normal temperatures detected by the Nest thermostat"

D-Link routers
DAP2553
DI-524


This is a short list...Mostly old legacy routers. 
 

[GreenBay42]

I sent it to higher ups. Hopefully HQ can test it

[FurryNutz]

Please let them know if they need any more info or test help, let me know. Really hope someone can fix this.