ccutrer
commented
8 months ago aurora_fetch and aurora_mqtt_bridge are using the exact same code to communicate with your heat pump, just providing different interfaces for you to interact with it. If you're having issues running it in systemd, your first step would be to run the bridge directly in your terminal, and not under systemd, to ensure it's not any sort of issue with running as a different user. The next step may be for me to allow the timeout to be configurable, so you can extend it to see if that helps.
The libffi comment is a red herring. As long as the gem install command works, it doesn't really matter which version you have.
As far as a specific USB adapter, that's not true. The gem should work with anything that presents itself as a serial port to the operating system, and doesn't have any weird idiosyncrasies (like requiring an additional line being asserted in order to write - any adapter based on the MAX485 chip will have this problem). The issue with the discussion on different serial chipsets ended up being a root cause of the MAX485. All that said, I simply provide a recommendation of the one I own and have tested.
Keep in mind that this is simply a hobby project to me. I don't get any compensation from it, and developed it for my own personal use. I'm of the opinion that I should share my work freely with others, so provide it here on GitHub. I try to answer questions and help people troubleshoot as I'm able, but have no obligation to do so, and definitely will not be purchasing and spending the time to test myriad RS485 adapters in order to "certify" them.
The last change to timeouts or actual communication with the unit is https://github.com/ccutrer/waterfurnace_aurora/commit/23a4bcc2ff685c9629afc8a0629f00fb1d975ba2, which was quite some time ago. I don't know what version you were previously using though. It's also possible that your unit isn't responding to a register that the mqtt bridge is assuming exists. aurora_fetch has extra logic to make smaller requests or to simply ignore individual registers that are timing out. If you can email me (cody@cutrer.us) a YAML file produced with aurora_fetch /dev/ttyHeatPump valid --yaml > myheatpump.yml, I may be able to tell if this is the problem.
kskenyon
jim0020
0n3man
I did a fresh raspberry pi OS bookworm install with the latest version of waterfurnace_aurora. I get this error and a systemd restart continuously.
aurora_mqtt_bridge[18308]: /var/lib/gems/3.1.0/gems/rmodbus-ccutrer-2.1.0/lib/rmodbus/client/slave.rb:275:in `rescue in query': Timed out during read attempt (ModBus::Errors::ModBusTimeout)
aurora_fetch ... valid > works fine and produces a nice yaml file with all the correct data.
I had this working prior to the update but I had to use Node-RED modbus to initiate a generic read every few seconds then the waterfurnace_aurora would work. Otherwise it too would time out waiting for data. It's always been pretty spotty with timeouts but now it's all the time.
Same after adding libffi per a suggestion in issues.
Did something change in the latest version that messed up the read timing in the regular app but not in aurora_fetch? Seems requiring a specific USB adapter is a bit too much. I do have the ones (2) that don't require a write before outputting data. Doesn't seem to work that way with waterfurnace_aurora.
Kevin