-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selector switch level names not supported #21
Comments
Hi - |
Alexa recognises my selector switches as "Light/Switch". |
The issue with InputController is that it doesn't allow custom names, so alot of your LevelNames wouldn't be recognised - |
I am still using alexa-domo. Has the Alexa support in Controlicz moved on? Did anyone get OAuth2 working for Domoticz yet? |
Ok, i've been looking at this, but the main issue is the Domoticz API. In order to change a Selector Switch level, you call: In order to handle Level Names, i'll have to do a lookup, which will make an extra call, and slow the request down. Additionally, we're then relying on Alexa understanding your request cleanly enough for me to take that input and then match against your Level Names |
Alexa-domo is using the deprecated Alexa API, which will be end of life at some stage. There is no OAUTH2 service in Domoticz, so you still have the same security issue, where I handle the tokens, and have to store (encrypted and hashed) your domoticz details. |
Is the Controlicz code available? I'm happy to hack in it to make improvements.. and less happy to use something I can't :) Thanks for all your work on this! |
Hi - |
Do you still use Lambda for Controlicz? I can live with the security thing; if I give you a password for the "alexa" user in my Domoticz, that's fairly much equivalent to doing things "properly" with OAuth2. But I have been getting very annoyed with the Lambda first-time spinup recently as we've been adding more devices and using it more, so I was getting very tempted to add support directly into Domoticz itself for being invoked directly: https://developer.amazon.com/docs/custom-skills/host-a-custom-skill-as-a-web-service.html |
Gr... except I don't think you can host anything except custom skills that way. Of course you ought to be able to host smart home skills on your local network and discover them with uPNP... |
yep, you can't run the smart home skill that way. Although you might be able to run the Smart Home skill on a lambda, which interacts with the IOT mqtt model, which your domoticz could work with. maybe. |
Yeah, I already have a dedicated "Alexa" user. It's calling off-site to lambda that really bothers me, especially the first time. Maybe using yours would be better because I'd only suffer the 20-second Lambda spinup if none of your users have used Alexa in the last ten minutes. Rather than whenever my skill hasn't been used in the last ten minutes. But still, it really sucks that Alexa won't talk directly to something over the local network. She does for Philips Hue! I'll go file an internal ticket and bitch about that... :) |
There's no obvious delay, given the nature of the lambda, it's unlikely that the lambda is constantly in action. I'm aware of the spinup issue with lambdas, but i'm not seeing it with Controlicz. |
Here's a selector switch as reported by
json.htm?type=devices
:I can tell Alexa, "Set lounge source to 20" and it'll select the Sky+HD box. This is a slightly suboptimal user experience for anyone who doesn't know the levels. Can we make this work with the names from the
LevelNames
field?The text was updated successfully, but these errors were encountered: