Aqara temp sensors show unavailable in HA but works in zigbee2mqtt

Third party integrations
,
#1

Hi all,
I just installed a new HA and a new Raspberry pi 4 with a CC26X2R1 card for zigbee2mqtt. The zigbee2mqtt seems fine, i get data from the sensors but in HA all show unavailable.
See data from the sensors (data which I can view also with mqqtexplorer)

This is zigbee2mqtt config

And this is how I see on all sensors in HA (so basically I see the sensors but not their data)

Any idea what I miss or did wrong on the setup?
Thank you very much

L.E. this is mosquitto broker config from HA

 logins: []
 customize:
   active: false
   folder: mosquitto
 certfile: fullchain.pem
 keyfile: privkey.pem
 require_certificate: false
#2

hi
any log in H.A (about mqtt) ?
sometimes sensors take ± 30 minutes to report states if the temp/humidity does not move a lot

#3

I don t see something helpfully in the log but I just warm up 2 sensors and I see I get data in zigbee2mqtt status about new temperatures but HA is like does not see them. I guess once pi send these to mqtt then HA should get them,

#4

yes it should…
hassio read mqtt
why your do not? see mqtt logs if clients are all connected or not.
have you other mqtt working devices (within hassio)?

#5

No other mqtt devices …where are the logs you talk about? I guess are somewhere in HA
At some point yesterday started to work and now after more than 24 hours I have again unavailable …meanwhile did nothing to any system…so something is happening

Ok, I used terminal adn subscribed to ‘homeassistant/#’ topic .
While in zigbee2mqtt service status I see messages sent to that topic with sensors and data, in HA console I see only
Client (null) sending PINGREQ
Client (null) received PINGRESP

That means the messages from zigbee2mgtt does not arrive in HA?
I also restarted both zigbee2mgtt and HA and same result

#6

Add this to configuration.yaml :


logger:
  default: error
  logs:
    homeassistant.components.mqtt: debug

Restart HA en post the log.

#7

I added your conf and restarted HA. Then go to Supervisor → Mosquito → Log

[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... 
[21:29:02] INFO: Setting up user mqtthass
[21:29:02] 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.
[21:29:02] INFO: Starting NGINX for authentication handling...
[21:29:03] INFO: Starting mosquitto MQTT broker...
1633717743: mosquitto version 1.6.12 starting
1633717743: |-- *** auth-plug: startup
1633717743: Config loaded from /etc/mosquitto/mosquitto.conf.
1633717743: Loading plugin: /usr/share/mosquitto/auth-plug.so
1633717743:  ├── Username/password checking enabled.
1633717743:  ├── TLS-PSK checking enabled.
1633717743:  └── Extended authentication not enabled.
1633717743: Opening ipv4 listen socket on port 1883.
1633717743: Opening ipv6 listen socket on port 1883.
1633717743: Opening websockets listen socket on port 1884.
1633717743: Warning: Mosquitto should not be run as root/administrator.
1633717743: mosquitto version 1.6.12 running
1633717743: New connection from 127.0.0.1 on port 1883.
1633717743: Socket error on client <unknown>, disconnecting.
1633717743: New connection from 172.30.32.1 on port 1883.
1633717743: New connection from 172.30.32.1 on port 1883.
1633717743: New client connected from 172.30.32.1 as auto-A1F17FB2-0B2A-3E3A-B2F2-AC22D44CA97B (p2, c1, k60, u'mqtthass').
[21:29:04] INFO: Successfully send discovery information to Home Assistant.
[21:29:04] INFO: Successfully send service information to the Supervisor.

and this is zigbee2mqtt status

Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d000588a12a/pressure/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158d00
Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d000588a12a/voltage/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158d000
Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d000588a12a/linkquality/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158
Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d0006795415/battery/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158d000
Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d0006795415/temperature/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158
Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d0006795415/humidity/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158d00
Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d0006795415/pressure/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158d00
Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d0006795415/voltage/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158d000
Oct 08 21:30:05 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:30:05: MQTT publish: topic 'homeassistant/sensor/0x00158d0006795415/linkquality/config', payload '{"availability":[{"topic":"homeassistant/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00158
Oct 08 21:31:35 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:31:35: MQTT publish: topic 'homeassistant/temp-dormitor-noi', payload '{"battery":100,"humidity":47.98,"linkquality":120,"pressure":1015.3,"temperature":24.45,"voltage":3005}'

Now I am surprised because I have no idea who is "172.30.32.1 " but looking on terminal on HA i see HA has this ip on eth0. why? And seems somehow mosquito will start on this ip i guess

In supervisor → system my ip is 192.168.55.10/24 which is the one I am accessing the interface also and is defined on zigbee2mqtt as mqtt server.
Zigbee2mqtt client have the ip 192.168.55.11 but i don t see it anywhere in log…

What is wrong with my configuration ?
thanks a lot for log suggestion :slight_smile:

L.E. - I rebooted HA (host ) and after came back I have this in log of HA

[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... 
[21:46:11] INFO: Setting up user mqtthass
[21:46:11] 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
[21:46:12] INFO: Starting NGINX for authentication handling...
[services.d] done.
[21:46:12] INFO: Starting mosquitto MQTT broker...
1633718772: mosquitto version 1.6.12 starting
1633718772: |-- *** auth-plug: startup
[21:46:13] INFO: Successfully send discovery information to Home Assistant.
[21:46:13] INFO: Successfully send service information to the Supervisor.
1633718772: Config loaded from /etc/mosquitto/mosquitto.conf.
1633718772: Loading plugin: /usr/share/mosquitto/auth-plug.so
1633718772:  ├── Username/password checking enabled.
1633718772:  ├── TLS-PSK checking enabled.
1633718772:  └── Extended authentication not enabled.
1633718772: Opening ipv4 listen socket on port 1883.
1633718772: Opening ipv6 listen socket on port 1883.
1633718772: Opening websockets listen socket on port 1884.
1633718772: Warning: Mosquitto should not be run as root/administrator.
1633718772: mosquitto version 1.6.12 running
1633718772: New connection from 127.0.0.1 on port 1883.
1633718772: Socket error on client <unknown>, disconnecting.
1633718773: New connection from 192.168.55.11 on port 1883.
1633718773: New client connected from 192.168.55.11 as mqttjs_b1d52a3c (p2, c1, k60).
1633718789: New connection from 172.30.32.1 on port 1883.
1633718789: New client connected from 172.30.32.1 as 5sBTAyWxFbyaSzz6TYXHJI (p2, c1, k60, u'mqtthass').

and if I am looking on the zigbee2mgtt log I see this

Oct 08 21:45:55 clhomezgb01 npm[11056]: Zigbee2MQTT:error 2021-10-08 21:45:55: Not connected to MQTT server!
Oct 08 21:46:05 clhomezgb01 npm[11056]: Zigbee2MQTT:error 2021-10-08 21:46:05: Not connected to MQTT server!
Oct 08 21:46:13 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:46:13: Connected to MQTT server
Oct 08 21:46:13 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:46:13: MQTT publish: topic 'homeassistant/bridge/state', payload 'online'
Oct 08 21:46:49 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-08 21:46:49: MQTT publish: topic 'homeassistant/temp-dressing-etaj', payload '{"battery":100,"humidity":48.92,"linkquality":42,"pressure":1017.6,"temperature":21.47,"voltage":3035}'

So, somehow the zigbee2mqtt is connecting to my HA …but I still have devices unavailable …

#8

What does the homeassistant log say?

#9

this one?

21-10-09 07:16:50 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-10-09 07:46:11 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-10-09 07:46:43 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-10-09 07:46:50 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-10-09 08:16:51 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-10-09 08:20:11 INFO (MainThread) [supervisor.host.info] Updating local host information
21-10-09 08:20:12 INFO (MainThread) [supervisor.host.services] Updating service information
21-10-09 08:20:12 INFO (MainThread) [supervisor.host.network] Updating local network information
21-10-09 08:20:13 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-10-09 08:20:13 INFO (MainThread) [supervisor.host.manager] Host information reload completed
21-10-09 08:37:34 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:34 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:37 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:37 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:40 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:40 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:40 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:40 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:41 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:41 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:41 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:41 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:42 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:42 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:42 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:42 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:43 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:43 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:44 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:44 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:44 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:44 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:45 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:45 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:45 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:45 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:46 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:46 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:46 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:46 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:47 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:47 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:47 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:47 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:48 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:48 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:48 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:48 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:49 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:49 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:49 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:49 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:50 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:50 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:50 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:50 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:51 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:51 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:51 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:51 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:52 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:52 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:52 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:52 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:52 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:52 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:52 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:53 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
21-10-09 08:37:53 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session cad9b7337e024b7fcfe04cb20220636c840ee7df2b006b500607a61efd2edbd63550c9074a50da72102215fd36da7e21b6b1219e91bbbb3c338614587a1cf184
#10

No , HA : configuration → logs

#11

i see only one client (zigbee2mqtt? ) connected, one disconnected (hassio?).
seems there are not all on the same network.

127.0.0.1 ----> docker network mode ‘host’ (= your host : 193.168.55.10)
172.30.32.1----> docker custom network ‘bridge’

#12

@francisp this is the HA log

Was too long to paste it here

@tomdudu38

192.168.55.11 is a raspberry pi which run zigbee2mqtt
192.168.55.10 is HA running on a intel nuc

Both are in the same network

#13

HA clearly receives messages from mqtt.

What bothers me, in that log there are no temperature or humidity messages, and zigbee2mqtt is offline.

2021-10-08 21:46:33 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on homeassistant/bridge/state (retained): b'offline'
#14

this is from now on zigbee2mqtt

[email protected]:~ $ sudo systemctl status zigbee2mqtt.service
[sudo] password for clhome:
● zigbee2mqtt.service - zigbee2mqtt
   Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-10-08 21:29:58 EEST; 21h ago
 Main PID: 11056 (npm)
    Tasks: 23 (limit: 4915)
   CGroup: /system.slice/zigbee2mqtt.service
           ├─11056 npm
           ├─11067 sh -c node index.js
           └─11068 node index.js

Oct 09 19:09:37 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:09:37: MQTT publish: topic 'homeassistant/temp-bucatarie', payload '{"battery":100,"humidity":48.84,"linkquality":36,"pressure":1023.1,"temperature":23.2,"voltage":3005}'
Oct 09 19:09:48 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:09:48: MQTT publish: topic 'homeassistant/temp-dormitor-luca', payload '{"battery":100,"humidity":50.88,"linkquality":72,"pressure":1015.8,"temperature":23.57,"voltage":3025}'
Oct 09 19:10:14 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:10:14: MQTT publish: topic 'homeassistant/temp-hol-etaj', payload '{"battery":100,"humidity":51.03,"linkquality":96,"pressure":1019.1,"temperature":22.77,"voltage":3025}'
Oct 09 19:10:14 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:10:14: MQTT publish: topic 'homeassistant/temp-hol-etaj', payload '{"battery":100,"humidity":51.06,"linkquality":96,"pressure":1019.1,"temperature":22.77,"voltage":3025}'
Oct 09 19:10:14 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:10:14: MQTT publish: topic 'homeassistant/temp-hol-etaj', payload '{"battery":100,"humidity":51.06,"linkquality":96,"pressure":1019,"temperature":22.77,"voltage":3025}'
Oct 09 19:11:24 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:11:24: MQTT publish: topic 'homeassistant/temp-dining', payload '{"battery":91,"humidity":48.29,"linkquality":72,"pressure":1018.6,"temperature":23.45,"voltage":2985}'
Oct 09 19:11:24 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:11:24: MQTT publish: topic 'homeassistant/temp-dining', payload '{"battery":91,"humidity":48.46,"linkquality":75,"pressure":1018.6,"temperature":23.45,"voltage":2985}'
Oct 09 19:11:24 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:11:24: MQTT publish: topic 'homeassistant/temp-dining', payload '{"battery":91,"humidity":48.46,"linkquality":75,"pressure":1018,"temperature":23.45,"voltage":2985}'
Oct 09 19:17:49 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:17:49: MQTT publish: topic 'homeassistant/temp-baie-parter', payload '{"battery":100,"humidity":52.15,"linkquality":48,"pressure":1019.4,"temperature":22.85,"voltage":3025}'
Oct 09 19:19:17 clhomezgb01 npm[11056]: Zigbee2MQTT:info  2021-10-09 19:19:17: MQTT publish: topic 'homeassistant/temp-dressing-etaj', payload '{"battery":100,"humidity":51.19,"linkquality":21,"pressure":1018.6,"temperature":23.04,"voltage":3035}'
[email protected]:~ $

So this is not offline…
What do you think I can do or try to fix it…:frowning:

Thanks anyway for all help you gave me …

#15

how did you install mqtt?
did you use the integration or manual config?
seems you used manual config
u could add dicovery:true in ha / mqtt config or try the integration

#16

I installed it by Supervisor - Add-on store
I changed config at some point looking for a solution to my issue
actual config is

logins:
  - username: mqtthass
    password: xxx
customize:
  active: false
  folder: mosquitto
certfile: fullchain.pem
keyfile: privkey.pem
require_certificate: false

When I installed it discovered all aqara devices from zigbee2mqtt and run about 1 or 2 days without any issues and without I doing something …then problems started

…

#17

I think I will uninstall mqtt addon and reinstall it again… don t know what else I could do to make it working

#18

Do you use other mqtt devices beside zigbee2mqtt ?

#19

No, that zigbee2mqtt is the only one integration that I have on mqtt.
Found something weird…I did uninstall mqtt from supervisor and then rebooted the host

mqtt is gone now which is normal

But when I go to Configuration → integrations I still see mqtt there and i am able to configure it ???

Shouldn t be gone also from here? Maybe somehow I had it double ?

How to make sure I get rid off it and make a clean installation of mqtt?

I see there is a delete button, I will delete it from here as well

#20

2 mqtt brokers seems the reason for this strange behavior.