EverAction

Control4 does not publicly post release notes.

There's no built in function within the driver to virtually group zones together (always felt it was a major limitation to the C4 amps). However, this can be done via programming but it's a bit of a pain. We used to call it "follow" programming. When the variable for Volume/Input/Mute was changed on one zone (let's call this the master zone), set the variables of the other zones to equal that of the master zone's variable. Much easier to do this via wiring. Just get some Y-adapters.

Just remember to take 1 step at a time and give it time to normalize before taking another step. If you make too many moves at once you won't know where you're at with this.

Why in the world would you think that's not the problem? Did you ever think that since you have two Sonos players un-accounted for possibly in the realm of WiFi, Mesh, Wired setup could be looping your network. Once again your assumptions are getting the better of you. Let's eliminate them from the mix while you're troubleshooting all of this since you can't control them anyways. Keep them unplugged from power until further notice. So what I'm looking at is a Playbar that's using WiFi (as denoted by WM:1) and directly pairing in the surrounds and subs (as denoted by WM:2). You said one Playbar is wired. Is this Master Bedroom the wired Playbar? If it is, it's not setup in wired mode. Please change your Sonos configuration from WiFi to wired. If done successfully, that Master Bedroom Playbar should be denoted as WM:0. EDIT: Sorry just re-read and saw you have 6 (!) missing Sonos players on your network. Unplug power to all of those during troubleshooting. EDIT2: Re-read your old post, you're absolutely sure the Playbar isn't wired up correct? If so just unplug the ethernet wire from the Playbar and keep it in WiFi mode. Unplug power to the 6 missing Sonos players. Give everything time to settle down and observe if you have any major network issues going forward.

Yep, either IR or if you have an Apple TV 4th and an EA controller you can do it via the IP driver.

AFAIK CA-10 does not have the Zigbee antenna. I guess you could run the server on it, but then there's the question of why (I guess the server will be redundant for holding the Zigbee server info so that's the only benefit I see). Might make sense to just keep all Zigbee on the EA-5.

Be more specific. New AppleTV update? New update to the AppleTV driver (which driver)? Both? As you can see from all the recent posts, there is definitely an issue. But without more info, your issue can be one or many.

Need to stop with the assumptions. Mirroring what @lippavisual said it sounds like your Sonos is still misconfigured. Please post the "About My System" from your Sonos app so we can eliminate the guessing.

If the Playbar is wired, why would changing around SSID's affect its connectivity? Or the connectivity of the other wireless Sonos players? Once one Sonos is wired, the whole setup should be in a "Wired" setup, aka the wireless players are not connecting to the network via WiFi but through the Sonos mesh. If you have a player Wired and other players are still connected via WiFi, then it is still not setup properly. Maybe copy the info from "About My System" in the Sonos app and post it here.

This is most likely the issue. You have to be very careful with connecting two Sonos devices with a hard-wire as you risk looping the network if the network equipment can't handle STP properly. Now since you have wireless Sonos devices involved, you can only shut off WiFi on one of them. Which every Playbar is closest to the other wireless Sonos devices, leave it alone don't touch any of the settings. You want to disable WiFi on the *other* wired Playbar. From the Sonos app go to settings, then System, then choose the Room of the Playbar you want to turn WiFi off. Then click on Playbar under Products. Choose to Disable Wi-Fi. Give it 5 -10 mins for the network to figure itself out (or it might even be wise to reboot the router and network switches to clear the ARP tables).

TvOS updates have no affect on the IR receiver/codes of the AppleTV. That's one thing they need to keep the same, unless they want to break "integration" with hundres of URC that utilize IR. Try power cycling the device, it could just be locked up.

Well kind of related, I did upgrade to 13.1.2 so maybe that triggered TouchID to stop working within the app. It's been a tough week keeping up with the iOS updates lol. But at least it hasn't started to crash the app again. EDIT: On second thought I think you're absolutely right @brentethat this is an iOS issue and not an app issue. Sorry for the false alarm! @jakblak

Hey @jakblak so the app has been solid, no crashing. However, after a period of time the app no longer asks for TouchID, it just sits at the passcode screen. It accepts the passcode and lets you into the app. I went into Preferences and verified TouchID is still on. Had to be a few days before this started happening since I've installed the beta app.

Hope so. It would be the nail in the coffin for AppleTV for CI.

Totally. In the C4 world, Roku is the undisputed king no question. I feel like they're the gold standard for CI.

Let's not embellish too much. Their walled garden is the issue here, not so much bugs. Granted iOS 13 has been a bit bumpy, but we were due for that considering how iOS 12 focused on tightening things up and 13's focus is adding features. Anyways I digress. Instead of providing a method of control outside of their walled garden, their idea of using HomeBridge as a proxy into the garden has quite obviously not gone well. Will it get fixed at some point, hopefully. But IMO, the damage has been done with integrating Apple stuff a long time ago. Apple diehards don't care about the shortcomings in regards to integration, but they are losing the fringe users.

Nah I know who Kevin is and what he's involved in. Was hoping to trick him!

Ditto, I call bullshit on this!

It still baffles me how there is even a discussion around this. Apple made the requirements for the API, Control4 is just following their lead. IIRC Savant and Crestron are also dealing with the same exact issue, also going the IR route. Apple has singlehandedly created this issue (many times over I may add).

Please re-read the entire thread. You’ll find an answer as to what is causing both issues along with a beta version of the 2.10 iOS app to try out if this is a critical issue. The beta app has been working for me just fine. Fixed the landscape and TouchID bug.

Add programming, when AppleTV selected as video source send home button command to AppleTV.

The link no longer works but that's what it's known as for dealer's who need to find it on the dealer forums. EDIT: Here's the latest post from the dev of the driver:

This is fantastic! I will load it up shortly and report if I run into problems.

Yeah I just saw it, that's a bummer. Maybe talk to your dealer about this see if he'll give you a break since its an extenuating circumstance. If connecting the IR is easy (a local connection not off of an extension) that you can do it, maybe convince them to send the IR to you so you can place it. Then they can remote in and make the changes while saving a truck roll.

It's unfortunately not up to Control4. Apple released the specs to make certified drivers. C4 is just working within their realm and had put out warnings that the old IP driver might stop working after they released the bridge driver. And TvOS13 made that true. This is totally on Apple. Just hook up an IR and use the free driver that's been floating around and you'll never have to worry about this again.