-defunct-

The C4 driver uses the device's local API, not the cloud one.

Reasoning being, volume and such should be controllable regardless of if your internet works.

Is that the cloud api? If so, it won't be added to the C4 driver.

The next step is checking your router to see if the hc250 shows up in your dhcp list.

If it does and the controller is still not working, then the project may need looked at.

You'll need the dealer software to configure the IP.

It would be easier to change the subnet of the new router.

I would disable 802.3az EEE. It is supposed to save power on inactive ports and any 'smart' feature like that could cause connection issues since the Control4 system expects immediate and consistent connections between devices.

I'd also be wary of dropping the power available to POE devices.

If an unmanaged switch cannot have the feature turned off, I would recommend replacing with a managed switch.

Hmm, that would explain it. I use the apps and touchscreens with the lighting menu and custom buttons.

Hmm, has not been my experience. All of my bulbs change together with the one drag of the slider.

The group drivers should send one command. It's why I use them instead of popcorning 17 single bulb drivers.

But you can do what works for you. Just thought I'd give a tip as an active user and the person who tested the drivers for a few years.

That is why I use the group drivers.

I have 17 color bulbs and stopped using independent bulb drivers because it was way too easy to overload the hub.

Be aware that a driver update will likely override the modification.

3) is what needs prioritized. Since the bug has been open since May, my options of 1 and 2 are more likely the permanent solution.

Two solutions exist at the moment even though both may not be ideal.

1) Don't reboot the controller.

2)Don't use the 'last used values' config.

I work for Snap One.

It's in a nonpublic bug reporting system.

Looks like it was reported in May.

I'll put in a comment to see if it gets prioritized.

Hmm, confirmed here.

I didn't notice with my personal system because all of mine have startup values.

What bulb are you using it with?

What version of white warmth driver are you using?

To have no delay, you'll want to run a cable from the ATV to the audio matrix.

All shairbridge streams and all audio inputs on C4 controllers are delayed by 1.5-2.5 seconds for bufferring.

Some TuneIn stations will cut off access to reduce idle/dead connections and each station has its own timeout.

The only way to get this resolved is  through Control4 tech support (and your dealer if you aren't one), so that they can review the audio logs to determine if some programming is turning it off or if the station is killing the stream.

Also, for the best audio experience, I would suggest you be on Control4 OS version 3.2.4.

Yes, I do.

The app requires FireOS 6 as a minimum. Anything stuck on FireOS 5 is not supported with the OS3 app.

Log4shell is the primary one that is concerning.

The rest are only exploitable in custom configs.

Acunetix, Nessus, and Crowdstrike have been good about keeping up with the vulns.

I'll have to review again, but the critical test (active exploit scanning) found nothing, so if it is a vulnerable version it is not configured in a way that allows the vulnerability.

22 minutes ago, DanITman said:

You sure your SOLR driver search wasn't impacted?  That is Java based and there is a public service for it. 

According to our scanners, it was not.

15 minutes ago, ekohn00 said:

A vulnerability need not have to be directly related to "a customer".

Sure, we looked at situations that would indirectly impact customers as well and none existed. We don't use log4j.

Are you indicating you feel vulnerable regardless of the reassurance?