mypyllant broke since HA Core 2025.5.0

[PV-Joe]

trafficstars

Problem description

Updated to HA Core 2025.5.0 and myPyllant stopped working:

Logs

Setup failed for custom integration 'mypyllant': Requirements for mypyllant not found: ['myPyllant==0.9.0'].

Unable to install package myPyllant==0.9.0: × No solution found when resolving dependencies: ╰─▶ Because mypyllant==0.9.0 depends on pydantic>=2.10.4,<2.11.dev0 and pydantic==2.11.3, we can conclude that mypyllant==0.9.0 cannot be used. And because you require mypyllant==0.9.0, we can conclude that your requirements are unsatisfiable.

Please fix 😀

[PV-Joe]

Found this quick fix and it's working:

https://github.com/signalkraft/mypyllant-component/issues/319#issuecomment-2860634857

[matejsalamon]

The same issue on my site after HA update.

[rholligan]

Same issue here after HA Core 2025.5.0 update

[beezly]

Duplicate of #315

[PaulC1965]

Same issue here. Deleted the integration and then readded and got following message: Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble. I’m restoring my backup now and wait to read further in this forum to see what will happen. Not sure whether anyone else got this,message.

[lanthi63]

same issue here

[wardog-82]

Ebenfalls das gleiche Problem

[bauchschuss]

Same issue on my HA instance

[PV-Joe]

Easy fix for the problem until the developer releases a new version:

https://github.com/signalkraft/mypyllant-component/issues/319#issuecomment-2860634857

[boelle]

Easy fix for the problem until the developer releases a new version:

#319 (comment)

i just tried... did not work

{
  "domain": "mypyllant",
  "name": "myVAILLANT",
  "codeowners": [
    "@signalkraft"
  ],
  "config_flow": true,
  "documentation": "https://github.com/signalkraft/mypyllant-component#readme",
  "integration_type": "hub",
  "iot_class": "cloud_polling",
  "issue_tracker": "https://github.com/signalkraft/mypyllant-component/issues",
  "requirements": [
     git+https://github.com/arturonaredo/myPyllant.git@main#egg=myPyllant
  ],
  "version": "v0.9.2b0"
}

[boelle]

trying to downgrade... on commandline use this command

ha core update --version 2025.4.4

will report back if it works

[PaulC1965]

I just rolled back my backup to HA 2025.4.4 and worked just fine. It took two hours but it worked. I did not give the below a try as it is using a pre-release and I don’t want to use that I am on version": "v0.9.1”. I’ll wait for a final new release before upgrading to latest core. Sent from my wireless device. On 9 May 2025, at 17:06, Bo Herrmannsen @.***> wrote: boelle left a comment (signalkraft/mypyllant-component#320) trying to downgrade... on commandline use this command ha core update --version 2025.4.4

will report back if it works

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[boelle]

i could go back, but it does still not load... will do a reboot

but yes if it then loads i will wait until a prober fix is released

[PaulC1965]

But it takes a long time. On my case more than two hours. It includes the historical database which is 7GB large. I had to be patient. First thought it didn’t work either but eventually it all worked out well. Sent from my wireless device. On 9 May 2025, at 17:14, Bo Herrmannsen @.***> wrote: boelle left a comment (signalkraft/mypyllant-component#320) i could go back, but it does still not load... will do a reboot but yes if it then loads i will wait until a prober fix is released

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[boelle]

for me i had to redownload the integrartion and restart...

@signalkraft we are all looking towards your corner :-D

[arvdrpoo]

The same thing happened with HA 2025.1 if I remember correctly.

How can we prevent this from happening in the future?

[boelle]

The same thing happened with HA 2025.1 if I remember correctly.

How can we prevent this from happening in the future?

i dont think you can unless you know how to write code, and even then there is the risk an update will break things, that is why you should always backup so you can go back

[boelle]

@signalkraft

btw this a dublicate of:

https://github.com/signalkraft/mypyllant-component/issues/319 https://github.com/signalkraft/mypyllant-component/issues/315

[mike4001]

I really hope @signalkraft is still around.

This time it´s an easy fix but an abandoned integration is not good ...

[PaulC1965]

I hope so too Mike. I haven’t seen any reaction from @signalkraft yet on this specific topic. Maybe he has some time off. Let’s hope so. I’m also building a lot on this integration, if it is not going to be maintained anymore this would be a real pity here.

On 11 May 2025, at 09:21, mike4001 @.***> wrote:

mike4001 left a comment (signalkraft/mypyllant-component#320) https://github.com/signalkraft/mypyllant-component/issues/320#issuecomment-2869567967 I really hope @signalkraft https://github.com/signalkraft is still around.

This time it´s an easy fix but an abandoned integration is not good ...

— Reply to this email directly, view it on GitHub https://github.com/signalkraft/mypyllant-component/issues/320#issuecomment-2869567967, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJOXDX7MSJFTV62ECOBMBJL2533AFAVCNFSM6AAAAAB4VPFK7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNRZGU3DOOJWG4. You are receiving this because you commented.

[Seliaks65]

Easy fix for the problem until the developer releases a new version: #319 (comment)

i just tried... did not work

{
  "domain": "mypyllant",
  "name": "myVAILLANT",
  "codeowners": [
    "@signalkraft"
  ],
  "config_flow": true,
  "documentation": "https://github.com/signalkraft/mypyllant-component#readme",
  "integration_type": "hub",
  "iot_class": "cloud_polling",
  "issue_tracker": "https://github.com/signalkraft/mypyllant-component/issues",
  "requirements": [
     git+https://github.com/arturonaredo/myPyllant.git@main#egg=myPyllant
  ],
  "version": "v0.9.2b0"
}

This did work for me - looks like you've left off the quotation marks that should be at the beginning and end of git+https line:

"git+https://github.com/arturonaredo/myPyllant.git@main#egg=myPyllant"

[PV-Joe]

@boelle

Try with the quotation marks! I'm sure it will work for you after that.

Here they go (marked in red):

[boelle]

maybe @arturonaredo should make a pull request ?

[boelle]

anyways...

=

[plastikschnitzer]

Same issue here also in HA 2025.5.1 and mypyllant 0.9.2b0

[Seliaks65]

anyways...

Is there a stray | symbol immediately after the quotation mark at the end? That shouldn't be there. Remove that, then restart HA. I presume you're saving the yaml file before reloading.

[boelle]

anyways...

Is there a stray | symbol immediately after the quotation mark at the end? That shouldn't be there. Remove that, then restart HA. I presume you're saving the yaml file before reloading.

nope, thats the cursor

[boelle]

Q... its easy to do an fork, but what file changes would be needed to make it work?

i'm not a programmer but willing to host a fork until @signalkraft chimes in

https://github.com/arturonaredo/myPyllant does not have the same file structure so i think something is missing or been left out on purpose

[Seliaks65]

anyways...

Is there a stray | symbol immediately after the quotation mark at the end? That shouldn't be there. Remove that, then restart HA. I presume you're saving the yaml file before reloading.

nope, thats the cursor

Thought it might be the cursor. The only thing I can think is whether the indentation is correct at that line. In the version posted elsewhere the first quotation mark of the added line is in line with the first e in requirements, whilst in yours it's in line with the q - may need to delete a space?

[boelle]

well i just placed it there as that is where the org line began

i might try again later after dinner, maybe tomorrow... and i wonder why the fork link is not a 100% fork (ie it has files missing and a few folders are left out)