Aqara temp sensors show unavailable in HA but works in zigbee2mqtt

Third party integrations
,
21

I reinstalled it and leave default config in supervisor tab

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

Then I changed zigbee2mqtt as well and removed user/pass

homeassistant: true
permit_join: true
mqtt:
  base_topic: homeassistant
  server: mqtt://192.168.55.10:1883
serial:
  port: /dev/ttyACM0
devices:
  '0x00158d000465705c':
    friendly_name: temp-living
  '0x00158d00067cf4f8':
    friendly_name: temp-dining
  '0x00158d00067d99bd':
    friendly_name: temp-bucatarie
  '0x00158d00067bed0d':
    friendly_name: temp-baie-parter
  '0x00158d0001d72a39':
    friendly_name: temp-baie-luca
  '0x00158d00033de11b':
    friendly_name: temp-dormitor-luca
  '0x00158d00057f9436':
    friendly_name: temp-hol-etaj
  '0x00158d000411a1e0':
    friendly_name: temp-dormitor-noi
  '0x00158d0001d7658c':
    friendly_name: temp-dressing-etaj
  '0x00158d000588a12a':
    friendly_name: temp-baie-noi
  '0x00158d0006795415':
    friendly_name: temp-dormitor-mijloc

Then I see a notification for new devices and saw in integration mosquitto broker and added it
I removed user/pass from here also

So now I am waiting to HA discover the zigbee2mqtt devices

Are these correct steps?

22

Not quit. The latest mqtt add-on does not support anonymous connections. User/Password are always needed.

23

Ok, Added in mqtt conf in supervisor user /pass

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

saved and restarted

then go to configuration → Integrations and added user pass here also on mqtt

Then changed conf on the pi as well

homeassistant: true
permit_join: true
mqtt:
  base_topic: homeassistant
  server: mqtt://192.168.55.10:1883
  username: 'mqtthass'
  password: '12345678'
serial:
  port: /dev/ttyACM0
devices:
  '0x00158d000465705c':
    friendly_name: temp-living
  '0x00158d00067cf4f8':
    friendly_name: temp-dining
  '0x00158d00067d99bd':
    friendly_name: temp-bucatarie
  '0x00158d00067bed0d':
    friendly_name: temp-baie-parter
  '0x00158d0001d72a39':
    friendly_name: temp-baie-luca
  '0x00158d00033de11b':
    friendly_name: temp-dormitor-luca
  '0x00158d00057f9436':
    friendly_name: temp-hol-etaj
  '0x00158d000411a1e0':
    friendly_name: temp-dormitor-noi
  '0x00158d0001d7658c':
    friendly_name: temp-dressing-etaj
  '0x00158d000588a12a':
    friendly_name: temp-baie-noi
  '0x00158d0006795415':
    friendly_name: temp-dormitor-mijloc

and restarted zigbee2mqtt as well

1 Like
24

Still waiting for devices to appear again but nothing happened yet…is there any way to configure them manually?
First time when I installed it they show up under configuration / integrations mqtt but now is still empty

25

Strange problem. How is Zigbee2MQTT installed ?

26

Followed this tutorial and using a raspi 4 and a CC26X2R1 card.
I am thinking to move the CC26X2R1 card directly in intel nuc where HA is running and install zigbee2mqtt addon …

L.E. sorry missed the link

27

What tutorial ?

28

Sorry missed the link

29

Ok, an installation on bare metal. Probably Raspbian if on pi4.

Try :
apt-get update && apt-get upgrade -y
and then

apt-get install mosquitto

to install mosquitto on your Pi 4

then configure HA to access the mqtt on your Pi4

30

You mean to configure mqtt broker on the pi and not on the HA

31

Indeed. :+1:

32

Meanwhile I moved CC26X2R1 card on the nuc and installed zigbee2mqttaddon…seems till now is working. If that will be fine, then I will move the nuc in the place of pi in order to have all xiaomi sensors in range…one point of failure less :slight_smile:

Will keep you posted anyway

Thanks a lot for all you help, really appreciated

33

I had a similar issue and found the credentials in the MQTT broker were not what I had set when setting up Mosquito.
Setting>core-mosquitto MQTT?Configure>Re-configure MQTT> Enter the MOsquito Username and password you set up initially.

Worked for me !