HAOS v18.0 oddness?

[browellm]

Anyone noticed Predbat weirdness after moving to HAOS v18? My Predbat install was constantly showing calculating "active" with plans about 10 minutes behind but nothing untoward showing in the logs and no particular CPU issues.

I rolled back my VM to a prior snapshot and everything OK again. Seems to be nothing to do with Prebat versions either - currently on 8.40.14 and all is well. I will take another snapshot again shortly and attempt HAOS v18 again to confirm it.

[ggr01]

Im also seeing predbat constantly "active" since upgrading to HAOS v18

[Adrian57]

Yep, me too. Calculation time seem very slow - longer than the cycle time (10 mins). I am getting " Plan data is stale (last updated >15 minutes ago)" regularly. Full reboot of hardware seems to fix it for a few hours.

Edit: reverting haos to 17.3 fixes it.

[symonchester]

Likewise, same issue here

[browellm]

@springfall2008 few reports confirming this now. Do you want me to open this as an issue?

I have held off updating to HAOS v18 after reinstating my earlier snapshot.

[thewishy]

"ha os boot-slot other" to save others looking :)

[Metal-rock]

Ive found to fix this you now need to use the IP address (http://xx.xx.xx.xx:xxxx) instead of http://homeassistant.local:xxxx for givtcp_rest in apps.yaml

[ggr01]

Replacing with IP address in apps.yaml worked for me, using HAOS v18 and seems to play nice now. Thanks @Metal-rock
@springfall2008 think the documentation and default YAML needs to be updated if nothing else