Good morning! What is the best practices to migrate from old v2 tags to v3 metadata?
Can I delete [“Lighting”] and add the metadata like this:
{channel="knx:device:176c8fbf:c", alexa="PowerController.powerState"}
after that, have I to delete and rediscovery the item on alexa or she automatic update them?
thanks for support
Hi, I have the same issue as omatzyo. All devices unresponsive for a few days through the alexa skill. Everything works fine through the myopenhab server, only the skill has stopped working. The response from the links you provided omatzyo are both very quick. I only have a dozen devices and one group so I’m not sure if it can be a processing delay (happy to send the output from the links if needed), I have been through the discovery process several times, restarting openhab, dissabling and re-enabling the skill etc but still nothing. Any help would be very much appreciated.
I have the same issue.
All depends on the level of customization you need. The v2 tags are here to stay for the time being, so you can stick with the ones you currently have, add new items with v3 metadata to start getting familiar the with new configuration settings, and ultimately start converting some of your v2 setup that can leverage the advanced functionalities such as group endpoints and mode/range/toggle interface controllers.
Keep in mind that both v2 tags and v3 metadata configuration can coexists with the latter taking precedence, and if you are using other integrations such as Google Assistant or HomeKit, you will need to keep these tags.
The conversion example you provided would make your item a switch that can just be turned on/off. You can refer to the examples listed in the metadata labels documentation section and you should familiarize yourself with the concept of display categories. If you want to only use v3 metadata, you can just migrate the v2 tags as v3 metadata labels or if you prefer to have granular settings, replace the tags with the relevant metadata capabilities and parameters.
As far as updating devices on the Alexa side, you just need to trigger a rediscovery via the mobile app, website or by asking your favorite echo device to “discover”. No need to delete devices unless you removed/unlinked an item from your OH configuration. In that event, these devices would show as offline in your Alexa smart home console.
Could you, in order of sequence, (1) try sending an Alexa command to one of your previously working discovered device, (2) initiate a discovery, and then (3) provide me the exact timestamp you completed these actions, your Amazon account location and the OH item name you tried to send the command to? This would help us find your requests in the relevant skill logs.
If you could provide me with the same information I requested above, that would be much appreciated.
My devices stopped responding after the update to V3.
When I click on the metadata link above it takes quite a few seconds before returning this;
{"error":{"message":"GET url \u0027https://alexa.amazon.co.uk/api/behaviors/entities?skillId\u003damzn1.ask.1p.music\u0027 failed: Bad Request","http-code":500,"exception":{"class":"org.openhab.binding.amazonechocontrol.internal.HttpException","message":"GET url \u0027https://alexa.amazon.co.uk/api/behaviors/entities?skillId\u003damzn1.ask.1p.music\u0027 failed: Bad Request","localized-message":"GET url \u0027https://alexa.amazon.co.uk/api/behaviors/entities?skillId\u003damzn1.ask.1p.music\u0027 failed: Bad Request"}}}
Which link are you referring to? And where are you seeing this error? This error message seems to be related to the Amazon Echo Control binding
Location: Germany / Munich
16:45 GMT+1 ReInstall Openhab Skill on Alexa.Amazon.com
16:51 discovery devices
Switch Deckenlicht "Wohnzimmer Deckenlicht" <Light> (GrpWzLicht) ["Lighting"] {channel="mqtt:topic:mqttlocal:WohnzimmerLicht:Deckenlicht"}
Switch Esstisch "Esstisch" <Light> (GrpWzLicht) ["Lighting"] {channel="mqtt:topic:mqttlocal:WohnzimmerLicht:Esstisch"}
Switch Schmetterling "Schmetterling" <Light> (GrpWzLichtKlein) ["Lighting"] {channel="mqtt:topic:mqttlocal:WohnzimmerLicht:Schmetterling"}
Switch Wohnwand "Wohnwand" <Light> (GrpWzLichtKlein) ["Lighting"] {channel="mqtt:topic:mqttlocal:WohnzimmerLicht:Wohnwand"}
@RonnyB I see a couple discovery requests failing for various reasons during that timeframe making it hard to pinpoint your request. I have updated the troubleshooting steps above. Could you please try again? No need to enable/disable the skill.
The link was https://myopenhab.org/rest/items?metadata=alexa,channel,synonyms&recursive=true
I do use the alexa control binding also - sorry for the confusion.
My setup was working until the V3 update. Then when I asked alexa to turn my lights on it would respond “hmm lights are not responding”. I removed my devices from alexa and now it doesn’t find them after a discovery.
Any ideas?
If it takes more than 10 seconds for the content of that link to be output, then this is a known issue with large item collection setup and we are working to resolve this one very shortly.
@Scotsman So I have taken a closer look at this and I actually noticed in the skill logs that a bunch of users have been getting the strange error message you listed above when requesting a discovery.
@michi any idea why the Amazon Echo Control binding would interfere with a rest api call?
I have deployed @jeshab changes for the discovery issue to production. @omatzyo and anyone else having discovery issues, can you try again?
2 Likes
Hurray! it works! You guys are the best. Thank you. I’m looking forward to digging into V3 soon.
FYI, regarding above. I also use the Amazon Echo Control binding on my two systems and have not had any errors.
1 Like
Yes, this was an issue in the 2.4 release, there was an REST call in the StateDescriptionProvider. But this is already fixed in the 2.5 release.
Thanks for confirming. So the recommended solution for the affected users is to either disable the binding when using 2.4 or update to the latest 2.5 milestone?
It works, you are the Best!!!
1 Like
Hi,
looks like I have to report a nother issue.
Since the skill update most of my lights are not working anymore. I have some lights with a TPLink-Plug they work still fine, but all my lights on my Siemens Logo are not available via alexa.
They work via the openHAB interface - I already updated to M2 but that did’t help.
I have done the search for new devices several time in the alexa app and with a echo device.
What i can see so far is the following metadata difference (from https://myopenhab.org/rest/items?metadata=alexa,channel,synonyms&recursive=true):
Working item:
{
“link”: “https://myopenhab.org/rest/items/TPLink_Whz_Stehlampe”,
“state”: “ON”,
“metadata”: {
“channel”: {
“value”: “tplinksmarthome:hs100:6F9012:switch”
}
},
“editable”: false,
“type”: “Switch”,
“name”: “TPLink_Whz_Stehlampe”,
“label”: “Stehlampe”,
“category”: “light”,
“tags”: [
“Lighting”
],
“groupNames”: [
“Erdgeschoss”,
“gLogoLightProxySwitch”
]
}
Not working:
{
“link”: “https://myopenhab.org/rest/items/Proxy_Logo_1_Q_10”,
“state”: “OFF”,
“editable”: false,
“type”: “Switch”,
“name”: “Proxy_Logo_1_Q_10”,
“label”: “Wohnzimmer - Gartenseite”,
“category”: “light”,
“tags”: [
“Lighting”
],
“groupNames”: [
“gErdgeschoss”,
“gLogoLightProxySwitch”
]
}
Any ideas?
My Alexa APP is telling me that “Openhab Smarthome Skill” was updated 3 days ago (to v3). I did not force a rediscover of my devices. Everything is controllable with the voice, but the “devices view” in Alexa APP is flapping. You also can switch the devices there, but many of the devices reporting then (although it was switched correctly) “there was a problem”. And some states (ON or OFF) are not updated correctly.
Should I rediscover devices? Or what else to do?
Are you initiating the commands vocally while having the Alexa App opened to monitor the states? If so, this is a known issue. The skill currently only provides state updates when Alexa requests them (polling).
There are plans to implement proactive reporting in the future which would allow state updates, along with item configuration updates, to be pushed directly from the OH server. Until that, the states in the Alexa App may not fully reflect the current OH state especially, if you currently have the app opened and you don’t force refresh.
Would you be able to provide with a distinct item name that experienced the problem you observed along with the time you issue the request and your country location? I will try to see if there are any errors in the skill logs.