Hi Jeremy, very good hint. I double checked, but all the hints which are given in the troubleshooting guide I tried already.
When I start the discovery no new items are added, but the existing ones are working fine. If I delete a working item in the Alexa app and start discovery again, its also not found anymore…
Nothing in the openhab log which can be linked to the problem.
Yes, as I wrote before: I can control the existing items perfectly since a long time. Thats the reason why I don’t want to delete them. If someone tell me that there is a known issue with the alexa skill that I need to delete all devices before I can add new ones I would give it a try… But I don’t find such an issue here…
sudo systemctl start openhab2 or you may need to reboot sudo reboot
Also make sure you don’t have simple mode turned on in PaperUI if using files as this can create duplicate items/issues.
What version of Amazon binding are you using? I’m on OH 2.4 stable with amazon control binding version 2.4.0.201812011454.jar that I manually placed in ‘/usr/share/openhab2/addons’. Not sure what beta version this is but if I had to guess it’s either 7 or 8.
There are no known issue with the Alexa skill. Basically, if tweaking the items doesn’t fix your problem, then it’s a server availability issue. You have to check that you can access the REST API service via the myopenHAB cloud service.
Also, since you are using 2.4, keep in mind there is a know issue when using the Amazon Echo Control binding, released in that version, that breaks the REST API service.
thanks a lot! That an important info.
I am using the old Alexa skill. I will try the 2.5 version as soon I get home and give feed back, if it solves my problem.
I changed from version 2 syntax to version 3 syntax last week and had no problems (Snapshot #1665 which is basically Milestone 3)
Did you follow the recommendation to check the server availability?
To resolve this error, make sure that your server is running, your openHAB cloud service is configured with mode set to “Notifications & Remote Access”, and showing online under your myopenHAB account.
Hey, first of all, myopenhab.org is running with your system. If you control your items over myopenhab.org its great, with App for example. After that, check if configuration–services-io- openhab cloud- activate items for apps. Than, test the cloud again. Now your items, its wrong you have to change: Look to the picture. One reboot, discover with alexa and the openhab skill, and normally it works.
You use the metadata conf, or you can test it to delete your space like this {alexa=“Switchable”}
The v2 style will be translate in v3… Thank you for that🤓
@Bjorn_Hamburg: Thank you that you repeated this. As I wrote before I checked all this already.
Neither V2, V3 syntax works for my new added titems. They are not added to Alexa. All items which I see in Alexa already are working fine (54!).
How can I check that the 2.5 M2 alexa control binding is running? May be the problem is still there.
In PaperUI is the binding uninstalled and the 2.5 binding is in the addon folder. My alexas can be controlled. But can I be sure that the 2.5 binding and not the 2.4 binding is running?
Ok, Do you check v2 Syntax? Its also a possibility at alexa app. Settings–alexa privacy- Smarthome things delete… If you check this, than avs or the server delete the logs. Its very complicated to see the logs of avs. Best regards
That item definition object you provided looks good. How long would you say the response time from that link takes? Is the JSON object returned truncated?
Also, if you provide me with the exact time you triggered a discovery request and the region you are located, I could try to see if your request is generating any errors in the skill logs.
The JSON link opens fast. I don’t see a delay.
I triggered another search today (3.11.2019) at 17:16:05: “No new devices found”.
Meanwhile I connected also Google Home to openHab. I see the missing devices there and can control them (I added also V2 syntax for that).
If your log does not help I think I will reset the openHab connection to Alexa completely and try to connect it new.
Is the JSON object returned truncated?
I don’t see something truncated also no error message.
Is the skill developed by you? If yes, thanks for the great works!! Don’t understand it wrong if I ask for fixing this problem… In general its a great skill!!
Based on the time you posted your last reply, I will assume that you are in Europe and the CET timezone. Looking at the logs between 17:10 and 17:20 CET, there are no obvious errors that would be tied to your discovery request.
Have you tried to unlink and relink the skill on the Alexa side? Sometimes, the authentication can get messed up and requires a relink. Other than that, I am running out of possible reasons on how to fix your issue.
Yes, I was part of the effort in getting v3 up and running.