Qingping Pro AQM integration doesn't work since HA Core update 2025.9.0

[camhome108]

Hi there 🙂 Since yesterday, after applying the HA Core update 2025.9.0, my Qingping Pro AQM integration extension is no longer able to retrieve the data sent by my CGS2 sensor. The device still manages to connect to the MQTT broker if we believe the logs ! However, it now becomes offline and all data appears unavailable. A message also appears in the HA Core logs. I tried to re-install the extension, but nothing is happening. Thanks for your help 🙂

[icq5564476]

same malfunction

[camhome108]

It's solved : Look at the bottom of the discussion :)

[camhome108]

Updating to HA Core 2025.9.1 does not fix the problem !

[mash2k3]

I am on 2025.9.1 and all my sensors are working, 3 CGS1 and 1 CGS2

[mash2k3]

Also can you translate this error and also expand it so we can see where its failing

Another difference i see is the firmware, mine is 4.5.6_0156 and yours 4.5.6_0167. i wonder if qingping changed something
can i get the output of your mqtt data

[camhome108]

Hi :)
Here is the google's translation of the last message I get in my HA Core Logs :

"This error is caused by a custom integration.

Logger: custom_components.qingping_cgs1.sensor
Source: custom_components/qingping_cgs1/sensor.py:163
Integration: Qingping Pro AQM (documentation, issues)
First occurred: 09:03:04 (66 occurrences)
Last logged: 10:04:02

Error processing MQTT message: Attribute hass is None for "

After restarting the MQTT service, this is exactly what I get in the logs :

"[10:10:00] INFO: Starting NGINX for authentication handling...
[10:10:00] INFO: Starting mosquitto MQTT broker...
2025-09-13 10:10:00: Warning: Mosquitto should not be run as root/administrator.
2025-09-13 10:10:00: mosquitto version 2.0.22 starting
2025-09-13 10:10:00: Config loaded from /etc/mosquitto/mosquitto.conf.
2025-09-13 10:10:00: Loading plugin: /usr/share/mosquitto/go-auth.so
2025-09-13 10:10:00: ├── Username/password checking enabled.
2025-09-13 10:10:00: ├── TLS-PSK checking enabled.
2025-09-13 10:10:00: └── Extended authentication not enabled.
2025-09-13 10:10:00: Opening ipv4 listen socket on port 1883.
2025-09-13 10:10:00: Opening ipv6 listen socket on port 1883.
2025-09-13 10:10:00: Opening websockets listen socket on port 1884.
2025-09-13 10:10:00: Opening ipv4 listen socket on port 8883.
2025-09-13 10:10:00: Opening ipv6 listen socket on port 8883.
2025-09-13 10:10:00: Opening websockets listen socket on port 8884.
2025-09-13 10:10:00: mosquitto version 2.0.22 running
2025-09-13 10:10:02: New connection from 172.30.33.3:57674 on port 1883.
2025-09-13 10:10:02: New connection from ::1:52028 on port 1883.
2025-09-13 10:10:02: New client connected from 172.30.33.3:57674 as mqttjs_29559da0 (p2, c1, k60, u'mqtt').
2025-09-13 10:10:02: Client disconnected due to protocol error.
2025-09-13 10:10:05: New connection from 172.30.32.1:51555 on port 1883.
[10:10:06] INFO: Successfully send discovery information to Home Assistant.
2025-09-13 10:10:05: New client connected from 172.30.32.1:51555 as 79mw4loTe71XOIwPApwdiN (p2, c1, k60, u'homeassistant').
[10:10:09] INFO: Successfully send service information to the Supervisor.
2025-09-13 10:10:16: New connection from 192.168.1.97:38472 on port 1883.
2025-09-13 10:10:16: New client connected from 192.168.1.97:38472 as qingping-582D34709469 (p2, c1, k30, u'qpam').
2025-09-13 10:10:16: Client qingping-582D34709469 disconnected.
2025-09-13 10:10:44: New connection from 172.30.32.2:39954 on port 1883.
2025-09-13 10:10:44: Client closed its connection.
2025-09-13 10:10:46: New connection from 192.168.1.97:38474 on port 1883.
2025-09-13 10:10:46: New client connected from 192.168.1.97:38474 as qingping-582D34709469 (p2, c1, k30, u'qpam').
"

[camhome108]

I received my CGS2 sensor on August 16th 2025 ... I can't know if it was already with firmware 4.5.6_0167 or if it has been updated on first boot (or after ?) : The history indicates only 4.5.6_0167. I just can say I configured it "day one" at the reception to integrate it with HA : reports worked very well until the 2025.9.0 update !

[camhome108]

I'm not very familiar with Python, but I can investigate and answer any questions you may have about my setup or logs :)

[mash2k3]

I'm not very familiar with Python, but I can investigate and answer any questions you may have about my setup or logs :)

you can get the mqtt output using mqtt explorer app

[camhome108]

OK, using MQTT Explorer App connected to the broker, here is an example of a received message :

{"mac":"582D34709469","sensorData":[{"battery":{"status":1,"value":100},"co2":{"status":0,"value":898},"humidity":{"status":0,"value":62.79999923706055},"noise":{"status":0,"value":39},"pm10":{"sn":"P945501578","status":3,"value":99999},"pm25":{"sn":"P945501578","status":3,"value":99999},"temperature":{"status":0,"value":21.700000762939453},"timestamp":{"value":1757777731},"tvoc_index":{"status":0,"value":49}}],"third_state":1,"timestamp":1757777731,"type":"12","version":"4.5.6_0167"}

[mash2k3]

mqtt data looks good

i am on the latest core 2025.9.3 and still no issues on my side

[camhome108]

Did you try to update the firmware of your CGS2 ?

[camhome108]

I just figured out where my problem was coming from and I just fixed it easily. In fact, in the Diagnostic section, the reports for the MAC address and Report Type fields were disabled ! I just had to reactivate them and everything is OK again !

[camhome108]

It is still surprising that this appeared just after the 2025.9.0 update...?

[mash2k3]

yea that is weird, glad it is working for you tho

[camhome108]

Thanks for your help and sorry for the time I took you :
Maybe you should point out somewhere that the Diagnostic section is essential for the integration to work, that it is not just intended to display reports !

[camhome108]

It is also surprising that such settings remain active despite a complete reinstallation of the integration !