Domoticz-Google-Assistant (dzga) Topic is solved

[mark.sellwood]

I gave up with this and moved back to Controlicz.
Domoticz-Google-Assistant worked but I never managed to get DZGA-Flask working due to issues with nginx. Looking at GitHub this hasn't been updated for 8 months & the owner hasn't been active for some time also the group on Discord went quiet back in May.

[Filip]

I am working with DZGA since a very long time... All is working nice... I have one protected device... Initially working with Google Assistant worked fine: asking to switch the device generated the request to say the code... However since a few months, it doesn't work anymore: Google Assistant is asking for the code, but then cuts the conversation making it impossible to say the code. Hence the switching the device doesn't work anymore.
Somebody has the same?
I did not yet migrate to DZGA-Flask (see my open topic viewtopic.php?t=42671). So I ignore if the problem would be solved by using DZGA-Flask.
Thanks for your help!

[Filip]

From the docker-compose (/opt/dzga-flask/instance:/instance) and a quick look in the /opt/dzga-flask/instance, I understood that all the settings are kept in this location. Am I then also right that updating the docker image could also erase these files? Wouldn't it be better to keep these outside the docker environment? Like my domoticz "user data" is also on my pi home folder. Any advice is welcome...

[jpvaneijk]

Dear all,

I solved the below with a reinstall of the entire SD card on my Raspberry Pi5 on Bookworm. For completeness, also created a new smart-home-key.json with different IDs. I will leave the post for further reference. Thanx!

Hello people,

I have both Flask (DZGA) and Domoticz installed fine and the all the devices from Domoticz are in Flask's web interface.

In my Google Home app the login interface comes up and seems to connect however I get the following message which I have not had before with the same devices. See below.

No compatible devices were found in your [Test} Flask account
You may need to set up these devices with [Test} Flask first. If you have allready set up devices, they may not support Google Home. In other casus, devices may not be available due to a teporary error.
Please wait a few minutes and try again.

Does anyone have an idea why I can't connect or how to fix this?

Thanks in advance!

[heggink]

Has anyone managed to get dzga-flask running behind a reverse proxy (npm)? If so, what settings have you used for Authorization URL and Token URL in teh google the developer console?

[heggink]

Nvm, figured it out. Works really well now.

[waltervl]

Nvm, figured it out. Works really well now.

Would be nice how and what you have figured out. For the next one that needs to do this ...

[mark.sellwood]

That would be good, I gave up in the end as I couldn't work it out

[heggink]

Nvm, figured it out. Works really well now.

Would be nice how and what you have figured out. For the next one that needs to do this ...

You are right. In thought this was me being stupid and only just now figuring it out. I will post my config later. It's a bit of fiddling but it is worth it.

[heggink]

Here's what I did to get it to work:
Go through the setup in the wiki (https://github.com/DewGew/DZGA-Flask/wiki) up to setup actions on google
Go through these steps except for Actions on Google Console.
Rather than doing that section, look at https://github.com/DewGew/DZGA-Flask/issues/120 and follow the steps for the developer console (the wiki is outdated here) but, once done, continue with the wiki again (so you have enabled homegraph api, created teh service account and account keys, saved these in smart-home-key.json)
Then go back to the developer console again (as per issue 120) and ensure you have the right urls (you could have done that first time around btw). Mine (using a reverse proxy) are:
https://<your reverse proxy url>/oauth (auth url)
https://<your reverse proxy url>/token (token url)
https://<your reverse proxy url>/smarthome (could fulfillment url)

That did the trick for me. From then, I can add the service on google home again *search for the name you gave your dzga flask service), authenticate and all my devices were there again.

Happy to hlp.

Herman

[daniellejorge]

Is there any dummies guide for this???

I started reading and got stuck in the first requirements:

"Public IP
python >= 3.5
Make local deployment available trough HTTPS with valid certificate with one below:
Use ngrok for a secure SSL tunnel with valid public HTTPS URL
Configure reverse proxy with domain name and valid certificate using Lets Encrypt
SSL with own domain or dynamic DNS, require ssl key and ssl certficate"

Any guidance for that??? I've used homebridge the last years but now they're charging.

Any help is appreciated.

[klarf]

Hi,

I've recently encountered a problem because I wanted to change some devices in my Domoticz setup. My issue is that I can no longer add devices in DZGA.
I did some research on my end, but I didn't find a solution. However, I did find a workaround and might have some ideas for reproducing the bug.

I had to replace a Fibaro Z-Wave smart plug that broke down. I switched brands (Aerotec Smart Switch 7 in Zwave+), but I wanted to keep my consumption history. So, I carefully saved the kWh and wattage consumption in Domoticz. But by mistake, I deleted the rest of the old plug's settings, including the on/off button. No big deal, I thought... The new on/off button had a new IDX, 4375 instead of 1205. I added it to the plan used in DZGA and synchronized it there. I lost a device in DZGA. I tried renaming the plug to 4375 and changing the plug type, but nothing worked. I manually added it to the DZGA configuration file, but it deletes it during synchronization.

Since I use this outlet very often, I backed up the Domoticz database from before the removal of the 1205 On/Off button and replaced it with the new button, without changing the IDX, which therefore remains 1205. Everything works this way; I can synchronize in DZGA, and it doesn't lose it.

I tried creating a "dummy button" or older device with an IDX >2600, but it wasn't detected in DZGA (for example: IDX 2585 is recognized but not 2601).
I tried deleting the DZGA database, creating a new user, and changing the plane number in DZGA (and the 0 plan), but it didn't change anything

I've already done the same thing because the Fibaro sockets are not reliable at all, but I hadn't forgotten to keep the original IDX of the on/off socket (idx 1140).

Thank you in advance for your help, I really appreciate DZGA which truly simplifies the use of Google Home and Domoticz.

edit:

I looked, but I can't find any information on the IDX 2999, which is a smart plug.

However, I did find this, which seems strange to me:

Code: Select all

{
        "id": "OnOff_890",
        "type": "action.devices.types.OUTLET",
        "traits": [
          "action.devices.traits.OnOff",
          "action.devices.traits.Timer"
        ],
        "name": {
          "name": "Prise HT",
          "nicknames": [
            "Prise HT"
          ]
        },
        "willReportState": true,
        "attributes": {
          "maxTimerLimitSec": 7200,
          "commandOnlyTimer": true
        },
        "customData": {
          "check_state": true,
          "dzTags": false,
          "idx": "890",
          "domain": "OnOff",
          "protected": false
        },
        "roomHint": "Bureau",
        "notificationSupportedByAgent": false,
        "deviceInfo": {
          "manufacturer": "Domoticz",
          "model": "2023.2",
          "hwVersion": "1.0",
          "swVersion": "1.0"
        }
      },

Each device is running Domoticz version 2023.2, while I'm currently on 2025.2.

I even have this information in DZGA:

Code: Select all

About
DZGA-Flask Version: 24.10
Domoticz Version: 2025.2

This could correspond to devices running version 2023.2 or higher.

[klarf]

I tried to figure out where the problem was coming from.

By redoing the DZGA installation tutorial, I found the solution.

I'm using a different Domoticz user account in DZGA. I hadn't authorized all the devices on this account, which I only use for this purpose. That's why I only had old devices, which must date back to the installation of DZGA.

So it's not a big deal... I still see "Domoticz 2023.2" but everything works.