Hey Don,
Thanks for your continued support -- the plugin has come a long way!
One thing I have noticed and I think may be impacting my Echo and IFTT integration is a side-effect of the plugin. I've noticed when I create a virtual device, it takes on the 'interface value' of 'LutronRA2' and sometimes even takes on the 'Address' of 'LutronRA2--'.
I've been troubleshooting virtual switches not triggering events and I'm starting to think this may be the cause. Or maybe this is simply a cosmetic issue and doesn't matter -- I'm not certain how HS3 uses these values to route control. Do you know if this might have some impact and if so, how I can adjust this setting for devices and stop new ones from inheriting the wrong info? Cheers, Matt
Thanks for your continued support -- the plugin has come a long way!
One thing I have noticed and I think may be impacting my Echo and IFTT integration is a side-effect of the plugin. I've noticed when I create a virtual device, it takes on the 'interface value' of 'LutronRA2' and sometimes even takes on the 'Address' of 'LutronRA2--'.
I've been troubleshooting virtual switches not triggering events and I'm starting to think this may be the cause. Or maybe this is simply a cosmetic issue and doesn't matter -- I'm not certain how HS3 uses these values to route control. Do you know if this might have some impact and if so, how I can adjust this setting for devices and stop new ones from inheriting the wrong info? Cheers, Matt
Comment