I have been doing that and nothing new comes up, nothing from openhab.
I changed my garage door to match the one described and it showed up, not sure if it was just a waiting game or what:
Switch GarageDoorSwitch “Garage Door” (Garages) [“Lighting”] {myq=“0”}
I tried basically the same syntax for one of my zwave switches, saved and alexa app does not discover:
Switch StairLights “Stair Lights” (Basement) [“Lighting”] {zwave=“7:command=basic,refresh_interval=120”}
Did you try with [“Switchable”] ?:
http://docs.openhab.org/addons/io/homekit/readme.html#item-configuration
@Rob_Pope Thanks for your answer. I’m glad to hear that my configuration is correct but there’s another problem.
I’m tried removing the Skill from the App. Then deleting the Application and redoing thing but still not get any devices to show after scanning for new devices with the App.
My Test Switch looks like this as well
Switch TestSwitch "Test Switch" (Lights) ["Lighting"] { channel="zwave:device:1587fb1d72a:node3:switch_binary" }I tried playing with the ‘order’ of the [“Lighting”] moving after the group and Channel, etc but still no success.
I wonder if anything to with an Android vs IOS or other issue? I an Android home, but do have a Kindle Fire in the home to maybe try with.
I’m using the discovery function on an Android device without any issues.
To be sure it’s not your mobile device which is causing your problems you could try the browser version of Alexa:
Also check this thread if you network setup is causing the problem:
This is not needed for Alexa, only IFTTT. Discovery is completely done by using the REST interface proxied through myopenhab.org.
They are very similar, the main benefit of the Alexa skill is Thermostat support. Also while this skill was in review they added the ability to ask Alexa for the current temperature and target temperature on devices ( which i have working, I just need to commit it). Hopefully they will continue to add functionality we can use.
So this feature was added to the API on Feb 17th, I would hope this gets deployed to other regions soon!
Excellent news! I can tell Alexa to set the temperature of my faux thermostat and she tells me it’s set to auto and what the temperature is, which is 90% of the way there. Looking forward to the update!
When i disable all devices, i cant see any device on openhab.org! But i can find them via Alexa.
@Rob_Pope Which version of Alexa (dot) device software are you using?
Under Settings -> Devices -> choose your echo device and scroll down.
The app is saying 567200820, which doesn’t sound like any software version I’ve seen before!
Thats true. Mhh
How did you realise to ask alexa for current temp and set a temp too?
But thats only possible by using hue emulation.ATM
I swear it worked once and I don’t have Hue Emulation. Can I get it to work now? Nope!
At the moment, i’m thinking about switching back to hue emulation, because of more commands.
Yes, it does work. I did not check yet asking for the temperature, but setting the temperature works okay.
The setup needs to be with a group, see the docs:
http://docs.openhab.org/addons/io/homekit/readme.html
Does this work using Amazon’s “Device Cloud” ? i.e. a cloud external to one’s home network? Is no one else bothered by this architecture? This means every time I merely want to turn on a light Voice->Echo->AmazonCloud->OpenHabDeviceCloud->MyOpenHabServerWithinMyNetwork->MyLight. Everywhere spewing logs of my every move.
Granted the loop Voice->Echo->Amazon->Echo is a must to get the voice recognition capabilities. But why can’t echo talk to openhab directly within my network a la the Hue Interface? I realize there is a Hue Emulator but I’m concerned of the general architectural direction.
