[MQTT Exporter] High praise!

🧰 Built-In Apps and Drivers
1

Can't believe such a useful feature appeared quietly in a point release to v2.4.4!

I've been fulfilling my hunger for outgoing MQTT from Hubitat by posting events using the Maker API to Nginx using some string and sticky-tape . It's been solid as a rock, but this new app is far more flexible, and incorporates Home Assistant topics too! :exploding_head:

Very impressed, thank you Hubitat crew!

As a bit of project self-promotion, if you didn't already know you can also get Zigbee2MQTT devices in to Hubitat using my Zigbe2MQTT Routing Driver, so everything suddenly ties together very nicely indeed! :heart_eyes:

2 Likes
2

Hehe, I have a feature request already!

I was replacing a couple of MQTT feeds with the new ones from Hubitat, but now get "The entity no longer has a state class" in the Home Assistant Repairs screen.

The MQTT feed needs the correct SensorStateClass declared to store long-term statistics. For most sensors this should just be the addition of "state_class": "measurement" to the MQTT payload. There are also SensorStateClass.TOTAL and SensorStateClass.TOTAL_INCREASING options too.

Any chance this could make its way into the app? :smiley:

6 Likes
3

Had this running a few days and was starting to notice some of my lights were getting very slow to respond. Hopped on to the C8 Pro and found "Elevated Load" warnings and the pages would barely load. Tried to disable the app and it continued to send messages, uninstalled the app and messages kept appearing on my MQTT debugger.

After a reboot the messages stopped and the hub seems to have returned to normal.

Tagging @bobbyD and @gopher.ny in the hope this'll drop in to the bug-fix queue! :slight_smile:

4

Just adding this for other Home Assistant users, this is what the error looks like:

The entity no longer has a state class We have generated statistics for 'House Boiler (Heating) Temperature' (sensor.house_boiler_heating_temperature) in the past, but it no longer has a state class, therefore, we cannot track long term statistics for it anymore. Statistics cannot be generated until this entity has a supported state class. • If the state class was previously provided by an integration, this might be a bug. Please report an issue. • If you previously set the state class yourself, please correct it. The different state classes and when to use which can be found in the developer documentation. • If the state class has permanently been removed, you may want to delete the long term statistics of it from your database. Do you want to permanently delete the long term statistics of sensor.house_boiler_heating_temperature from your database?
The entity no longer has a state class We have generated statistics for 'House Boiler (Heating) Temperature' (sensor.house_boiler_heating_temperature) in the past, but it no longer has a state class, therefore, we cannot track long term statistics for it anymore. Statistics cannot be generated until this entity has a supported state class. • If the state class was previously provided by an integration, this might be a bug. Please report an issue. • If you previously set the state class yourself, please correct it. The different state classes and when to use which can be found in the developer documentation. • If the state class has permanently been removed, you may want to delete the long term statistics of it from your database. Do you want to permanently delete the long term statistics of sensor.house_boiler_heating_temperature from your database?1234×1130 195 KB

The link sends you here.

It's possible to wrap the incoming MQTT messages and provide the state class manually, but that's a right faff that nobody needs. :slight_smile:

5

Just to add to the high praise for the MQTT Exporter it seems to be working very well for me. I have actually managed to use the MQTT Exporter in conjunction with Influxdb v3 and it's MQTT Subscriber Plugin. I am still running "InfluxDB Logger" for a older instance of InfluxDB v2 which is i consider my stable data, butt may not need to going forward with this new setup with the version of influxDB.

Kudo's guys on getting this going that is so light weight.

2 Likes
6

Flip side of the coin here, I'm afraid @mavrrick58. Just had to roll back to v2.4.3.173 on the C8 Pro, it became completely unreliable. :cry:

I've left the C7 on v2.4.4.156. That seems to be having no issues whatsoever, though it's never had MQTT Exporter installed on it.

7

What does that actually mean. What problems did you experience. There is atleast one issue that gets addresed in the next release. When i first tested MQTT i had a issue that caused my hub to become unresponsive and created a resource issue. Maybe the same problem. It seems to have been triggered by someting happening during change to the app configuration.

8

Mentioned it above, but Hub went into constant "Elevated Load" state, web interface became unresponsive. Had to use diagnostics page to reboot. Load went from between 0.6-0.9, to constant 1.8-2.0, Zigbee network going offline, devices unresponsive.

Back on v2.4.3.173 and it's solid as a rock again.

9

That is the effect of you disabling the sensor. Is not really an error. Is more of a warning that state value field was empty and can't be saved in the long term statistics. You should delete the records from the statistics and start over collecting the data when the sensor is active again. If you don't need statistics on the sensor, you can exclude the sensor in your configuration file and you will no longer see that error if you disable the sensor again.