mstafford388

It's honestly not worth the trouble of troubleshooting anything running on an HC-500 at this point.  They stopped selling that thing a decade ago.  Just get yourself a newer controller and be done with it.  If you don't want to spring for an EA even a used HC250 would do world better than the 500.  

Oh for sure.  I've lived the beta test nightmare that comes a long with a whole lot of "sorry hun".  That would be a pretty clear reason why you'd need to reboot though.  I just hate rebooting more than the very occasional one off without an explanation.  

Oh for sure.  I've lived the beta test nightmare that comes a long with a whole lot of "sorry hun".  That would be a pretty clear reason why you'd need to reboot though.  I just hate rebooting more than the very occasional one off without an explanation.  

Only exception that I can think of is when you are beta testing a driver... I’ve needed to do a good few reboots over the years when beta testing a driver 🤯

Like others I'm firmly in the camp of if you're needing to reboot the controller running director to fix issues you need to figure out why you have those issues in the first place.  Sure, fluky things happen here and there, although not much at all in a well built system, but if you need to reboot director with any regularity at all you should work with Control4 (through your dealer) to sort out what the root cause of the issue is.  

Like others I'm firmly in the camp of if you're needing to reboot the controller running director to fix issues you need to figure out why you have those issues in the first place.  Sure, fluky things happen here and there, although not much at all in a well built system, but if you need to reboot director with any regularity at all you should work with Control4 (through your dealer) to sort out what the root cause of the issue is.  

sounds like you're talking about the desktop app not composer and hardly anyone uses/used the desktop app so I wouldn't hold your breath on that one.  Also, Savant has focused on Mac users all along and it hasn't gotten them far.  

It would look (crudely) something like this....
Create a boolean variable called "scene active"
 
When motion sensor senses motion 
    If scene active is false -> turn on light
When motion sensor stops sensing motion
    If scene active is false -> turn off light
 
When lighting scene is invoked
   Set variable scene active to true
When lighting scene becomes inactive
   Set variable scene active to false 
 
FYI this falls apart completely if you are activating the same lighting scene with the motion sensors.  
 

You can program keypads to start Tidal playlists right in the Tidal driver itself and chose which room or rooms you want it to play in.  It's very simple. 

Just Add Power and AV Pro would really be the only I'd be comfortable recommending.  You're likely not saving much money if any though (depends how many sources and TVs).  If you don't want to pony up that kind of cash for video distribution, which I totally understand, I'd be more inclined to ditch video distribution all together and go with streaming options vs getting yourself into a cheap video switch that will likely drive you crazy.  

Just Add Power and AV Pro would really be the only I'd be comfortable recommending.  You're likely not saving much money if any though (depends how many sources and TVs).  If you don't want to pony up that kind of cash for video distribution, which I totally understand, I'd be more inclined to ditch video distribution all together and go with streaming options vs getting yourself into a cheap video switch that will likely drive you crazy.  

In the driver for the android box switch it to use on/off macros instead of discreet on/off.  then in the on macro in send some arbitrary command (cancel/menu/whatever), then a delay, then the power on command. 

One cool thing about the Neeo is if you leave the receiver available under the watch menu choosing watch -> receiver will give you the sound modes on the Neeo screen but leave the rest of the remote controlling the source you were on.  At least that's how it works with Anthem and Sony.  Sorry Mitch I know that probably doesn't help your motivation to make a driver 😜

One cool thing about the Neeo is if you leave the receiver available under the watch menu choosing watch -> receiver will give you the sound modes on the Neeo screen but leave the rest of the remote controlling the source you were on.  At least that's how it works with Anthem and Sony.  Sorry Mitch I know that probably doesn't help your motivation to make a driver 😜

There is a filter button in composer I'm sure you hit. It's by the search bar at the top of the system design tree to the right of the recycle looking icon.  Just clear all filters.  You should have no problems finding it based on my crude description of where it is lol. 

Ok that's why your toggle scene is never firing.  I wonder if something isn't report back accurately.  Do your panels all show online, pull the firmware into the driver etc?  In the advanced lighting scene you could start switching individual loads to don't track.  Then if you can get the scene to show active you'll at least be able to figure out where the problem lies.  

Cove Color wasn't tracking, fixed it! As the colors individually are tracking ok not real reason to keep it tracking. Thanks!

You could pull this off with a comm server and some fancy networking.  

That's just a limitation of Sonos integration from Sonos now.  Nothing you can do to be able to browse or search Sonos music services.  It's favorites only.  The sonos amp must have an audio feed from the Control4 controller which lets you see all of the control4 music services which you can browse. 

If he is re-adding the driver from his local database instead of the online database he could still have an outdated driver.  

I'm saying I have been on jobs with those issues.  C4 issues with Ubiquity networks are almost always broadcast/mulitcast traffic being blocked/filtered so things like intercom don't work properly.  Ubiquity has even touted managing (limiting) that traffic as a feature.  IGMP snooping is also a culprit to some C4 issues but I put that issue more on C4 hardware's inability to handle it vs on the network gear using a standard network protocol.  VLANs is a whole different issue misunderstood by most dealers but that wouldn't be an "out of the box" issue.  Again I'm not saying that you can't make a Unifi network work., you absolutely can.  On lots of jobs they will work out of the box.  I just think a lot of the fear mongering comes from dealers that don't understand networking, not from C4.  At the end of the day if you use good network gear and configure it properly you're going to have good results.  

FYI that lag is going to be pretty bad.  Not 15 seconds but very noticeable.  Also, my two cents is if you can use the audio out on the TV vs an HDMI extractor.  Those extractors always seem to be the first things to cause issues in a system like that.  

room control driver allows you to sync sources across rooms easily. 

Did you just resurrect a 5 month old thread just to try to point out something someone said was wrong?  which he's not by the way. 

They should be able to track warranty by MAC address.  Snap actually alerted us of every 700 we had in the field that would fall under their replacement program.