Solax X1 AC Inverter compatibility #149
Comments
|
I've added this as an inverter type in pre-release v4.0.0-alpha-4 along with the Sunsynk. You will need to install this as a Beta version through HACS and also manually copy the |
|
Thank you very much for this, really appreciate it. |
|
Not sure where the two files you requested are. If you can please let me know I can then go and hunt them down for you. However, here's an extract from the AppDaemon error Log:
2024-03-16 23:45:05.999301 WARNING pv_opt: ------------------------------------------------------------` |
|
Here's a screenshot of my dashboard: 
|
|
If you set up In v4.0.0-alpha-5 I have merged all the |
|
Thanks for this. I've copied the config.yaml contents, replaced the info in my local version as requested and uncommented and amended the various sections. AppDaemon is also working now (following your instructions it was "starting" and the log said it was running. However I had a red dot against it and it didn't appear to be running. I removed it, reinstalled and then set it up as default settings and it ran OK. I then amended the config and rebooted my RasPi, and it's working now. so, I think it's running, there are no log files being generated that I can see, and the charts are still as my earlier screenshot. Thanks |
|
In the absence of the log files are you able to copy the contents of the logs from the AppDaemoin web UI?
…On 18 Mar 2024 at 00:36 +0000, punkymuzzle ***@***.***>, wrote:
Thanks for this.
I must have misunderstood the bit about samba, as I thought it was optional, and as I have ssh access to my device I can access the files. So I've installed and configured samba and can browse to the shares with no issues. However, I still can't see any error.log or pvopt.log anywhere.
I've copied the config.yaml contents, replaced the info in my local version as requested and uncommented and amended the various sections.
AppDaemon is also working now (following your instructions it was "starting" and the log said it was running. However I had a red dot against it and it didn't appear to be running. I removed it, reinstalled and then set it up as default settings and it ran OK. I then amended the config and rebooted my RasPi, and it's working now.
so, I think it's running, there are no log files being generated that I can see, and the charts are still as my earlier screenshot.
Thanks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
When I look at the AppDaemon Web Gui, there are no logs to look at. None whatsoever. Not sure if I'm missing something to get this working?? Here's the AppDaemon Logfile: Add-on: AppDaemon
|
|
`--- longitude: -xx.xxxxxx logs: |
|
There is something wrong with your AppDaemon installation. It is not loading the HASS plugin correctly: The module it is trying to load is wrong. It should be |
|
OK - you need to correct: to |
|
Thanks for spotting that.... However, there is still one warning ref a missing URL, but not sure if that one matters (or if it does, where to put the URL) Logfile: Add-on: AppDaemon
|
|
I've tailored some of the chart sensors in the screenshot below (this still needs reworking as some of the numbers aren't right), but it still loos like the pvopt entities aren't being created: |
|
Do you have the expected log files now? They should be in the Web UI and the samba share |
|
No, nothing in any of the logs when looking via the AppDaemon webgui
…On Mon, 18 Mar 2024, 12:24 fboundy, ***@***.***> wrote:
Do you have the expected log files now? They should be in the Web UI and
the samba share
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR35Z774Q6HYDVOGVP53LYY3MHHAVCNFSM6AAAAABEY2DWYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTG43TINRVGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I think @solarjones had a similar issue with logging but I can't find his solution |
|
What he said was: Suggest you make sure that samba share is working and that you can create and read files in the folders you have referenced for the logs in |
|
Just checked and i can access the samba share, create, amend, and delete files here.
OK thanks for your help. Not really sure what else to do but I'll have another look around to see if I can stumble across them. Thank you |
|
The AppDaemon Logs visible via Refresh button are different to those written to Pv_opt.log, main.log and error.log. I was expecting the logs to be written within the HA folder structures when viewed from FileEditor or Visual Studio, but they aren't. That was my misunderstanding and struggled trying all sorts. In the end I simply followed the PV_Opt instructions to the letter for the config.yaml (I had different paths which weren't valid but didn't error) and samba share. It then sprang into logging life! |
|
@solarjones OK thanks very much, I'll revisit the instructions and double check. |
|
@punkymuzzle |
|
OK so I've gone through the AppDaemon config file again, restarted numerous times. There still seem to be no log files generated. I've:
AppDaemon logfile: `s6-rc: info: service s6rc-oneshot-runner: starting Add-on: AppDaemon
|
|
I've also checked the config.yaml file but can't see any errors in this either. File as follows: Internal configuration --- DO NOT EDIT ---pvpy: inverters: pv_opt: log: pv_opt_log debug: TrueUser configuration --- EDIT AWAY! ---========================================System parameters========================================If true the current config in HA will be over-written with that in the config.yaml.overwrite_ha_on_restart: true redact_personal_data_from_log: falseread_only: false ========================================Plant parameters========================================All parameters can be a number or point to an entity UNLESS they start with 'id_'. All ofthese are required but will be defaulted if not specifiedbattery_capacity_wh: 4500 maximum_dod_percent: 15charger_power_watts: 3500 ========================================Solcast configuration========================================id_solcast_today: sensor.solcast_pv_forecast_forecast_today ========================================Solar and consumption forecast parameters========================================Valid options are:Solcast - the Solcast mid-case forecast [Default]Solcast_p90 - the Solcast high estimateSolcast_p10 - the Solcast high estimateSet this using an "input_select" helper and it can be varied on the flysolar_forecast:
# consumption estimationuse_consumption_history: true ========================================Octopus account parameters========================================octopus_auto: False # Read tariffs from the Octopus Energy integration. If successful this over-rides the following parametersoctopus_account: ************ The following Can be omitted if either of the above options is working correctly:octopus_import_tariff_code: ******************************* octopus_import_tariff_code: E-2R-VAR-22-11-01-Goctopus_export_tariff_code: E-1R-AGILE-OUTGOING-19-05-13-Goctopus_import_tariff_code: E-1R-AGILE-23-12-06-G# octopus_export_tariff_code: E-1R-OUTGOING-LITE-FIX-12M-23-09-12-Goctopus_export_tariff_code: E-1R-OUTGOING-FIX-12M-19-05-13-Goctopus_import_tariff_code: E-1R-FLUX-IMPORT-23-02-14-Goctopus_export_tariff_code: E-1R-FLUX-EXPORT-23-02-14-G===============================================================================================================Brand / Integration Specific Config: SOLIS_SOLAX_MODBUS: https://github.com/wills106/homeassistant-solax-modbus===============================================================================================================These are the default entities used with the Solis Solax Modbus integration. You can change them here and over-ride the defaultsinverter_type: SOLIS_SOLAX_MODBUSdevice_name: solisbattery_voltage: sensor.{device_name}_battery_voltageupdate_cycle_seconds: 15maximum_dod_percent: number.{device_name}_battery_minimum_socid_consumption_today: sensor.{device_name}_consumption_todayid_grid_import_today: sensor.{device_name}_grid_import_todayid_grid_export_today: sensor.{device_name}_grid_export_todayid_battery_soc: sensor.{device_name}_battery_socid_timed_charge_start_hours: number.{device_name}_timed_charge_start_hoursid_timed_charge_start_minutes: number.{device_name}_timed_charge_start_minutesid_timed_charge_end_hours: number.{device_name}_timed_charge_end_hoursid_timed_charge_end_minutes: number.{device_name}_timed_charge_end_minutesid_timed_charge_current: number.{device_name}_timed_charge_currentid_timed_discharge_start_hours: number.{device_name}_timed_discharge_start_hoursid_timed_discharge_start_minutes: number.{device_name}_timed_discharge_start_minutesid_timed_discharge_end_hours: number.{device_name}_timed_discharge_end_hoursid_timed_discharge_end_minutes: number.{device_name}_timed_discharge_end_minutesid_timed_discharge_current: number.{device_name}_timed_discharge_currentid_timed_charge_discharge_button: button.{device_name}_update_charge_discharge_timesid_inverter_mode: select.{device_name}_energy_storage_control_switch==============================================================================================================Brand / Integration Specific Config: SOLIS_CORE_MODBUS: https://github.com/fboundy/ha_solis_modbus==============================================================================================================These are the default entities used with the Solis Core Modbus integration. You can change them here and over-ride the defaultsinverter_type: SOLIS_CORE_MODBUSdevice_name: solismodbus_hub: "{device_name}"modbus_slave: 1battery_voltage: sensor.{device_name}_battery_voltagemaximum_dod_percent: sensor.{device_name}_overdischarge_socupdate_cycle_seconds: 60id_consumption_today: sensor.{device_name}_daily_consumptionid_grid_power: sensor.{device_name}_grid_active_powerid_inverter_ac_power: sensor.{device_name}_inverter_ac_powerid_battery_soc: sensor.{device_name}_battery_socid_timed_charge_start_hours: sensor.{device_name}_timed_charge_start_hourid_timed_charge_start_minutes: sensor.{device_name}_timed_charge_start_minuteid_timed_charge_end_hours: sensor.{device_name}_timed_charge_end_hourid_timed_charge_end_minutes: sensor.{device_name}_timed_charge_end_minuteid_timed_charge_current: sensor.{device_name}_timed_charge_current_limitid_timed_discharge_start_hours: sensor.{device_name}_timed_discharge_start_hourid_timed_discharge_start_minutes: sensor.{device_name}_timed_discharge_start_minuteid_timed_discharge_end_hours: sensor.{device_name}_timed_discharge_end_hourid_timed_discharge_end_minutes: sensor.{device_name}_timed_discharge_end_minuteid_timed_discharge_current: sensor.{device_name}_timed_discharge_current_limitid_inverter_mode: sensor.{device_name}_energy_storage_control_switch==============================================================================================================Brand / Integration Specific Config: SOLIS_SOLARMAN: https://github.com/StephanJoubert/home_assistant_solarman==============================================================================================================These are the default entities used with the Solis Solarman integration. You can change them here and over-ride the defaultsinverter_type: SOLIS_SOLARMANdevice_name: solisbattery_voltage: sensor.{device_name}_battery_voltagemaximum_dod_percent: 15update_cycle_seconds: 60id_consumption_today: sensor.{device_name}_daily_house_backup_consumptionid_grid_power: sensor.{device_name}_meter_active_powerid_inverter_ac_power": sensor.{device_name}_inverter_ac_powerid_battery_soc: sensor.{device_name}_battery_socid_backup_mode_soc:id_timed_charge_start_hours: sensor.{device_name}_timed_charge_start_hourid_timed_charge_start_minutes: sensor.{device_name}_timed_charge_start_minuteid_timed_charge_end_hours: sensor.{device_name}_timed_charge_end_hourid_timed_charge_end_minutes: sensor.{device_name}_timed_charge_end_minuteid_timed_charge_current: sensor.{device_name}_timed_charge_currentid_timed_discharge_start_hours: sensor.{device_name}_timed_discharge_start_hourid_timed_discharge_start_minutes: sensor.{device_name}_timed_discharge_start_minuteid_timed_discharge_end_hours: sensor.{device_name}_timed_discharge_end_hourid_timed_discharge_end_minutes: sensor.{device_name}_timed_discharge_end_minuteid_timed_discharge_current: sensor.{device_name}_timed_discharge_currentid_inverter_mode: sensor.{device_name}_storage_control_mode===============================================================================================================Brand / Integration Specific Config: SOLAX_X1:===============================================================================================================These are the default entities used with the Solax X1integration. You can change them here and over-ride the defaultsinverter_type: SOLAX_X1 maximum_dod_percent: number.{device_name}_battery_minimum_capacity ===============================================================================================================Brand / Integration Specific Config: SUNSYNK_SOLARSYNK2:===============================================================================================================These are the default entities used with the Sunsynk Solarsynk2 integration. You can change them here and over-ride the defaultsinverter_type: SUNSYNK_SOLARSYNK2device_name: solarsynkinverter_sn: 000000 # enter {sunsynk_serial} from solarsynk2 addonmaximum_dod_percent: sensor.{device_name}_{inverter_sn}_battery_shutdown_capid_battery_soc: sensor.{device_name}_{inverter_sn}_battery_socid_consumption_today: sensor.{device_name}_{inverter_sn}_day_load_energyid_grid_import_today: sensor.{device_name}_{inverter_sn}_day_grid_importid_grid_export_today: sensor.{device_name}_{inverter_sn}_day_grid_importsupports_hold_soc: falseupdate_cycle_seconds: 300So unless anyone else has any more pointers, I'm all out of ideas. |
|
Here's the initial AppDaemon log from my setup. Note the Added log: PV_Opt entry. Before I had mine working, mine used to have this missing as per your entry posted above. On your PC/MAC, when you connect to your HA server via samba, under SHARE, create a directory LOG. No need to create the log files, they will automatically be generated. I did have to revisit the appdaemon.yaml to get it working by checked the tabbing on the logs section. Even one space out prevented it working for me. |
|
@solarjones Thanks very much for this. I've also SSH into the RasPi and looked at folder permissions in case it was unable to write there. I've changed permissions on the folder so any account can write to it, and then rebooted. |
|
The log files are set up by You might want to check the indentation in it to make sure it is correct. This is mine: Also please delete all |
|
@fboundy / @solarjones The cards are also looking a lot better as well: Thanks very much to you both for getting me this far, really appreciate it. Let me know if you need any more information. I'm working away tomorrow so won't have access to HA, but I'll catch up later in the evening. |
|
Thanks folks - I had the same indent issues with the log file setup in
appdaemon.yaml so hopefully I’ll be able to find those logs this evening !
🤞🏻
…On Mon, 18 Mar 2024 at 23:50, punkymuzzle ***@***.***> wrote:
@fboundy <https://github.com/fboundy> / @solarjones
<https://github.com/solarjones>
I've been through the config.yaml and double checked / amended the indents
etc, so it matches yours.
Rebooted and its started working a lot better !!!!!
That's weird, as the file editor wasn't showing any errors in my
indentation, so I thought it was OK.
I now have access to the logfiles as requested.
error.log <https://github.com/fboundy/pv_opt/files/14643545/error.log>
pv_opt.log <https://github.com/fboundy/pv_opt/files/14643547/pv_opt.log>
The cards are also looking a lot better as well:
image.png (view on web)
<https://github.com/fboundy/pv_opt/assets/10165751/afff71d5-74ab-4833-9664-69f49da49f2c>
image.png (view on web)
<https://github.com/fboundy/pv_opt/assets/10165751/80000512-911b-47ee-b3b2-2df9f509cd76>
image.png (view on web)
<https://github.com/fboundy/pv_opt/assets/10165751/e0e0b602-2949-46fa-bcbb-bf4ed896bccb>
image.png (view on web)
<https://github.com/fboundy/pv_opt/assets/10165751/b7658584-4881-4f91-b529-287718921081>
image.png (view on web)
<https://github.com/fboundy/pv_opt/assets/10165751/790c1592-5f26-4189-a4b4-9259c7a9a073>
Thanks very much to you both for getting me this far, really appreciate it.
Let me know if you need any more information. I'm working away tomorrow so
won't have access to HA, but I'll catch up later in the evening.
Thanks again
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMEIQ3ZOJIETQSM6GPVGJTYY54TRAVCNFSM6AAAAABEY2DWYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBVGMZTKOBSGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Hi all |
|
OK great, I'll keep an eye out for your message. |
|
Just to let you know that all of my dashboard cards now seem to be working. I hadn't touched them so I'm assuming it needed to run for a while to collect stats etc.
|
|
What hardware are you running HA on?
…On 28 Mar 2024 at 00:13 +0000, punkymuzzle ***@***.***>, wrote:
Just to let you know that all of my dashboard cards now seem to be working. I hadn't touched them so I'm assuming it needed to run for a while to collect stats etc.
Here's my Dashboard:
image.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
RasPi 4
…On Thu, 28 Mar 2024, 08:16 fboundy, ***@***.***> wrote:
What hardware are you running HA on?
On 28 Mar 2024 at 00:13 +0000, punkymuzzle ***@***.***>, wrote:
> Just to let you know that all of my dashboard cards now seem to be
working. I hadn't touched them so I'm assuming it needed to run for a while
to collect stats etc.
> Here's my Dashboard:
> image.png (view on web)
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR35YZQIK4WEYJPRNDGHDY2PGW3AVCNFSM6AAAAABEY2DWYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUGY2DEMBXGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
In your and Hoping to have something to you later today that will start to control the inverter for charging at least. Do you know the purpose of |
|
Also - I've done a bit of searching and as far as I can tell there is no way of forcing discharge on Solax inverters so I'm going to assume that the Forced Discharge switch is permanently off and disable it unless you tell me otherwise. |
|
OK, commented out in config.yaml as requested (second one was already commented out). The Lock state refers to access to the advanced menu in the Solax app. It allows access to advanced settings for the inverter: Hope the below helps, let me know if you need anything else. Lots of screenshots incoming.... :
Here's the descriptions of the different Charger Use Modes of the inverter, There doesn't seem to be a Forced Discharge option My Solax Dashboard looks like this: |
|
OK - so I'm going to assume we want "Unlocked Advanced" What does pressing the "Grid Export" button do and how does this relate to what mode you are in? |
|
I have pressed it but nothing has happened. The battery is not exporting. I think this may be a red herring as the Solax HA integration does not fully support my inverter (due to its age) so this may be a spurious entity which has no control over my inverter (that`s just my assumption). Shame really. Probably the closest thing I have to his is the feed in priority mode which dumps to the grid, but only after providing for the house load first? |
|
Yes, advanced unlock would be best as it gives access to all available entities |
|
OK - but Feed In Priority mode will only direct Solar to the grid and not battery charge? |
|
Yes, that`s true |
|
Give me some time and i will contact Solax support and ask the question. |
|
So not really any forced discharge capability then. The only time this has been of serious benefit to me is during the Octopus Saving Sessions which are almost certainly over now until next winter. |
|
|
|
OK installed and in read only mode. |
|
So I installed the dashboard that comes with Beta 10 - Looks like it's still referencing some of the Solis entities: I'll manually amend them again to match mine and let you know how it looks |
|
If it’s all looking OK still then please turn off read only, give it a couple of hours and then upload a copy of the log.
…On 28 Mar 2024 at 16:24 +0000, punkymuzzle ***@***.***>, wrote:
So I installed the dashboard that comes with Beta 10 - Looks like it's still referencing some of the Solis entities:
image.png (view on web)
I'll manually amend them again to match mine and let you know how it looks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
OK, amended the dashboard and it looks great:
|
|
You may also need to look at the entities in the dashboard.yaml, as I think it contains some of your data...... |
|
Another question: I have this entitiy: Assuming it doesn't interfere with your calculations? |
|
What you have in the dashboard as far as the output is entirely up to you. The only ones that matter for the calcs are those in the card under |
Shouldn't have done anything as the 1st force charge slot isn't scheduled till 22:30 but we are off peak now anyway. |
|
I'm closing this issue now as it's got very long! Have started #188 in its place |
|
Yes it seems to be OK thanks, battery is still feeding the house.
Read only has been off since 1715. I was going to let the first charge
start / complete and then upload the log files, as that might give you more
information?
…On Thu, 28 Mar 2024, 19:34 fboundy, ***@***.***> wrote:
If I take read only off, will it affect the battery now? I'm in the peak
price time and the battery is in self use mode and feeding the house.
Shouldn't have done anything as the 1st force charge slot isn't scheduled
till 22:30 but we are off peak now anyway.
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR35ZLX5BCSEON5AD6C43Y2RPD7AVCNFSM6AAAAABEY2DWYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVHE3DINRQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Sure |
|
OK thanks for letting me know
…On Thu, 28 Mar 2024, 19:38 fboundy, ***@***.***> wrote:
I'm closing this issue now as it's got very long! Have started #188
<#188> in its place
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR354KGMHV7GGNCQ45W23Y2RPRBAVCNFSM6AAAAABEY2DWYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVHE3TGMBVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi
This is an amazing addon for HA. Thanks very much for the effort being put into this.
Is there any possibility of making this compatible with the Solax X1 AC inverter? I believe that this is the gen 1 version of the current G4 inverter (although it's not Hybrid, so I have two Growatt string inverters feeding the PV charge).
I have managed to get my X1 AC working with HA, Modbus etc and have all the entities in place.
I went through the process of installing and configuring this, and tried to remap all the "solis" entities in the code to my corresponding solax entities. However, nothing seemed to work.
If this could be made to work for my Inverter this would be great (I know there are others out there as well with the same setup as me)
I'll try and provide as much information below as I can, but please ask if you need anything else.
Thank you very much
The text was updated successfully, but these errors were encountered: