Amazon Echo to Domoticz Bridge: switches, sensors & more

[Madgeni]

WAN port on https.

[heggink]

Unfortunately I am too dependent on alexa to test and fail (and suffer the wrath of 3 women in the house). I shall have to buy another echo dot for test purposes the week after next when I will be in Washington. I can run these side by side and give them different activation words. Given how dependent we are getting to be, maybe rename from alexa to domonatrix haha .

[Madgeni]

Well, if it's working, don't change it
Feedback so far is it works identically (backend is same), but without hassle of setup

[heggink]

Great to hear. In terms of new sw versions, how does that work?

[Madgeni]

there's the rub - if the complete solution goes live, which requires no effort from users, i'd look to stop developing both, and focus on the new one

[Freemann]

OK, looks like the Lambda testing of "TurnOffRequest" and "TurnOnRequest" actions are working, but the Discovery isn't working...
Skill discovery finds my Hue lights, but not the Domoticz devices. Also running the Lamba test for discovery still returns the 1sec timeout.

Anybody an idea?

This is the logoutput of the Lambda test discovery;

Code: Select all

START RequestId: 7e2a4560-5d91-11e7-8f71-11428d14354e Version: $LATEST
2017-06-30T12:41:52.741Z	7e2a4560-5d91-11e7-8f71-11428d14354e	http://???:????@???.???:???:???:XXX/json.htm?type=devices&filter=all&used=true&order=Name
END RequestId: 7e2a4560-5d91-11e7-8f71-11428d14354e
REPORT RequestId: 7e2a4560-5d91-11e7-8f71-11428d14354e	Duration: 1002.10 ms	Billed Duration: 1000 ms 	Memory Size: 128 MB	Max Memory Used: 38 MB	
2017-06-30T12:41:53.675Z 7e2a4560-5d91-11e7-8f71-11428d14354e Task timed out after 1.00 seconds

Going to:
"http://???:????@???.???:???:???:XXX/json.htm?type=devices&filter=all&used=true&order=Name" (offcourse with the appropriate IP/Port number)
Then I see the big JSON (maybe to big JSON ? )

[Madgeni]

hi - without wanting to get too stuck into this, can you first try running domoticz against https ?
If the url is correct (and it looks it), it's possible (probable) the error is around the connection, rather than the JSON payload being too big. If that was the case, which is hugely unlikely, the connection time would be bigger.
also generally i'd recommend any comms should run over https

[Madgeni]

Also, and this is totally my fault - you need to have the devices you want to be discovered in Room Plans in Domoticz first

I've just updated the manual, and put this in bold in big font at the beginning.

[Freemann]

Great update!

Question;
Whats the best practice for Lambda region, Dot language and Dot address?

I live in The Netherlands and my preferred Alexa language is English(UK).
Based on my Location I would say the Lambda should be hosted in Ireland.
But does it madder to which address I register the Dot to and on which language I set the Dot?

If so, whats for my situation the best combination of settings and is it possible to make a matrix for other users to ?

[Madgeni]

lambda and language of skill need to be the 'same' - so it's easy:
host in Virginia - use English (US) in the skill;
host in Ireland - use English(UK) in the skill;

can't say about language of the Dot, my continental friends can probably help

[Freemann]

OK thanks again!

For me only the combination "Virginia <> English US" is working.
Tried the "Ireland <> English (UK)", but that's just not working (for me) and as soon as I switch to Virginia; It works.....

[borcon]

@madgeni,
your current version on github does not find any scenes or groups from domoticz.

[Madgeni]

Hey @borcon - There was an issue previously, where it was including any scenes/groups not just those in Room Plans, this line:

if (device.planID === '0' || device.planID === ' ') { continue }

*Should * fix that, ignoring devices/scenes & groups NOT in a plan. Can someone else corroborate that this is not working?

Thanks!

[borcon]

Hey madgeni,
now it's working. I had only devices in room plans.
I thought the room plan restriction is only for devices.
Thanks

[Madgeni]

Hi
it wasn't supposed to be, but i just missed the scene logic out ages ago!

[borcon]

@madgeni,
if I ask Alexa "what is the temperature" in my room, then she speaks the temperature as a date.
I think the point in the temperature (26.5) from domoticz is the issue.
Can you help me to add a line in the alexa code to replace the dot with a comma? 26.5 --> 26,5
I hope this solves the issue.

Thanks

[Madgeni]

Hi there - is this the continental use of the comma for decimals? The issue is more with this being for the US/UK with Alexa, which use the full stop.
I'll do some tests

[Madgeni]

Looking at the doc, it expects a floating point -
"temperatureReading.value Floating point number that indicates the temperature in degrees."

[borcon]

@madgeni
yes, this is the continental use of the comma for decimals

[Madgeni]

think we might need to await the release into DE