Hey, sorry that I didn’t have the time to reply to your direct message - It’s better suited here anyway.
However, the reply would just have been the same as here: I do not use ezr2mqtt in add-on mode because I run it natively on my machine. The add-on build file is for the user’s convenience only.
Because of the lack of time, I do not have any intention in supporting add-on mode or adding it to any add-on store. See also Möhlenhoff Alpha 2 - climate controller - #53 by andyboeh
Well, first thanks for your answer.
So the Installation Instructions I found are not correct. I was already a little bit confused, as I had read your post, that you don’t have time to build an addon. (Wich I fully respect)
However, maybe you can guide me a little bit how to set it up separately on my ordroid ( I bought the deluxe bundle)?
I would really love to get it worked, but I have no idea, how I can run the Ezr2mqtt on my ordroid, respectively how to set it up, that it will run automatically (sorry, I am quite a newbie on homeassistant)
So far I have created a folder Ezr2mqtt inside of /config/addons and have place the Ezr2mqtt.yaml inside /config.
The yaml has the correct IPaddress of my Alpha2 and the domainname of the Mqtt Broker (mosquito) which I integrated into home assistant.
But nothing happens
So far I use http-requests in node-red to get the states out of the alpha2, but I can’t figure out how to send something in. For that I would prefer your solution.
Best regards
Karl
Which installation instructions?
The first thing you have to understand is that add-ons are just regular software programs that run in a docker container and are controlled by Home Assistant. For ezr2mqtt, this means: ezr2mqtt is a stand-alone application that talks to the Alpha 2 on one end and MQTT on the other end. Hence, you can easily run it completely separate from Home Assistant - and this is what I do since I use the Home Assistant docker container.
Basically, you have to (on any Linux machine!):
./ezr2mqtt.pyIf everything works, you can use the provided ezr2mqtt.service-file to start it via systemd.
From github
That’s what I have done so far, including adapting the ez2qtt.yaml to my configuration (IP of Alpha2 and domain of the mosquito browser)
Where do I find the Ezr2mqtt.config? And (most important) how do I run the ./ezr2mqtt.pay?
Did you then see the new “Local Add-On Repository” including this add-on in your Supervisor? Did you start the add-on and have a look at the log file? If the local add-on repository does not show up, you need to fix this first. See for example here: Tutorial: Making your first add-on | Home Assistant Developer Docs (I followed this tutorial when I added add-on supported and tested it once in a Virtual Machine with HassOS).
I thought you were not running HassOS. In Add-On mode, this is not required.
Thanks, I will look into this, seems I have to learn a lot 
Well, finally!
The issue has been, that I created the addon Folder using the file editor. However with the file editor it seems I cannot access the correct level to installthat folder.
I now connected via ssh and found the folder on root level, copied everything in this folder nd now it shows up.
I could install the addon, however so far I can’t see any related integration. I hope I figure out how too as well.
Thanks a lot for your help and patience with a newbie
Ok, here I am again,
I adapted the ezr2mqtt.yaml to my ip addresses and started the ezr2mqtt and the mosquito plug in. However, none diverse show up.
In the mosquito broker I get following protocol
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] mosquitto.sh: executing...
[15:58:45] INFO: SSL is not enabled
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[15:58:45] INFO: Starting NGINX for authentication handling...
[15:58:46] INFO: Starting mosquitto MQTT broker...
1635778726: mosquitto version 1.6.12 starting
1635778726: |-- *** auth-plug: startup
[15:58:46] INFO: Successfully send discovery information to Home Assistant.
[15:58:47] INFO: Successfully send service information to the Supervisor.
1635778726: Config loaded from /etc/mosquitto/mosquitto.conf.
1635778726: Loading plugin: /usr/share/mosquitto/auth-plug.so
1635778726: ├── Username/password checking enabled.
1635778726: ├── TLS-PSK checking enabled.
1635778726: └── Extended authentication not enabled.
1635778726: Opening ipv4 listen socket on port 1883.
1635778726: Opening ipv6 listen socket on port 1883.
1635778726: Opening websockets listen socket on port 1884.
1635778726: Warning: Mosquitto should not be run as root/administrator.
1635778726: mosquitto version 1.6.12 running
1635778726: New connection from 127.0.0.1 on port 1883.
1635778726: Socket error on client <unknown>, disconnecting.
1635778728: New connection from 172.30.33.3 on port 1883.
1635778728: New client connected from 172.30.33.3 as auto-6605ED7D-6FFC-3512-7698-8F78E6758477 (p2, c1, k60).
1635778729: New connection from 172.30.32.1 on port 1883.
1635778729: New client connected from 172.30.32.1 as 4I2jI7FKZ3IZL7x3X0n1xI (p2, c1, k60).
1635778766: New connection from 172.30.32.2 on port 1883.
1635778766: Socket error on client <unknown>, disconnecting.
1635778886: New connection from 172.30.32.2 on port 1883.
1635778886: Socket error on client <unknown>, disconnecting.
1635779007: New connection from 172.30.32.2 on port 1883.
1635779007: Socket error on client <unknown>, disconnecting.
1635779127: New connection from 172.30.32.2 on port 1883.
1635779127: Socket error on client <unknown>, disconnecting.
1635779247: New connection from 172.30.32.2 on port 1883.
1635779247: Socket error on client <unknown>, disconnecting.
1635779367: New connection from 172.30.32.2 on port 1883.
1635779367: Socket error on client <unknown>, disconnecting.
1635779487: New connection from 172.30.32.2 on port 1883.
1635779487: Socket error on client <unknown>, disconnecting.
1635779607: New connection from 172.30.32.2 on port 1883.
1635779607: Socket error on client <unknown>, disconnecting.
1635779727: New connection from 172.30.32.2 on port 1883.
1635779727: Socket error on client <unknown>, disconnecting.
1635779847: New connection from 172.30.32.2 on port 1883.
1635779847: Socket error on client <unknown>, disconnecting.
1635779964: New connection from 172.30.32.1 on port 1883.
1635779964: New client connected from 172.30.32.1 as 2Y0q3fkzmaCzbtY3yjNs0j (p1, c1, k60).
1635779964: Client 2Y0q3fkzmaCzbtY3yjNs0j disconnected.
1635779967: New connection from 172.30.32.2 on port 1883.
1635779967: Socket error on client <unknown>, disconnecting.
1635780087: New connection from 172.30.32.2 on port 1883.
1635780087: Socket error on client <unknown>, disconnecting.
1635780095: Socket error on client auto-6605ED7D-6FFC-3512-7698-8F78E6758477, disconnecting.
1635780141: New connection from 172.30.33.3 on port 1883.
1635780141: New client connected from 172.30.33.3 as auto-E7B018B9-20E5-0486-FB62-FDD8F9A5DC64 (p2, c1, k60).
1635780157: Socket error on client 4I2jI7FKZ3IZL7x3X0n1xI, disconnecting.
1635780169: New connection from 172.30.32.1 on port 1883.
In ezr2mqtt addon I do get the following protocol
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Subscribed: 5 (128,)
Subscribed: 6 (128,)
Subscribed: 14 (128,)
Subscribed: 15 (128,)
Subscribed: 23 (128,)
Subscribed: 24 (128,)
Subscribed: 32 (128,)
Subscribed: 33 (128,)
Subscribed: 41 (128,)
Subscribed: 42 (128,)
Subscribed: 50 (128,)
Subscribed: 51 (128,)
is anyone able to flag what the problem might be?
Looks fine from the ezr2mqtt side - “Subscribed” means that it connected to MQTT and set up the discovery structures etc.
Did you also add the MQTT integration in Home Assistant? Does it work? Do devices show up?
In my integrations I do see the mosquito MQTT broker. When I click on Konfiguration there is not a lot to configure and I actually don’t know what I could/should change here.
Beside this I don’t see any devices related to my alpha2
You should see “MQTT”, not the broker. This integration needs to connect to your broker which, as I assume, is another add-on you are using. Check Home Assistant’s log file if the MQTT integration works. You can also try to publish something from the integration’s configuration page and use any MQTT browser (like MQTT.fx) to check if it works. In the MQTT browser, you should also see the Alpha 2 topics.
Sorry, yes in integrations I do see MQTT, which is configured with the host-Name of the mosquito-Mqtt broker addon (core-mosquitto)
However no entities show up
Well, I just assumed that I have to install the mosquito-Mqtt broker, I also used this Hostname (core-mosquitto) in the ezr2mqtt.yaml, is that correct?
Anyone any idea?
I don’t have a clue, what’s the reason I can’t see the entities. However, it might be related to 2 questions I have:
I am aware that I probably making some basic mistakes and probably even don’t ask the correct questions.
However, I am working with HA now since a few weeks only. I already learned a lot, but obviously not enough
Thanks for any help
ad 1. Yes of course! The broker is the MQTT server, both HA and ezr2mqtt need to connect to it!
ad 2. That depends on your system configuration. Only you can answer that.
I already told you to use an MQTT browser like MQTT.fx to check if the topics are published.
I am sure, I am missing something basic, but I can’t find out. Some of my settings, below
Thanks for your patience and help
Karl
My ezr2mqtt.yaml looks like
ezr:
- host: 192.168.177.xx
name: Erdgeschoss
prefix: eg
matt:
host: core-mosquitto
port: 1883
debug: false
username:
password:
discovery prefix: homeassistant
topic: alpha2
general:
interval: 30
My mosquito broker Settings are
logins: [ ]
customize:
active: false
folder: mosquitto
certfile: fullchain.pem
keyfile: privkey.pem
requir_certificte: false
Netzwerk
Container Host Beschreibung
1883/tcp
Normal MQTT
1884/tcp
MQTT over WebSocket
8883/tcp
Normal MQTT with SSL
8884/tcp
MQTT over WebSocket with SSL
I repeat myself once more: Use an MQTT browser like MQTT.fx to check if you can connect to your broker and if the topics are published. This way, you can also find out if Home Assistant and/or ezr2mqtt are able to connect to the broker. Then you know at least where the problem is.
Nun, das Mqttool ist nach meinem Verständnis auch ein entsprechender Browser, aber ich werde mal meinen Mac hochfahren (nutze eigentlich nur iPad) und den Mqtt.fix installieren
This is an English speaking community. Please post in English.
I overread that you tried it with MQTTOOL:
If there are none, then neither Home Assistant nor ezr2mqtt connect properly to your broker.
I just set up HaOS in a virtual machine and wrote detailed installation instructions for add-on mode: Installation on HaOS · andyboeh/ezr2mqtt Wiki · GitHub