DLite

13 minutes ago, ekohn00 said:

Do a backup, then just start from scratch. No VLANs, nothing special and see if it works. I've run into problems when trying to simply upgrade from one unit to another, but then when i start from scratch all is well.

Good luck!

 

 

Thanks. Mine is a simple, flat network with threat management off. I am generally a pretty simple-minded guy!

27 minutes ago, msgreenf said:

Bad firmware from unifi? Never...

1 hour ago, ekohn00 said:

I double checked mine, and they look exactly as you displayed too (just different address space).

Just a thought, based on “wording”…..  I personally have all my C4 use dedicated addresses. This way there’s no reason to rely on the DHCP requests. Then I go into UniFi and make them a fixed address (so UniFi knows). At the same time they are all outside of the range my DHCP gives out too.

if your doing all this, time to do into trouble shooting mode if your still getting delays on the c4 gear.

 

 

Thanks for investigating, @ekohn00.  It turns out that my problem was the UXG-Max router.  It is not clear whether it was a defective unit or just buggy firmware for a recently released product, so I'd be curious to know if anyone else has successfully deployed the UXG-Max so far.

After tearing my hair out for several days, I finally just popped my trusty old USG router back into the network and removed the UXG-Max yesterday afternoon.  After doing so, I could no longer reproduce the problem, and I've had no issues since then (knocks wood). My fingers are crossed that this holds up.

Notably, the USG is EOL, so its firmware is 18 months old.  Thus, it's not totally clear whether my problem was an idiosyncratic hardware failure with that particular UXG-Max unit or a more general issue with the latest UXG-Max router firmware.  I plan to return the unit anyway, but I am likely to try again in a few months with another unit after the firmware (hopefully) matures.

Thanks all for the advice and insight!

1 hour ago, ejn1 said:

This looks completely normal.... Just like mine is set up but I use larger DHCP range than you have chosen.

Thanks, that helps narrow things down a bit.

26 minutes ago, ekohn00 said:

That’s because you set the DHCP range to .176-.254, do your router won’t give out the full range. This is not what’s fully routinely, this is stating what DHCP addresses your UniFi router is dishing out. You can of course use statics between .5-.175 for instance.

To be honest, this issue has become confusing.  I have about 100 devices with address reservations in the 2-175 range and all are working normally (except for the C4 lag).  I posted my settings on the Ubiquiti board and was told that my settings are consistent with what I want to achieve.  Someone else on the Ubiquiti board confirmed that their settings show up the same way, and they also have address reservations below the DHCP range, etc.  I believe @Popolou made the same point above.  

51 minutes ago, Cyknight said:

That doesn't ELIMINATE the possibility. IF there's another device on static that you reserved an IP on, there's still a confict.

I'd change the reserved address of the TScreens and main controller, reboot, scan network. Also you're using 192.168.0.xxx - did you ensure your ISP modem/router isn't using the same range?

Yes, you are absolutely correct, and I misunderstood the terminology the first time @msgreenf raised the issue.  To be clear, the only devices with static addresses on my network are the Unifi network devices -- the CloudKey, the APs, and the switches.  I have confirmed there is no duplication of their addresses with either the DHCP range or any of the fixed DHCP reservations in the system.  My ISP modem is using 192.168.100.  

Nonetheless, I'm happy to give new address reservations a shot.  To be clear, I would create new DHCP reservations for all touch screens and just the primary controller?  And then, I reboot all the C4 hardware?  Finally, sorry to be dense, but I'm not sure I understand what "scan network" means.  

Thanks to all!

1 minute ago, Popolou said:

It's just the quirkiness of how Unifi display it. The DHCP scope is still within the subnet but limited to the upper 79 addresses.

So, in other words, the settings are correct?

1 minute ago, msgreenf said:

/24 is 255 addresses. Something is wrong somewhere...

 

I'm not a unifi guy so can't really help 

Even after 10 years with their equipment, it is clear I am not a Unifi guy either , but something does seem off here.

10 minutes ago, msgreenf said:

Looks like you found the problem 

Agreed, but it is not yet obvious to me how to fix it.  The IP range seems to be auto-generated by the CIDR, which seems(?) both correct and inconsistent with the displayed IP range.  

8 minutes ago, Popolou said:

Best you take a look in case something defaulted there and it's the cause for the network connectivity.

The IP range is actually defined by the CIDR that you enter in the GatewayIP/Subnet field so if it is /24 then the subnet range is from .0 to .255. What does yours say?

Wow, I am so confused. It does say /24, but then it doesn't give that corresponding IP range.  See the attached screenshot.

2 hours ago, ekohn00 said:

you said fixed outside the DHCP range (all on the Unifi side)....  In the devices are you setting a static IP or DHCP?

I use fixed addresses on Unifi, but keep them within the DHCP range and on those devices use a static IP. This way either a static or DHCP reserved approach works for these devices and I don't have conflicts.

Being this is a new router, I'd just clear everything and redo the addressing part so there's no accidental conflicts.

Interesting.  You can see my intended setup explained just above. This always worked fine for me, but I am wondering if something has gone awry. It may even be due to a Unifi OS update rather than the router swap itself.  On the Unifi boards, I often see the advice to reserve part of the IP range to be outside the DHCP range and to use that range for fixed IP addresses. However, maybe that is now screwing things up somehow.

1 hour ago, Popolou said:

All network settings confirmed as unchanged post-move? The only other unifi oddity i could think of resembling this is how they implemented storm control under the network profiles. I normally turn this off but if the switch (under L3 routing) or the router (through L2) is delaying/stopping the packets because it thinks there is a device flooding the network, this could have that same result.

I may not have looked closely enough at the network settings to confirm they remained the same after the router swap. I just noticed something that looks odd to me, but maybe I don’t understand something.

The way my network is supposed to be configured is as follows. My router is at 192.168.0.1.  All of my fixed IP addresses should be between 192.168.0.2 and 192.168.0.175.  And, my DHCP range should be 192.168.0.255.  
 

I have confirmed that the Unifi network settings for my main VLAN correctly show the DHCP range as 192.168.0.176 to 192.168.0.255. However, it also shows the “IP Range” as 192.168.0.176 to 192.168.0.255.

Isn’t that “IP range” wrong?  Shouldn’t the IP range be 192.168.0.1 to 192.168.0.255? My C4 Director and all my other resident devices live between 192.168.0.1 and 192.168.0.175.  Could this “IP Range” setting be the problem or am I confused about how the settings should work?

thanks a lot

25 minutes ago, msgreenf said:

DHCP reservations and static IPs are not the same 

I left out one important detail. The address reservation is outside the DHCP range, so a conflicting assignment is not possible.  Sorry for the lack of clarity. Let me know if I’m still missing something here.

8 minutes ago, msgreenf said:

Does your controller use a static IP?

Yes. The Unifi controller reserves a fixed IP for the C4 controller.  The C4 controller itself is set to use DHCP, so the static addressing is handled on the network side. Does that answer your question? 

IP conflict?

11 minutes ago, Popolou said:

Check the DHCP settings handed out to clients when you moved to the new router and check its logs to see if there are any indications what it could be. If it is network wide, i'd start at the common denominator and work back (ie the router). All the settings were copied over as they were before such as which DNS servers are being to forward LAN queries?

Huh. Here's something interesting from the Unifi logs.  One of my wired C4 touch screens is showing 2 orders of magnitude more network traffic over the past 24 hours compared to all the other touch screens.  No idea what would cause that, but I am going to try switching that touch screen off.

5 minutes ago, Popolou said:

Check the DHCP settings handed out to clients when you moved to the new router and check its logs to see if there are any indications what it could be. If it is network wide, i'd start at the common denominator and work back (ie the router). All the settings were copied over as they were before such as which DNS servers are being to forward LAN queries?

Thanks a lot.  All the DHCP settings and reservations appear to be unaffected. Those are controlled by my Unifi CloudKey, not the router itself, and they all look normal to me.  Also, I think the problem is isolated to C4, rather than network-wide.  I am able to access non-C4 network resources instantly during these periods of "downtime."  

Might there be relevant C4 log files to check as well? 

5 hours ago, enzeder said:

I have all unfi gear including a uxg and running latest firmwares (beta) and C4 is fine.


Sent from my iPad using Tapatalk

Thanks.  Just out of curiosity, are you also running the new UXG-Max?  

47 minutes ago, Popolou said:

Limited to wifi endpoints?

No, I am unable to control wired devices, including Roku and a McIntosh receiver. As another note, during this period of lag, I am able to control other devices on the network — e.g., I am able to pause music if I use the Roon (not Control4) app.

Eventually, all the C4 commands are executed at once. It seems like something is hammering the controller for a few seconds, but I am at a loss as to what has changed besides the router and Unifi firmware.

On Sunday, I replaced my Unifi USG router with a UXG-Max. As part of that process, I updated all my Unifi gear — switches, APs, and Cloud Keys — to the latest firmware.  None of the other network settings were changed.

It may be a coincidence but since then I have been experiencing random periods of non-responsiveness from Control4. Every so often, for about 5-10 seconds, navigators (iOS apps and Zigbee remotes) do not seem to control devices or respond. (I _think_ the problem is specific to the navigators.)

I have restarted my controller, and I removed the most recently installed driver (installed about a week ago), but that did not resolve it.

Has anyone else upgraded to latest Unifi firmware? Or maybe it is the new router?

thanks

[Deleted]

14 minutes ago, DLite said:

It turns out the Kwikset lock won't fit our new front door, because the door is 2 1/4" thick and the Kwikset supports a maximum door width of 2".  Does anyone have ideas for how to find a lock that would fit a door this thick but still be capable of integration with C4?

To answer my own question: Kwikset has a thick door kit that their customer service will mail out on request.  Fingers crossed that it works!

It turns out the Kwikset lock won't fit our new front door, because the door is 2 1/4" thick and the Kwikset supports a maximum door width of 2".  Does anyone have ideas for how to find a lock that would fit a door this thick but still be capable of integration with C4?

5 hours ago, Time2Jet said:

I might have a few left.  If I do, they'd be $75ea shipped.

I was able to purchase one. Thanks for the reply!

We currently use Yale C4 Zigbee locks on all our doors. We are about to replace our front door, and, for aesthetic reasons, we decided to go with the Kwikset 910 in Antique Bronze.  It turned out that C4 doesn't offer the antique bronze color for that lock, so my dealer suggested buying the antique bronze Z-Wave version from Home Depot and then switching out the Z-Wave card for a C4 Zigbee card designed for that lock model.  

However, I just noticed that there seems to be a native C4 driver for the Z-wave version of the Kwikset 910 lock.  Is there actually any good reason to switch out the existing card for a Zigbee one, or can we just stick with the Z-wave version?  I ask because we've had GE Z-Wave in-wall electrical outlet receptacles integrated into C4 for almost a decade, and they have been absolutely 100% bulletproof. (We have the USB Z-wave dongle plugged into an EA-1.) Would z-wave locks be any less reliable?

Thanks!

Hi,

PM me with any possibilities. 

Thanks