Jump to content
c4forums | The Control4 Community

Rexabyte

c4Forums Member
  • Content Count

    210
  • Joined

  • Last visited

  • Days Won

    7

Rexabyte last won the day on August 5 2018

Rexabyte had the most liked content!

1 Follower

About Rexabyte

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2,542 profile views
  1. The IDs are quite consistent across regions and models, you generally shouldn't have any issues.
  2. If they update the application ID you would need to update the mini driver as well. It's been v4 since I created the WebOS driver a few years ago though. For both the base youtube mini driver as well as the kids one. I've been thinking about changing the functionality to work against app names as a fall back as the TV Guide application ID actually changed in WebOS 4.X.
  3. When I have a minute I'll add support for it.
  4. You can find the application ID by launching the application on the TV and looking at the Application ID property in the driver. It will always display the foreground application ID. You can also print out a list of all installed apps and their IDs by hitting the "Display Applications" action and looking at the Lua output window. I would recommend leaving Debug Mode set to Off.
  5. The C4:urlGet command would be sufficient. It also has a callback function containing the body of the response. Should be extremely easy to parse, if there's a need to parse at all. Throw it in a repeating timer and you're basically done.
  6. Good to know. Looking at the library it looks a little bit like how you would poll for a device_code grant with Control4 bridging the OAuth2 gap for you. Has anyone implemented anything with it yet?
  7. Documentation can be found online here: https://github.com/control4/docs-driverworks I would skip DriverEditor entirely and just use something like VS Code. As long as you format the files and build the manifest file for the project to spec you can just build it with the command line using DriverPackager.exe (comes with DriverEditor). Information about the manifest file can be found here: https://control4.github.io/docs-driverworks-fundamentals/#what-is-a-c4zproj-file Most of the C4:urlXXX commands should do what you need if the protocol for the API is HTTP. As for things like OAuth C
  8. The driver comes with a 21 day trial.
  9. It's based on the filename as far as I'm aware, not the model. For example if my driver filename was um_netflix.c4z the path should be: <Icon height="300" width="300">controller://driver/um_netflix/...</Icon>
  10. Yes, you can also launch the application on the TV and then look at the Application ID property in the driver. It should always tell you the ID of the active foreground application. I've reproduced the '.zip' issue on my android device, it's not happening with my desktop (windows). But msgreenf is right the file is just a zip, cut out all the extensions at the end (my android device is showing '<name>.c4z.zip') and just make the extension .c4z and you should be good.
  11. Clicking download should give you a single .c4z file which is the mini driver. Changing the source field will change which driver the mini driver will work for. The WebOS option will build a driver for the annex4 LG WebOS driver. Viera will do the annex4 Panasonic Viera driver and universal will build a universal mini driver. You can upload existing universal mini drivers to add or change application ID values as well.
  12. You can now modify or build your own universal mini drivers here: https://mdc.rjboucher.com There's a few 'source' options for things like the annex4 LG and Panasonic driver, but as of the latest push it will do universal mini drivers as well. There's also a field for entering Vizio Application ID's for the universal mini drivers as support for mini drivers will be available with the annex4 Vizio driver soon.
  13. The power portion of the SmartGlass protocol does not require any encryption. It's actually quite simple and there's a github repository in Python that will let you power on the Xbox. The funny part is the off command is encrypted, so you can only easily power it on, not off. All that being said there is documentation on SmartGlass but last I looked it would be a serious amount of work to implement into Control4.
  14. Likely this, there's likely a driver doing something on initialization or shortly after that's causing problems. Director log should show a sigkill event, you may want to see if there are any logs related to drivers before it. Deleting the driver from /mnt/internal/c4z (both the .c4z and unpacked folder) should allow director to start properly once the problematic driver is gone.
×
×
  • Create New...