fboundy / pv_opt

Home Assistant PV Optimisation for Solis Inverters
MIT License
22 stars 5 forks source link

Unable to locate pv_opt.log #266

Open Pyinthesky99 opened 4 days ago

Pyinthesky99 commented 4 days ago

I have, hopefully, installed all prerequisites and installed pv_opt via HACS but am unable to locate pv_opt.log to check that it is running. I assume it is not as there are new entities in /Settings/Devices and Services/Entities in Home Assistant.

I am running the Solarman Integration on HAOS running in a Proxmox vm accessed via Edge on Win 11.

Pyinthesky99 commented 4 days ago

AppDaemonlog.txt no entry "added log pv_opt.log" in Appdaemon log

stevebuk1 commented 4 days ago

It doesnt look like appdeamon is finding your Pv_opt install.

Section 11 of the install guide talks about editting appdeamon.yaml, here:

https://github.com/fboundy/pv_opt?tab=readme-ov-file#11-configure-appdaemon

The important line is this: app_dir: /homeassistant/appdaemon/apps

as HACS installs Pv_opt to this location (/homeassistant/appdaemon/apps)

Check:

1) that the Pv_opt files exist at /homeassistant/appdaemon/apps/pv_opt (they are pv_opt.py, pypy.py and solis.py, plus others) 2) that your appdeamon.yaml contains a line app_dir: /homeassistant/appdaemon/apps

Note that appdeamon.yaml (and helloworld.py, which from your logs is loading correctly) is in a completely different area. Mine is in /addon_configs/a0d7b954_appdaemon/

Pyinthesky99 commented 3 days ago

Hi Steve. Thanks for the response. As below, assuming the ‘top’ CONFIG is “/homeassistant’, immediately below. in the tree is /addon_configs/a0d7b954_appdaemon/ which contains appdaemon.yaml with the necessary pv_opt changes On the same ‘level’ is /appdaemon/apps/pv_opt/ which contains pv_opt files but critically not pv_opt_log. Doing a linux find . -name “pv_opt_log” from root returns no result. From root, I am assuming again, /homeassistant resides in /mnt/data/supervisor. Interestingly there is, along with /homeassistant , another(?) /addon_configs directory which contains (another?) /a0d7b954_appdaemon directory which contains an appdaemon.yaml and /compiled /dashboards /namespaces and /www directories and an /apps directory that contains apps.yaml and hello.py. This appdaemon.yaml is un-modded, it contains none of the pv_opt script, unlike the one below.

image

All very confusing, am I looking at the correct appdaemon.yaml?

stevebuk1 commented 3 days ago

Ok, really not sure about whats at /mnt/data/supervisor. I'm on a Pi4 and /mntis empty.

Ignoring that path for the moment, your directory structure looks the same as mine, i.e.: /addon_configs/a0d7b954_appdaemon and /homeassistant/appdaemon/apps/pv_opt

The log file is called pv_opt.log (not pv_opt_log) and confusingly isnt in the pv_opt area or even the apps area, it should be here: /homeassistant/appdaemon/pv_opt.log

All errors are logged to this file: /homeassistant/appdaemon/error.log

Do you have these?

If so, please post these and also this file: /homeassistant/appdaemon/apps/pv_opt/config/config.yaml

Pyinthesky99 commented 2 days ago

Apologies, pv_opt_log was a typo, a find on pv_opt.log returned nothing.

Using the path in the previous comment to /homeassistant the only thing in /appdaemon is another folder /apps which contains folder /pv_opt, no log files so no error.log

image

This is a copy of pv_opt/config/config.yaml (I haven’t the technology for a direct copy so copy/pasted via notepad) config.yaml.txt

stevebuk1 commented 2 days ago

Thanks for the screengrab. This is all sounding remarkably similar to this issue : #264 and specifically this post: https://github.com/fboundy/pv_opt/issues/264#issuecomment-2318202733.

I think the correct appdaemon.yaml to edit is the one at mnt/data/supervisor/addon_configs/a0d7b954_appdaemon/appdaemon.yaml, and not the one inside the homeassistant directory.

@pbcjh10, would you mind sharing the additional init.py file you had to create and also the location of your appdaemon.yaml file and its contents?

Pyinthesky99 commented 2 days ago

Thanks for the info, I was looking at #264 earlier and thought it looked rather familiar. I have edited the other appdaemon.yaml and will await the info from @pbcjh10 Regards