Help wanted! Product ID mapping #75
Comments
|
Just confirming Envoy is showing 800-00656-r06 / Envoy-S-Standard-EU / ENV-S-WB-230 as well Firmware D7.6.175 My inverters are IQ7A Microinverter SKU: IQ7A-72-M-ACM-INT with PN 800-01127-r02 reported in inventory.json Inventory.json reports for these as well And these numbers show as firmware on Enphase web
|
|
Oh, my IQ 3 phase relay has label/sku on it: Q-Relay-3P-INT and shows in Inventory as |
|
Thanks for all the work Vincent. Just installed beta 5. Hope i can add the solar system to the energy dashboard. Envoy-S Metered |
|
Hi @1nsomnia, thanks! Which inverters do you have? |
Hmm, same hardware id, different SKU. I'd opt to use this SKU though, as it matches with the other ones 😄 |
|
Yeah. No clue what the ACM part in the other SKU is. |
It showed on the enphase website in my quipment list. I checked again, but it's showing for all 24 inverters. So if you hit that specific SKU you know it's an IQ7A I'd say. |
|
I’ve got these inverters: |
|
Greetings from the author of https://github.com/Matthew1471/Enphase-API 😄 Europe:
and North America:
The blanks for the IQ8s I can get they're just more annoying to populate. Their asset system also lists a part number for each software release - but I'm not sure of the value of including that given it will be re-generated for every build? |
|
Thanks @Matthew1471 ! You were able to crawl this data from some public available source? I don't think the software release is of that much value indeed. Also nice library you have made there :) Edit: Unfortunately the table does not seem to exactly match earlier reports from people. Seems like Enphase is making a bit of a mess, or the source is not that accurate. |
Hehe "public available source" hehe 😀 Shh.. 🕵️
Thanks, I wanted to make something people can include in their projects so we could all have a consistent library.. there's a lot of rubbish code out there to talk to the IQ Gateway and it meshes the program logic in with the Enphase logic.. The library is on PyPi so it can just be included as an abstract library without anyone needing to specifically understand the IQ Gateway platform.
Did I get a RegEx wrong? Which ones don't match and I can go back to the source file.. fairly sure my source is accurate considering where I got it from 😀, any mistakes are way more likely to come from the RegEx I wrote. I manually checked a few in this thread and they seemed to check out. I couldn't RegEx the IQ8s but they are in the file, if it was useful I can hand extract those. Let me know if you need any other info. |
|
@Matthew1471 Probably it is just Enphase naming things differently in the source than other places. But for example: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the newest version of the integration we started displaying friendly model names for Enphase devices. Since there is no way to get these names from the Envoy API itself, and a public mapping does not seem to exist, we need to create this mapping ourselves.
We would be very happy if you could add the product number (this can be found in Home Assistant at the device page and then
Hardware) and corresponding product name for the Enphase devices you own to this issue, so we can add them to the mapping.Our current mapping
Thanks 🚀
The text was updated successfully, but these errors were encountered: