cannot set lights to dim

[drmcp]

i cannot go into the status graphics and set the control use for dim to dim and it stay after clicking done at the bottom, i go back in to the setting and it is back to "not specified" so thus if i give Alexa a command to dim office light to 50% she responds with that command doesn't work on office light.

[vasrc]

I believe I have the same/related problem.

Has anyone found the secret sauce to make a VIRTUAL device look like it's dimmable to Echo? Clicking "Is dimmable" doesn't work. I've also experimented with several different Types and subtypes, but that doesn't work either.

Thanks
Z

[wkomorow]

I believe I have the same/related problem.

Has anyone found the secret sauce to make a virtual device look like it's dimmable to Echo? Clicking "Is dimmable" doesn't work. I've also experimented with several different Types and subtypes, but that doesn't work either.

Thanks
Z

I have a fibaro light and it dims fine (real not virtual device). The only differences I see is that the range is 1-98 with no offset.

[drmcp]

the real issue is when i change the "control use" from Not Specified to Dim and click Done, and go back in and "control use" has defaulted back to Not Specified and thus Alexa does not see it dim as an function for that device.

I have a fibaro light and it dims fine (real not virtual device). The only differences I see is that the range is 1-98 with no offset.

[ATTACH]52713[/ATTACH]

[wkomorow]

I really do not know but should your dim values be less than on and more than off?

[will.i.am]

the real issue is when i change the "control use" from Not Specified to Dim and click Done, and go back in and "control use" has defaulted back to Not Specified and thus Alexa does not see it dim as an function for that device.

This happens to me as well, but with the thermostat heat and cool points. I set them and then go back in to the Status Graphics page and they are set to 'Not Specified' again.

[drmcp]

It must not matter that it don't completely work

I have a fibaro light and it dims fine (real not virtual device). The only differences I see is that the range is 1-98 with no offset.

[ATTACH]52713[/ATTACH]

This happens to me as well, but with the thermostat heat and cool points. I set them and then go back in to the Status Graphics page and they are set to 'Not Specified' again.

[Daweeze]

the real issue is when i change the "control use" from Not Specified to Dim and click Done, and go back in and "control use" has defaulted back to Not Specified and thus Alexa does not see it dim as an function for that device.

The ability to keep/modify the control use can depend on your plug-in that the device belongs to. Yours looks similar to my screen since I believe you are also a HAI Plug-In User. The PI developer (Rob Mason) is working on a version that resolves this issue with "Control Use" issue. HS3 Beta 3.0.0.255 released today was required in order to implement the fix for those of us that are HS3 HAI users. I suspect if other users have devices with the same issue, the issue is related to the Plug-In the Owns/Created the Device and is not specifically an HS3 issue. For instance, my buddy uses the Spud UPB Plug-In and can Dim just fine and does not have the issue.

-Travis

[vasrc]

the real issue is when i change the "control use" from Not Specified to Dim and click Done, and go back in and "control use" has defaulted back to Not Specified and thus Alexa does not see it dim as an function for that device.

Is this a virtual device (ie one you created manually?) or is it owned by a Plugin as mentioned previously?
If virtual, I was able to fix it by writing a short script that sets ControlUse to Dim for that Status pair. Not sure why it won't work from the GUI page.

Z

[Pete]

Relating to Rob's current version of the HAI OmniPro plugin relating to UPB it does work a bit.

IE: If I send out a dim command from the HS2 OmniPro 2 plugin (or OmniTouch screens or PCA); the new HS3 plugin sees the status of the UPB light and changes the unit status accordingly.

If I send out a dim command from the HS3 OmniTouch UPB unit the HS2 HAI, PCA, Omnitouch screens do not see it.

[drmcp]

I am using the HAI Plug-in I didn't think it would be tied to that because dimming works just fine from HS3 web interface and from an HSTouch screen just not from Echo.

Glad to hear it is being address

The ability to keep/modify the control use can depend on your plug-in that the device belongs to. Yours looks similar to my screen since I believe you are also a HAI Plug-In User. The PI developer (Rob Mason) is working on a version that resolves this issue with "Control Use" issue. HS3 Beta 3.0.0.255 released today was required in order to implement the fix for those of us that are HS3 HAI users. I suspect if other users have devices with the same issue, the issue is related to the Plug-In the Owns/Created the Device and is not specifically an HS3 issue. For instance, my buddy uses the Spud UPB Plug-In and can Dim just fine and does not have the issue.

-Travis

[will.i.am]

The Control Use issue is only happening with my thermostat, which doesn't use a plugin, AFAIK.

[Rupp]

The Control Use issue is only happening with my thermostat, which doesn't use a plugin, AFAIK.

If it's a Z-Wave stat then it uses the Z-Wave plugin.

[will.i.am]

If it's a Z-Wave stat then it uses the Z-Wave plugin.

The Control Use field for all of my zwave lights work correctly. And the Mode and Fan Mode fields for the same thermostat also work correctly. It is just the Heat and Cool Set Points that cannot remember the Control Use setting.

Is there an update coming for the zwave plugin to make this work?

[drmcp]

upgrading to 3.0.0.258 did not fix the issue of being able to save the control use settings to dim.

I am using the HAI Plug-in I didn't think it would be tied to that because dimming works just fine from HS3 web interface and from an HSTouch screen just not from Echo.

Glad to hear it is being address