Another UPDATE: The AsyncMqttClient works pretty well; I think better than PubsubClient, which can only send a QoS (quality of service) level 0 which just sends it with no confirmation as I believe. AsyncMqttClient can send 0, 1, or 2, and I’m using QoS 1. The LEDs turning on when they’re not supposed to is still an issue but doesn’t seem to affect the performance of the station.
UPDATE: I have AsyncMQTT working pretty well, I think. Now I have a couple NEW issues. Jeez. One, apparently now the 034B humidity sensor is reading low – like almost 1/2 what it’s supposed to be. And two, for some reason the MCP23008 GPIO expander is turning on LEDs randomly. For the previous issue, the sensor readings, I added some code so I can ground a test point to turn on the +12-volt boost regulator, required by the sensor. This works and I see a good voltage at the ADS1115 ADC showing 0.52 volts which translates to 52% humidity. I’m adding a delay in the code so +12-volts is there longer.
As far as the LED weirdness, I read that all the UNUSED GPIO pins should be pulled-up or pulled-down, so I’m going to try that. Or just set them to outputs and set them low. More to come.
I’ll be glad when I get this MQTT timing thing figured out since I want to use JavaScript gauge widgets on my Node-RED dashboard; they look really awesome! And I can’t really do that until this MQTT message issue is put to rest. Per my previous post, I’m seeing delay or missing (!) MQTT messages on the broker and I don’t know what’s going on. The Mosquito broker is on a Raspberry Pi and it is NOT overloaded. Right now, it sees (or supposed to see) messages and the MOST once per 30 seconds.