RyanE

MOSFET failure is most likely the error you were seeing. MOSFETs are the switching transistor in the dimmer. https://en.wikipedia.org/wiki/MOSFET When they fail, occasionally, they'll fail shorted, and your light will be on 100% from that point on. It's likely a coincidence, but it's also possible the Flash memory in your dimmer had an issue, and the MOSFET Failure is a side effect of a failure of the dimmer to be able to flash new firmware onto the dimmer. MOSFET failures are pretty rare, but of course, not impossible. Sometimes a load (or less likely, the wiring) {will short and cause it as well. RyanE

The full info on what fields are defined as is in the DriverWorks XML documentation: https://snap-one.github.io/docs-driverworks-xml/ There is no code generator for it (Driver Editor is no longer supported, and didn't work all that well), usually the quickest way to get started is to copy the XML of an existing driver of the same proxy. Creating a new driver.xml from scratch is admittedly quite painful. Capabilities are dependent on what proxy (or proxies) a driver is implementing. Bindings (Connections) are pretty straightforward, and defined in the 'Connections XML' section of the DriverWorks XML docs, linked above. Building a driver, the recommended way is to use Driver Packager (best currently and future supported driver packager is 'dp3'). It's also available in Control4's public repo: https://github.com/snap-one/drivers-driverpackager Driver Packager is pretty well documented, and is the only supported way to build drivers. That said, some people roll their own, because honestly, making a .c4z is not that difficult, if you get your XML and Lua code working. It's just a .zip file. All the complexity is that you can include other files, you can squish and/or encrypt your Lua code, etc. There are a handful of us on here who answer driver development questions, but typically, you really have to dig in yourself. RyanE

Control4 doesn't typically write drivers for devices where it's the thing being controlled. Device drivers in Control4 typically control the devices, and get feedback as to status. They're usually a direct connection (RS232/485 or IP connection), and not a listening socket to get status updates from a device. The same functionality on the Control4 side to update the proxy's status works whether the device is controlled traditionally or if the device is listening for updates from a 3rd party device. I don't do consulting on driver development, but the documentation is available to do what you're wanting, but there's no "cookie cutter" way of accomplishing what you want. RyanE

To update a proxy, you send a proxy notify. The values you send can be found in the appropriate DriverWorks documentation: https://snap-one.github.io/docs-driverworks-proxyprotocol-lightv2/#license-copyright-and-trademark In this case, since you are using a light_v2 proxy at proxy binding ID 5002, you would make the following Lua calls: C4:SendToProxy(5002, "LIGHT_LEVEL", { LEVEL = 0 }) -- OFF C4:SendToProxy(5002, "LIGHT_LEVEL", { LEVEL = 100 }) -- ON RyanE

There are likely exactly 0 navigator / app devs on this forum, just FYI... Glad to hear it's fast for you, though... :P

I have not heard of "a lot of" drivers needing to be reworked to work at all in X4. There have not been a lot of changes in Director that apply to driver functionality, unless they used deprecated functions, which driver devs have been warned not to use for literally years. None of the many drivers I've developed and released have needed updates. I can't think of a single one. RyanE

And their order can be changed in the 'Home Screen' agent. RyanE

It's almost like Control4 wants their dealers to have materials they can use to help explain the X4 changes to their customers, the public... :) RyanE

I've never used the UIButton JS API, which is what it appears you're trying to use. It's possible the web browser on the Android App doesn't expose the functionality required to support the UIButton JS API. What Android devices are you trying it on? Phones? Control4 Touchpanels? RyanE

Don't post multiple times. RyanE

What OnDataToUi function are you talking about? Apps don't expose internal datatoui functionality to end users. RyanE

I think you're confusing Control4 Device Variables (that you create with AddVariable) with driver variables. For example, your 'TimeNumber' is not the name of a Lua variable, so if you're setting a property to that value, it won't work, since there's no Lua variable with a value in it. For simplicity, I'm going to assume your tally isn't persisted across director restarts... You should create a Lua global variable, and use that to increment the tally for the number of times the timestamp has been saved, and use that variable to set the TimeNumber Control4 Device Variable, and also as the value in the UpdateProperty. So somewhere above your ExecuteCommand, add the line: gNumberOfTimestamps = 0 Then, in your 'Save Timestamp' code, add: gNumberOfTimestamps = gNumberOfTimestamps + 1 C4:SetVariable("TimeNumber", gNumberOfTimestamps) C4:UpdateProperty("LastNumber", gNumberOfTimestamps) I don't know why you have an "Update Property" command. It seems to me that you would always want to update the variables and properties every time a new timestamp is saved. You may wan to add a 'Clear Count' command, so you could reset the global gNumberOfTimestamps back to 0. Hope that's helpful. RyanE

Buy and mount a 12V AC Coil relay somewhere near the IO Extender, wire AC input to the relay's coil, wire 12v DC from controller to the relay 'C' (common) connection, wire the relay NO (normally open) connection to the IO Extender input. Easy Peasy. RyanE

And why is someone asking this on a thread that's months old? Things only break when the boss is out of town... :P RyanE