Official Alexa Smart Home Skill for openHAB 2

Announcements
, ,
242

Anyone else had this and what suggestions for a workaround?

Unfortunately not, she very much gets confused on some words.

  1. Does CurrentHumidity work? I see it is in the Homekit list, but does not work for me.

The Alexa Smart Home API does not support this, as soon as it does we can add it easily

Any suggestions how I can use the same label e.g. “Kitchen Radio” to Power OFF and Volume % value?

I have been thinking about how to do this as well as the Alexa API seems to want to support this by having a device respond to multiple types of commands. One quick solution would be to create a dimmer item that triggers a rule. In the rule whenever the item receives a command. You would turn off the squeezebox if the command is OFF or 0, turn on and set volume to the command if the command is > 0, and turn on and use the last volume level or a default volume level if you receive command of ON or 100

243

@digitaldan - Thanks tor the reply.

As for the Alexa words, I have had to be creative e.g. Second Socket.
Great idea to create a rule for the volume <= 0 or OFF etc. I am porting over from OpenHab 1.8, so will add this to my rules.
I am watching another development going of for Alexa control for Squeezebox (I use Max2Play as well on my Pi).

244

@christoph_wempe Feel free to improve my excel sheet…

https://drive.google.com/file/d/0BxwDFjYKpMNMWlZYeko1UmFMZ0E/view?usp=sharing

245

Hi @digitaldan - any luck in looking a the logs to see why the discovery isn’t working?

246

Same still no luck with discovery here

247

Apologies for the delay I can see 500 errors being returned from the cloud service in our lambda logs, but I don’t see exactly why that’s happening. I just pushed a small change to production that will hopefully give some more useful logs. If not, I will have to look at increasing the log levels in the cloud service.

248

I just did 3 scans on a row just seconds before this post if it helps pin it down

249

Thanks, I realized I had a typo in the error debug code, I fixed that and will monitor the logs today, hopefully we will find the issue. I suspect its something with the oauth key and authentication.

250

Can those that are having discovery issues make sure that calling /rest/items , either locally or through https://myopenhab.org/rest/items returns correctly? I just saw an error where OH is throwing an exception b/c of a bad item config (java.util.IllegalFormatConversionException)

251

Scanned 10 seconds ago, no issues, all devices found.

Edit: Snapshot build #921
206 | Active | 80 | 2.1.0.201705151816 | openHAB Cloud Connector Bundle

252

Hi @digitaldan - i can still successfully hit the REST API through myopenhab. Still no luck discovering devices - tried again at 7:30AM AWST (Australia).

253

Can you confirm that you hit the that URL exactly (/rest/items) and not an individuale item ( like /rest/items/foo)?

254

Hi Dan - yes, I can hit just the /rest/items, both locally and myopenhab.

255

I can too - get a heap of text when going to https://myopenhab.org/rest/items which is all my items - is this what you mean?

256

Is it right, that alexa always return [ “CurrentTemperature” ] without decimal value in german language?

257

Hi @digitaldan - any luck in finding the problem?

258

This is a limitation of the OpenHAB Cloud service, I you can install your own version of the openHAB Cloud service and modify the nodejs script to return a decimal value.

1 Like
259

Probably a simple parse issue? https://github.com/openhab/openhab-alexa/issues/37

260

I pushed out a new version, hopefully that fixes it.

I’m not sure what you mean, the cloud service does not have any function but to proxy requests back and forth between Alexa and your OH instance, it does not modify or even know what the data is that it is proxying. Alexa uses the OH rest API for its functions.

261

I have not yet, so strange! I’m hoping to get some more time to look into this soon.