c4toys

Lol

Sent from my SM-S916U using Tapatalk

others have posted in different groups that a factory restore of the roku fixes the issue.

Not everyone had issues with the NEEO's. I'd actually be interested in seeing how many issues on those were actually chipset related at all to be honest (in many cases I saw, the problems had nothing to do with the NEEO itself).
You're saying you had issues with the NEEO's, and now you're saying you're having issues with Halo's?
You also are saying you have a faulty CA10 Ethernet port (and from my understanding, both ports work independently?
It could be worth checking your network to be honest

It could be a few things. 
 
no1 if the box is controlled via IR the flasher may have fallen off or stopped working. You can test this by putting the box on and standing in front of it and pushing buttons from Control4 to see if the IR bud flashes. 
 
no2 if the box is connected via IP the boxes IP address may have changed and needs to be re entered into composer
youll need a dealer to do the IP change.
PM me if you’d like me to assist you in diagnosing further. 
 
Thanks 
Muj 

There is though. CPU is the same, but RAM amount is not, and if memory serves, much like EA, the Core1 doesn't have a separate audio card, and the Core5 has two offloading all audio handling from the CPU.
That said a system that ran fine on an HC800 should run fine on a Core3 all else equal.

I wrote a sun positioning driver that I need help testing.
Driver allows you to trigger events in Control4 based on the suns location.  This is great for shades and allows you to mimic control like Lutron's Natural Light Optimization. Driver calculates the sun position based on your project location and timezone.  This driver does not require an outside API and all calculations are done on the driver itself.
Below are the variables that you can use for conditionals.  Driver fires an event on every calculation of the sun position.

Sun Interval: How often the sun position should be calculated. 
Azimuth: Direction of the sun as compass coordinates.
Altitude: Angle of the sun in degrees.  (Positive - Sun is above horizon | Negative - Sun is below horizon)
Season: Current Season based on Location
Trending: If the Sun is going UP or DOWN
Last Event: Day, Night, Civil Twilight, Nautical Twilight, Astronomical Twilight, Solar Noon, Solar Midnight
If interested in testing, please DM me your email and I'll send you a beta trial. 
Thanks

C4 doesnt play well with Zone 2.
A work around is to treat zone 2 as another receiver and learn your Z2 codes into the second driver. you would also create another room for that receivers end points

Put an ir emitter on it and add a rx-v6xx ir driver, copy/learn z2 ir codes as the main codes for the new driver, connect your end point to room "Patio", add "Patio" to announcement, done!
thats your best bet, you have just had free advice from some of the best C4 guys around, myself not included in that statement!

ZigBee ISNT updated, it's in the process, and even once updated, that won't mean any and all devices will just become 'magically' compatible. If anything, the move is to the udated zigbee protocol, and likely (if any) only devices that might be able to connect using a more 'open' zigbee would be those that compy with those new protocols - existing nyce HA zigbee devices wouldn't.
 
Note that I have no specific/special knowledge or insight of where C4 is going with their ZigBee, but I wouldn't advise anyone to hold there breath thinking all zigbee devices will become directly integrated into C4. Nor am I claiming/stating they won't (eventually) get to that point. If AND when that happens is pure speculation at this point based on what I've seen.

Then you're having mostly set up right. Look at the driver properties for the TiVo. There's a channel entry method. Change it to the other one

you want to think everyone is honest, I do but I pass on most online sellers because of seeing these type post. Hopefully the items are in the mail and seller is on vacation. wishful thinking!!

Anthem used another developer in the past for their MRX drivers and they had problems with the driver they developed.  As such they approached us about developing a solid driver which we did and released a few months back.  Has had extensive testing by ourselves, Anthem and a bucketload of dealers.
An additional feature we added in that wasn't speced in the scope was that the driver automatically turns on the system when Playfi is detected.  Pretty neat.

I've created a new Control4 app for Windows PCs. It's intended to be run on a dedicated in-wall touch screen in Windows kiosk mode, but it can also be run as a normal app on any computer. It's intended to fill a similar role as the Control4 touch screens, but more responsive and better looking.
The app requires no drivers, no login, and no configuration. Simply run the app and it will locate your Control4 controller and connect to it automatically. It will use the same configuration as any other Control4 navigator. The app supports all your Control4 devices.
The app also adds new functionality. For example, if you have any Sonos devices, it provides a user interface to search Apple Music or Spotify and add songs to your queue. It also will display a QR code that allows your guests to add songs using their phones, even if they aren't on the same network.
If you would like to help beta-test the new app, please fill out this short form here: https://forms.gle/bXgGaujECV5Kiag97
Thanks!
 

I get the same message on my.control4.com. With c4 changing the website (merging dealers to snap site) they must have broke something.

I get the same message on my.control4.com. With c4 changing the website (merging dealers to snap site) they must have broke something.

Great.
I guess that means I’m going to license yet another Chowmain driver.  
 
At some point I may have to refer to it as my Chowmain system instead of my Control4 system …

Are you sure you can’t get what you need from one of the remote dealers on this forum?

Variable loopit, number
Variable maxruns, number
Timer Wave
Wave Timer starts
If loopit = 0
—cancel timer
—stop
If loopit = 1 scene1
If loopit = 2 scene2
etc
Timer expires
Maxruns +1
If maxruns =y
—stop
Loopit +1
If loopit =x set loopit =1 (x is 1 more than total scenes needed so restarts wave sequence)
Restart timer
Button
If loopit >0
—set loopit = 0
—cancel wave timer
—scene lights default
—stop
Set loopit = 1
Start wave timer
When project loads (extra caution)
Set loopit =0

Please try this version and let me know it is resolves the issue with lighting.  I don't have a way to test lighting.
 
npcloud.c4z

The new driver solved the lighting problem. Thank you!

I wouldnt use any system that locks me into a camera brand so Unifi would be out.
In my home I have cameras from Vivotek, Dahua, Panasonic and Amcrest.  They all fit different needs for price/size/color/FOV and other misc features.  That is why I never suggest going to Costco and buying 8 identical cameras + an NVR or looking at Unifi that locks you in.
As someone asked above, I am not 100% sure, but I believe Synology will work with any ONVIF camera.
For me, Blue Iris + 1,000's of ONVIF compatible cameras + a free (or for more features paid) C4 driver available.  

FYI, I had to create a variable to ensure ALL doors were closed before triggering the LED's to change back to their standard color otherwise I ran into the same problem from my original post.

Built my house with a closet in mind, but it lacked circulation and the components were running hot, especially with a dense rack. Threw this together with online parts (the main ones being a Cloudline T6 and a Tripp Lite exhaust duct) -- works great and is good for a ~20dg temp. drop (not shown, FYI) while reducing net noise due to fan speed. Sharing for inspiration/if helpful.

 

Control4 has a current bug (reference LIGHT-3612) with shade programming effecting all shade drivers. You cannot use Open or Close.  Toggle / Stop commands are not affected
To get around this issue please utilise Open Target Level or Close Target Level.

No you're not using a schedule to set the blinds - you're using the action of 'when blinds are opened' to then CHECK the schedule if the time is xx/yy to set them to 50%
Your thinking is backwards of what it needs to be.
I assume that what you WANT to happen is:
During a specific time of the day, IF the blinds are fully open, set them to 50% instead.
 
Programming wise you would create a schedule event at time xx.

 
WHEN {that scheduled event happens} IF the blind is fully open set blind to 50% {note the indent here, if the set blinds isn't looking like that, the IF statement isn;t working}  
You could still have the programming you did as well, which would force the blinds back to 50% if someone were to open them (if that is what you want) but you'll want to add a delay at the front (a second should be fine here) to ensure you're not sending too many commands to the blind/blind bridge to register. Aslo, again, ensure the 'set blinds' is properly indented under the if statement