So I got a PCAN tool to help do some decoding of the CAN buses, with emphasis on helping decode climate control and remote queries. Playing around with it today, I used TickTock's doc to help find climate related values on the car CAN bus. Here's some observations:
510 byte 4- tracks "climate control" under the energy info screen exactly (goes up and down in lock step)
50a byte 18- 1A/1B observed with AC on (too cold for full AC power), up with compressor engagement (when I hear the compressor kick on) and slowly drops down to 18 when turning off climate control. I think it is "refrigerant pressure signal detection value sent from VCM" as listed in the service manual
5a9 byte looks to be eco mode flags for climate/other reasons. I observed a change when switching back and forth between eco and drive (but remained stationary) but NOT between drive and park.
Climate on (heat):
eco 16 30 de c3 50 00 00
drv 78 14 50 0d 83 00 00
eco 87 18 b0 de c3 50 00
drv 86 16 80 0d 43 00 00
The first byte varied by 1 bit in a few readings though.
I observed a new message header/address of 68 on the EV CAN bus that appears exactly 1 time when invoking a remote climate request. I tried sending this through PCAN View but it didn't do anything. Bummer. I suspect it is the TCU (it is on the EV bus according to the service manual) but there might be more to it...
I'm looking at trying out CAN Trace
for a free 30 day trial, but it's 495€ for the full version.
It does have some very nifty "database" options which can convert hex to "real world" values, and there is logging and other features... wish they made a "lite" version!