Yasdi and/or yasdi2mqtt

[marcvl64]

If install the yasdi2mqtt container with docker-compose, will the container also include the yasdi prerequisite or should i set up a separate container for yasdi?

[pkwagner]

Yes, yasdi and all of its requirements are packed inside the container - so you should be good to go!

[marcvl64]

Great thank you. I installed everything, but I'm getting following error:
WARN src/mqtt_client.c:108: Unknown error while connecting to mqtt broker (status: -1). Going to retry in 10 seconds...

I verified MQTT is running and other containers (rtl433tomqtt) are successfully sending messages that are picked up by Home Assistant. The configuration is very basic, just running on localhost, without username/password, so as simple as can be.

Any suggestions on how to troubleshoot this further?

Marc

[dalklein]

try testing mqtt separately if this is the first use of mqtt. mosquitto can publish and subscribe to messages to check that it's working.

[marcvl64]

Yes, as I mentioned, mqtt is running fine. I use it to publish messages from 433Mhz sensors (using rtl433tomqtt). I wrote a script on Home Assistant that will do autodiscovery of these sensors. Im using mosquitto_sub to check that messages are flowing back and forth, so I’m sure mqtt is operating properly.

[pkwagner]

Hm, that sounds odd. What happens if you attach to the yasdi2mqtt container (using something like (docker exec -it <container_name> /bin/sh) and try to run mosquitto_sub there (the package should be installed)?

Did you double-check the credentials and SSL certificates? Also, you may try to connect to a public test server.

[marcvl64]

Ok, so a few results:
1/ mosquitto_sub is not found when attaching the container. I can run perfectly from my login shell. But it's not available to the container. While mosquitto runs in its own container, I installed mosquitto-clients directly from the login shell.
2/ I'm not using any credentials or SSL certificates
3/ while i had the container attached, it tried yasdishell and was able to find my inverter (SI6048UM SN:xxxxxxxx) but it reported 'no spot channels available' (with 'a'). --- CORRECTION: tried it again and it now shows 142 spot channels available. Yay!!
4/ then i modified docker-compose to point to test.mosquitto.org. That worked fine
5/ it took a few minutes before the system reported the device was online. then a few minutes firing 'event 3' and downloading channel list. and now it fired event 2 and starting device value fetch.... 10 minutes later ... still looping

[pkwagner]

Perfect, then you've probably reached the goal! It's quite normal for the device data download to take a few minutes, that's why I added persistence for the data folder to docker-compose.yml. If it's fetching data multiple times in a row without producing errors in between, that's a good sign that everything went fine. If I recall correctly, if everything succeeds, no other MQTT log outputs are emitted.

So the only missing bit seems to be the MQTT configuration for your personal broker. The two hazards that come to my mind are SSL or authentication problems. Do you use one of these?

[marcvl64]

No, i'm not using any SSL or authentication.

[pkwagner]

Hm... Have you then double-checked that you've deleted the MQTT_USER and MQTT_PASSWORD entries from the docker-compose.yml file? Does your mqtt broker maybe provide some connection failure logs?

[marcvl64]

this is what yasdi2mqtt reports as MQTT configuration:

yasdi2mqtt      | 17:45:05 INFO  src/main.c:42: Configuration | MQTT_TOPIC_PREFIX = solar/inverter
yasdi2mqtt      | 17:45:05 INFO  src/main.c:43: Configuration | MQTT_SERVER = localhost
yasdi2mqtt      | 17:45:05 INFO  src/main.c:44: Configuration | MQTT_PORT = 1883
yasdi2mqtt      | 17:45:05 INFO  src/main.c:45: Configuration | MQTT_SSL_CERT = (null)
yasdi2mqtt      | 17:45:05 INFO  src/main.c:46: Configuration | MQTT_QOS_LEVEL = 2
yasdi2mqtt      | 17:45:05 INFO  src/main.c:47: Configuration | MQTT_USER = (null)
yasdi2mqtt      | 17:45:05 INFO  src/main.c:48: Configuration | MQTT_PASSWORD = (null)

that all looks good. My docker-compose.yml does not have any user or password entries. Finally, I checked the mosquitto logs and it shows successful connections from other apps (rtl4332mqtt and ha), but no entry that relates to yasdi2mqtt. No failure or success in the logs. Nothing.

[marcvl64]

It's really weird. I tried entering ip address 127.0.0.1, tried localhost, tried raspberrypi.local, nothing works. Tried entering a completely fake name 'blabla' and getting exactly the same error.
I tried to use MQTT_explorer from another machine on my local network to see if there is anything weird, but don't see any issues. MQTT_explorer connects fine, and shows both homeassistant and rtl_433 connected and sending messages.

[pkwagner]

Ah, that could be the problem. If you're using Docker, it's spanning a completely new subnetwork, so that localhost or 127.0.0.1 don't refer to your local host, but rather to the very yasdi2mqtt container. I'm not sure about raspberrypi.local, in theory this one should get resolved - but sometimes Docker messes up with DNS a bit.

So you could try to insert the IP address of your Raspberry Pi. Another idea would be to start the container using the host network - which should allow the use of localhost.

[pkwagner]

Oh, and if that doesn't help, you could also try setting the following additional environment variables in the compose file:

MQTT_C_CLIENT_TRACE=ON
MQTT_C_CLIENT_TRACE_LEVEL=PROTOCOL

Both come from paho (the underlying MQTT library) and should hopefully make the errors a bit more detailed.

[marcvl64]

adding host network did the trick. I modified my docker-compose.yml as follows:

services:
  yasdi2mqtt:
    ....
    network_mode: host

Everything is working great. Thanks so much for your help. Weird that I didn't have to do this for the homeassistant and rtl4332mqtt containers.

[pkwagner]

Amazing, great to hear!