Domoticz

Hello,

I am gladly still using mydomoathome for my Imperhome interface. However when trying to upgrade to domoticz 2023.2 I notices a lot of log entries about a depreciated format seeming to come from mydomoathome. Look at the Github page it seems epierre / empierre is aware of this, but I am not sure if there is an update for mydomoathome to work with domoticz 2023.2 stable.

I enjoy having the program so stick to domoticz 2022.2 for now. If there is an update, please let me know

Thank you.

Hello, so someone is suing it still I'll look to see if I can upgrade to the new and not backward compatible API of Domoticz

Thank you so much epierre! I will definitely appreciate it. I did not realize it will not backwards compatible and that this results in more management work for you. I am sure there will be more people appreciating this upgrade

Hello,

New 0.3.1 version from this week-end with fixes on:
- domoticz API
- nodejs changes
- docker image upgraded as well as nodejs version
- dockerhub image

Hello,

New 0.3.6 with API fixes

https://e-nef.com/domoticz/mdah/node-my ... -0.3.6.deb

I have until today imperihome lite 3 0 11 with imperi home pro 2 0 1 on my phone with mdah 0 2 41
Upgrade domoticz broke everything so i upgraded mdah to 0 3 6 and its working fine, main and devices page work as it shut be, but imperihome stop seeing devices on phone. Not a single one.
What is the correct version of imperi to work with mdah 0 3 6 and where to find it? When i download 4 3 17 i can't get to login to it. Evertygo servers not working
node 12 22 12
npm 6 14 16
mdah work on ubuntu.

Added:
in imperi config when i go to configuration wizard i have System found MyDomoAtHome message

Hello,

Try refreshing imperihome first, then if it is on port 3002, try

Http://myserver:3002/devices

Do you see your devices ?

yes i did that- dashboards without devices and on flat devices list no rooms and devices at all exept cameras configured directly in imperi.
I wrote previously - "main and devices page work as it shut be" - devices page work on 3002 port /devices
{"devices":[{"id":"S0","name":"MyDomoAtHome","type":"DevGenericSensor","params":[{"key":"Value","value":"0.3.7","unit":"","graphable":"false"}]},{"id":"SC1","name":"All Off","type":"DevScene","room":"Scenes","params":[{"key":"LastRun","value":1639748191000}]},{"id":"SC4","name":"Brama Otwórz","type":"DevScene","room":"Scenes","params":[{"key":"LastRun","value":1700240255000}]},{"id":"SC7","name":"Salon Off","type":"DevScene","params":....

Me I am in 3.0.11 and it is fine

I think i have something. Imperi connect only via remote, Local not working because current SSID is unknown for imperi app.
When i connected via rproxy by chrome or by Imperi i have error on devices page
"Please add this gateway in Setup/settings/Local Networks","type":"DevGenericSensor","room":"Utility"
So I added rproxy adres to domoticz local subnet and added 127.0.0.1 and still not working Any Ideas?

Edited:
When in connection i remove external link it still not working
but when i remove external link and remove login and password, imperi connects and see devices.
user nad pass is for rproxy only and its deferent from users and pass used normally in domoticz.

New domiticz imposes a login, I use the nopasswww option during dz srartup

ok but I also use domoticz app on other phones and sending it via Rproxy that add https and cert. And i need users and password from domo to recognize users. It still be working with that switch? I don't think so.

Edit:
Strange. When i use mdah address with basic auth http://aaa:[email protected]:3002/devices/ it works in chrome and i see devices
So why when i wrote only username and password in imperi a can't see devices and have in utils please add this gateway in setup... and adres http://aaa:[email protected]:8080/json.htm...
External api url is empty.
why this have different behavior? If domoticz see basic auth and want to autorize why this works via browser?

Edit2: when i connect via browser to rproxy to MDAH i see in {"devices":[{"id":"S00","name":"Unable to connect to Domoticz","type":"DevGenericSensor","room":"Utility","params":[{"key":"Value","value":"http://aaa:[email protected]:8080/json.htm"}]},{"id":"S01","name":"Please add this gateway in Setup/settings/Local Networks","type":"DevGenericSensor","room":"Utility"}]}
Maybe if you pass access to domoticz api via http://10.10.0.42:8080/json.htm without passing username and pass from rproxy?

I enabled in domoticz basic auth to api in security but it changes nothind:(

How to configure in config.json interface to bind mydomoathome?
I installed docker on domoticz serwer and mydomo bind to one of docker interface

tcp 0 0 172.17.0.1:3002 0.0.0.0:* LISTEN off (0.00/0/0)

Hello,

if you are going through docker, internal port is 3002, by default exposed as 3002

on command line this should be:
docker run --name=mdah --env DOMO="http://your_ip:8080" --env TZ=Europe/Paris -p 3002:3002 epierre/mdah

No i have mdah installed on base system and after adding docker it started to binding to docker interface and on normal interface is not visible.

a docker always use an internal interface to bind to the outside, here 0.0.0.0 means any

But netstat is from base system. MDAH is INSTALLED on base system and work many years. I installed docker and MDAH is not working because base system now have 2 interfaces eth0 and docker0 and MDAH after stop and start bind to docker0 interface with ip 172.17.0.1 not eth0 interface with ip 10.10.0.42 from my home network.

netstat show that only one listen 3002 is on docker interface.
root@domoticz:/home/domo/domoticz# netstat -ano | grep 3002
tcp 0 0 172.17.0.1:3002 0.0.0.0:* LISTEN off (0.00/0/0)
root@domoticz:/home/domo/domoticz#

So, what I can write in mdah config to tell him to bind eth0 and not docker0?
This is problem with multiple network interface not with docker at all.

maybe some ideas there: https://community.synology.com/enu/forum/1/post/145037

but on a PC when I run the docker with the above CLI it works on http://system_ip:3002/

Hello Epierre,

I would just like to express my thanks for implementing my request so fast. I was able to update both domoticz and mydomoathome to version 3.6 without any issues. In addition compared to the version I came from it seems to use less computing power.

Thanks again from a very happy user

OK, thanks for help. I manage to run mydomoathome on docker and with version 3.5 currently in docker image its working locally and remote with remote proxy on newest domoticz stable version.