gcoan
commented
2 weeks ago Hello and welcome to Predbat
I'll try and help answer your questions...
Based on instructions I think I need to replace the contents of /addon_configs/46f69597_appdaemon-predbat/apps/apps.yaml with the contents of givenery_cloud.yaml and then modify that version.
Yes that's correct. My intent is to collapse all the different template files down into ideally just one 'master' template file as having lots of different templates might make it easier for the newcomer to have the right starting point, but it adds an additional 'copy the right template file in' step, and moreover what happens is that new features don't get added consistently to all the different apps.yaml files and this causes different problems.
I see references to geseriale with e on the end, but is that a mistype? I think it should be without e on the end?
Yes that is a typo, I will correct that, it should be 'geserial' as per apps.yaml:
'# Set to auto-match with a GivEnergy serial number, but you can override the serial or the sensor names
'# if it doesn't work or if you have more than one inverter you will need to list both
geserial: 'cexxxx'
geserial2: 'ceyyyy'I only have 1 inverter. Do i need to comment all the references to second inverter {geserial2} throughout the yaml?
Yes you should do.
And then I see reference to separate sensors for each of the 3 phases, but sorry I don't know where to get that information. Is it possible to add instructions for how to deal with 3 phase GE inverter?
In the apps.yaml documentation https://springfall2008.github.io/batpred/apps-yaml/#data-from-home-assistant the 'add entries for each phase' is in the section for configuring Predbat to use PV, load, import and export data from Home Assistant. It doesn't appear in the following section for GE cloud data so I think the assumption is that the GE cloud data when retrieved is for all 3 phases, not just for a single phase. Indeed there's no configuration options to look at different phase data so if the GE cloud data doesn't cover all 3 phases then we have a different issue.
I will update the documentation to make this clearer.
Are there other things I need to change due to 3 phase? I was also trying to look at installing dashboard from predbat_dashboard.yaml but I can't find it. I guess this will also be complicated by 3 phases?
I'm not sure that you being on 3 phases should affect the dashboard as predbat manages all phases together and there isn't separate sensors for the different phases. When GivTCP is working for the 3 phases then yes you probably will want to have different dashboard views for the different phases and use eg the GivTCP battery card to show the phase activity.
But the predbat_dashboard appears to be broken. In my own install the logfile says that the dashboard is being written to but the last write of it is April 2024.
I'll raise a separate predbat github issue for that to Trefor to look at
LeeFarm11
Is your feature request related to a problem? Please describe.
Sorry if this is in wrong place. If it is wrong place, please can you point me to the correct place.
I have Gen 3, 11kw 3 phase inverter. GivTCP is not yet working (I'm working with britkat1980). I'm trying to install Appdaemon-Predbat combined install, but with ge_cloud. I'm struggling with template file in https://github.com/springfall2008/batpred/tree/main/templates Based on instructions I think I need to replace the contents of /addon_configs/46f69597_appdaemon-predbat/apps/apps.yaml with the contents of givenery_cloud.yaml and then modify that version.
I see references to geseriale with e on the end, but is that a mistype? I think it should be without e on the end?
'# Set to auto-match with a GivEnergy serial number, but you can override the serial or the sensor names '# if it doesn't work or if you have more than one inverter you will need to list both geserial: 'cexxxx' geserial2: 'ceyyyy'
'# Sets the maximum period of zero load before the gap is filled, default 30 minutes '# To disable set it to 1440 load_filter_threshold: 30
'# '# Sensors, more than one can be specified and they will be summed up automatically '# '# For two inverters the load today would normally be the master load sensor only (to cover the entire house) '# If you have three phase and one inverter per phase then you would need three load sensors '# '# For pv_today if you have multiple solar inverter inputs then you should include one entry for each inverter '# load_today:
sensor.geinverter{geserial}_solar_today
'# Load forecast can be used to add to the historical load data (heat-pump) '# To link to Predheat '# Data must be in the format of 'last_updated' timestamp and 'energy' for incrementing kWh '#load_forecast: '# - predheat.heat_energy$external '# '# If you enable ge_cloud_data then the load/import and export data will be fetches from the GE cloud instead of from GivTCP sensors '# this is usually less efficient and of course prone to internet downtime, but could be useful if you lost your GivTCP data '# Set the serial to the inverter serial to pull the data from and the key to your API key '# When this is set load_today, import_today and export_today are not used '# ge_cloud_data: False ge_cloud_serial: '{geseriale}' ge_cloud_key: 'xxxx'
'# Controls/status - must by 1 per inverter '# num_inverters: 1 inverter_type:
I only have 1 inverter. Do i need to comment all the references to second inverter {geserial2} throughout the yaml?
And then I see reference to separate sensors for each of the 3 phases, but sorry I don't know where to get that information. Is it possible to add instructions for how to deal with 3 phase GE inverter?
Are there other things I need to change due to 3 phase? I was also trying to look at installing dashboard from predbat_dashboard.yaml but I can't find it. I guess this will also be complicated by 3 phases?
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.