Alexa problem
-
I created a lot of X10 on/off switches for Alexa using parameters true.
The one for my kitchen light called "kitchen" would not work by voice, (device not supported error) but would turn on if clicked in the gui or web page for triggercmd.
After trying to fix it I gave in, deleted it and created again fresh. This would not get found and added to Alexa. I ended up creating the exact same command using same bat files etc but called "sink" instead, this one has appeared. Logged in and out of everything but "kitchen" switch still not appearing.
Any ideas? -
So this morning I'm even more baffled. I can now control the light with the 'kitchen' triggercmd switch even though it's not visable in Alexa. The version called 'sink' is there and works too.
So I can voice control 'kitchen' light but it's not available to use in routines by timer etc. -
So think I've got it all working again, not 100% sure what was happening but in case anyone else has a similar Alexa problem I suspect it's because I had a light switch called "kitchen" and there was a room in Alexa called "kitchen" too. Renaming the room to "kitchen room" seems to have got everything back to normal.
Was working fine when I had two separate switches "kitchen on" and '"kitchen off" but everything started going strange once I had the parameters on/off switch.TLDR: Alexa doesn't like a triggercmd switch with same name as a room.
-
@chrischickshow, that makes sense. I'll add something about that to the docs to warn people not to use the name of a room in their voice words..
