Amazon Echo to Domoticz Bridge: switches, sensors & more

[Madgeni]

post the error here and i'll take a look

[heggink]

Sent from mTalk

[heggink]

Here's the endpoint I added:



Sent from mTalk

[Madgeni]

endpoint looks fine. Re error - you need to zip the following, then upload them (Code Entry Type dropdown)

domapi.js
conf.json
package.json
/node_modules dir

[heggink]

Did that

[heggink]

Sent from mTalk

[Madgeni]

Then i'm confused. If you upload the zip file, you can't post in the code inline (which you can't do, as it relies on the other dependencies in node_modules/conf.json). so Code entry type should be "Upload .Zip file"

[Madgeni]

also, updated the code to handle the lack of Room Plans (you need Room Plans)

[heggink]

I downloaded your code yesterday afternoon so hope the roomplan update was part of that. If not then I need to update.
I did upload through ZIP. It's just that, when I upload the zip, it then switches to edit code inline and shows domapi.js.
Are you saying that it should not do that?

Sent from mTalk

[Madgeni]

definitely not - just recreated it in case there was a lambda change that did this. Seem to recall someone having an issue with zipping the files on Windows in this thread, maybe it's that?
You really only need the roomplan bit if you forget to create RoomPlans and put devices in them in Domoticz

[heggink]

I zipped on the raspberry pi and checked/uploaded on windows. I'll try to re-upload using my ubuntu desktop.
Any way to debug this stuff?

Sent from mTalk

[Madgeni]

maybe chmod -R 777 on the files/folders to sort perms out before zipping?

afraid there's no debugging of the upload process into a lambda as far as i know

[heggink]

Sorry to have wasted your time. Finally bumbed into a helpful google search: https://forums.developer.amazon.com/que ... lidch.html
Basically indicates that this is a win10/Edge/IE11 issue. As soon as I switched to firefox, all was well (well, firefox crashed but before that, I saw a result with all my devices in the rooms ).
Next is trying to figure out why I see no items in Alexa. One step at a time.
Thx so far.

H



Sent from mTalk

[Madgeni]

No worries

as an FYI i can't run it from EU:West, i use English(US) from Virginia, and the alexa skill works fine. Saying that, nigels0 runs it from EU:West just fine, but worth considering.
Latency and language are NOT an issue if you run it from Virginia.

[heggink]

Here's an example of when I run a test discover. The list is big tho. This seems to look good. IMO, correct?

{
"applianceId": "388",
"manufacturerName": "Thermostat",
"modelName": "SetPoint",
"version": "temp",
"friendlyName": "HomeTemp",
"friendlyDescription": "Thermostat",
"isReachable": true,
"actions": [
"setTargetTemperature"
],
"additionalApplianceDetails": {
"WhatAmI": "temp"
}
},
{
"applianceId": "372",
"manufacturerName": "AEOTEC",
"modelName": "Switch",
"version": "Dimmer",
"friendlyName": "Dinner table",
"friendlyDescription": "Light/Switch",
"isReachable": true,
"actions": [
"incrementPercentage",
"decrementPercentage",
"setPercentage",
"turnOn",
"turnOff"
],
"additionalApplianceDetails": {
"switchis": "Dimmer",
"WhatAmI": "light"
}
},


Sent from mTalk

[Madgeni]

Those look good to me

If the Alexa Skill isn't triggering the lambda (check the CloudWatch logs) - then maybe reproduce the lambda in Virginia, bind the skill to that Lambda selecting Englishg(U.S) - this works for me

[heggink]

I did manage to switch a light. I'll test switching to Virginia and see if that makes a difference. Thanks for the help so far.

Sent from mTalk

[heggink]

That did the trick. I have devices now . Thx!!

Sent from mTalk

[Madgeni]

boom. Stupid Amazon

[heggink]

Yup. Just weird that you get thrown off so easily by weird error messages caused by OS/browser combinations and then need to solve all sorts of other intricacies. Anyways, brilliant stuff!
ps: any thoughts on how to change friendly names? I now find that I never anticipated device naming to have to be workable in English (being Dutch myself) and being spoken

Sent from mTalk