Nitin

21 minutes ago, bnorman said:

@Nitin, @South Africa C4 user device naming has been added as the top row in Preferences in the app update that is rolling out today.

confirming that the feature works. I was able to rename my device on the app and the updated name showed up on customer.control4.com

@bnorman very much appreciate the fix and the follow-up!!

8 hours ago, bnorman said:

@Nitin @South Africa C4 user, in a future update we are going to have the default device name be your device model, "iPhone 15 Pro" as an example (this is how Android does it today). Likely in the same update we are going to add back the field to change your device since many households likely have multiples of the same model iPhone/iPad. I'll let you know when this happens and where exactly in the app you'll be able to find this relatively soon.

Fantastic, thank you!

4 hours ago, South Africa C4 user said:

That is interesting! If users don’t have the ability to change the device name (within Control4) going forward it will make it very messy (especially for new installs in Apple households).

Agree 100%. If I don't know how to recognize my devices, how will I be able to assign/select notification preferences without a whole lot of trial and error?

@bnorman could you please take this feedback/question back to the product team and broker a response?

8 hours ago, bnorman said:

@Nitin, I’ll investigate this tomorrow and get back to you. There was a spot in the old Settings where you could change your device name. I don’t think it currently exists in the new Settings.

Glad to hear you say that cause I do remember a place in the settings where I could change this and was wondering why I could not locate it anymore.

I had to re-install C4 on my iphone and post re-install, when I log into my account on customer.control4.com, I see my device name listed as "localhost" even though the device has a different name as far as iOS goes. My other devices on which C4 is installed show their correct iOS name.

How can I have the correct device name show up vs "localhost"?

3 minutes ago, appliedautomation said:

You wont, its done via https://app.ovrc.com/ 

I have no idea about that site/platform. So this means I cannot change this behavior at all?

46 minutes ago, appliedautomation said:

That's the OvrC hub on the controller doing a site scan. It will check for open ports on all available hosts. The port list is defined within the site settings, the defaults are, 22, 23, 80, 443, 5000, 8008, 8080, 8443, 8888.

@appliedautomation Thanks for that info. Where on Composer Pro will I find this? Could not locate it on the properties of the highest level entry on my project.

I use opnsense for my router/firewall and am seeing these log entires on opnsense every hour originating from the internal IP address of my C4 controller. Any clues?

The driver for the blinds/shutters is the same in all rooms, yet it shows a different UI for the kitchen (in image below). Any clues?

Had a full power outage the day before and when the lights came back on, I found the KNX panels with the yellow lights blinking. They did not do that before. Everything seems to be working ok in the house, so I am unsure what is going on and how to fix it. If someone is familiar with KNX, I'd appreciate any insights.

Thanks

1 minute ago, msgreenf said:

That is old legacy programming.  Basically some older releases didn’t clean up programming properly when you removed devices.  Don’t worry about it. The only way to fix it is via the project XML and is HIGH risk.

Letting it be then! Thanks.

8 minutes ago, Andrew luecke said:

It's probably a dynamic event. It will show up in programming though most likely

I thought so too, but there's nothing under ID Agent→Programming

Using Detective Suite, I can see this "unknown item" under "Identity Agent→Events"

I can't delete it or do anything. ID agent, when viewed on the "Agents" tab/area (where all agents live), correctly shows the two users on my account.

How do I get rid of this?

Yep, linking works now.

26 minutes ago, neil12011 said:

Google voice services are down also (I'm actually running both on my system).

Thanks for that info.

This would then logically imply that the issue is on the C4 side cause chances of Amazon and Google being down at the same time are slim.

1 hour ago, neil12011 said:

Same problem here also.

Is there a way to ask C4 if they recognize this as a known issue? Their status page says everything is ok.

1 minute ago, Jobu604 said:

Also not working for me today. Wonder if it’s a widespread issue. 

Snap One's status page shows all green. But if its busted for you as well, then it could indeed be a widespread issue. Hopefully others can test and chime in.

Getting the "XYZ device is not responding" msg from Alexa. Everything was ok as of yesterday. No changes made.
Tried disconnecting C4 skill and reconnecting, getting the attached error msg.

Is your Alexa integration working ok?

Where does Snap One report outages?

I ran into this today. Alexa was telling me that the lights were not responding, so I decided to redo the skill on Alexa. Dead now. Can't link Control4 and Alex, get the same error msg as shown above.

Also rebooted the controller, no luck.

23 minutes ago, Andrew luecke said:

What version iOS app are you using? 

323.55

5 minutes ago, mujtaba.khokhar said:

updated our office system to OS3.4 and work phones to IOS 17 - same issue with the KNX driver its hit and miss. 

android doesn't seem to be a problem - YAY Apple! 

Called C4 - said theres an update coming to the app to fix some bugs. 

lets see...

No more OS3.4 updates for now 

Muj

Thanks for pinging C4.

Waiting for the update now

50 minutes ago, Andrew luecke said:

Do a refresh Navigators, and it will possibly fix it.. And ensure your locale is US. Otherwise, speak with your dealer (it could be something easy)

Refreshing navigators did not solve the issue. For locale, did you mean on the iOS devices?

More info... this only happens on iOS. It does not happen on C4 touchscreens.

15 minutes ago, Andrew luecke said:

I don't think we've had any calls for our (Chowmain) thermostat drivers and this issue so far. So, statistically, less likely to be a app bug or OS bug. More likely driver or system configuration related

I'd agree with you but the point made above by @eon where he's having the same issue but with a completely different driver points to the issue being outside the driver or config.

I am stumped. Unsure what to do next.