pb with the apsystem integration in core 6.0

[yepp31]

The problem

Hi, Sorry for my English. before core 6.0 update I had local apsystem api. the integration was very good but with the migration, the Apsystem power status button (allowing the micro inverter to be turned on) disappeared. it is the same with the possibility of limiting the output power of the microinverter (from zero to 800w). here is an image of the previous version framed in red. is it possible to put these two functions back in the core version? THANKS

What version of Home Assistant Core has the issue?

6.0

What was the last working version of Home Assistant Core?

5.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

apsystem

Link to integration documentation on our website

https://www.home-assistant.io/integrations/apsystems

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @mawoka-myblock, @sonnenladengmbh, mind taking a look at this issue as it has been labeled with an integration (apsystems) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `apsystems` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign apsystems` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

apsystems documentation apsystems source _{^{(message by IssueLinks)}}

[joostlek]

Thank you for reaching out. We use GitHub for tracking issues, not for providing support or tracking feature requests.

If you want to suggest a feature, you should try our Community Forum: Feature Requests.

If you have additional questions, feel free to join our Discord chat server.

Thanks! 👍

[malosaa]

Hi @joostlek the codeowner closed the repo from the hacs integration, and pointing to the new one. So if the new one is lacking needed features than i ain't gonna go in the community forum asking this feature that already existed. As said the same codeowner is the same one who maintains this code as well..

Also there is also no way to seamless migrate from his old code to the new one.. messing up my old data.. Would like the owner make a topic at Community Forum: how to migrate and fix the problem @yepp31 was talking about.

Right now i'm sticking with the hacs version.

[joostlek]

I know, and I also know he's working on the other two. And I know he has seen this issue as well so it's not that I don't want to say it's a non issue, but it's not suitable for an issue here on GitHub :)

[mawoka-myblock]

Don't worry, I'll address this once the max output PR will be merged. Then, I'll add the on-off toggle and after that, I'll add support for the EZ1-H.

[sippeeey]

How is it possible to migrate all statistic data from old entitys into the new, because when i delete the custom repo, it will be delete the old entitys?

[mawoka-myblock]

You can migrate relatively easily, just follow the instructions here: https://community.home-assistant.io/t/how-to-apsystems-modell-ez1-m-monitoring/603132/86?u=mawoka