While I wait for my post cooldown I should clarify that I have tried running the ESP32 from both panel locations as a substitute for a panel, and also tried it piggybacking off the AM24 panel (as it lives right now). Behaviour of the last 4 zones ‘flipping’ in HA seems the same in all 3 scenarios.
And here is the AM24 panel (upstairs).
Yep, that’s how it should be from what I understand.
In your led_proto2.h file in ESP code there should be a section doing publishing:
cool->publish_state(ledProto.p[clsLedProto::COOL] != 0);
auto_md->publish_state(ledProto.p[clsLedProto::AUTO] != 0);
room5->publish_state(ledProto.p[clsLedProto::ROOM5] == 0);
run->publish_state(ledProto.p[clsLedProto::RUN] != 0);
room8->publish_state(ledProto.p[clsLedProto::ROOM8] == 0);
room7->publish_state(ledProto.p[clsLedProto::ROOM7] == 0);
room6->publish_state(ledProto.p[clsLedProto::ROOM6] == 0);
timer->publish_state(ledProto.p[clsLedProto::TIMER] != 0);
fan_cont->publish_state(ledProto.p[clsLedProto::FAN_CONT] != 0);
fan_hi->publish_state(ledProto.p[clsLedProto::FAN_HI] != 0);
fan_mid->publish_state(ledProto.p[clsLedProto::FAN_MID] != 0);
fan_low->publish_state(ledProto.p[clsLedProto::FAN_LOW] != 0);
room3->publish_state(ledProto.p[clsLedProto::ROOM3] != 0);
room4->publish_state(ledProto.p[clsLedProto::ROOM4] != 0);
room2->publish_state(ledProto.p[clsLedProto::ROOM2] != 0);
heat->publish_state(ledProto.p[clsLedProto::HEAT] != 0);
room1->publish_state(ledProto.p[clsLedProto::ROOM1] != 0);
inside->publish_state(ledProto.p[clsLedProto::INSIDE] == 0);
Change “!=” to “==” for zones 5-8.
Hold down each button for long enough to get a stable voltage reading.
@everydayimhassling Thanks for the details.
I’ve just released a new version with updated code that flips those bits.
You might need to clear your cache when you rebuild in esphome but try without first as it will probably be faster
Thanks John, I have updated from your repo and the last 4 zones are correct in HA now. Much appreciated!
Hey John and @Breddo
Great progress on this. I too would love something a bit more professional and compact. Are you thinking of a custom PCB? If so, I’d certainly be interested also. If you were in Sydney I’d be happy to contribute to the cost of production on shipping.
Yep that did the trick, thank you!
@johnf
What a great thread and so much great work put in. I am fairly new to Home Assistant, but am going to jump in and give this a try 
I have ordered all the parts, just waiting for delivery before getting the soldering iron out.
Whilst waiting, I have installed the HACS package. One thing I did notice was a formatting error in the Actron Esphome card.
I have an 8-zone controller (5 zones active), and when configured for more than 4 zones, the zone buttons are not displayed correctly - they appear in the top half of the card.
Looks like it is an omission to define zones 5 through 8 in the src/styles.ts.
Need to add zones 5-8 in the .card-content layout and in the /* Zone Buttons */ section
Thanks again, really looking forward to getting this up and running
@NevilTh Thanks for the heads up. I’ve just deployed a new version and that should be fixed.
Perfect, thank you.
I am trying my hand at implementing this project and am toying with a change to the circuit to try and address what some have mentioned as voltage drift.
I am using an op-amp to measure the voltage across a shunt resistor (R1 22Ohm), which then provides feedback to the inverting input of the op-amp.
This feedback should lock the voltage drop (and therefore current) across the shunt.
The op-amp output stabilises when the inverting and non-inverting inputs match. I have also put a voltage divider on the input to the op-amp to expand the voltage range on the input and decrease sensitivity.
So far, I have bench tested this successfully, looking to try it out over the weekend. Can anyone advise what sort of voltage drift they were getting and under what conditions? Hopefully, I can simulate and see if this design helps (or even works).
I’m not sure if I’m seeing any voltage drift. I’ve stuck my unit inside the wall so temperature is probably more stable.
I haven’t had any issues with buttons not working since I put it in a few months ago.
FYI my component is now available directly via HACS
Hmm, I am tending to think it may be more related to power supply than the circuit design. When running it off USB I could see fluctuations in the range of .3 to .4V on the collector of the transistor (key line). Enough to cause issues of key detection. Putting the meter on vcc rail got similar fluctuations, so unstable power source.
I did briefly hook it up to the A/C unit like this and did get some misread button presses.
I have since put the DC-DC buck converter in place (with input from a PC power supply) and this seems to be much better, vcc is now stable, and the Collector of the transistor is now fluctuating only by a few millivolts(using a 1K pull-up resistor). I need to hook it all up and test it in place again when I get some time.
It’s a long time since I have delved into electronic circuits, so it’s taking a bit to get my head around it all.
By the way, when I did have it hooked up for a bit I did receive a
“Unknown 7-segment pattern: 0x5F” message in the log.
I think this was for the “S” in the display output when the fan was in ESP mode.
I didn’t know ESP mode was a thing! I’ve added the segment code.
Do you have any details on how it works? Is it another fan mode? How do you enable it?
I suspect that how we cycle through the fan modes might need adjusting if the unit has ESP
@djelusive Thanks
Does the display have an extra LED for this alongside high/med/low or does it just show the S on the display?
I’ve released the first major version, please note it has some breaking changes. I’ve moved the zone naming config into the integration instead of the card.
NOTE: This is a major release and has breaking changes. You should:
BREAKING CHANGESLovelace card configuration has changed. The card now requires a climate_entity instead of entity_prefix and zone_count. Zone naming and preset configuration has moved to the integration’s config/options flow.
Add zone_names and custom_presets to integration config/options
Add config entry migration from v1 to v2
Simplify Lovelace card editor to a single climate entity picker
Card reads zone names and count from climate entity attributes
Add preset_menu with add/remove preset steps in config flow
