Rexabyte

Just to bump this as I don't think we actually announced that the driver is released. The driver supports digest authentication and as such all events, all real-time.
https://annex4.link/drivers/amcrest-ptz-camera

@R_Willis I'd assume it works for that model, but I don't have it on hand to confirm. As with all our drivers there's a 21 day trial so you can verify for yourself before making a purchase.

3 hours ago, timbooo said:

Thanks. Does that mean I need an instance of the mini driver for each TV?

Yes.

6 hours ago, timbooo said:

Sorry if I'm a dumbo but what's the procedure for connecting the mini apps?

Bind the Mini Driver to the "WebOS App #" and "LG WebOS Mini Drivers" connections.

As of today you can now find it on our website: https://annex4.link/drivers/nanoleaf-aurora

Refer to the associated drivers for the webview portion.

Still looking for a couple people to beta test some of the Rhythm functionality, PM me if you're interested and have the Rhythm.

It will not be on drivercentral.

Looking for people that have T3 touchscreens and Nanoleaf Aurora panels to beta test a driver. If interested please PM me.

 

21 hours ago, R_Willis said:

This driver work well?   worth it?

I've been running it since day 1 (as I wrote it) and I haven't had any hiccups with it. The volume ramping can be a little odd at times, as we only send the next request after we receive a confirmation for the previous request and I've noticed the TV is sometimes slow to respond to the HTTP requests for volume. This may have been fixed in recent firmware, it's just something I noticed when I initially wrote the driver. It means sometimes you'll get a small delay when ramping volume. It only occurs with volume which is even more strange, everything else instantly responds. Holding directional inputs for example doesn't experience the same issue.

Pairing is easy and can be done without the original remote. Power on occurs discretely over a HTTP command and doesn't require WOL. It's one of the drivers we never really get support calls for, it just works and the install is simple.

If you have any questions about technical details PM me.

The following would cause 'Hello World!' to be played. As soon as it finishes it would then play the time and date. No requirement to explicitly play the announcement unless you want to replay the previous wav file.

Synthesize commands should definitely be rendering the audio and playing the associated announcement. Make sure that the 'Announcement' property matches the announcement you created as it is case sensitive. By default the property is 'polly'.

The 'Announcement Finished' event occurs when the announcement is finished playing. We included it so you could accurately have something execute after the announcement was finished.

@livitup Hopefully this clears up any issues. If you still have issues feel free to PM me.

1.7.167 is from the old and now obsolete version of the driver. We phased it out and implemented a new proxy to fix some usability issues. Due to the proxy change we couldn't auto-update the driver as it may have caused project issues.

You'll need to get 2.9.195. https://annex4.link/drivers/udp-203?changelog=latest

Properly ID'd shades will return the following: !###D001vD## (Where 001 is the shade ID, you'll get 002, 003, etc.).
Problematic shades will return the following: !###D...vD##; If you see this in the debug log we can't communicate to the shade as it has no ID.

Edit: Got in contact. The hub is only returning the 2 shades mentioned, the other 5 are completely missing.

The App is not a good indicator of control through serial by the Hub. They're completely separate yet we keep seeing the comparison.  The issue occurs when the shades have not been ID'd for serial communication properly.  Shoot us an email and we can see what's up. You'll likely just need to pair the shades that aren't showing up.

There's a new revision that I just released. If auto update is enabled on the driver and you had the LiNK driver it should be updated at this point. Otherwise you'll need to download the latest from our site (2.9.195).

Are you using the latest version of the driver? 2.9.190?

Not abandoned, I'm actually using it locally in my own home, it's just not ready for release or beta yet.

What's done - Unifi Controller:

• Realtime events for the following:
  • Admin Login
  • LAN [Connection\Disconnection]
  • LAN [Guest Connection\Disconnection]
  • WIFI [Connection\Disconnection]
  • WIFI [Guest Connection\Disconnection]
  • Unifi Devices [Connection\Disconnection Adopted\Readopted]
  • Unifi Access Point [Interference]
  • WiFi User Roamed
• Programming commands:
  • Restarting of ports on switches
  • Trigger speed test

What's done - UAP:

• Integrated with our voice genie driver to directly play and upload .ogg files
• Commands to playback any audio files on the device

What's done - Webview

• Tab for displaying all client devices on the network
• Tab for displaying all Unifi devices on the network
• Tab for displaying events
• Tab for general settings information

To come:

• Triggering and display of speed test on Webview
• Programming events for completion of speed test
• Programming variables for speed test results
• More realtime events
• Modal dialog (Webview) for switches to allow restarting of ports, viewing connected devices, etc
• General control of Unifi Devices like the controller
  • Lights, Restart, Upgrade, Block,  Reconnect, etc.

EDIT: The API is pretty open ended, almost anything can be accomplished that the Unifi Controller webpage can do. We'll be sure to see all the features mentioned in the thread implemented as well.

If you run out of memory (depending on how large your project is) drivers won't be added and you'll get that error. Not sure if this is your case but it may be a possibility.

Are you writing drivers for yourself or to create solutions for other dealers? Is your goal to sell the drivers?

Learning Lua won't be an issue, it's an easy move from any language. Gaining the knowledge of the underlying protocols being used to talk between devices (Websockets, HTTP, etc) will be the more difficult part unless you are already familiar. It will also take a bit of time to get used to the Control4 environment from a Driverworks perspective.

Webviews seem to be the cool new thing so it likely won't just be Lua you'd be writing drivers in. It will be other common web languages and markups, HTML, CSS, Javascript, etc.

9 hours ago, South Africa C4 user said:

I don’t think the driver gives you full control, but rather let’s you use the HC200’s inputs and outputs rather than simply brick it. But I may be wrong...

This is correct.

@turls It's the first I've heard of that error in relation to the driver. If you could collect the director log shortly after you replicate the issue and send it to us I can take a further look into the issue. The driver does not use any new API calls from 2.10. It should go as far back as the .c4z file format.

In this menu you only have 'digest' as an option? 'basic' or 'digest/basic' will work.

Select basic, and re-enter the ip or port. It should pull back device information.

I just pushed out an update to the driver that includes the missing documentation. It covers how to program against the events.

https://annex4.link/drivers/hikvision-camera?changelog=latest

On 3/16/2018 at 4:34 PM, enzeder said:

There is a connection for DLNA video, and the first post says DLNA support is coming.

Is this working (and if so how would it be set-up), and if not is there an ETA?

I assume by DLNA we will be able play files direct rather than go manually through the network menu as I do at the moment?

 

 

No ETA at the moment, but there are some things in the works. I'll provide more information when things get closer to release.

Get your dealer to send us an email with some debug logs and we'll take a look into the issue. They'll need to set the 'Debug Mode' property to 'Debug' and then issue the on/off requests.