Alexicz - FREE Domoticz to Alexa Integration

[kitopopo]

I changed https by http in configdz-template.json or configdz.json in "url" https://myexternalip was replaced by "url" http://myexternalip.
making this change alexa works with my domoticz perfectly but I am afraid of security problems, either because I use http or because I give my username, password, public ip and port in that configuration file. I am giving all my data.

Do you think it is safer if I use https? Besides this, is it not dangerous to put all my data in that file? thanks in advance

Aha, that's allowed because you are not publishing the skill and it's for personal use only in your dev-account. It's a very bad idea though, as your Domoticz is fully exposed with no protection. It's not 'if' you will be hacked, but 'when'...

You already have an external IP address, right? Have you tried getting an SSL cert for it from LetsEncrypt?

Thanks for your answer,

No, I should start using the LetsEncrypt certificates as soon as possible. But even so, do you think it does not bring any security risk to give the public ip, port, user and password even if the LetsEncrypt certificates are used and it is via https?

this is my doubt, leave alexa running permanently delivering all my data.

thanks in advanced

[philchillbill]

I changed https by http in configdz-template.json or configdz.json in "url" https://myexternalip was replaced by "url" http://myexternalip.
making this change alexa works with my domoticz perfectly but I am afraid of security problems, either because I use http or because I give my username, password, public ip and port in that configuration file. I am giving all my data.

Do you think it is safer if I use https? Besides this, is it not dangerous to put all my data in that file? thanks in advance

Aha, that's allowed because you are not publishing the skill and it's for personal use only in your dev-account. It's a very bad idea though, as your Domoticz is fully exposed with no protection. It's not 'if' you will be hacked, but 'when'...

You already have an external IP address, right? Have you tried getting an SSL cert for it from LetsEncrypt?

Thanks for your answer,

No, I should start using the LetsEncrypt certificates as soon as possible. But even so, do you think it does not bring any security risk to give the public ip, port, user and password even if the LetsEncrypt certificates are used and it is via https?

this is my doubt, leave alexa running permanently delivering all my data.

thanks in advanced

When https, everything is safe. The data cannot be intercepted.

[kitopopo]

Aha, that's allowed because you are not publishing the skill and it's for personal use only in your dev-account. It's a very bad idea though, as your Domoticz is fully exposed with no protection. It's not 'if' you will be hacked, but 'when'...

You already have an external IP address, right? Have you tried getting an SSL cert for it from LetsEncrypt?

Thanks for your answer,

No, I should start using the LetsEncrypt certificates as soon as possible. But even so, do you think it does not bring any security risk to give the public ip, port, user and password even if the LetsEncrypt certificates are used and it is via https?

this is my doubt, leave alexa running permanently delivering all my data.

thanks in advanced

When https, everything is safe. The data cannot be intercepted.

But amazon aws have my data, public ip, password and port.

[philchillbill]

Thanks for your answer,

No, I should start using the LetsEncrypt certificates as soon as possible. But even so, do you think it does not bring any security risk to give the public ip, port, user and password even if the LetsEncrypt certificates are used and it is via https?

this is my doubt, leave alexa running permanently delivering all my data.

thanks in advanced

When https, everything is safe. The data cannot be intercepted.

But amazon aws have my data, public ip, password and port.

I wouldn’t worry about that. It’s encrypted in storage. Same as any cloud storage.

[andromo]

Hi all,

I have been using alexicz for a while. It is very nice. I don't like to have a open port at home, so I added port knocking to the api() function in the lambda, so before adressing the domoticz port it knocks 3 different ports in the correct order. I dont't know much about python, but now it's working. My firewall (mikrotik router) has input firewall rules for acepting connections only from IPs that did the correct port knocking combination, and Alexicz is doing it right now (https://wiki.mikrotik.com/wiki/Port_Knocking)

By the way, I'm trying to control an AC split with an ESP8266 board and IR LEDs. Now I have a thermostat setpoint that can be cofigured with Alexa with no problem. But I want to change de mode also (HEAT, COOL). I have seen in the Alexicz code that if you set an ligth/switch selector with Alexa_extra:{ "OFF": 0, "HEAT": 10, "COOL":20} It should work, but I really don't know what I'm doing, and alexa says there is a problem with the discovered thermostat (from the Selector switch configured with alexa_extra).

Can some one who use or know about this feature help me please?

Thanks
Andrés

[andromo]

I have seen that in my domoticz version, "LevelNames" are base64 encoded, I have managed this, but the Thermostat selector is still not working at all... any clues?

Hi all,

I have been using alexicz for a while. It is very nice. I don't like to have a open port at home, so I added port knocking to the api() function in the lambda, so before adressing the domoticz port it knocks 3 different ports in the correct order. I dont't know much about python, but now it's working. My firewall (mikrotik router) has input firewall rules for acepting connections only from IPs that did the correct port knocking combination, and Alexicz is doing it right now (https://wiki.mikrotik.com/wiki/Port_Knocking)

By the way, I'm trying to control an AC split with an ESP8266 board and IR LEDs. Now I have a thermostat setpoint that can be cofigured with Alexa with no problem. But I want to change de mode also (HEAT, COOL). I have seen in the Alexicz code that if you set an ligth/switch selector with Alexa_extra:{ "OFF": 0, "HEAT": 10, "COOL":20} It should work, but I really don't know what I'm doing, and alexa says there is a problem with the discovered thermostat (from the Selector switch configured with alexa_extra).

Can some one who use or know about this feature help me please?

Thanks
Andrés

[tarmacalastair]

Silly question but I assume you have checked that the setpoints are working via a browser?

Since I upgraded from Domoticz 2020.2 to 2021.1 I have had no end of problems with my thermostat setpoints. Everything was working fine in 2020.2 and no one seems to have a solution. I've been told to clear browser cache, change from ZWave to zwavejs2mqtt. I've done both of these things on completely fresh installs of Domoticz and no progress so far. The swap from Zwave to zwavejs2mqtt causes the setpoints to behave exactly the same.

(See my postings at viewtopic.php?f=6&t=34838 and viewtopic.php?f=6&t=37456)

Apologies if you've already checked they are working through the browser interface...

[andromo]

Thank you for your answer tarmacalastair.
The set point is working rigth for my needs. I am using it from amazon Alexa voice commands. What I can't make work is the thermostat selector device that is defined in the Alexicz skill.
Now I have a virtual switch to switch on/off AC and a virtual thermostat to set the target temperature. Both are working from alexa interface.
I want to set mode of the thermostat to COOL or HEAT, I see that this is managed throught a switch selector in alexicz skill, but is not working for me. Thats why I ask help from someone that use that feature or understand how it works...
Thanks!!!

[binbo]

I have just been told that Python 3.6 is being dropped on AWS.

You’ve got to upgrade to 3.9

Is Alexicz compatible with this version of Python?

[fibigod]

Same here, don’t know if it is compatible, there are always some issues when upgrading.

AWS will support the current version, but doesn’t gives any support and you cannot make new lambda’s with that python version.

So if nothing changes, you don’t have to upgrade the scripts.

[Jorn]

I've set up Alexicz successfully lasty week, the only strange thing than I'm heaving is when using scene's/groups, when I tell Alexa to activate a scene it responds with "I'm having trouble reacing null" but the scene is activated, so it's only the response that is faulty.
Is this a known issue?

[vco1]

I've set up Alexicz successfully lasty week, the only strange thing than I'm heaving is when using scene's/groups, when I tell Alexa to activate a scene it responds with "I'm having trouble reacing null" but the scene is activated, so it's only the response that is faulty.
Is this a known issue?

Same issue here.

Also the question re. an upgrade of the Python version.

[tarmacalastair]

Still hoping someone might be able to post some up to date instructions on how to set this up. I tried a year or so back and Amazon had changed so many steps that it didn't make sense to me and I gave up.

It would be lovely if someone (who understands) could spare a few minutes to update the instructions.

Thanks.

[marco92120]

Hello Python 3.9 runtime update worked fine for me.
What I've done :

1/ Logon AWS console and go on functions : https://eu-west-1.console.aws.amazon.co ... /functions
2/ Select Alexicz function by clicking on it
3/ At page bottom in "Runtime Settings" section select Edit on the right
4/ Select Python 3.9 in runtime popup menu
5/ Click save

You're done. On my side I got no errors or side effects for all my switches and thermometer.
If something goes wrong for you, probably selecting python 3.6 in "Other supported" should bring you back to previous state

[Jpaul78]

Hello,

First, sorry for my English (I am french, professionally retired and don't practise English anymore).

I am trying to make alexicz skill working.
From the test console, using the test json exemples :
It retrieves my devices.
I can make one of the lights on and off.

But when I am on my android phone I can't discover the devices.

I guess that, as I was confused on the Account Linking step and don't complete it, it could be the reason.
I finish by seeing the "https://layla.amazon.com/api/skill/link/xxxxxxx" part at the end of the configuration page and now I have an error telling :

Code: Select all

Instance at property path "$.accountLinkingRequest.scopes" is expected to be present when instance at property path "$.manifest.apis.smartHome" is present.

I don't understand that message. Can any one help me ? Thanks in advance.
Jean-Paul

[Jpaul78]

Hello all,

I finished to solve my problem selecting the right location in the console page and create again my lambda. So it was working but now I have a new problem...
When I ask :
"Alexa allume la chambre." (for : "Alexa turns on the bedroom.")
I have a reply telling :
"L'appareil chambre ne répond pas." (means : "Room device not responding.")

What is following is a Google translation :
The problem appeared after a previous socket failed and I replaced it with a new one. So I deleted the old socket in domoticz connected the new one. Checked it was OK with domoticz then reloaded the devices on alexa. Device rediscovery told me that it found a new device that I installed but when I ask to turn it on I have the problem telling that the device is not responding.
The other devices were working. I deleted all my devices on Alexa, asked again for device updates, Alexa found them all but none of them worked, I got the message that the device is not responding.

Am I alone to encounter this problem ?

Does anyone have a solution to this problem ?

Thanks in advance,
Jean-Paul

[philchillbill]

Hello all,

I finished to solve my problem selecting the right location in the console page and create again my lambda. So it was working but now I have a new problem...
When I ask :
"Alexa allume la chambre." (for : "Alexa turns on the bedroom.")
I have a reply telling :
"L'appareil chambre ne répond pas." (means : "Room device not responding.")

What is following is a Google translation :
The problem appeared after a previous socket failed and I replaced it with a new one. So I deleted the old socket in domoticz connected the new one. Checked it was OK with domoticz then reloaded the devices on alexa. Device rediscovery told me that it found a new device that I installed but when I ask to turn it on I have the problem telling that the device is not responding.
The other devices were working. I deleted all my devices on Alexa, asked again for device updates, Alexa found them all but none of them worked, I got the message that the device is not responding.

Am I alone to encounter this problem ?

Does anyone have a solution to this problem ?

Thanks in advance,
Jean-Paul

If you visit the Amazon Cloudwatch log for your Alexicz you will see the error message in the logs. Google how to access Cloudwatch.

[Jpaul78]

Hi,

Just for information in case someone encounters the same problem : everything went back to normal after a few days without changing anything.

Regards,
Jean-Paul

[Jpaul78]

If you visit the Amazon Cloudwatch log for your Alexicz you will see the error message in the logs. Google how to access Cloudwatch.

I just see your reply now, thanks a lot for it. I will look at that Amazon Cloudwatch if I have some problem again in the future.

Best regards,
Jean-Paul

[xavierlp]

Hello all,

As you maybe know, Controlicz will be discontinued at the end of 2023.

So I would like to have a look on Alexicz. I could discover that the project is not supported.

I followed to How to , and I can not discover my devices.

If I made a test on AWS console I've got this error

{
"errorMessage": "'directive'",
"errorType": "KeyError",
"requestId": "b72988b4-04c0-4fe0-bbbd-9464317feebe",
"stackTrace": [
" File \"/var/task/lambda.py\", line 49, in event_handler\n response = AlexaSmartHome.handle_message(dzRemote, request)\n",
" File \"/var/task/AlexaSmartHome.py\", line 320, in handle_message\n message = message[API_DIRECTIVE]\n"
]
}

the code is

dzRemote = DomoticzHandler.Domoticz(config.url, config.username, config.password)
dzRemote.configure(config)
response = AlexaSmartHome.handle_message(dzRemote, request)

The 3 variables are correct - I use the same with contrloicz without issues.

Have you got any ideas on how I can troubleshoot this error.

Thanks a lot