I think it is useful to make a dedicated topic wrt migration from dzga to DZGA-Flask.
I have a specific question: is it possible to stop dzga and switch to DZGA-Flask without any other changes needed?
* I have currently dzga running on a RPI as a service. Domoticz is running on the same RPI.
* I installed DZGA-Flask through docker on another RPI . I used the same Smart-home-key.json, uploaded in DZGA-Flask. I am also using the domoticz user/password as in dzga. The separate RPI is only temporarily. Once tested, I will move it to the RPI running dzga & domoticz.
* I have a Reverse Proxy running on a NAS that proxies a server name "dzga.xxx.com" to the internal IP address; the server name is also used in Actions on Google, so no fixed IP addresses...
DZGA-Flask is running well, I have the devices synchronized with Domoticz... I updated the Reverse Proxy to use the IP address of DZGA-Flask (instead of IP address of dzga) and I can use the Reverse Proxy from a browser to open the DZGA-Flask UI... So DZGA-Flask is working fine...
But when using then Google Assistant (to switch on a lamp or even to sync the devices), Google Assistant reports back that "mijn domotica" [name of my application
] cannot be reached. While it uses the server name and the Reverse Proxy routes it through the RPI with DZGA-Flask.So I was wondering if I can simply switch from dzga to DZGA-Flask without relinking the services "mijn domotica" in my Google Home settings? Or is it just mandatory to relink (or remove and link again) the service? And do we also the reason why? As I just changed the "backend" from dzga to DZGA-Flask... Setting back the Reverse Proxy to the IP of dzga, all is working fine again...
And a small side-question... In dzga it was possible to define the port number (using it as a service)... I didn't found anymore this possibility in DZGA-Flask... I see also that this is "hardcoded" in the docker configuration Is a change of port number no longer supported?
Thanks for your feedback!
Filip