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...