EverAction
-
Posts
103 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Gallery
Downloads
Events
Posts posted by EverAction
-
-
2 hours ago, linkdog said:
I have a C4-16AMP-3-B at a restaurant and want to use the first 3 zones for one area or zone. Can this amp be programmed to do this. I tried setting the Audio Endpoint to zone 1, then moved to zone two, set the Audio Endpoint to the same zone and it is replaced with zone two. I would think I'm not the first person to try this, Please help!
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.
-
32 minutes ago, time2jet said:
Thanks so much!
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.
Only meaning that the SSID changed and I never re-added the other 6.
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.
Sorry, in a prior post, I indicated that NOTHING was connected via ethernet. There is an ethernet cable connected to the master playbar that is just tucked inside the equipment box, never connected.
EDIT: Sorry just re-read and saw you have 6 (!) missing Sonos players on your network. Unplug power to all of those during troubleshooting.
Only a playbar that you don't see is plugged in. I will unplug that. The other 5 speakers are unplugged and have been since the switch over several weeks ago.
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.
I will unplug that ethernet cable at the master Playbar
If I could interject some info here... This weekend I removed the main switch and used only the Modem>Router>PoE+ Switch>4 WAPs to test and although there was a slight improvement, it was negligible. (I rebooted each device in sequence). Which leads me to believe that there is a chance "loops" are not the issue... Now, this doesn't exclude wireless devices causing issues (Sonos for instance). But I do feel l like the power settings and the channels for the SSID's in the WAPs could be a potential issue. I will screenshot the inSSIDer screen tonight so you can see where the WAPs are channelwise and powerwise and how they are reading. I have a second SX-8P PoE+ switch new in the box. I might try to install that instead of the one on currently on the system. That could eliminate that as an issue. Leading me to believe it could be the modem, router, cabling or WAP's (once the PoE switch is eliminated as a potential). There are 2 WAPs that seem to be broadcasting very good signal and connect to the internet. I moved one of the "good" one's to the cable that has a "bad" one to no avail. What I didn't try, was moving one of the "bad" ones to the good one's cable and location. I have to try that tonight.
I know this is a lot.
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.
-
15 hours ago, time2jet said:
Here is the system. There are only 4 devices currently on. Lost 6 in the SSID change. But right now, that’s not the problem.
Have a look (the screenshots overlap)
Sent from my iPhone using TapatalkWhy 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.
-
43 minutes ago, boykie said:
The new AppleTV update no longer allows control over IP. Everything has to go through HomeKit. So I’m guessing I need to go to IR?
Yep, either IR or if you have an Apple TV 4th and an EA controller you can do it via the IP driver.
-
24 minutes ago, South Africa C4 user said:
So my CA10 is being installed tomorrow... has anyone here put one in a system yet? Is it worth the price tag?
If it solves the issues I’ve had for the last month or so, it will be worth the price for me... if it speeds the system up then it will be a big big plus.
And a question, should I move Zigbee to the CA10?
I will have a CA10, an EA5 and 2 HC800s in my system (plus a number of EA1 and HC250s).
I currently have 2 Zigbee networks (on the 2 HC800s) and the EA5 does something for Zigbee also (I think it is the Cordinator and the HC800s are the Zigbee Servers but I may have my terminology confused)...
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.
-
14 minutes ago, boykie said:
Anyone having issues controlling Apple TV with the new update?
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.
-
11 minutes ago, time2jet said:
Yes, they are. I assume they are actually all connected to 1 particular WAP and that one is the one that has the most issues actually.
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.
-
On 10/4/2019 at 4:11 PM, time2jet said:
I’m sure glad you all couldn’t hear my 10 minute expletive rage. I rushed home excited to try this and unbeknownst to me, only one Playbar is Ethernet. The other is wireless, like the Sonos Ones on the system. And that Playbar apparently fell off of the system when I split out and renamed the SSIDs. I’m struggling to get it to recognize to add it back. I was somehow able to with the Ones.
Saga continues.
Sent from my iPhone using TapatalkIf 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.
-
On 9/30/2019 at 10:07 PM, time2jet said:
2 playbars are ethernet with optical for. One room also has a sub and surrounds (wireless).
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).
-
11 hours ago, jebt2921 said:
I have an Apple TV 4 (believe it’s the version just prior to 4K) in one room which has been controlled via IR since day 1 of my install. However it self upgraded to os13 and now doesn’t work. Does the new OS also break previous IR drivers? I’m aware if the 4K issues but not this.
Anywho, might could use someone to add this or another updated IR driver for me.
Sent from my iPhone using TapatalkTvOS 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.
-
51 minutes ago, brente said:
On iOS 13? If so, seems to be a known touchid bug in iOS...
https://9to5mac.com/2019/09/30/ios-13-iphone-touch-id-login-bug/
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
-
On 9/27/2019 at 4:45 PM, jakblak said:
A new version of the 2.10 beta app is out and it has the fix for crashing at startup when using biometrics (TouchID/FaceID). If you've already downloaded TestFlight you'll be notified of the new build, if not, then you can use this following link (it's the same one from my previous post).
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.
-
Just now, therockhr said:
yep. I have an ATV 3 (?) that uses the old unsupported IP driver and it is still kicking but I use Roku as my main streamer now. I only use the apple tv for airplay and the apple movies I have previously bought. apple is supposed to be making an apple tv app for roku for their apple tv + service. wonder if it will let users view movies and tv shows they have bought as well (that is if they even make the app outside of ATV).
Hope so. It would be the nail in the coffin for AppleTV for CI.
-
-
17 minutes ago, msgreenf said:
Cause Apple is perfect! They are the Perfect tech company - no bugs, no problems (how many releases of iOS 13 already)?
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.
-
10 minutes ago, msgreenf said:
you call BS on the fact that Kevin has a relationship with Ring and they would share it with him? That has already has access to the API and uses it already....ok....go for it!
Nah I know who Kevin is and what he's involved in. Was hoping to trick him!
-
24 minutes ago, LollerAgent said:
Are these RTSP URL's top-secret or can you share them?
Ditto, I call bullshit on this!
-
11 minutes ago, Cyknight said:
No this was choice by the API author
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).
-
2 hours ago, cg@asu said:
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.
-
-
2 hours ago, Amr said:
Where is this driver?
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:
-
3 minutes ago, jakblak said:
A new version of the 2.10 beta app is out and it has the fix for crashing at startup when using biometrics (TouchID/FaceID). If you've already downloaded TestFlight you'll be notified of the new build, if not, then you can use this following link (it's the same one from my previous post).
This is fantastic! I will load it up shortly and report if I run into problems.
-
3 minutes ago, pinkoos said:
I know, I was actually directing my ask to @jakblak, but I appreciate the explanation
If you've been following the other thread about tvOS 13 and my Apple TVs, you'll see that adding the IRs will not be a simple (or cheap) feat for my current setup, unfortunately
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.
-
39 minutes ago, pinkoos said:
Since we have your ear, any way to get my remote working again with TvOS 13 and OS 2.0/Director 2.9?
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.
Os 3.0 release notes
in General Control4 Discussion
Posted
Control4 does not publicly post release notes.