search

HomeSeer / Plugin-SDK

Plugin development kit for the 4th major edition of the HomeSeer platform.
https://www.nuget.org/packages/HomeSeer-PluginSDK/
GNU Affero General Public License v3.0
20 stars 4 forks source link

Alexa/Google Voice Control Ignored for Dimmer #259

Open mcsSolutions opened 2 years ago

mcsSolutions commented 2 years ago

A user of a WiFi Bulb interfaced via mcsMQTT was created with a HS Device with two features. One with ON/OFF buttons. One with a Slider for brightness control. Slider range is 0 to 100. ON/OFF single values of 0 and 1. MISC settings set for Google Discovery, Alexa Discovery, Voice Control. Also tried with Is_Light MISC setting in both states.

User is able to request the ON/OFF feature via voice and the light responds. User attempts to control dimmer/sider/brightness via voice and no response.

User submitted a support ticket and the ticket requested that the plugin developer submit a GitHub issue for support to identify the requirements for setting up a feature for controlling a light's brightness via voice.

Sgt-Shultz commented 2 years ago

This may be an issue of overlapping values. The 0 and 1 for on/off are also in the dimming range. Even though they are on different features, they are both grouped under one device. My first suggestion is to set the off/on to 0/100 and set the dimming range to 1/99, then rediscover. Make sure the control use of each is set. If this doesn't resolve your issue we will look into it further for you.

mcsSolutions commented 2 years ago

What guidance can you provide for the RGB light where there are three controls (Color, Brightness, OnOff)? Should be the Color be in the positive range and the other two in negative range so they are not overlapping?

From: "Sgt-Shultz" @.> To: "HomeSeer" @.> Cc: "mcsSolutions" @.>, "Author" @.> Sent: Thursday, 17 February, 2022 9:46:32 AM Subject: Re: [HomeSeer/Plugin-SDK] Alexa/Google Voice Control Ignored for Dimmer (Issue #259)

This may be an issue of overlapping values. The 0 and 1 for on/off are also in the dimming range. Even though they are on different features, they are both grouped under one device. My first suggestion is to set the on/off to 0/100 and set the dimming range to 2/99, then rediscover. If this doesn't resolve your issue we will look into it further for you.

— Reply to this email directly, [ https://github.com/HomeSeer/Plugin-SDK/issues/259#issuecomment-1043172458 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AALJP6YQBJ57FSYBNAIQ3L3U3UQ6RANCNFSM5OTPE4MQ | unsubscribe ] . Triage notifications on the go with GitHub Mobile for [ https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 | iOS ] or [ https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub | Android ] . You are receiving this because you authored the thread. Message ID: @.***>

mnsandler commented 2 years ago

this is the same issue i reported here. starting the dim/slider range at 0 is the issue. https://github.com/HomeSeer/Plugin-SDK/issues/257

as a test, change the dim range start to 1 and it will probably work.

Sgt-Shultz commented 2 years ago

What guidance can you provide for the RGB light where there are three controls (Color, Brightness, OnOff)? Should be the Color be in the positive range and the other two in negative range so they are not overlapping?

The on, off, and brightness have control uses you can tie to them so they can be recognized by the echo.

If the rgb uses a color palette, then there is a control use for that as well. The echo doesn't recognize individual colors selectors as part of it's system.

spudwebb commented 2 years ago

Is this still an issue?