ccutrer / waterfurnace_aurora

Library for communication with WaterFurnace Aurora control systems
30 stars 7 forks source link

Series 7 single zone system not providing climate.waterfurnace_zone_1 on MQTT #59

Closed 0n3man closed 6 months ago

0n3man commented 6 months ago

This is great work. It pulls a ton of information and makes it available on MQTT. However it not reporting the desire temperature and current temperature values. Using aurora_fetch valid I get

Set Point (501): 70.0F Ambient Temperature (502): 68.1F

Which appear to be the values I'd want.

Attached is the full yaml output. I'm a coder from way back but have never done any ruby and currently have no idea how I'd update the gem to do some debugging. I'm willing to assist making this work if it's possible. Hoping for some direction on how I might look to move forward. Thanks

myheatpump.txt

0n3man commented 6 months ago

After additional review I've found that Heating set point on my unit is 507, cooling set point 508 and relative humidity is 509. I noticed that these values where mapped to 741, 745 and 746 in

/var/lib/gems/3.0.0/gems/waterfurnace_aurora-1.4.8/lib/aurora/registers.rb /var/lib/gems/3.0.0/gems/waterfurnace_aurora-1.4.8/lib/aurora/thermostat.rb

Not really knowing what I was doing I changed these mapped values from the 700 values to the 500 values. I restarted the aurora_mqtt_bridge hoping the information would end up getting push to HA. I didn't see any new topics with MQTT explorer and nothing new showed up in HA.

Any input on what I need to do ? Considering this is all in github updating the files as I didn't wouldn't be the correct approach. Is there already some method of handing different values for different hardware?

0n3man commented 6 months ago

It is interesting if I just do

aurora_fetch /dev/ttyUSB0 known > ~/myheatpump_known.txt

Then the changes I mentioned above do show up in the output.

myheatpump_known.txt

0n3man commented 6 months ago

So I'm thinking the issue is that I have no zones and my thermostat doesn't support AWL communications. My thermostat is only version 1.04 and it needs to be above version 3.0 to support AWL. I will keep pushing to see if I can figure out how to make sure the registers I need are added to the read list and how to use the results to populate the hass_climate node. If anyone has any thoughts on this please let me know what you think.

0n3man commented 6 months ago

Seems I got most of the data pulled and populated. I was hoping maybe there would be an option to change the target heat and cooling values. I couldn't figure out how to write a register using the mqtt modbus pass through to try and update the set points. If I could get a little clarification on how that's supposed to work I could try writing the set points. Still need to see if I can find the register that hold the system mode (off, auto, heat ...) and fan mode.

image

So based on what I see in the code, it seems if I can get the thermostat software updated to a version above 3 that maybe things would just work. I just have a thermostat connected to the system, hopefully I don't need an AID or AWL. If either of those is required please let me know. I'm going to see if I can get the thermostat software updated.

Let me know if it's worth me trying to clean up the modes I've made to do a pull request. If it's just a firmware update to thermostat then maybe it not worth including.

0n3man commented 6 months ago

It appears I have all the correct registers to get the status related to the thermostat. It's really just status mode as you can't change anything on the system. Next step is to see if I can get thermostat firmware updated and then hopefully the changes will not be required.

image

0n3man commented 6 months ago

I had the software on the furnace board and the thermostat updated to 3.04 and now everything looks like it works. I verified I can now control the furnace temperature set points from HA through this software. The configured registers appear to be correct, without any changes required.