David Rapan
David Rapan
Ah, I see. I wouldn't have guessed that it would be solved this way. But in this case I really have no idea why the profile didn't work for you...
* [feat: Add support for all three configurations H1, H2 and H3 of Pylontech Force](https://github.com/davidrapan/ha-solarman/commit/c0e7e50eed207998e0c087e49041b1246bb810e4) * [refactor: Rename profile pylontech_force-h to pylontech_force](https://github.com/davidrapan/ha-solarman/commit/d583c8b1c4da2c295da7dd440e5c2ca2d56fb36f)
What did it do? Loaded profile w/ default modifier value?
Oh yeah the migration only works w/ the default profile and modifier is universal for many other profiles, that’s why. But I should have made it a selector. You’re right....
Hi @lucky5822, did you tried every profile available (for Afore)?
Can you show me debug log w/ profile set to `afore_hybrid`?
I'll need the entire file. Just drag and drop it here. 😉
Keep Alive
Your device most likely uses different register ranges and therefore a new separate profile is needed, but unfortunately without documentation there is very little we can do.
Hi @jeffersonbernardo1981, what exact device and model you have?