Rexabyte

19 minutes ago, mujtaba.khokhar said:

https://annex4.link/drivers/udp-203

This one is for the 203, but i rekon it could work for the 103 too. 

Worth a shot 

Thanks

Muj

The protocol was the same across TCP and Serial for the 203. It was also just an extension on existing APIs. If the TCP port is open and supported on the bdp the driver should work with TCP commands as well.

The IDs are quite consistent across regions and models, you generally shouldn't have any issues.

On 1/20/2021 at 9:57 AM, ILoveControl said:

Ok so I got the following:

 

I am assuming I use: 

If so when the app updates and say changed to v5 do I have to redo the driver?

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.

On 1/20/2021 at 12:15 PM, cpereira said:

This is an awesome tool! Thanks for sharing!

OT, but, When you have a chance, do you mind updating it to support the UM_NV_SHIELD miniapp type for the new NVidia Shield driver?

 

 

When I have a minute I'll add support for it.

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.

https://mdc.rjboucher.com/

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.

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?

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 Control4 has a library and example here: https://github.com/control4/docs-driverworks/tree/master/sample_drivers/oauth_example although it does appear you need to contact them for an API Key to use it.

AUTHORIZATION = 'C4 API Key for OAuth ', -- provided by C4 on per-application basis

If you need specific help with anything you can PM me directly.

The driver comes with a 21 day trial.

On 3/2/2020 at 10:45 AM, DLite said:

Right. This is exactly my question.

After a bunch of trial and error, I finally noticed that my driver only worked when the “model” matches the pathname. However, Vince’s example driver earlier in the thread works perfectly, even though the model is “hottub” and the path is “experience-button-hottub.” The two do not exactly match, but that driver still works. How come?


Sent from my iPhone using Tapatalk

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>

7 hours ago, ILoveControl said:

Thank you. What its doing now is its giving a zip file in the zip file is the driver.xml, lua file, www folder with the images. No driver file.

For the application id I am specifying the “com.” that Display Apps action button gives me. That correct ?


Sent from my iPhone using Tapatalk Pro

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.

3 hours ago, ILoveControl said:

Just a few questions on the link.

You create the mini driver and download. It downloads a  few files. Do I need to open it in DriverWorks and compile it to a .c4 driver file before I can use it?

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.

9 hours ago, ecschnei said:

I thought annex4 said they could build any mini driver someone wanted

Sent from my SM-G965U using Tapatalk
 

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.

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.

1 hour ago, msgreenf said:

sounds like a bad driver if it works for a minute then stops

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.

@JJ7 I tried to reproduce the issue you're describing but was unable. Both paths you describe run the same underlying function to turn the device on. If you can set 'Debug Mode' to 'Debug' in the properties and then replicate the issue a log will appear in the Lua Output tab that should display what's happening. If you want to PM that to me I can take a further look and see what's up.

Is anyone else experiencing power on issues as described?

2 hours ago, LollerAgent said:

... or just get the Vizio IP driver - which is likely going to be easier and cheaper in the long run.  

They added support for launching apps through the API recently. We'll be tying them into the universal mini drivers.

It might but I doubt it has Wake on LAN capabilities, so while you likely have control you won't have a functional way to power it on besides IR.

That driver from Bitbucket is the one I initially wrote, for anything newer than 2016 you'll want to use the v2 version from here: https://annex4.link/drivers/vieratelevision-v2

Update pushed out with the changes. Direct download here: https://control4drivers.s3.amazonaws.com/2.9.206/oppo_udp203_bluray_annex4.c4z

@turls '6' seems to be working, no error. I'll create a new HDMI connection for you and add it as a command as well.

On 12/9/2019 at 10:29 AM, turls said:

@TheWizard Is there any chance we will get a driver update to include the new input choice for HDMI Bypass, which was included in the latest firmware (which has been out a while)?  This is the same input, but bypasses processing Dolby Vision content.

I can probably program around this limitation if this driver isn't getting more updates, which would be understandable.

I'm not seeing the a command in their uploaded API doc. I do see this referenced in the last firmware update though. It may just be the next number in their sequence of inputs which would be '6'. Making the changes now to check, I'll keep you updated.

2 minutes ago, jfh said:

The first function I want is when a particular MAC connects/disconnects from the network, as real time as possible.  Will/do you have such an event?  (Poor man’s geofencing using “is the phone connected?”

It exists real-time via the 'Wifi Connection' event. You'll need to program a conditional against the 'User' variable with the MAC address you want to monitor for.

• Events
  • annex4 does not poll the Unifi Controller for information, instead it connects via websockets and monitors events in realtime as they happen.
  • Cinegration "The driver 'polls' the Unifi system once a minute.  We've found in testing that the response time of PoE reboots, wifi on/off and online notifications might take up to 2 minutes before seen by Control4."
    • "offline is determined by no communication for at least 3 hours"
  • I'm not sure how many events Cinegration offers in their driver, but I think there's 2 that annex4 doesn't in the entire API.
• Webview
  • annex4 has one that allows a quick overview of your network with an easy and quick method to block, unblock, authorize or unauthorize guests and clients.
  • Cinegration doesn't have a webview
• Commands
  • Restart Devices - Both (I think Cinegration offers this)
  • Restart Ports - Both
  • Authorize/Unauthorize Guest - Annex4
    • Authorize last guest - Annex4
  • Speed Test - Annex4
  • Block/Unblock client - Both
  • Turn on/off Wifi - Cinegration
• Relays
  • Cinegration adds relays for PoE devices to turn on/off ports
• Extras
  • annex4 offers Polly text to speech to UAP's (no extra cost).

All of the above is as of the Beta version everyone has. There's a few more things coming like light control on devices so you can modify the brightness of LED's on AP's and other gear.

EDIT: As far as install goes it's basically the same. The only thing we did extra was make it so the site selection is a drop down to make it a little easier to select the correct site.