Mosquitto working but won't load devices

Configuration
1

Hello,

I searched the forum but didn’t find what I’m looking for. so I’m asking here, if you have any idea how to help me just point me in the right direction.

so I just installed my new hassio - raspberry pi system.
I got the mosquitto broker addon.
and it looks like my device can connect to it and probably send the data. But the problem is that I can’t seem to load the device information in my sensors page.

I can’t follow the BRuh videos because it looks like I can’t do the “apt get” or “sudo” commands in the new version because it’s in core ssh and not bash.

if you can help me load the devices it’ll be great.

This is the config.yaml mqtt part (That I’m not sure I even need but if I do please let me know what to put in it):

mqtt:
broker: 172.17.0.1

and this is my sensors.yaml:

  • platform: yr
  • platform: mqtt
    state_topic: “sensor/fats_temperature_small”
    name: “CFStorage”
    qos: 0
    unit_of_measurement: “°C”
  • platform: mqtt
    state_topic: “sensor/fats_temperature_big”
    name: “FFStorage”
    qos: 0
    unit_of_measurement: “°C”

The thing is that I can see the yr icon, but I can’t see the other 2.
Please help me and let me know what else you need to help me solve this faster.

Thanks in advance.

2

Are you using something to monitor the messages that your device is publishing? I use MQTT fx but there are others. Sometimes it’s thing like leading / or _ vs -

3

I’m not, it used to work fine… but since the last update something went wrong…

do you have any guide for how to use this MQTT fx software?
Thanks again in advance.

4

I think you may be experiencing this issue

5

I had hassbain before, and that is sort of what happened to me, so I reinstall HASSio now… but forgot to save the config files… so I’m starting from nothing…

managed to get the MQTT to work because my esp node is connected to the server and submitting the data. I just can’t seem to fine the mistake in the config.yaml so it won’t show on the screen…

not sure what to do.

6

How is the message being published? Maybe you need a value_template in your configuration?
value_template: ‘{{ value_json.temp }}’

7

Yes, because of this:

why are you using that IP?

8

just what I saw on the internet…

since I posted this I made changes and it still doesn’t work.

9

@cyn it doesn’t work. how can I see what is being submitted? with the software you mentioned.
do you have a guide for me to work with?
Thanks again for the help.

10

just heading out but quickly…
google mqtt.fx
download onto your PC, connect to your broker
subscribe to everything using #
look at the transactions coming across

11

the IP address should be the IP address of your broker

12

ok it looks like I could connect to the broker.
but my node sends data and I can’t seem to see anything. where should I see the payload?

13

your devices have to send the data TO THE BROKER. What broker address are your sensors using? You would see the payload on the broker if the devices were sending data to it.

14

ok so the node and me uses the same address with the same username and password. we both manage to connect because I have a log of the connection both on the broker and on the node.

the things is that I didn’t change how the sketch of the esp-node worked, only the ip and the other configurations. and it worked before the update broke it… :frowning:

15

if you subscribe to # on your mqtt client application (mqtt.fx?) you should see ALL the topics your devices are logging to.

16

I subscribed to the # channel on the software.
but I see nothing, and if I publish something I still see nothing.
I even restarted the broker on the hassio.

17

so what do your logs for your broker say?

18

[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] 00-banner.sh: executing…

Hass.io Add-on: MQTT Server & Web client v0.1.1
Mosquitto MQTT Server bundled with Hivemq’s web client
From: Community Hass.io Add-ons
By: Franck Nijhof [email protected]

armhf / HassOS 1.12 / HA 0.82.0 / SU 139 / stable

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing…
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing…
INFO: Password is NOT in the Have I Been Pwned database! Nice!
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-patches.sh: executing…
patching file /app/index.html
[cont-init.d] 11-patches.sh: exited 0.
[cont-init.d] 20-mqtt_broker.sh: executing…
INFO: Adding configuration for MQTT Server…
[cont-init.d] 20-mqtt_broker.sh: exited 0.
[cont-init.d] 21-mqtt_web.sh: executing…
[cont-init.d] 21-mqtt_web.sh: exited 0.
[cont-init.d] 40-nginx.sh: executing…
Adding password for user Sagi
[cont-init.d] 40-nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Starting mosquitto MQTT Server…
1542301120: mosquitto version 1.4.15 (build date 2018-03-04 15:35:59+0000) starting
1542301120: Config loaded from /opt/mosquitto.conf.
1542301120: Opening ipv4 listen socket on port 1883.
1542301120: Opening ipv6 listen socket on port 1883.
INFO: Starting NGINX for the MQTT client…
1542301120: New connection from 10.0.0.89 on port 1883.
1542301120: New client connected from 10.0.0.89 as 2b5de1e8d9f44fc6bd0db0324083e871 (c1, k60, u’Mansensors’).
1542301123: New connection from 10.0.0.15 on port 1883.
1542301123: New client connected from 10.0.0.15 as ESP8266Client (c1, k15, u’Mansesnsors’).

I hope it’s clear enough…

19

ok so I don’t know what I did but right now I can see the devices on the hassio page… but I don’t see the values. what does it mean now?

again thank you both for the help!

20

When you are setting up your sensors, make sure EVERY device has a UNIQUE client ID. If you leave it as ESP8266Client for every device, MQTT loses its shit.

You see the devices because you configured sensors. You can’t see the values because they arent showing up on the message bus (mqtt)