System "health" monitoring?

[gmcmicken]

Longer term, I am thinking about using P1P2 library to gain outdoor unit thermistor readings to calculate roughly how the system is operating, in sort of a green/yellow/red indicator fashion. I found some information: https://hvacbasics.com/non-invasive-testing/

For my model FTQ-PB (Outdoor RZQ-P) the only regularly reported information over p1p2 is very basic status is for the thermostat (that I can see so far) but there is a request type packet to obtain outdoor unit thermistor status. I don't know if additional temperature sensors might be necessary as well.

[Arnold-n]

Have you seen packets on P1/P2 to request the outdoor unit status? That would be interesting. Not sure if the auxiliary controller could also initiate these requests (for E-series systems this is not always possible, so P1P2Monitor simply inserts messages even if it is not intended by the protocol). Alternatively you could monitor the F1/F2 line between indoor and outdoor unit to see if any thermistor related messages are regularly communicated - but only if the F1/F2 lines have a DC voltage of at least 10V and at most 25V.

[gmcmicken]

Okay so it was my fault, when I upgraded the Arduino IDE I had auto save on, but I turned it off at some point when I was working on something (I think the undo/redo was giving me trouble so I didn't want to save the file until I was ready)

Anyway I changed the config before compiling but didn't save it, and autosave was off.

[gmcmicken]

The new IDE works well with git though, so that's a major improvement!

[gmcmicken]

There is a - also very experimental - command to write individual 000010* / 000011* messages using the W command in L1 mode. It cycle-steals one 00F030 reply slot to send one individual message. It has only been tried once on my system with other packet types. This might work to restore the original values, but the BRC may overwrite the values if it doesn't accept the new heat pump replies. it requires the definition of ENABLE_INSERT_MESSAGE in P1P2Config.h, but again: very experimental, results uncertain.

Can you give an example? If I issue "w 0000A3" will it send message 0000A399?

[Arnold-n]

Indeed. It will send that message exactly once (after a 00F030 message, in the time slot where P1P2Monitor is supposed to send 40F030*), and you will need to observe/log P1P2/R to see the 4000A3* reply (if any).

[gmcmicken]

Okay so I tried "w 0000A3" and it queued it up but didn't write it as I guess the 00F030 message is only seen when there is not a secondary controller already exchanging 00F038? So I used "L0" then "w 0000A3" and I got the message inserted, seemed to work fine.. Obviously I probably don't want to toggle L0/L1 all the time to put this in though so what is your suggestion?

[gmcmicken]

Okay I'm trying to add packet 4000A3 to ParameterConversion_F, this is the response packet:
4000A380000080000080000040085F002A9880000000C8
and I think (from the screen) it contains 6 thermistor readings (but mine reports only two).

4000A3 800000 800000 800000 40085F 002A98 800000 00C8
         1      2      3      4      5      6

Do you have a suggestion how to implement?

[Arnold-n]

The last payload byte 0x00 could match the (outdoor) unit no, so if anyone has multiple outdoor units, I'd be interested in logs, otherwise I'll just keep the code simple for one outdoor unit only.

[gmcmicken]

Thanks! I tried to cycle the "unit number" to see if that byte changed but it won't let me cycle (I suppose it's smart enough to not allow if you don't have another unit connected).

I'll flash these and give it a try.

[gmcmicken]

I'm not seeing th4 or th5 come into home assistant, I removed all the config (even mqtt integration) and added it back. I'm expecting to see T1_Th4 and T1_Th5 in homeassistant/sensor config but it's not there.

Anyway I temporarily set up mqtt sensor on topic P1P2/P/#/T/1/Th4 and 5, as that is working.

[Arnold-n]

Forgot to update the history code, should work now.

[gmcmicken]

Thanks! It looks like the 'w' command is still waiting for 00F030 packet only (not 3x as you described), maybe just an error in #define ENABLE_INSERT_MESSAGE_3x