jackstone

What's the led on the dmx engine looks like? One should be on, dmx should flash quickly and the third should be off

Sometime you have to powercycle le dmx engine to get the firmware to show up at the first time. Also, some time the rs232 port of the core5 does not go to the right baudrate for some reason, you can try the serial port 4 (ir 2) ans reboot both the core5 and the dmx engine. Once it work and start communicating, it never stops.

No it doesn't, the driver is pretty dated and wasn't that popular. Someone else have done a newer driver I think, not sure if it needs the cloud connection or not, or if it'll work with the device you're looking for though...

"Flickering is most likely caused by the decoder that can't handle fast DMX datarate. There is a setting in the DMX Engine that can switch to "Slow" and thus fix the Flickering issue. This setting is already present in the Engine but I will make it easily toglable within C4 in the next version.

There is no limitation to 4-ch with the current DMX Driver, you can use any number of single channel driver to control a device that needs any number of channel. Also the Effect Switch driver have some option to control moving head fixture, it's mostly integrated and meant for doing dynamic effect but it's there. As for your request, I think multiple single channel driver is the way to go.

@evian_domino1 It is available either from Amazon ou Engineering Solution directly, here's some links for US and Canadian dealers: https://www.amazon.com/Engineering-Solutions-Inc-RS-232-Double/dp/B078T16V4X/ref=sr_1_2?dchild=1&keywords=dmx+engine&qid=1610741203&sr=8-2 https://www.amazon.ca/-/fr/RS-232-double-moteur-de-DMX/dp/B078T16V4X/ref=sr_1_1?dchild=1&ie=UTF8&keywords=dmx engine&language=en_CA&qid=1610741249&sr=8-1 And you can get the one with RJ-45 output from Engineering Solutions: http://response-box.com/gear/product/dmx-engine-output-select/ Same price everywhere.

New version now available, now support all Shelly sensors such as the Shelly H&T, Shelly Floor, Shelly Smoke, Shelly Gas and any new sensor that may exist in the future. So it's now the only Shelly driver on the market that support ALL Shelly devices!

A New version of the Shelly AIO driver released. This version was made to fulfill many dealers requests that wanted support for Shelly EM/EM3 and the Shelly Duo. This version 2.1.0 mainly add support the the Shelly EM line using the relay driver. It brings all the available information from the Energy Meter module into Control4 and allow programming on variables. The Shelly Duo bulb is also fully supported through the Dimmer driver. Available at the BlackWire marketplace

I'm pretty sure you'll be fine. Please post back on the forum to let everyone know if it work on 2.10.6. Thanks

I did not tried it on 2.10.6 but I confirm the drivers will load on 2.10.6, so there is good chance it'll work. Try it using the free trial.

Ok I think I figured it out, the binding ID I was using was below 5000 and this prevented the Outlet Light to become Online...

I'm trying to get the newer Outlet Dimmer Light to be Online. I'm not sure what command to send... I've sniffed what C4 sends from the Outlet Module when an Outlet Light connects: it sends C4:SendToProxy(id, "ONLINE_CHANGED", {data = "True"}) Witch differs from the usual Online command C4:SendToProxy(id, "ONLINE_CHANGED", {STATE = "True"}) Either of those commands does not work when sent to a bound Outlet Dimmer Light from my driver... the light stays offline. I tried everything logical to me: C4:SendToProxy(id, "ONLINE_CHANGED", {STATE = "True"}) C4:SendToProxy(id, "ONLINE_CHANGED", {["STATE"] = "True"}) C4:SendToProxy(id, "ONLINE_CHANGED", {STATE = true}) C4:SendToProxy(id, "ONLINE_CHANGED", {data = "True"}) C4:SendToProxy(id, "ONLINE_CHANGED", {["data"] = "True"}) C4:SendToProxy(id, "ONLINE_CHANGED", "True") And nothing seems to be able to make the Outlet Light becomes online.. Someone know what is the right command to send? TIA

This feature is not yet implemented, just as the LABEL and TRACK properties you need to add manually to the xml using a text editor. DriverEditor is clearly due to a major update...

Send me a PM i'll send you the driver

Yes and no. The driver is officially pulled out because it is dated and does not support recent Insteon devices. It is also cumbersome to setup and not user friendly at all. Also we do not plan to release an update due to lack of popularity. That being said, we can still provide the driver on demand, it will tied to a Blackwire account for a small fee and will come with no support. You'll be on your own. You can still try the drive for free an unlimited number of time.

We have just release a new version of the driver, with some nice and often requested features: - New ColorPicker interface that support RGBW / RGB+CCT / White Temperature, all into one interface supported on T3/T4 and Mobile devices. - The ColorPicker wheel is now hosted by an highly reliable repository, no more black screen and spinning wheel. It will work. - The Tunable White dimmer now support CCT as well as Circadian Lighting. The Cicardian lighting option is entirely automated, no need to mess with C4 schedule. - Lot of bug fixes. Here's the new ColorPicker: Circadian Lighting Option:

I think I got it, at least for my case. I only have 8 daily tasks to schedule within the driver, so instead of polling os.time periodically, I just have to get the current time once a day, then start 8 timers each 24h interval, each timer will be set to the number of seconds before triggering based on the actual epoch time. 8 timers should be more efficient than a recurring one plus a loop of IF-THEN to check if an event is set to trigger...

Yeah I understand that part.

I see... so you're pulling os.time only once and then trust your recurring timer to keep track of time?

Thanks Alan, the method I've figured out is to do a recurring timer that read os.time in epoch format, than do some math to see if the current time match a schedule each time the looping timer expire. With some tolerance since the time input comes from an interval and not real time. I'm not really sure if that is close to what you've explained?

This question is aimed at C4 driver developers. I know there is not really mutual help between us but I'm throwing the question anyway... I'm looking for a simple way to schedule stuff within a Lua script, without using C4 scheduling agent and without using the C4 API that only add scheduled event but can't add task to run.. I know there is a way, some of you guys have done it, maybe someone will have the kindness to share how he have done it... Or maybe C4 staff on this forum can help on that? TIA

https://www.blackwiredesigns.com/store/shelly-light-relay-rgbw-aio-driver-suite-for-control4/

New version of the Shelly AIO driver now released. It now support most of the Shelly Inputs devices such as the Shelly i3 and Shelly Button1 as well as the input option on many other Shelly devices. Use this to trigger anything within Control4 using Contact and Keypad bindings. It also add support for instant feedback using Web Triggering, and it's all auto-configured and plug and play! Available at the BlackWire marketplace

That is just a dual white LED strip with one LED for cool and one for Warm, very easy to manage with the actual DMX driver and a multi-channel DMX decoder, the Tunable White driver is what you need and it is readily available. There will be some added features in the next version to manage dual-white and CCT from a Color Wheel UI and more ways.

Other thing to be aware, if you need an RS-232 DMX Engine you can still purchase it through Engineering Solutions webstore or Amazon. Blackwire will not stock RS-232 Engines anymore. Price remain the same. Here's the Amazon links: https://www.amazon.com/RS-232-Double-DMX-Engine-Output/dp/B078YFV7ND/ref=sr_1_2?dchild=1&keywords=rs232+dmx&qid=1603755514&sr=8-2 https://www.amazon.ca/RS-232-Double-DMX-Engine-Output/dp/B078YFV7ND/ref=sr_1_1?dchild=1&keywords=rs232+dmx&qid=1603755545&sr=8-1