Closed mnederlof closed 11 months ago
Open to suggestions for improvements π
Nice! I do think we need to lose the -rXX
in the mapping. Iβve seen multiple Envoys of the same type with different numbers there. Probably the revision or something.
Yeah, that is already done, while matching the hardware id; while resolving, it also loses the 800-
prepend in a second round of trying to match; see https://github.com/vincentwolsink/home_assistant_enphase_envoy_installer/pull/73/files#diff-0ac076ba3a419c22e8f034c216efb6b0347ddbac74545ec2eac8ceb10b067e4aR58
Ah yes indeed. π
Now we need to crowdsource for product IDs I guess π
I'm just a bit sad the SKU with hardware id does not fit on one line for the inverter... π
If you drop the 800 and revision in the mapping already, it does π
If you drop the 800 and revision in the mapping already, it does π
yeah, but that kind of defeats the point of showing it alltogether π€
Ah, you were talking about the screenshot. I was looking at the code. I agree but letβs keep it like this, itβs fine.
And the CT model is now also generated based on either the EnvoyData class name, or the ALIAS value set in that class (which is the same value for you, but it will now show to which data class it has resolved to)
Not really sure if it is what i expected, but so far it looks like this:
envoy device:![image](https://github.com/vincentwolsink/home_assistant_enphase_envoy_installer/assets/7044570/1b24267b-346b-4cd4-b7ee-bbf383488855)
inverter device:![image](https://github.com/vincentwolsink/home_assistant_enphase_envoy_installer/assets/7044570/d1dc5033-8577-4eee-a4dc-34e910887914)
relay device:![image](https://github.com/vincentwolsink/home_assistant_enphase_envoy_installer/assets/7044570/10cb84bf-3a76-412a-b9d5-97cf6f713ee2)