SY3

As a mobile dev that works for Snap One (Control4) one of the duties we perform is to look on the forums for issues being reported on the mobile platform. If you would like your issue to be noticed you can help out by creating your title in a manner that helps us identify the post as one that's in need of some help/troubleshooting for the mobile apps. The posts that catch our eye are ones that are in the Troubleshooting and bugs discussion board. I propose you start your title first with the platform you're having an issue with then the feature or component that doesn't seem to be working correctly. 
Example Titles
iOS: Intercom not working on ..... iOS: Camera does not stream when (remote/local) etc Android: Now Playing doesn't..... Another thing we will always ask you when trying to support you is what is your director version and app version. It's helpful if you can already include that in the description of your post along with the steps you follow to cause the issue. Once we see your post we'll reach out to let you know we are creating a ticket and ask you to PM your email so we can work with you directly on the issue. We would also most likely ask for your application logs at this point in the direct communcation.
So recap
Post in Troubleshooting/Bugs Include Platform(iOS/Android/etc) in the title along with feature or component that is the issue Include app and director version in the body as well as the steps your following to produce the issue

The PLAY, PAUSE and STOP buttons on remotes are mapped to keypress/Play on the Roku API.
There are no Pause and Stop commands available in the Roku API, which makes sense, since there is also no STOP button on the Roku Remote, and the play button is combined with the pause button.
You are welcome to look at your Roku remote, and confirm with the Roku API, which is publicly available:
https://developer.roku.com/docs/developer-program/debugging/external-control-api.md
You can also see what is being sent to the RokuTV in the driver's Lua output.  When Play, Pause, or Stop are pressed on the Control4 remote, you should see this:
12/09/21 09:11:31 : ----- > 'http://192.168.29.63:8060/keypress/Play' []
If those keys are not working for you on particular apps, it's likely an issue with the app itself, not with Control4's RokuTV driver.
RyanE

I picked up a TCL 55" Roku TV for our guest bedroom during Black Friday.  Used the free Control4 Roku TV driver.  Works very well.  Only issue I have is with the stop/play/pause function.  I have to use the select button instead.  So not a big issue but wish they worked as expected.  Using Wifi without issues (I would have prefered LAN but couldn't make the run)

Assuming you're getting the Automate Pulse 2.  Found it here https://www.avoutlet.com/window-treatments/shade-components/motorized/remote-controls/rollease-pulse-2-mobile-device-interface/.  I ordered a lot of my shade parts from them and they have been great to work with.

I would highly recommend contacting @msgreenf.  I have a decent dealer but Mitch surpassed their knowledge and accessibility in about 15 minutes.  He has my system working exactly as it should and has helped me add various components multiple times.  He is a rockstar in the C4 area!!
 

Not quite.  I mean, I'm on your side here, but you should try driving a Model S without that center screen.  It's so difficult that may end up as a NHTSA safety recall.  At least you can't crash your TV.
 

Roku

Yup. That’s where I got mine.  
 
Pulse V2 has been a significant improvement over v1.  With the Annex drivers the shades just work.  I’d like to see some minor improvements in the drivers but using the Rollease motors saved me a boatload of money.

Was going to post the same thing.  I use them as well. At their prices for cellular monitoring, it was a no brainer to pay for the service. 
https://smiththompson.com/

The ones from Amazon won't work with Control4.  Not the same Zigbee stack.

I have 2 of the Yale Touchscreen locks and 2 Kwikset locks all on Control4.  The 2 Yale locks are protected due to covered porches - front and back.  1 of the Kwiksets is exposed to the elements in Southern Texas so the heat wears on the finish.  I've seen a Yale lock do the same.
I personally like the Yale locks better since they respond to C4 much faster.  There is a slight delay on the Kwiksets.  

The ones from Amazon won't work with Control4.  Not the same Zigbee stack.

I received confirmation from support that they will be making this version available for the NVR 501 models.  Unfortunately, can't test until then and still need IE or IE extension for Chrome.

These are the instructions I received from someone when I was enabling my box.  Make sure you have the right firmware and set a static IP address or do a DHCP reservation.
VERIFY FIRMWARE VERSION:
1)  To find the Firmware version of your supported STB, use the About page:
  * Go to Settings and scroll down to the About page.
   -or-
  * Using Xfinity Voice control, say "About" into the voice remote.
2)  Look for firmware with 3.2p1 in the tag line.
  
  * Example – for an Arris Xg1v4, you should see this: AX014AN_3.2p1 . . . There will be additional letters/number in the build line, but as long as you see 3.2p1, the STB is ready for IP. As Firmware continues to upgrade, all builds after 3.2p1 will be ready for IP Control. Example - if you see 3.2p3 or 3.3, etc., the STB is ready for IP Control.

SETUP STEPS:
1) Activate IP Control on your STB (this requires the Xfinity Remote and an Ethernet connection to the SB):
  * Press and Hold the Xfinity button for 3 seconds.
  * Press the "DOWN", "DOWN", "3" buttons.
  * This will open the STB Diagnostics Menu (there will be several seconds of lag while it loads).
  * Scroll down to 'Remote Controls' and select.
  * Scroll to IP Control and select.
  * With the Diagnostics IP Control page open:
    - Press and Hold "A" for 5 seconds.
    - Press "4", "7", "7" buttons ("I","P","R").
    - Press and Hold "A" for 5 seconds.
  * A message will tell you that you are activating IP Control and your STB will reboot.
2) After STB reboot, return to the Diagnostics Menu and return to the IP Remote section.  Verify that IP is enabled, and note the IP Remote LAN Address.
3) Setup a static IP Address registration in your router's DHCP menu (beyond the scope of this document).
4) Reboot the STB if necessary to obtain the new IP Address.
5) In ComposerPro's Connections -> Network Tab -> IP Network section, find the Xfinity X1 driver, and enter it's IP Address in the Identify Window.
6) In the Xfinity driver's Actions Tab, press the 'Pair to Xfinity X1' button.  This will pair Control4 with the STB.
7) In ComposerPro's Connections -> Control/AV tab, make appropriate A/V connections from the Xfinity X1 driver to appropriate endpoints.
😎 In ComposerPro, select File -> Refresh Navigators.
The Xfinity X1 STB should be controllable through Control4.
 

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.

If there was a recall, the notice didn’t filter down to me but the replacement was approved without any issue.

I have 2 Card Access WMS10-2 motion sensors that I've using outdoors for the past 4 years without any issues.  Just replace the batteries when needed.  They have survived the extreme Texas summers.  Not sure about sub-zero temps.  

Door stop? Shooting range? Landfill?

Sorry for the late reply.  Just got back from Denver.
The driver was developed for Control4 OS 3.1 but should be compatible with Control4 OS 2.9.0+

Maybe because it isn't as good as it gets? At least for the world of C4
pfSense first and foremost is software, not hardware. The biggest issue is that there's too many variables, too many things that could be set wrong. It's just plain overkill.
Less is more sometimes
 

Thank you for this.  I decided to go with the Araknis 300 for now.  I have several other SnapAV products and with OvrC, made sense. 
It will be interesting to see which router line stays after the merger.  I feel comfortable with the Araknis since its already part of the SnapAV family but we'll see.  
Thank you again for your suggestions.  Appreciate it.

Thank you for this.  I decided to go with the Araknis 300 for now.  I have several other SnapAV products and with OvrC, made sense. 
It will be interesting to see which router line stays after the merger.  I feel comfortable with the Araknis since its already part of the SnapAV family but we'll see.  
Thank you again for your suggestions.  Appreciate it.

USG Or draytek 

We only use Ubiquiti with great success.
Good: ERLite 3 or USG
Better: ER4 or USG Pro 4

Huh? You may want to have a closer look at how it works, because THAT particular statement is just plain incorrect. Pakedge allows setting all APs etc from the router (or online via BakPak, one of the easiest remote connection options), setting VLANs is all done from the router, unless you want to VLAN by port (in which case you set it up in the router, then assign which port on the switch is part of which VLAN via color coding).
Not to mention it's ability to monitor for almost anything Control4, and many other devices as well, and built in tools for Control4 controllers and more.
Pakedge offers an INCREDIBLY powerful tool for C4 systems.
Now, whether or not it's really needed, or worth the price, are completely different discussions.
If money is no concern (which it or course pretty much always is) Pakedge is a no-brainer for a Control4 system.