You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Advice: Switching from GECloud Integration to PredBat's internal GECloud?
#4122
I am currently using the GE Cloud Integration but think it's time to switch to the internal engine.
I'm a bit nervous and have had some strange battery drift issues recently so think I should align myself with the all in one solution. Could I please ask for some guidance as to what the correct approach to this, to ensure that I keep my existing sensor names the same (i.e. not create new ones)?
Is my current YAML OK for a GE EMS with 2x AC3 inverters? extract of relevant sections below.
Do I just change ge_cloud_data: from False to True and disable the GECloud stand alone integration and will the entity names stay the same?
Are my Inverters correctly specified for the EMS and 2x AC3 inverters? (type GEE)
Can I delete the REST control section?
### INVERTER Information
geserial: 'ce2209G009'
geserial2: 'ce2244G991'
geseriale: 'ems2308155'
balance_inverters_seconds: 0
num_inverters: 2
inverter_type:
- 'GEE'
- 'GEE'
### ENERGY Sensors (Incrementing kwh)
load_today:
# - sensor.ge_inverter_{geseriale}_consumption_total
- sensor.ems_load_energy
#- sensor.ems_load_energy_daily
# - sensor.ems_load_energy_weekly
# - sensor.ems_load_energy_monthly
import_today:
- sensor.ge_inverter_ems2308155_grid_import_today
export_today:
- sensor.ge_inverter_ems2308155_grid_export_today
pv_today:
- sensor.ge_inverter_{geseriale}_solar_total
# 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: 'redacted'
# If not using REST then instead set the Control here (one for each inverter)
# You should keep this section even when using REST as a fallback if it fails and for charge curve calculations
**charge_rate:
- number.ge_inverter_{geserial}_battery_charge_power
- number.ge_inverter_{geserial2}_battery_charge_power
discharge_rate:
- number.ge_inverter_{geserial}_battery_discharge_power
- number.ge_inverter_{geserial2}_battery_discharge_power
battery_power:
- sensor.ge_inverter_{geserial}_battery_power
- sensor.ge_inverter_{geserial2}_battery_power
pv_power:
- sensor.ge_inverter_{geseriale}_solar_power
- 0
# - sensor.ge_inverter_{geserial}_solar_power
# - sensor.ge_inverter_{geserial2}_solar_power
load_power:
- sensor.ge_inverter_{geserial}_consumption_power
- sensor.ge_inverter_{geserial2}_consumption_power
soc_percent:
- sensor.ge_inverter_{geserial}_battery_soc
- sensor.ge_inverter_{geserial2}_battery_soc
soc_max:
- sensor.ge_inverter_{geserial}_battery_size
- sensor.ge_inverter_{geserial2}_battery_size
reserve:
- number.ge_inverter_{geserial}_battery_reserve_limit
- number.ge_inverter_{geserial2}_battery_reserve_limit
# inverter_time:
# - sensor.ge_inverter_{geseriale}_inverter_time
# - sensor.ge_inverter_{geseriale}_inverter_time
charge_start_time:
- select.ge_inverter_{geseriale}_charge_start_time_slot_1
- select.ge_inverter_{geseriale}_charge_start_time_slot_1
charge_end_time:
- select.ge_inverter_{geseriale}_charge_end_time_slot_1
- select.ge_inverter_{geseriale}_charge_end_time_slot_1
idle_start_time:
- select.ge_inverter_{geseriale}_discharge_start_time_slot_1
- select.ge_inverter_{geseriale}_discharge_start_time_slot_1
idle_end_time:
- select.ge_inverter_{geseriale}_discharge_end_time_slot_1
- select.ge_inverter_{geseriale}_discharge_end_time_slot_1
charge_limit:
- number.ge_inverter_{geseriale}_charge_soc_limit_1
- number.ge_inverter_{geseriale}_charge_soc_limit_1
discharge_start_time:
- select.ge_inverter_{geseriale}_export_start_time_slot_1
- select.ge_inverter_{geseriale}_export_start_time_slot_1
discharge_end_time:
- select.ge_inverter_{geseriale}_export_end_time_slot_1
- select.ge_inverter_{geseriale}_export_end_time_slot_1**
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I am currently using the GE Cloud Integration but think it's time to switch to the internal engine.
I'm a bit nervous and have had some strange battery drift issues recently so think I should align myself with the all in one solution. Could I please ask for some guidance as to what the correct approach to this, to ensure that I keep my existing sensor names the same (i.e. not create new ones)?
Is my current YAML OK for a GE EMS with 2x AC3 inverters? extract of relevant sections below.
All reactions