Jump to content

SWL keeps saving as Contact Sensor in Portal


andrew77

Recommended Posts

Posted (edited)

Hi guys,

I have a SWL that wouldn't respond to alexa voice command (Turn on, dim, etc)

I went to the ISY Portal and noticed it was saved as a Contact sensor. 

I switched it to Light and saved, closed, and backed out. I had Alexa browser app forget the device and rediscover it.

When I try a voice command same problem.

I go back to ISY Portal and find its switched back to Contact sensor.

I'm not sure what I'm doing wrong.

Drew

 

Upon second glance many lights are listed as contact sensor but they respond to Alexa voice command.

Edited by andrew77
Posted
5 minutes ago, andrew77 said:

Hi guys,

I have a SWL that wouldn't respond to alexa voice command (Turn on, dim, etc)

I went to the ISY Portal and noticed it was saved as a Contact sensor. 

I switched it to Light and saved, closed, and backed out. I had Alexa browser app forget the device and rediscover it.

When I try a voice command same problem.

I go back to ISY Portal and find its switched back to Contact sensor.

I'm not sure what I'm doing wrong.

Drew

 

Upon second glance many lights are listed as contact sensor but they respond to Alexa voice command.

What is the ISY Category (The "ISY Cat." column) ?

After switching it to light and saving, does the Alexa Cat. column still shows it as Light?

Posted (edited)

Hi bmercier

Sorry for not including that.

ISY Category is Device and Alexa Category is Device/Light

I should also add Alexa says "Library doesn't support that" when I ask Alexa to dim or turn on library SWL

 

Edited by andrew77
Posted
29 minutes ago, andrew77 said:

Hi bmercier

Sorry for not including that.

ISY Category is Device and Alexa Category is Device/Light

I should also add Alexa says "Library doesn't support that" when I ask Alexa to dim or turn on library SWL

 

To help troubleshoot this, keep an eye on that page. You can refresh using the refresh icon. No need to edit it. Technically, it should never be changed, except when editing if the values are considered invalid. 

I would suggest to change the spoken and retry. Sometimes, Alexa will understand incorrectly, especially if you have other devices with similar spokens. Try with something simple like "test", "kitchen" or "living room", common names that are easily recognizable.

  • Thanks 1
Posted
On 4/14/2019 at 4:50 PM, bmercier said:

I would suggest to change the spoken and retry.

Hi bmercier

Adding another spoken command worked great. I called it 'book room' but was tempted to use 'Libary' a la Fonzie. haha

I'd like to know why it didn't recognize library as a command as its not an uncommon word.

Would that be something I'd give as feedback to amazon? or an Alexa forum?

Regardless, thanks again.

 

Drew

 

Posted
4 hours ago, andrew77 said:

Hi bmercier

Adding another spoken command worked great. I called it 'book room' but was tempted to use 'Libary' a la Fonzie. haha

I'd like to know why it didn't recognize library as a command as its not an uncommon word.

Would that be something I'd give as feedback to amazon? or an Alexa forum?

Regardless, thanks again.

 

Drew

 

Feedback to Amazon I guess. I never tried to report/investigate why a specific spoken would not work.

Benoti

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...