Jump to content

dw886

c4Forums Member
  • Content Count

    60
  • Joined

  • Last visited

About dw886

  • Rank
    Control4 End User

Recent Profile Visitors

229 profile views
  1. dw886

    C4 driver for nVidia Shield

    One other thing that I've noted, is that I keep getting this in the Lua Output on the IRUSB driver: [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) [string "Lua Code"]:747: attempt to compare number with nil (ReceivedFromNetwork) It happens over and over. I have my Shield on a Matrix, and after selecting a source that would change my video matrix to the Shield, I can see that my matrix then keeps going back to the shield indefinitely (like it's stuck in a loop). I can manually change it to Input 1, and after a few seconds, it'll go back to Input 5 where my Shield is...
  2. dw886

    C4 driver for nVidia Shield

    One more that doesn't work: Disney. I have both the Disney Channel and Disney Junior universal mini drivers installed, and connected both of them to my shield (even though the only Android TV App is for Disney Channel, which I have installed). Neither works when connected to the shield in composer. Also, just in case this is useful for anyone else, here's the QLAUNCH commands for some of what I'd consider the more common apps in the US: HBOGo: QLAUNCH android-app://com.hbo.go#Intent;component=com.hbo.go/.LaunchActivity;end Movies Anywhere: QLAUNCH android-app://com.moviesanywhere.goo#Intent;component=com.moviesanywhere.goo/com.disney.brooklyn.tv.ui.signin.TVSignInActivity;end NFL: QLAUNCH android-app://com.gotv.nflgamecenter.us.lite#Intent;component=com.gotv.nflgamecenter.us.lite/tv.youi.viper.ViperBootActivity;end NFL Sunday Ticket: QLAUNCH android-app://com.directv.sundayticket#Intent;component=com.directv.sundayticket/.view.ui.activity.SplashActivity;end VUDU: QLAUNCH android-app://air.com.vudu.air.DownloaderTablet#Intent;component=air.com.vudu.air.DownloaderTablet/.TvMainActivity;end
  3. dw886

    C4 driver for nVidia Shield

    I ran these and that seems like it did the trick - thanks! Is there supposed to be any confirmation after running the command? On this thread, it almost looks like it's possible to add custom qlaunch URLs to the driver via the LUA: Is it possible to add new links into the driver by doing something like this, so that I can simply wire up the Universal MiniDrivers for the apps that aren't in the IRUSB driver? urltablegp["MoviesAnywhere"]="QLAUNCH android-app://com.moviesanywhere.goo#Intent;component=com.moviesanywhere.goo/com.disney.brooklyn.tv.ui.main.TVMainActivity;end\r";
  4. dw886

    C4 driver for nVidia Shield

    I can't get the WatchESPN Universal Mini-driver to launch the app. All of the other supported Universal Mini Drivers (Disney, Netflix, Plex, Amazon Prime Video, etc) seem to work. What's the best way to approach troubleshooting why the WatchESPN app won't launch? Connections are present, and the app is installed on the Shield. Hitting the WatchESPN app changes the source to the nVidia Shield, the only thing is that the app doesn't launch.
  5. dw886

    Weather Underground update

    Well, that doesn't sound as smooth as I had hoped. If they change the API, I'm guessing there are going to have to be driver updates to at a minimum point to a new web service endpoint. I'd assume that if changes are required, this will pretty much kill any 3rd party use of the WU API, because no one is going to want to invest the time to do this with a very limited amount of potential users...for this driver, or anything else that uses WU. I have a Davis PWS - wondering if I should be doing this differently, or if there's a better location to pull my data from...
  6. dw886

    C4 driver for nVidia Shield

    Awesome! Thank you for doing this - I can't wait to give this a try! Three follow-up questions as I have a few universal mini-drivers that aren't in the zip file that I use (Plex, HBO Go, NFL Sunday Ticket, Movies Anywhere, NFL, and VUDU): Are there plans to add support for these in the future, or is the current coverage as far as you're going? If there are no plans to add more, is there a way for me to manually add them, or should I just use the older mini-drivers instead? For Universal Mini Drivers that aren't supported, will they just fail to work, or is it that they're just untested?
  7. This is really hard to troubleshoot without more information, but from what I can read on this thread, you have a control4 setup that was working on an unknown IP Range / Subnet. The infrastructure was replaced, and now its on another unknown IP Range / Subnet. You're connecting to this via the Android app, and either trying the local connection option or using 4sight. If your network changed IP Ranges, and your controller had a static (permanently assigned) IP address from your old network, when you connect to the new network with a device that doesn't have a static ip, it's going to get automatically assigned an ip via DHCP in the new IP Range. Unless you've made a number of manual Subnet changes, your devices on the new network can't communicate with your controller that was configure for the old network. You'd need to put a computer/phone manually on the same IP Range as your old network, and your (assumingly) controller. Then change the network settings on the controller to be in the IP range of the new network, or simply change it to DHCP so it gets an ip address automatically on the new network. Once you have the controller on the new network, then move the device back, and you should be able to connect. Many assumptions here, because I don't know the network topology if your old or new networks. I don't even know if the controller is hard-wired or if it's on wifi... I would assume the former, but not everyone pushes physical cables...
  8. I was simply wondering what others were doing. I didn't want to cut a non-standard box into the wall (like the ds2 mini back box) because who knows what the future brings. With my siding I couldn't cleanly flush mount, so I didn't want a proprietary hole when I'm surface mounting. I also knew I'd need a hole to fish wires, and I wanted to have a decent seal. Cutting in a standard single gang box gave me the hole, a place to spool wire, and it was completely concealed when I surface mounted the ds2 mini. I ended up using a flush mount plate because the surface mounted ds2 was barely taller than the siding, and concealed the siding cuts.
  9. Not sure if you still have the normal doorbell chime in your home, but if you do, you can connect the old doorbell wire to the relay on the DS2. Then when someone presses the button on the DS2, the relay on the DS2 momentarily closes, simulating a traditional doorbell press. You can do this in addition to the other things, like playing sounds at the touchscreens, announcing over multi-room audio, etc.
  10. I never got a response on this, but wanted to follow-up in case this helps someone else, as I clearly missed this in the documentation. To be clear, I wanted to setup buttons like the "Deliveries" and "Turn on Light" as shown below: In order to do this, the custom buttons on the DS2 Intercom properties must be enabled, and have a name. Once this is done, it opens up the programming options within composer for when these buttons are pressed.
  11. dw886

    DS2 Height

    Adding some feedback on what I've observed now that I've had my DS2 mounted for a while: I ended up putting mine where my existing doorbell was. The height really hasn't been much of an issue, but what I'm finding is that my security cameras that cover the same area actually do a much better job than the integrated camera on the DS2. My other cameras have a higher angle, and are looking from the side towards the door (vs looking out at the yard from the door). The DS2 is right next to the door, and facing outward. We have a covered entry to our house, so what ends up happening is that the background is always much brighter than under the covered entry. The DS2 basically gives me an over-exposed shot of the person at the door, so they're a black shadow. My overhead cameras look fine...
  12. I never got a reply on this, but I went forward with putting a single gang box behind the DS2. It helped me to have enough space to deal with the extra cat6 cable, and the cable for the doorbell chime which is run to the DS2 relay. The mini will cover a single gang box nicely...
  13. Using Android, and I've still been getting IA calls when someone rings the doorbell on the DS2 Mini. I can't speak for iOS...
  14. I was having HDCP issues with an nVidia shield and a KD 8x8 matrix, and swapping out the HDMI cable to one capable of HDCP 2.2 resolved it. I was going through many of the same steps that you are trying - my cables / devices worked when I went directly to from my Shield to my Denon receiver or to a TV directly, but when I had the matrix in the middle I'd get nothing. I was messing with EDID settings on the matrix thinking that it was an EDID thing. It ultimately ended up being an HDCP issue with the cable (I could log into my matrix and see an HDCP fail message on that input - that's how I isolated it).
  15. dw886

    C4 driver for nVidia Shield

    Awesome! I'll wait for this rather than using the IRUSB Mini Drivers from your site and changing the URLs. Great news!
×