Hi @bfisch,
I didn’t forget about your question!
That parameter (or any of the parameters) is set when to tap on the Configure tile in the device type. If you look at my device type as a reference, you can see this bit of code:
def configure() {
log.debug "Configuring...." //setting up to monitor power alarm and actuator duration
delayBetween([
zwave.associationV1.associationSet(groupingIdentifier:3, nodeId:[zwaveHubNodeId]).format(),
zwave.configurationV1.configurationSet(configurationValue: [25], parameterNumber: 11, size: 1).format(),
zwave.configurationV1.configurationGet(parameterNumber: 11).format()
])
}
You can see a few things going on, but the one you’re interested in is where a configuration value is set. While my code is setting parameter 11, you should change that to 3 and the value in brackets from 25 to 1. You really only need that second zwave.configurationV1 line.
Here’s where that technical info comes from that Steve from FortrezZ references:
http://fortrezz.com/index.php/component/jdownloads/send/3-brochures/16-mimolight-technical-appendix
I haven’t done anything like what you’re doing, but you could put together a device handler that does the basics like knowing the relay state, but more importantly - the configuration of parameter 3 that you need.
I do have a question about your overall goal with the booster fan and a potential SmartApp solution. Is the booster fan something similar to Suncourt’s? If so, you could use a zwave/zigbee outlet or appliance module, a zwave thermostat with a “tweaked” device handler, and a SmartApp to do the same thing. I’m doing something very similar with a portable humidifier. In my scenario, whenever I see a power draw from the outlet where the humidifier is plugged in, the HVAC’s fan is turned on.