Jump to content
c4forums | The Control4 Community

DanITman

c4Forums Member
  • Content Count

    54
  • Joined

  • Last visited

About DanITman

  • Rank
    Control4 End User

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Are you really hitting a RAM limit? What does System Resources show? Go into terminal and run the uptime command. This will show you averages on the processor. I would bet your slowness is more related to a driver than the controller itself. When did the slowness start? Take a peek at the logs and see if you can find any errors that are being produced. One memory leak or bad driver can really throw off a controller.
  2. T4 only work with POE so you need to buy a T3 if you don't have ethernet ran to a touch panel location. You can't get T3s either.
  3. Working on testing some new LUA code and I want to ignore SSL cert issues. Any code examples on how to make a GET call and ignore ssl? Thanks
  4. I have almost an identical setup as you. I just upgraded to the UDM Pro as well. Did you backup your config file on your cloud key 2 and then restore it on the UDM Pro? This is the correct method. It worked well for me.
  5. The 4232 is a beast to get working. Once you do get it working its pretty solid. First, look at the address for the 4232 CBM. This is the address in the properties section. Do you have any other touchscreen keypads (Tuxedo) in your system? These are referred to as AUI keypads. The instructions tell you to set an address at 17,18. This is not correct and shouldn't be followed. On a vista 20p there are only 4 address that an AUI keypad can have. Those are 1,2,5,6. If address 1 doesn't work you can try address 2,5,6. Again, it requires some trial an error but eventually will work
  6. They could write an integration without nvidia’s approval. The api is not public and it was also exposed without the driver being encrypted.
  7. Yes, it’s true. I reported it to @RyanE Unless nvidia had other keys already on the shield, it will require a an update to make a new key work. It will also require an update to revoke the existing key.
  8. Revoking it will probably require an update the shield as well. It will probably be a while.
  9. Because Nvidia forgot to encrypt the driver. Their private key was exposed in the driver package. It will be up to Nvidia to decide a path forward now that their key is out in the wild. Will they revoke it and push an update? We will see.
  10. This is very cool and I might pick up a firestick to test it. I was looking at doing something similar with NeTV. https://www.adafruit.com/product/609
  11. I do as well, on my roku the right and left of the four way are the skip buttons. Holding it down goes in FF/Rew. Works great.
  12. This really isn't a SnapAV branded item. You have two options for interfacing with a Honeywell panel. 1.) HSIM module which snapAv gets from here: http://www.alarmdecoder.com/catalog/product_info.php/cPath/1/products_id/31 2.) 4232cbm module. http://security.honeywell.com/product-repository/4232cbm Both have free drivers in Control4. The HSIM module uses a slightly different communication method that can potentially have delays. The 4232cbm is what I recommend as it emulates an AUI kepad and has instant updates. You can find the 4232cbm pretty cheap on ebay.
  13. I run all Unifi gear from Ubiquiti without issue. I think the C4 warning is about their edge products which are older. Sonos, which also runs on a broadcast network functions fine on Unifi gear.
  14. Yes, the Honeywell driver does work with this panel. I would recommend having a dealer re-add the driver for you and download all the zones. There is a bug in this driver that it needs to be re-added tot he project to get new zone information.
×
×
  • Create New...