-defunct-

Factually incorrect that they don't communicate. Status.control4.com 

Root login is no longer possible since 3.1 (or so)

you don't have to upgrade to 3.x but the Sirius XM requires at least 2.10.x

There is a native music service for Sirius XM.
What controller, OS and country are you located in?
Are you using Native Control4 Audio?

I'll agree to that as well. PCNA is supposed to address that a little, but setting up good networks is an advanced art and finding that specialist can sometimes be difficult.

Just a note on Mesh WiFi and why it is never recommended:
A Control4 system relies on multicast and most Mesh systems disable or extremely restrict multicast.
You might have internet, but that uses unicast.
Mesh APs are okay when not configured in mesh, and instead are configured as individual APs with a wire going back to a central switch.
I'm not at all surprised you have issues because your phone likely can't find the Control4 system due to the multicast being blocked. (The app uses multicast to find the system).
Most IT specialists hate multicast because they don't know how to properly configure a network for it and they don't use products that need it. If you ask any corporate IT specialist, they'll tell you they disable multicast and set up specific routes for unicast traffic. Smart home systems require a significantly more capable network engineer to set the network up properly.

2 aps was never enough for 6000 sqft! Mesh or not. It wasn't properly designed. 
Yes you probably need some DHCP reservations and IPs updated as likely the IP scheme has changed. 

Control4 does not provide tools to decrypt even your own drivers, and Control4 will not decrypt drivers for partners (dealers or developers).
RyanE

If encryption, which is not yours, can be decrypted, then it wouldn't be much of an encryption. 😉
The answer is: You use the driver SDK and should be able to encrypt and decrypt your own drivers.

It's not possible since unifi publishes the snapshot and h264 on different ips and today the proxy requires a single ip

I will check if this has been put in our system as a request for the camera driver. Seems like a reasonable request.

There is a lot of technical debt and thanks for your work in pointing it out. 😉 Your help is appreciated. Not everything has been reviewed, but will be. Your work just bumped up the priority of the mobile apps and cloud interactions.

Understanding of unauthorized use? Nah, that is taken seriously.
Publishing an official doc condemning the integration followed by a legal cease and desist is something I could look into. Probably not what you were wanting by publishing official docs.
It's easier when the integration is approached honestly, otherwise my job is to ensure it is shut down.

Sounds like a call out and a challenge.
Honestly would have hoped you would have reached out like an honest and worthy integrator rather than shrug it off like it's moral.

Assuming you're using Home Assistant to trigger CONTROL4 devices, they would indeed care, and would not want back-door methods to be used that could jeopardize 'proper' integration and existing or in-the-works partnerships/co-operations (see Sonos, MyQ and others).
If you're using it stand-alone for some other lighting - they wouldn't care of course.

If you want DIY, Control4 is not the solution you want. It is not a DIY solution, it is a professionally installed and maintained system.

I’ve actually been looking into this as my dealer now works with Josh.ai.
 
One more thing, after running device discovery on Alexa, each zone is setup as a device, which uses a TV icon making it even more confusing when settings things up. When enabling/disabling/renaming devices on the Control4 website for Alexa integration after running discovery, they’re all clearly listed individually under rooms. Any idea what the purpose of this is, and if they can be disabled? If I’m creating groups within each zone, it normally causes a conflict because the name of the zone is usually the same name given to the Alexa device within that zone. Unless the Control4/Alexa website was reconfigured to list each zone and then list each device within that zone (similar to the System Design layout in Composer), which would then allow you to name 2 devices the same name (I.e. lights) as long as they were in separate zones, I don’t understand the point of have a zone configured as a device in Alexa. Since each device has to be setup with a unique name which normally includes which room it’s in, what’s the point of having the individual rooms configured as devices?

To be fair, the integration and setup is still a pain in the ass.
You'd be better off tossing the Amazon stuff and going with Josh.ai.

Composer me doesn't exist anymore. You have to use composer home. Composer me did not allow any programming it only allows media management

Melissa 
Unfortunately control4 is a dealer based system and dealers must add all drivers. 
Mitch
 
 

Adding silence to the beginning of your announcement audio file might help much more than extending the start delay.

A dealer can set up stuff for OvrC Home, but OvrC itself is not an end user tool, nor is it expected to be.

Start delay only delays the start of the announcement sequence.
The delay set to allow devices to switch inputs, unmute, set volume, and whatever else is baked in and cannot be changed. If you have announcements cutting off the beginning of the file, it means you have too many zones for the baked in delay and will need to add silence at the beginning of the announcement.
 
Aside from utilizing rooms with AVRs that have a long power on delay, the start delay only needs to be about 2000ms, single room announcements could have a start delay of 500ms.

Adding silence to the beginning of your announcement audio file might help much more than extending the start delay.

I think it does benefit a homeowner in a meaningful way as it allows the dealer to have better visibility into the network and therefore provide better service...