Domoticz-Google-Assistant (dzga) Topic is solved

[EddyG]

What is the use of those ntp file(s)? I don't think there is a ntp server running in the container.
Because of these files in the docker-compose.yaml file

Code: Select all

      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro

those files should exists with the right content in the filesystem of the Synology NAS.

[marsflow]

Hi,


the command "sudo systemctl start dzga" does not work anymore, I run it manually and it remains bugged on the command.

Code: Select all

pi@raspberrypi:~ $ sudo systemctl start dzga
(after 2 min press CTRL C)

pi@raspberrypi:~ $ sudo systemctl status dzga
● dzga.service - Domoticz-Google-Assistant Service
   Loaded: loaded (/etc/systemd/system/dzga.service; enabled; vendor preset: enabled)
   Active: inactive (dead)

and

sudo service dzga start (its good)

why ?

thank you

hello,

I installed an old package-list and the sudo systemctl start dzga command was working,
but mosquitto was not working

I have removed and installed mosquitto and it works again but the sudo systemctl start dzga command does not work,

someone has this problem?

[DAVIZINHO]

hello I have maybe a stupid question but important to me.
I have some "tasmota autodiscover" devices that write info in the description of the devices.
Information like this:
{
"Topic": "cmnd/Bu_Regleta_Impresora",
"Command": "POWER5",
"Device": "Schalter",
"Type": "5",
"Name": "Bu_Regleta_Impresora_Octo_Telefono 5"
}

But i need to push this adition info in the description:
<voicecontrol>
devicetype = outlet
</voicecontrol>

Do you know how i can write the both information in the description? if i push all. the tasmota autodiscover fails

[fabry91]

Hello everyone,

I'm having some problem to start DZGA on my RS815+ with docker.

I succesfully installed the DZGA docker but when I run "sudo docker-compose -f /volume1/${USER}/Domoticz-Google-Assistant/docker-compose.yaml up -d" it returns with this error:



The default_config file is in the config folder.

Thank you in advance

[fabry91]

Hello everyone,

I'm having some problem to start DZGA on my RS815+ with docker.

I succesfully installed the DZGA docker but when I run "sudo docker-compose -f /volume1/${USER}/Domoticz-Google-Assistant/docker-compose.yaml up -d" it returns with this error:



The default_config file is in the config folder.

Thank you in advance

Hello, merry christmas to all the Domoticz Family!

Anyone could please help me about this problem?

Thank you very much

[vodor]

Hello everyone,

I'm having some problem to start DZGA on my RS815+ with docker.

I succesfully installed the DZGA docker but when I run "sudo docker-compose -f /volume1/${USER}/Domoticz-Google-Assistant/docker-compose.yaml up -d" it returns with this error:



The default_config file is in the config folder.

Thank you in advance

Hello, merry christmas to all the Domoticz Family!

Anyone could please help me about this problem?

Thank you very much

Your docker cannot access the volume location you specified volume1. Check permissions and or try and move it to another location and confirm docker has permissions to read/write to it

[fabry91]

Hello everyone,

I'm having some problem to start DZGA on my RS815+ with docker.

I succesfully installed the DZGA docker but when I run "sudo docker-compose -f /volume1/${USER}/Domoticz-Google-Assistant/docker-compose.yaml up -d" it returns with this error:



The default_config file is in the config folder.

Thank you in advance

Hello, merry christmas to all the Domoticz Family!

Anyone could please help me about this problem?

Thank you very much

Your docker cannot access the volume location you specified volume1. Check permissions and or try and move it to another location and confirm docker has permissions to read/write to it

Hello, and thank you for your reply!

I've cheched all the permission under file station, I set all to "Full Control", the container starts but after some seconds it stops automatically.

[vodor]

I don't know the synology nas devices. I use a qnap myself but that error is pretty much a standard docker error when it cannot find and/or mount a volume. So I would go read up on that if I am you.

[fabry91]

I don't know the synology nas devices. I use a qnap myself but that error is pretty much a standard docker error when it cannot find and/or mount a volume. So I would go read up on that if I am you.

Have found some more error that seems related to this post on GitHub:

https://github.com/DewGew/Domoticz-Goog ... issues/205

here there is the complete log of the restarting of the container on Synology:

Spoiler: show

2021-12-31 10:17:41 stdout Upgrading Pip...
2021-12-31 10:17:41 stdout Pip requirements file detected!
2021-12-31 10:17:41 stdout OK: 208 MiB in 62 packages
2021-12-31 10:17:41 stdout fetch http://dl-cdn.alpinelinux.org/alpine/v3 ... DEX.tar.gz
2021-12-31 10:17:41 stdout Installing all APK requirements...
2021-12-31 10:17:41 stdout First run, checking for any requirements...
2021-12-31 10:17:37 stderr /entrypoint.sh: line 144: 16 Killed pip install $PIP_FLAGS --upgrade pip
2021-12-31 10:17:35 stdout Upgrading Pip...
2021-12-31 10:17:35 stdout Pip requirements file detected!
2021-12-31 10:17:35 stdout OK: 208 MiB in 62 packages
2021-12-31 10:17:35 stdout fetch http://dl-cdn.alpinelinux.org/alpine/v3 ... DEX.tar.gz
2021-12-31 10:17:35 stdout Installing all APK requirements...
2021-12-31 10:17:35 stdout First run, checking for any requirements...
2021-12-31 10:17:32 stderr /entrypoint.sh: line 144: 16 Killed pip install $PIP_FLAGS --upgrade pip
2021-12-31 10:17:31 stdout Upgrading Pip...
2021-12-31 10:17:31 stdout Pip requirements file detected!
2021-12-31 10:17:31 stdout OK: 208 MiB in 62 packages
2021-12-31 10:17:30 stdout fetch http://dl-cdn.alpinelinux.org/alpine/v3 ... DEX.tar.gz
2021-12-31 10:17:30 stdout Installing all APK requirements...
2021-12-31 10:17:30 stdout First run, checking for any requirements...
2021-12-31 10:17:28 stderr /entrypoint.sh: line 144: 16 Killed pip install $PIP_FLAGS --upgrade pip
2021-12-31 10:17:27 stdout Upgrading Pip...
2021-12-31 10:17:27 stdout Pip requirements file detected!
2021-12-31 10:17:27 stdout OK: 208 MiB in 62 packages
2021-12-31 10:17:27 stdout fetch http://dl-cdn.alpinelinux.org/alpine/v3 ... DEX.tar.gz
2021-12-31 10:17:27 stdout Installing all APK requirements...
2021-12-31 10:17:27 stdout First run, checking for any requirements...
2021-12-31 10:17:25 stderr /entrypoint.sh: line 144: 15 Killed pip install $PIP_FLAGS --upgrade pip
2021-12-31 10:17:24 stdout Upgrading Pip...
2021-12-31 10:17:24 stdout Pip requirements file detected!
2021-12-31 10:17:24 stdout OK: 208 MiB in 62 packages
2021-12-31 10:17:24 stdout fetch http://dl-cdn.alpinelinux.org/alpine/v3 ... DEX.tar.gz
2021-12-31 10:17:24 stdout Installing all APK requirements...
2021-12-31 10:17:24 stdout First run, checking for any requirements...
2021-12-31 10:17:23 stderr /entrypoint.sh: line 144: 15 Killed pip install $PIP_FLAGS --upgrade pip
2021-12-31 10:17:21 stdout Upgrading Pip...
2021-12-31 10:17:21 stdout Pip requirements file detected!
2021-12-31 10:17:21 stdout OK: 208 MiB in 62 packages
2021-12-31 10:17:21 stdout fetch http://dl-cdn.alpinelinux.org/alpine/v3 ... DEX.tar.gz
2021-12-31 10:17:21 stdout Installing all APK requirements...
2021-12-31 10:17:21 stdout First run, checking for any requirements...
2021-12-31 10:17:19 stderr /entrypoint.sh: line 144: 17 Killed pip install $PIP_FLAGS --upgrade pip
2021-12-31 10:17:16 stdout Upgrading Pip...
2021-12-31 10:17:16 stdout Pip requirements file detected!
2021-12-31 10:17:16 stdout OK: 208 MiB in 62 packages
2021-12-31 10:17:16 stdout Executing busybox-1.31.1-r9.trigger
2021-12-31 10:17:15 stdout (25/25) Installing linux-headers (4.19.36-r0)
2021-12-31 10:17:15 stdout (24/25) Installing libc6-compat (1.1.24-r3)
2021-12-31 10:17:13 stdout (23/25) Installing git (2.24.4-r0)
2021-12-31 10:17:13 stdout (22/25) Installing pcre2 (10.34-r1)
2021-12-31 10:17:13 stdout (21/25) Installing libcurl (7.79.1-r0)
2021-12-31 10:17:13 stdout (20/25) Installing nghttp2-libs (1.40.0-r1)
2021-12-31 10:17:13 stdout (19/25) Installing build-base (0.5-r1)
2021-12-31 10:17:13 stdout (18/25) Installing fortify-headers (1.1-r0)
2021-12-31 10:17:13 stdout (17/25) Installing make (4.2.1-r2)
2021-12-31 10:17:07 stdout (16/25) Installing g++ (9.3.0-r0)
2021-12-31 10:17:07 stdout (15/25) Installing libc-dev (0.7.2-r0)
2021-12-31 10:17:06 stdout (14/25) Installing musl-dev (1.1.24-r3)
2021-12-31 10:16:58 stdout (13/25) Installing gcc (9.3.0-r0)
2021-12-31 10:16:58 stdout (12/25) Installing mpc1 (1.1.0-r1)
2021-12-31 10:16:58 stdout (11/25) Installing mpfr4 (4.0.2-r1)
2021-12-31 10:16:58 stdout (10/25) Installing libatomic (9.3.0-r0)
2021-12-31 10:16:58 stdout (9/25) Installing libgomp (9.3.0-r0)
2021-12-31 10:16:57 stdout (8/25) Installing isl (0.18-r0)
2021-12-31 10:16:57 stdout (7/25) Installing gmp (6.1.2-r1)
2021-12-31 10:16:57 stdout (6/25) Installing file (5.37-r1)
2021-12-31 10:16:57 stdout (5/25) Installing libmagic (5.37-r1)
2021-12-31 10:16:56 stdout (4/25) Installing binutils (2.33.1-r1)
2021-12-31 10:16:56 stdout (3/25) Installing libstdc++ (9.3.0-r0)
2021-12-31 10:16:56 stdout (2/25) Installing libgcc (9.3.0-r0)
2021-12-31 10:16:56 stdout (1/25) Upgrading musl (1.1.24-r2 -> 1.1.24-r3)
2021-12-31 10:16:56 stdout fetch http://dl-cdn.alpinelinux.org/alpine/v3 ... DEX.tar.gz
2021-12-31 10:16:56 stdout Installing all APK requirements...
2021-12-31 10:16:56 stdout First run, checking for any requirements...

I also noticed that the file in "/usr/local/lib/" named "python3.7.3" does not exsist in that path

[wimmme]

Guys,

i really need help here. I have DZGA running for over a year now in a docker Container.
Now i want to move that container to another host, but for the love of God, i cannot get it to work.
The new container is up and running, I use the same smart-home-key.json, same docker-compose.yaml file.
If i delete the container and recreate it form scratch given the same files, it runs fine on the original host.
If i do that on the new host, container starts but always gives me a connection error:

Code: Select all

Connection to Domoticz refused! Check configuration.

But i connects just fine ! When looking at dzga.log it even retrieves the domoticz version:

Code: Select all

2022-01-11 16:39:09 - DEBUG - Starting new HTTP connection (1): 192.168.0.12:8080
2022-01-11 16:39:09 - DEBUG - http://192.168.0.12:8080 "GET /json.htm?type=devices&plan=0&filter=all&used=true HTTP/1.1" 401 91
2022-01-11 16:39:09 - DEBUG - Starting new HTTP connection (1): 192.168.0.12:8080
2022-01-11 16:39:09 - DEBUG - http://192.168.0.12:8080 "GET /json.htm?type=settings HTTP/1.1" 401 91
2022-01-11 16:39:09 - DEBUG - Starting new HTTP connection (1): 192.168.0.12:8080
2022-01-11 16:39:09 - DEBUG - http://192.168.0.12:8080 "GET /json.htm?type=command&param=getversion HTTP/1.1" 200 216
2022-01-11 16:39:09 - DEBUG - {
  "dzversion": "2021.1 (build 14018)"
}

Anyone an idea ? It's not in the part 'Actions on google' or my reverse proxy (nginx), i can switch those fine between the 2 running DZGA's.
Tried other Domoticz versions, other DZGA versions, all the same result.


UPDATE: nevermind, found it, it was the Domoticz password ... Removed and re-enabled it and BANG it works

[fabry91]

Hello, merry christmas to all the Domoticz Family!

Anyone could please help me about this problem?

Thank you very much

Your docker cannot access the volume location you specified volume1. Check permissions and or try and move it to another location and confirm docker has permissions to read/write to it

Hello, and thank you for your reply!

I've cheched all the permission under file station, I set all to "Full Control", the container starts but after some seconds it stops automatically.

Hello, anyone can help me to solve this problem about the pip installation failed?

This is what happend when I run

Code: Select all

docker-compose -f /volume1/docker/Domoticz-Google-Assistant/docker-compose.yaml up -d

via ssh on my Synology nas, the docker

[sander88]

I have just added dzga (V1.10.9) to my test setup. I have create simple light (virtual switch) in Domoticz and I can control it using Google Home. The status is not always in sync. I have 2 scenarios...

1. When I switch a light in Domoticz, the state is NOT instantly updated in the Google Home app. I have to manually refresh it (by doing a pull down of the scrollarea in the app).
2. When I switch the test light on or off using the Google Home app then the state is NOT always updated in Google Home, but the light is changed correctly in Domoticz. The state shows correctly in the Google Home after a manual refresh (by doing a pull down of the scrollarea in the app).

I'm not sure this is by-design or an issue in my setup. Can someone tell me what behavior is expected here?

Note that I use the iOS Google Home app. I have currently no access to an Android device.

[DAVIZINHO]

hell!.
Its posible to setup a blind in DZGA for speach the percentage of open or close?
If I setup the blind as windows, i can open and close with voice, but not perentage
Exist a specific type for a blinds??

thanks

[Flappie]

Did a clean install of Raspbian Buster, latest Domoticz stable and DZGA.
Tried to play a sound and getting this:

Page not found!: name 'cast' is not defined

Any ideas?

[heggink]

Over the weekend, I tried to install this. I get quite far but the moment I set use_ssl to true, nothing works. It doesn't matter whether using a docker approach (keeps restarting) or an direct installation (starts and then stops). As soon as I set it to false, I can access the settings page but then the google assistant won't authenticate the service as it needs ssl...

Any thoughts what I am doing wrong? I tried both the beta and master branch. This is on an RPI4.

[heggink]

Doing some fiddling, it seems like it IS working when I run everything by hand:

Code: Select all

sudo /home/pi/Domoticz-Google-Assistant/env/bin/python3 /home/pi/Domoticz-Google-Assistant/

Starting either the service or running from docker doesn't work. Both keep restarting.
Forgot to mention: there is nothing in the logs...

[wimmme]

I run it in docker, works great, just a bug when asking the temperature for a non thermostat device, that's not working.
my docker-compose.yaml:

Code: Select all

version: '3'
services:
  dz-googleassistant:
    image: dewgew/domoticz-google-assistant:latest
    container_name: domoticz-google-assistant
    environment:
      - PUID=1010
      - PGID=1010
    ports:
      - 3030:3030
    volumes:
      - ./config:/config
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
    

[heggink]

I run it in docker, works great, just a bug when asking the temperature for a non thermostat device, that's not working.
my docker-compose.yaml:

Code: Select all

version: '3'
services:
  dz-googleassistant:
    image: dewgew/domoticz-google-assistant:latest
    container_name: domoticz-google-assistant
    environment:
      - PUID=1010
      - PGID=1010
    ports:
      - 3030:3030
    volumes:
      - ./config:/config
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
    

What system are you on? I am starting to htink that my pi4 is what's causing the issues.

[EdwinK]

When I try to get this working

Apr 15 13:16:28 DomoServer systemd[1]: dzga.service: Service RestartSec=100ms expired, scheduling restart
Apr 15 13:16:28 DomoServer systemd[1]: dzga.service: Scheduled restart job, restart counter is at 10.
Apr 15 13:16:28 DomoServer systemd[1]: Stopped Domoticz-Google-Assistant Service.
Apr 15 13:16:28 DomoServer systemd[1]: dzga.service: Start request repeated too quickly.
Apr 15 13:16:28 DomoServer systemd[1]: dzga.service: Failed with result 'exit-code'.
Apr 15 13:16:28 DomoServer systemd[1]: Failed to start Domoticz-Google-Assistant Service.
~

I had it working, sort of, so that I could acces 192.168.0.11:3030/setting and could see the settings page, but not anymore. Safari gives an error that server unexpectedly closed the page. Chrome couldn't even locate the page.

I believre the problem started when I entered the api-key for ngrok.com

[EdwinK]

config.yaml

Code: Select all

 username: Edwin
Low_battery_limit: 9
PidFile: ''
auth_pass: Fire2010
auth_user: Edwin
loglevel: Info
logtofile: true
ngrok_auth_token: ****
ngrok_tunnel: true
pathToLogFile: ''
port_number: 3030
ssl_cert: ''
ssl_key: ''
use_ssl: false
userinterface: true

Edit: I removed the ngrok stuff and now I can access the settings page again. So, it seems I have done somethign wrong there. Guess it will be something for the weekend.