(My reply via browser didn’t go, so imagine my previous one to be after this resend of the missing one. *grin*) Get a hub. I finally gave up on the ISY and my fanlinc, as I REALLY needed to get my wife a fan solution. The ISY thought it was working the fan, but nothing was right. Comm failures, no power out to the motor, reboot loops with a load on the light output, buttons worked and the ISY saw the state, but couldn’t change it. I was getting V.00 on a query. So I introduced this fanlinc to a hub, giving the address and a name, and letting it figure out the rest. It went through the 10-step comm test quickly, and then wrote something to the fanlinc. I tested it from the IOS app, and the light worked. So... I deleted it from the ISY and re-added it, putting it back into the scenes I had built, and now everything is working fine on the bench. My guess is: There is some initial configuration item that was probably hardcoded in the firmware of the old fanlincs, that is not In the new ones, and nobody at Smarthome knows that, because they always test with a hub, which automatically fixes the issue. They don’t see your problem, and the working RMA’d units we get back clearly spent their last minutes on the bench talking to a hub. So, fresh, out-of-the-box fanlincs are braindead until they bond with a hub. Sent from my iPad using Tapatalk