Closed coserotondo closed 1 year ago
Hi, Yes, its receiving a value that the LOOKUP cannot interpret / convert. I experienced the same with different registers. See closed issue #255. I removed the lookup portion of the code and recorded the values. Then added the missing values to the Lookup. You will just need to research what the value means.
Thanks, trying this approach to decode the message.
Il giorno sab 29 apr 2023 alle ore 21:25 qfinucane @.***> ha scritto:
Hi, Yes, its receiving a value that the LOOKUP cannot interpret / convert. I experienced the same with different registers. See closed issue #255 https://github.com/StephanJoubert/home_assistant_solarman/issues/255. I removed the lookup portion of the code and recorded the values. Then added the missing values to the Lookup. You will just need to research what the value means.
— Reply to this email directly, view it on GitHub https://github.com/StephanJoubert/home_assistant_solarman/issues/242#issuecomment-1528855732, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5CAQBEXETSVXBAG4GUNBF3XDVTLZANCNFSM6AAAAAAVU4TXEI . You are receiving this because you authored the thread.Message ID: @.***>
Decoded the messages, no more LOOKUP.
I'm using the following lookup values for Inverter Alert but sometimes the outcome is literally the 'LOOKUP ' string instead of one of the value for the relative key. Does it mean that the received data is not in the keys provided?