alanchow

Glad to hear that its working for you now.
For some reason the Zappiti guys made it the same version number which is why you need to uninstall then re-install.  I asked them to increment it but they told me that the procedure we need to tell owners is to uninstall and re-install.  I did the same method via Zappiti Services which worked for me.

Zappiti have fixed the issue.
Note customer's will need to uninstall Zappiti Video and install it again for it to work.
No changes needed at Control4's end.

The driver is no longer available.  You will not be able to integrate Tuya.

Overview
Ozuno is a premium lighting control systems company, that utilises extensive in-house technology innovation, engineering and development capabilities. They design, develop and produce lighting control and power management products specialising in DALI, Phase DIM, Ethernet, Emergency and 240V. The RAPIX Lighting Control system is a powerful, cost effective means for delivering smart DALI Lighting Control solutions simply and easily. RAPIX Lighting Control scales from very small and simple, to very large and complex.
Control Lighting using DALI, including DALI phase dimmers and DALI relays. 100% DALI Compliant to IEC 62386. Supports DALI Device Type 8 for colour temperature (tunable white) and RGB. Program offsite to save time on site. Designed in Australia by industry veterans. Driver Features
Manufacturer sponsored FREE driver Bi-directional IP based communications / feedback. Ability to automatically import Zones (Light v2 proxy) Scenes (Light switch proxy) Flags (Experience button proxy) Ability to automatically detect capabilities of zones or manually set capabilities. Zone Features On Off Dimming Color Color Temperature Scene Features On Off Flag Features On Off FAQ
How much does this driver cost?
This driver is manufacturer sponsored and is provided free of charge.
Where i can i learn more about RAPIX?
Please visit the Ozuno website for more information about the RAPIX lighting system.
What hardware will this work on?
The driver will work on Control4 OS 3.3.0 or higher and will work with RAPIX Zone Controllers.
We recommend updating RAPIX to the latest version of firmware to ensure compatibility.
Note it will not work with RAPIX eHub hardware due to the API we are using.
What can I use flags for?
Flags are on/off based variables used in RAPIX. This can be manipulated within Control4 to trigger RAPIX programming.
It can also be used with RAPIX triggering Control4 programming. This is useful for when for example you want the flag change (eg button press) to trigger Control4 programming (eg all off macro).
The driver will not connect even though the IP address entered is correct.
The Control4 Director must be on a static IP Address and listed in the Unencrypted Connections list in the RAPIX project. See enabling third party control section of this document.
The capability of the DALI load is incorrect.
The driver will obtain the capabilities of the zone. Unfortunately not all Dali loads can be automatically detected due to non compliance to standards by certain manufacturers. As such if the capabilities are not detected then you can override the capabiltiies in the zone driver’s properties page.
How do I find out more information about the driver?
Please see the links below for more information about the driver.
Driver Link
 
 

Hey all. I've been fighting with this as well and thanks to a helpful pointer from @chopedogg88, I've got it working. I'm going to walk through the steps I took so that others can benefit from my experience.
First of all, here's what I've got:
Bromic Wireless Dimmer Control: spec doc: https://pim.bromic.com/wp-content/uploads/2021/06/Smart-Heat-Electric-Dimmer-Control-Product-Brief-US.pdf user manual: https://pim.bromic.com/wp-content/uploads/2021/06/Dimmer-Controller-Installation-Manual-US.pdf a 7 button remote: http://teamwpd.com/images/servicemanuals/Bromic Controller Remote Manual.pdf A Bromic Smart-Heat Link Home Automation device: https://www.bromic.com/product/smart-heat-link-home-automation-plugin/ The manual for the Smart-Heat Link is... not great. I followed their directions and used DockLight to try to program the remote control to memorize channel 500, then tried to transmit on that channel to the Bromic Controller. However, no matter what I did- this always resulted in an "ID > 2000" error when I tried to transmit on that channel. I believe that this is an issue with the firmware in the Smart-Heat Link. I also tried programming ids less than 201 and that resulted in an "ID < 201" error. So I can program 201 and up, but I can't use it. Or I can use IDs 1-200, but I can't program them. Argh.
I'm outlining the sequence of steps I took below. Don't be dismayed by the length- once you understand it, the whole process takes about 2 minutes. 
Set up and connect the drivesr Install the Teleco TVLINK TVTRX232-916 device driver from their website Install a TVLINK driver. I'm using "TVLINK Generic" because I just want on and off, but you can install whichever one you want. Plug the Smart-Heat Link into your Control4 Controller. I plugged it Serial port 1 using a DB-9 cable. In System Design go to the Properties pane on your TVLINK TVTRX232-916 and set the "Number of physical transmitters" to 1 and hit "Set". Setting the number of physical transmitters creates new connections starting at 201. So if you set it to 1, you get "TRANSMITTER ID 201" in your connections list. Somewhere along the line when I was doing this, I created a TRANSMITTER ID 202 in my list and for some reason my system now thinks that my remote is 202, so for the rest of this example I'll use 202. But you should try using 201 first. Now go to Connections for your TVLINK TVTRX232-916 and Connect its Serial RS-232 Control Input to the right port. In my case that's "EA5->SERIAL 1 (DB-9)" Connect "TRANSMITTER ID 202" to your device, in my case that's "Generic TVLINK Device->TRANSMITTER" Go to the Properties panes of both TVLINK devices and set "Debug Mode" to "Print". This will be helpful for you to see that it's working correctly. In the "Actions" for the TVLINK TVTRX232-916 try doing "Delete all memory" and you should see it say: That means that you've got your serial connection set up correctly (good job) and that the device is working nominally. You'll probably have to set the number of physical transmitters back to 1 (or 2, or whatever) after you do this since that'll get wiped out- but it's a good way to verify that you've completed this part of the process.
Configure the Generic TVLINK Device to be able to transmit Go to your GENERIC TVLINK device Actions panel and click "Memorize channel". Then go back to Properties and click the "OFF CHANNEL" label. It'll get a blue line underneath it letting you know it's ready. Click the "off" button on your physical remote once. You'll see it say something like "memorized" in the "Last update" field. Click the "off" button a second time and it should say "Received Channel 8". Do the same for the On channel. And any other button you want to program. Then go to the LUA tab and you should see this in the debug output when you hit the various buttons: That means that your proxy is attuned to your remote (good!). If you click the button in your app, you should see something like this:
 
That's a good sign too- it means that your button is hooked up correctly.
BUT NOT SO FAST! This is where the Bromic Smart-Heat Link is not working the way I'd expect it to.
If I go to the TVLINK TVTRX232-916 debug Lua panel, when I click the "turn on the heat" button in the app I see this:
 
This means (a) the proxy button sent a request for signal 1 (that's my "high power" setting). It then sent a message to the Bromic Smart-Heat Link saying "54" (transmit) "00 CA" (on channel 202) "00 01" (high power) and "1F" (checksum to make sure that we didn't f' up the command). 

But the system responds with the very frustrating "ID > 2000" error. Which makes no sense to me because... the ID is 201. But, ok.
So alternatively, let's take that data that we just memorized, and tell Control4 to broadcast it on channel 1 instead of channel 202
Go back to your TVLINK TVTRX232-916 Connections tab and switch the connection to "TRANSMITTER ID 001".
Now try tapping the heat button in your app and look at the debug output. You'll see

Alright! Notice that it's sending now on channel "00 01" (and this time I'm sending the power off signal which is "00 08"). The response code is "54" (received transmission) "06" (acknowledged). We are in business! Except that... the heater didn't turn on. Why is that? It's because we need to tell it to listen.
So now we have to program the Controller to listen to channel 1.
This is very straightforward. You're going to follow page 8 of this manual: https://pim.bromic.com/wp-content/uploads/2021/06/Dimmer-Controller-Installation-Manual-US.pdf
Open up your remote control to find the hidden P3 button. Press the button and you'll hear your Controller make a continuous tone.
Press a button on the front of the remote control and your controller will pause, then re-issue the tone.
Press one of the heat buttons on your app (turn it on or off, doesn't matter) and you'll here a beeping tone from the controller.
Now your Bromic Heat Controller is listening to your Control4 app.
 
Share and enjoy!

Given its worked for such a long period of time its likely the issue was caused by a drop out of communications.
Certain control4 user interfaces sends a START_VOL_UP, STOP_VOL_UP and START_VOL_DOWN, STOP_VOL_DOWN proxy command via director to drivers.  If communications is cut and the STOP_VOL_UP / DOWN command is not issued or received by the device (say due to zigbee or wifi issues - attenuation, interference, range, etc) then the driver will keep ramping forever.  Regardless of who the driver is developed by.  This even happens on drivers built via driver wizard / AVGEN in Control4 composer.
This is the architecture of Control4 and has been the case since 2006 / Control4 OS 1.x

Given its worked for such a long period of time its likely the issue was caused by a drop out of communications.
Certain control4 user interfaces sends a START_VOL_UP, STOP_VOL_UP and START_VOL_DOWN, STOP_VOL_DOWN proxy command via director to drivers.  If communications is cut and the STOP_VOL_UP / DOWN command is not issued or received by the device (say due to zigbee or wifi issues - attenuation, interference, range, etc) then the driver will keep ramping forever.  Regardless of who the driver is developed by.  This even happens on drivers built via driver wizard / AVGEN in Control4 composer.
This is the architecture of Control4 and has been the case since 2006 / Control4 OS 1.x

I know this is an old topic but it looks like alot of you guys have trouble with Uniview cameras.  We worked closely with Uniview to create our Uniview driver for Control4 which automates the setup process of cameras along with setup of the driver and all the smart events implemented.  See below
 
 

My favorite is the Chromecast with Google TV.  Supports 4k HDR and is bang for buck if you're after streaming services.
Works great with the following driver.
https://www.chowmainsoft.com/android

The two massive ones are BMR Group and Electronic Living

Very nice, thanks for the driver Alan! Nicely done integrating with Uniview's LightAPI so all the camera functions are available.
I work with a security distribution company in Canada; we are recommending this driver to our clients who install Uniview cameras and control4 systems together. 👍
Edit: You got a shoutout from Uniview themselves - https://global.uniview.com/News/News/202209/952430_169683_0.htm

G'day, 
There is no free driver, however, we sell: https://chowmain.software/drivers/control4-big-ass-fans-haiku
We have drivers available for both the old protocol (haiku app), and the new firmware via Big Ass fans app (strongly recommended to upgrade). It's also OS3.3 compliant so colorwheel support is available. 
If it works in the Big Ass Fans app, it should work on our driver. Almost everything is exposed via variables read/write variables. If there are any variables missing write capabilities which are required, let us know (and we'll add the additional setting support). 

It is not officially supported.
Note all of our drivers come with a 90 day trial so please test before committing to licence purchase.

G'day, I wrote the chowmain shelly driver. Our Shelly driver only uses Cloud for self-healing of IP's, easy auto-setup of devices and other non-critical functionality (a lot of installers don't even install the agent). The modules themselves only use standard WIFI for communications, and we communicate to them using local network.  No RF or mesh. They're as stable as your local LAN. 
There are 2 generations of devices, and the second generation performs even better than the older ones (no need for polling for status feedback, so they're also very CPU efficient)
Any questions, happy to help. 
More info is on: https://chowmain.software/drivers/control4-shelly-generic

By the way, all of our drivers have a 90 day trial too. So, if there are others you wanted to try, you could get them installed at the same time

For reference all lighting drivers irrespective of developer requires to be replaced.  Control4 had to do this as there was no standards for how RGBW lighting worked before hand with multiple lighting proxies being used, some camera proxies and webviews.  As such there was no upgrade path.  Hence why you have to install manually.
Luckily for us Control4 gave all the major developers plenty of time to rewrite all of their drivers which we took advantage of to make sure that all of our licenced drivers were upgraded to support this new OS 3.3 lighting proxy.

Major Update
Version 20220725 - 2022-JUL-25
By popular request, we went back to the drawing board and are proud to introduce our new LIFX V3 drivers. LIFX V3 is our new from-scratch rewritten LIFX driver. Designed for OS 3.3 or later, it now utilises UDP / Local Network Connections for improved performance and reliability, and no longer requires the cloud. Due to the large number of changes required, it is not backwards compatible with our existing drivers, and they will need to be replaced entirely.
Some of the new benefits over V2/V1 includes:
Faster performance. Latency of commands is reduced from seconds to milliseconds More reliable communication with the ability to resend unacknowledged commands Infrared light brightness support via command (compatible hardware required) HEV disinfection support to kill bacteria and sanitise surfaces (compatible hardware required) Modern Diagnostics / Troubleshooting infrastructure Significantly faster deployment. New One-Touch Auto-Setup will install drivers and setup devices. Personal Access Token is no longer required. And many new features Our new driver is composed of 2 parts:
LIFX V3 Agent (Optional)
Provides device management, IP Healing capabilities and troubleshooting Detect and display information on all devices One-Touch Automatic setup of new drivers This new Agent replaces the original Master Driver. Tokens are not required for local control (for many installers, it will be plug and play) LIFX V3 Light
Provides Lighting control Auto-Detection of lighting capabilities, and self-setup of the device This new driver requires OS 3.3 or later. Please note:
Because of the breadth of the LIFX changes, LIFX V3 is not compatible with LIFX V2/V1, and it is strongly recommended to replace all old drivers Due to deficiencies in the LIFX Group LAN/UDP protocol, native LIFX groups are not supported. Advanced Lighting scenes may be used as an alternative (and native C4 scenes are expected to be implemented in the future) We would like to thank everyone who assisted with testing including:
All of our Beta testers Tony Audia TundraSonic Mitch Greenfield Carlos Kam Version 20220609 - 2022-JUN-09
More defence against Code crashes. Bad feedback won't break feedback for all lights (Master) Fix Crash caused when Lights are added after initial setup. Detected by Automated code tests (Master) Version 20220608 - 2022-JUN-08
Fix Voice Scene / Alexa support (Light) - Thanks Trey Nolan / Eldon Version 20220602 - 2022-JUN-02
This is a huge new release with some major new changes
New OS3.3.0 compliant Lighting driver, with Lightwheel support (Light V2). This new driver supports both groups and lights Native Color Support Hue / CCT button links for integration with SnapAV's Keypads or other compatible hardware. -- Thanks Kenton Matthews Add Power On Behavior to adjust default Power on Mode (Light V2) - Thanks Kenton Matthews Improved Ramping System (Light V2) -- Thanks Kenton Matthews Load Groups Lights can now be used in combination with Control4's Dimmer Load Group Driver for control of multiple lights with a single driver. Please note, color control is not supported at this time New Diagnostics System (all) Improved Debugging on all drivers to assist with troubleshooting Self-diagnose issues. Simply use the Display Diagnostics action built into the driver. Or, for additional assistance, use Submit Diagnostics to send a diagnostic report to the Chowmain support team, which you can use in your support ticket. Fix Crash on Feedback for original V1 Lighting Driver (Light) Improve Handling of bad feedback (Light) Fix Turn On / Off Light Action (Light) -- Thanks Mitch Greenfield Allow Poll Rate To be Set for general polling, and post-action polling to improve performance. WARNING, setting these rates too fast may lead to Rate Limits being hit on server (Master) Fix Minor Crash (Master) - Thanks Mitch Greenfield Remove Auto Setup From Group Driver. (Group) Modify Button Link Connections. Add Hue / CCT button links. Fix All Button Links (Light V2) -- Thanks Kenton Matthews

Major Update
Version 20220725 - 2022-JUL-25
By popular request, we went back to the drawing board and are proud to introduce our new LIFX V3 drivers. LIFX V3 is our new from-scratch rewritten LIFX driver. Designed for OS 3.3 or later, it now utilises UDP / Local Network Connections for improved performance and reliability, and no longer requires the cloud. Due to the large number of changes required, it is not backwards compatible with our existing drivers, and they will need to be replaced entirely.
Some of the new benefits over V2/V1 includes:
Faster performance. Latency of commands is reduced from seconds to milliseconds More reliable communication with the ability to resend unacknowledged commands Infrared light brightness support via command (compatible hardware required) HEV disinfection support to kill bacteria and sanitise surfaces (compatible hardware required) Modern Diagnostics / Troubleshooting infrastructure Significantly faster deployment. New One-Touch Auto-Setup will install drivers and setup devices. Personal Access Token is no longer required. And many new features Our new driver is composed of 2 parts:
LIFX V3 Agent (Optional)
Provides device management, IP Healing capabilities and troubleshooting Detect and display information on all devices One-Touch Automatic setup of new drivers This new Agent replaces the original Master Driver. Tokens are not required for local control (for many installers, it will be plug and play) LIFX V3 Light
Provides Lighting control Auto-Detection of lighting capabilities, and self-setup of the device This new driver requires OS 3.3 or later. Please note:
Because of the breadth of the LIFX changes, LIFX V3 is not compatible with LIFX V2/V1, and it is strongly recommended to replace all old drivers Due to deficiencies in the LIFX Group LAN/UDP protocol, native LIFX groups are not supported. Advanced Lighting scenes may be used as an alternative (and native C4 scenes are expected to be implemented in the future) We would like to thank everyone who assisted with testing including:
All of our Beta testers Tony Audia TundraSonic Mitch Greenfield Carlos Kam Version 20220609 - 2022-JUN-09
More defence against Code crashes. Bad feedback won't break feedback for all lights (Master) Fix Crash caused when Lights are added after initial setup. Detected by Automated code tests (Master) Version 20220608 - 2022-JUN-08
Fix Voice Scene / Alexa support (Light) - Thanks Trey Nolan / Eldon Version 20220602 - 2022-JUN-02
This is a huge new release with some major new changes
New OS3.3.0 compliant Lighting driver, with Lightwheel support (Light V2). This new driver supports both groups and lights Native Color Support Hue / CCT button links for integration with SnapAV's Keypads or other compatible hardware. -- Thanks Kenton Matthews Add Power On Behavior to adjust default Power on Mode (Light V2) - Thanks Kenton Matthews Improved Ramping System (Light V2) -- Thanks Kenton Matthews Load Groups Lights can now be used in combination with Control4's Dimmer Load Group Driver for control of multiple lights with a single driver. Please note, color control is not supported at this time New Diagnostics System (all) Improved Debugging on all drivers to assist with troubleshooting Self-diagnose issues. Simply use the Display Diagnostics action built into the driver. Or, for additional assistance, use Submit Diagnostics to send a diagnostic report to the Chowmain support team, which you can use in your support ticket. Fix Crash on Feedback for original V1 Lighting Driver (Light) Improve Handling of bad feedback (Light) Fix Turn On / Off Light Action (Light) -- Thanks Mitch Greenfield Allow Poll Rate To be Set for general polling, and post-action polling to improve performance. WARNING, setting these rates too fast may lead to Rate Limits being hit on server (Master) Fix Minor Crash (Master) - Thanks Mitch Greenfield Remove Auto Setup From Group Driver. (Group) Modify Button Link Connections. Add Hue / CCT button links. Fix All Button Links (Light V2) -- Thanks Kenton Matthews

@alanchow An excellent and significant development. Our congratulations and thanks to you, Justin and the wider team.

MAJOR UPDATE
Chowmain is proud to release a major upgrade to our Hikvision driver for Control4. The driver now supports additional doorstations including the much requested DS-KD8003-IME1 modular doorstation including keypad and card scanner modules.

Supported devices include
DS-KV6113-PE1(B) DS-KV6113-WPE1(B) DS-KV8113-WME1(B) DS-KV8213-WME1(B) DS-KV8413-WME1(B) DS-KD8003-IME1 Doorstation integration to Control4 provides a budget friendly integration for those who want to add bi-directional audio/video communications from Hikvision intercoms to Control4 T3, T4, iOS* and Android* based devices.

On top of calls the driver also provides the ability to control and monitor doors, execute doorbell announcements, send push notifications on button press and motion detection and more.

Looking at providing MDU installations with Control4? The driver is designed to be compatible with Control4 MDU communications server meaning you can now use the KD8003 to call different homes.

On top of doorstation functionality our Hikvision suite of drivers provides integration to Hikvision IP Cameras, NVRs and DVRs.

For more information please see the link below.
https://chowmain.software/drivers/control4-hikvision-ipcameras

MAJOR UPDATE
Chowmain is proud to release a major upgrade to our Hikvision driver for Control4. The driver now supports additional doorstations including the much requested DS-KD8003-IME1 modular doorstation including keypad and card scanner modules.

Supported devices include
DS-KV6113-PE1(B) DS-KV6113-WPE1(B) DS-KV8113-WME1(B) DS-KV8213-WME1(B) DS-KV8413-WME1(B) DS-KD8003-IME1 Doorstation integration to Control4 provides a budget friendly integration for those who want to add bi-directional audio/video communications from Hikvision intercoms to Control4 T3, T4, iOS* and Android* based devices.

On top of calls the driver also provides the ability to control and monitor doors, execute doorbell announcements, send push notifications on button press and motion detection and more.

Looking at providing MDU installations with Control4? The driver is designed to be compatible with Control4 MDU communications server meaning you can now use the KD8003 to call different homes.

On top of doorstation functionality our Hikvision suite of drivers provides integration to Hikvision IP Cameras, NVRs and DVRs.

For more information please see the link below.
https://chowmain.software/drivers/control4-hikvision-ipcameras

Our Big Ass Fans driver now supports i6, ES6 and Haiku (on firmware 3+).
 

Hi everyone,
We have now released the new Big Ass Fans driver for Control4 which supports the new Big Ass Fans API.  Developed from the ground up by our very talented @Andrew luecke this driver supports all IP controlled fans including Haiku (firmware version 3+), ES6 and i6 fans with the following functionality.
Fan Speed Control Preset Speed (On speed when toggled) Whoosh, Fan Direction Light Dimming Light Color Temperature Adjustment. Temperature & Humidity Feedback Occupancy Sensor Support + more Existing Big Ass Fans Haiku Control4 driver customers can install this driver at no additional charge. Note customers must upgrade to the latest version of the firmware for this new driver to operate.
Big thank you to Big Ass Fans for their support on this project.
For more information please see link below.
https://chowmain.software/drivers/control4-big-ass-fans-haiku

Our Big Ass Fans driver now supports i6, ES6 and Haiku (on firmware 3+).
 

Hi everyone,
We have now released the new Big Ass Fans driver for Control4 which supports the new Big Ass Fans API.  Developed from the ground up by our very talented @Andrew luecke this driver supports all IP controlled fans including Haiku (firmware version 3+), ES6 and i6 fans with the following functionality.
Fan Speed Control Preset Speed (On speed when toggled) Whoosh, Fan Direction Light Dimming Light Color Temperature Adjustment. Temperature & Humidity Feedback Occupancy Sensor Support + more Existing Big Ass Fans Haiku Control4 driver customers can install this driver at no additional charge. Note customers must upgrade to the latest version of the firmware for this new driver to operate.
Big thank you to Big Ass Fans for their support on this project.
For more information please see link below.
https://chowmain.software/drivers/control4-big-ass-fans-haiku