Disclosure: I'm Emily and I work for HVAC Pro Solutions, a heating and cooling company on Long Island, New York.
On our HVAC maintenance visits, most of the problems we find come from clogged filters and systems that went too long between tune-ups. I'm wondering if anyone here uses Node-RED to track thermostat or furnace runtime (Ecobee, Nest, Home Assistant climate entities, a current clamp, etc.) and trigger a reminder when a filter change or service is due.
Do you count hours of runtime, use a simple calendar interval, or something smarter like heating and cooling degree days? I'd love to see example flows or hear what's worked for you. Thanks!
I have tracked actual run time for years on my furnace. I was curious how long each day the furnace ran. There is simply each day in a week no longer term data collection, after a week it is overwritten. To see run time I replaced the "on" relay with another relay that had multiple contacts and used a spare set that made when relay made to connect to pins on a Pi. When pins read zero furnace was on. I could have used a nodemcu and mqtt which I did for a while but I have a pi right there running other things so it was an easy change.
For filter reminders, count actual blower-on time if available: a heat/cool demand signal can miss fan-only operation. In Node-RED, accumulate elapsed time from the on/off transitions, keep the total in file-backed context, then use a Switch node for the reminder and a dashboard reset button for the filter change. Context defaults to memory only, so it needs storage configuration to survive restarts. Set the runtime threshold and calendar cap from the equipment/filter guidance rather than a universal hour count. Runtime is a reminder proxy, not a measurement of filter condition; keep visual inspection in the maintenance routine.
Cool! I work in Norway with HVAC or actually entire buildings to control and reduce energy consumption. We use modbus, bacnet or other protocols to speak to devices, like ventilation and heatpumps and they will report temperature, alerts, fan speed etc. We then send those to Thingsboard and can set up alarms based on telemetry there. Since some of this equipment can be quite old, like a decade or more, they can be noisy, so we take into account configuring how much alarms we want, how often etc. It seems your usecase is somewhat different. But I'm sure you'll be able to play around and have some fun in node red to solve it!