Domoticz

sudo /etc/letsencrypt/certbot-auto renew --webroot -w ~/domoticz/www/ --deploy-hook ~/domoticz/scripts/deploy-cert.sh >/dev/null

#!/bin/bash
sudo mv /home/pi/domoticz/server_cert.pem /home/pi/domoticz/server_cert.pem.org
sudo cat /etc/letsencrypt/live/mysite.duckdns.org/privkey.pem >> /home/pi/domoticz/server_cert.pem
sudo cat /etc/letsencrypt/live/mysite.duckdns.org/fullchain.pem >> /home/pi/domoticz/server_cert.pem
sudo cp /home/pi/domoticz/server_cert.pem /home/pi/domoticz/letsencrypt_server_cert.pem
sudo cat /etc/ssl/certs/dhparam.pem >> /home/pi/domoticz/server_cert.pem
sudo /etc/init.d/domoticz.sh restart

samourai47 wrote: ↑Tuesday 27 October 2020 12:11 Thank's xavier82 for your help
I try to install ngrok. It work's...
A question. With a free version of ngrok, i must change the configuration on console google each time i reboot the raspberry?
Thank for your help

# Configuration:
port_number: 3030
# Debug, Info or Error
loglevel: 'Info'
# Set logtofile: 'false' logs will not show in the LOG tab. Set logtofile: 'Overwrite' or true Log file will be overwritten when dzga server restarts
# Set logtofile: 'Append' Logs will append to logfile when dzga server restarts
logtofile: false
# If pathToLogFile is commented, removed or set to '', logs will be saved in Domoticz-Google-Assistant folder
pathToLogFile: ''
# Enable or disable UI
userinterface: true
# Check for updates
CheckForUpdates: true
# Change pidfile name and path if needed
# PidFile: '/var/run/dzga.pid'

# Instantly create a public HTTPS URL. Don't have to open any port on router and do not require a reverse proxy.
# When ngrok_tunnel set to True the auth token is required to keep the tunnel alive.
# Create account at ngrok.com and paste the token in this file.
# Ngrok assigns random urls. When server restart the server gets a new url.
ngrok_tunnel: true
ngrok_auth_token: 1j******************9el1_d5DS899GvZaspqPf3SZ3

# Use SSL encryption in HTTP server if not using ngrok
use_ssl: false
ssl_key: # /path/to/privkey.pem
ssl_cert: # /path/to/fullchain.pem

# Login on Google Home app and configuration interface
auth_user: 'admin'
auth_pass: 'admin'

# Google Assistant Settings:
ClientID: 'clientid_from aog'
ClientSecret: 'clientsecret_from_aog'

# Domoticz Settings:
Domoticz:
ip: 'http://192.168.0.120'
port: '8080'
roomplan: '0'
username: 'toto'
password: '?***********?'
switchProtectionPass: '1234' #Set this to false if ask for pin function is not needed

# Report low battry
Low_battery_limit: 9

samourai47 wrote: ↑Saturday 31 October 2020 22:41 Hello
I don't undestand. All works fine for 3 days. I must reboot aund dzga dosen't work. I change nothing, juste update and upgrade my system
The probleme is when i set ngrok_tunnel : true

Imossible to log to UI dzga. If i set to false no soucy
My config

# Configuration:
port_number: 3030
# Debug, Info or Error
loglevel: 'Info'
# Set logtofile: 'false' logs will not show in the LOG tab. Set logtofile: 'Overwrite' or true Log file will be overwritten when dzga server restarts
# Set logtofile: 'Append' Logs will append to logfile when dzga server restarts
logtofile: false
# If pathToLogFile is commented, removed or set to '', logs will be saved in Domoticz-Google-Assistant folder
pathToLogFile: ''
# Enable or disable UI
userinterface: true
# Check for updates
CheckForUpdates: true
# Change pidfile name and path if needed
# PidFile: '/var/run/dzga.pid'

# Instantly create a public HTTPS URL. Don't have to open any port on router and do not require a reverse proxy.
# When ngrok_tunnel set to True the auth token is required to keep the tunnel alive.
# Create account at ngrok.com and paste the token in this file.
# Ngrok assigns random urls. When server restart the server gets a new url.
ngrok_tunnel: true
ngrok_auth_token: 1j******************9el1_d5DS899GvZaspqPf3SZ3

# Use SSL encryption in HTTP server if not using ngrok
use_ssl: false
ssl_key: # /path/to/privkey.pem
ssl_cert: # /path/to/fullchain.pem

# Login on Google Home app and configuration interface
auth_user: 'admin'
auth_pass: 'admin'

# Google Assistant Settings:
ClientID: 'clientid_from aog'
ClientSecret: 'clientsecret_from_aog'

# Domoticz Settings:
Domoticz:
ip: 'http://192.168.0.120'
port: '8080'
roomplan: '0'
username: 'toto'
password: '?***********?'
switchProtectionPass: '1234' #Set this to false if ask for pin function is not needed

# Report low battry
Low_battery_limit: 9

cd /home/${USER}/
sudo systemctl stop dzga #If service is running
source Domoticz-Google-Assistant/env/bin/activate
python3 Domoticz-Google-Assistant

samourai47 wrote: ↑Sunday 01 November 2020 21:06 somewhere i found this line

Ngrok was unable to start. Error: 'NgrokTunnel' object has no attribute 'replace' is not valid
But ngrock seems to be ok because he give a new url.

in config.yaml i writed
ngrok_tunnel: true
ngrok_auth_token: 1-------------------yrO9el1_d5DS899GvZaspqPf3SZ3

I don't understand

fraisdos125 wrote: ↑Friday 06 November 2020 9:07 Hi,

Trying to get working dzga on rpi4.
Few infos on the RPi4 setup:
- Domoticz 2020.2
- Octoprint
- Homebridge
- Plex server,
- Nextcloud,
- Dzga
- in fex others servers,...
- reverse proxy with ssl management through haproxy.

Everything works impressively good expect few issues with current on progress configuration of dzga.
I can get syncing data through google and dzga.

Log level to Debug, but no errors in it.
anyway I think there is an mistake with the oauth currently.
I did the following tests:
- https://[my public url]/smarthome ---> not supported
- https://[my public url]/oauth ----> response_type must equal "code"
- https://[my public url]/token ----> Page not found!: '/token'

If I replace "https://[my public url]/" to "http://localhost:3030/" I get the same replies.
Then I believe there is something wrong into my config.yaml or smart-homekey.json.
Nevertheless I did follow the wiki https://github.com/DewGew/Domoticz-Goog ... stant/wiki upto chapter 4 without apparent issue.

Here is the log:


2020-11-06 08:43:02 - INFO - Connecting to Domoticz on http://192.168.1.2:8080
2020-11-06 08:43:02 - DEBUG - Starting new HTTP connection (1): 192.168.1.2:8080
2020-11-06 08:43:02 - DEBUG - http://192.168.1.2:8080 "GET /json.htm?type=command¶m=addlogmessage&message=Connected%20to%20Google%20Assistant%20with%20DZGA%20v1.8.13 HTTP/1.1" 200 49
2020-11-06 08:43:02 - DEBUG - Popen(['git', 'version'], cwd=/, universal_newlines=False, shell=None, istream=None)
2020-11-06 08:43:02 - DEBUG - Popen(['git', 'version'], cwd=/, universal_newlines=False, shell=None, istream=None)
2020-11-06 08:43:02 - DEBUG - Starting new HTTPS connection (1): raw.githubusercontent.com:443
2020-11-06 08:43:02 - DEBUG - https://raw.githubusercontent.com:443 "GET /DewGew/Domoticz-Google-Assistant/master/const.py HTTP/1.1" 200 9029
2020-11-06 08:43:02 - DEBUG - <pid.posix.PidFile object at 0xb5cefe68> entering setup
2020-11-06 08:43:02 - DEBUG - <pid.posix.PidFile object at 0xb5cefe68> create pidfile: /run/user/1000/dzga.pid
2020-11-06 08:43:02 - DEBUG - <pid.posix.PidFile object at 0xb5cefe68> check pidfile: /run/user/1000/dzga.pid
2020-11-06 08:43:02 - INFO - ========
2020-11-06 08:43:02 - INFO - Started DZGA v1.8.13 server at port 3030
2020-11-06 08:43:02 - INFO -
2020-11-06 08:43:02 - INFO - Visit http://localhost:3030/settings to access the user interface
2020-11-06 08:43:02 - INFO -
2020-11-06 08:43:02 - INFO - =========
2020-11-06 08:43:02 - INFO - Visit the Actions on Google console at http://console.actions.google.com
2020-11-06 08:43:02 - INFO - Under Develop section, replace the fulfillment URL in Actions with:
2020-11-06 08:43:02 - INFO - https://[your public url]/smarthome
2020-11-06 08:43:02 - INFO -
2020-11-06 08:43:02 - INFO - In Account linking, set the Authorization URL to:
2020-11-06 08:43:02 - INFO - https://[your public url]/oauth
2020-11-06 08:43:02 - INFO -
2020-11-06 08:43:02 - INFO - Then set the Token URL to:
2020-11-06 08:43:02 - INFO - https://[your public url]/token
2020-11-06 08:43:02 - INFO -
2020-11-06 08:43:02 - INFO - Finally press 'SAVE' and then 'TEST' button
2020-11-06 08:43:02 - INFO - =======
2020-11-06 08:43:02 - DEBUG - Starting new HTTP connection (1): 192.168.1.2:8080
2020-11-06 08:43:02 - DEBUG - http://192.168.1.2:8080 "GET /json.htm?type=devices&plan=0&filter=all&used=true HTTP/1.1" 200 3606
2020-11-06 08:43:02 - DEBUG - {
"Je pars": {
"idx": 1,
"type": "Scene",
"state": "On",
"lastupdate": "2019-05-08 17:10:06",
"willReportState": true
}
}
Many other lines for each device without error.

any idea what to do ? I believe that as long as I don't get a good answer to http://localhost:3030/token, I will not go ahead. How to see what is blocking this ?
Is there any others redirections required than the following ones for the reverse proxy ?:
- https://[my public url]/smarthome
- https://[my public url]/oauth
- https://[my public url]/token

samourai47 wrote: ↑Thursday 05 November 2020 9:21 Sorry but i have an another question.
I have many temperature in my house. For example an is
Temperature du Salon with idx : 150
I want when i ask the temperature Goggle voice said :" La temperature du salon" est de 19°, and no just "La température est de 19°"

DewGew wrote: ↑Friday 06 November 2020 14:11
Those cant be a local ip. Need to be accessed from internet

samourai47 wrote: ↑Wednesday 04 November 2020 21:13 hello
I make some change on my domoticz devices. (add devices, add room....)
I update sync devices on dzga and i restart TEST on google console
And the modifications aren't visible in google home

Where is the problem? How is it possible to update rooms, divices etc etc

server {
    listen 83;
    listen [::]:83;
    server_name toto.duckdns.org;
    #change to match your address
    return 301 https://$server_name$request_uri;
}

server {
        listen 443 ssl;
        listen [::]:443 ssl;

        server_name toto.duckdns.org;
        #change to match your address

        ssl_certificate /etc/letsencrypt/live/toto.duckdns.org/fullchain.pem;
        #change to match your address
        ssl_certificate_key /etc/letsencrypt/live/toto.duckdns.org/privkey.pem;
        #change to match your address
        ssl on;
        ssl_session_cache  builtin:1000  shared:SSL:10m;
        ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
        ssl_prefer_server_ciphers on;

        location / {
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Scheme $scheme;
                proxy_pass http://192.168.0.120:3030; #Local ipno to dzga
                proxy_read_timeout  90;
        }
}




location /domoticz {
      rewrite ^/domoticz/?(.*) /$1 break;
      proxy_set_header Host $host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Scheme $scheme; 
      proxy_pass http://192.168.0.120:8080; #local ipno to domoticz
      proxy_read_timeout  90;
}
location /assistant {
      rewrite ^/assistant/?(.*) /$1 break;
      proxy_set_header Host $host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Scheme $scheme;
      proxy_pass https://192.168.0.120:3030; #local ipno to dzga
      proxy_read_timeout  90;
}

 2020-11-08 09:30:03.454 Error: WebServer(SSL) startup failed on address 0.0.0.0 with port: 443: bind: Address already in use
2020-11-08 09:30:03.455 Error: WebServer(SSL) check privileges for opening ports below 1024 

DAEMON=/home/pi/domoticz/$NAME
DAEMON_ARGS="-daemon"
#AEMON_ARGS="$DAEMON_ARGS -daemonname $NAME -pidfile $PIDFILE"
DAEMON_ARGS="$DAEMON_ARGS -www 8080"
DAEMON_ARGS="$DAEMON_ARGS -sslwww 443"
#DAEMON_ARGS="$DAEMON_ARGS -log /tmp/domoticz.txt"
#DAEMON_ARGS="$DAEMON_ARGS -syslog"