GivTCP 1.1.7

I've been running this version for a week or so and as part of my original HA integration used the Print_Raw = True ENV to get more information out and into Node Red and hence HA - I use the REST API and Json.
Since the various updates to GivTCP I've changed my flow to no longer use the RAW registers - so this week turned off RAW.
I just looked at the output and I see that RAW is still enabled - I think someone else mentioned it was still active despite being off before.
Not too fussed about that, but what I noticed was when I grabbed the data and slapped it into a JSON formatter was the information available via the RAW output! The last section being interesting in particular:
"raw": {
"batteries": {},
"invertor": {
"active_power_rate": 100,
"arm_firmware_version": 450,
"battery_charge_limit": 50,
"battery_discharge_limit": 50,
"battery_discharge_min_power_reserve": 4,
"battery_low_force_charge_time": 6,
"battery_nominal_capacity": 160,
"battery_percent": 4,
"battery_power_mode": 1,
"battery_soc_reserve": 4,
"battery_type": 1,
"battery_voltage_adjust": 0,
"charge_and_discharge_soc": [
0,
0
],
"charge_slot_1": [
"00:00:00",
"00:00:00"
],
"charge_slot_2": [
"00:00:00",
"00:04:00"
],
"charge_soc_stop_1": 0,
"charge_soc_stop_2": 0,
"charge_status": 2,
"charge_target_soc": 100,
"charger_warning_code": 0,
"ct_adjust": 3,
"dci_1_i": 0,
"dci_1_time": 0,
"dci_2_i": 0,
"dci_2_time": 0,
"device_type_code": "2003",
"discharge_slot_1": [
"00:00:00",
"00:00:00"
],
"discharge_slot_2": [
"00:00:00",
"00:00:00"
],
"discharge_soc_stop_1": 0,
"discharge_soc_stop_2": 0,
"dsp_firmware_version": 450,
"e_battery_charge_day": 0,
"e_battery_charge_day_2": 0,
"e_battery_charge_total": 0,
"e_battery_discharge_day": 0,
"e_battery_discharge_day_2": 0,
"e_battery_discharge_total": 0,
"e_battery_throughput_total": 2614.5,
"e_discharge_year": 0,
"e_grid_in_day": 3.2,
"e_grid_in_total": 1964.6,
"e_grid_out_day": 0,
"e_grid_out_total": 156.2,
"e_inverter_in_day": 0,
"e_inverter_in_total": 115.2,
"e_inverter_out_day": 0.2,
"e_inverter_out_total": 2895.6,
"e_pv1_day": 0.1,
"e_pv2_day": 0.1,
"e_pv_total": 3068.6,
"e_solar_diverter": 0,
"enable_60hz_freq_mode": false,
"enable_ammeter": true,
"enable_auto_judge_battery_type": true,
"enable_bms_read": true,
"enable_buzzer": false,
"enable_charge": false,
"enable_charge_target": false,
"enable_discharge": false,
"enable_drm_rj45_port": true,
"f_ac1": 49.86,
"f_ac_high_c": 52,
"f_ac_high_in": 52,
"f_ac_high_in_time": 28,
"f_ac_high_out": 51.98,
"f_ac_high_out_time": 28,
"f_ac_low_c": 47,
"f_ac_low_in": 47.45,
"f_ac_low_in_time": 948,
"f_ac_low_out": 47,
"f_ac_low_out_time": 24,
"f_eps_backup": 49.85,
"fault_code": 0,
"firmware_version": "D0.450-A0.450",
"first_battery_bms_firmware_version": 3007,
"first_battery_serial_number": "BGXXXXXX",
"gfci_1_i": 0,
"gfci_1_time": 0,
"gfci_2_i": 0,
"gfci_2_time": 0,
"grid_power_adjust": 0,
"grid_r_voltage_adjust": 0,
"grid_s_voltage_adjust": 0,
"grid_t_voltage_adjust": 0,
"i_ac1": 0.17,
"i_battery": 0,
"i_grid_port": 2,
"i_pv1": 0.06,
"i_pv2": 0.07,
"inverter_countdown": 0,
"inverter_modbus_address": 17,
"inverter_model": "Hybrid",
"inverter_module": 198692,
"inverter_restart_delay_time": 30,
"inverter_serial_number": "SAXXXXXXXX",
"inverter_start_time": 30,
"inverter_state": [
0,
1
],
"inverter_status": 1,
"island_check_continue": 0,
"meter_type": 1,
"modbus_version": 1.4,
"num_mppt": 2,
"num_phases": 1,
"p_battery": 0,
"p_eps_backup": 215,
"p_grid_apparent": 487,
"p_grid_out": -181,
"p_grid_port_max_output": 6000,
"p_inverter_out": 292,
"p_load_demand": 473,
"p_pv1": 148,
"p_pv2": 162,
"pf_inverter_out": -0.3759,
"power_factor": -1,
"pv1_power_adjust": 0,
"pv1_voltage_adjust": 0,
"pv2_power_adjust": 0,
"pv2_voltage_adjust": 0,
"reactive_power_rate": 0,
"reverse_115_meter_direct": false,
"reverse_418_meter_direct": false,
"select_arm_chip": false,
"soc_force_adjust": 0,
"system_mode": 1,
"system_time": "2022-09-03 07:53:10",
"temp_battery": 21,
"temp_charger": 28.8,
"temp_inverter_heatsink": 28.9,
"usb_device_inserted": 2,
"v_ac1": 242.8,
"v_ac_high_c": 283.7,
"v_ac_high_in": 262,
"v_ac_high_in_time": 52,
"v_ac_high_out": 274,
"v_ac_high_out_time": 27,
"v_ac_low_c": 175.5,
"v_ac_low_in": 184,
"v_ac_low_in_time": 126,
"v_ac_low_out": 184,
"v_ac_low_out_time": 126,
"v_battery": 46.85,
"v_battery_over_protection_limit": 58.5,
"v_battery_under_protection_limit": 43.2,
"v_eps_backup": 242.4,
"v_highbrigh_bus": 135,
"v_n_bus": 0,
"v_p_bus": 377,
"v_pv1": 229.7,
"v_pv2": 217.2,
"v_pv_input_start": 150,
"work_time_total": 4439
}

Yeah I noticed on a runAll there was loads of new data in there. There will hopefully be smartplug data coming into the flows soon.
One of the wants from Giv is if you want anyone other than jo average to invest in them, the data from the plugs needs to be useable in HA for home brew automations.
I guess it will somehow be pulled from the Giv servers by the inverter and stuffed in the JSON somehow. Hopefully formatted by serial number, so they can be easily identified.
Dan said he would be in touch with you @Britkat to discuss the plug data in GivTCP

TheDragon (GivEnergy) I would hope the plugs would be usable outside of the givenergy world too otherwise they will be too niche to sell well. Imho!
I’m not too bothered about them at the moment as I can’t see what they bring to the party for a tinkerer like me- but for those who want to be able to more clever stuff without the added burden of other systems then they could make a smart home very simple.

anglefire problem is, us tinkeres are around 1% of their customer base.
Joe average wants everything in one eco system. So they will sell well for that reason I would bet on.

Agree for us, it's just another plug, but I'm hoping it will be easier to HomeAssistinlfy than Tuya. Which I can now do either with Tasmota of Tuya Integration that actually now works

TheDragon (GivEnergy) I agree to be fair.

I bought some growatt plugs thinking they would work in HA - but they don’t. They should be able to be flashed - but that has so far evaded me.

anglefire

Same here. I now have 3 double sockets. Knightsbridge ESP8266 based. But the wifi module has been patched. So cant exploit TuyaConvert.

So gave up and now have Tuya IoT working
So can monitor at the socket level.

Dearer than gosund plugs. 20 quid a socket.
But fit better behind the washer and dryer.

For the plugs to work with GivTCP, the invertor will need to take data into modbus registers and then use modbus registers for control. If I’m honest, I don’t see that happening. It wouldn’t really make sense… if there’s an cloud api, I can wrap that into GivTCP, if there’s any use in that from others.

Britkat The only other thing that may work is that the plugs have there own modbus ID and registers and the dongle is used as a gateway.

Given the plugs are stated to work with non GE customers (you can now setup your own accounts from the app if you sign out) it would be a bit odd for it to rely on the inverter to make it all work.
I'm guessing they get all the info from the cloud, which if the update rate stays at 5 mins is going to be a very stilted experience for solar matching I guess!

(Although we can't rule out they work in two routes if it finds an inverter on the network I guess)
I honestly think these are just Tuya but pointed to the GE API and not Tuya personally. Guess we'll see...

Britkat I've finally buckled and installed HA to control my immersion heater as i just can't be bothered with powershell and UDP.
Plus I can just call GivTCP as normal through HA even though it's an addon so no change required for anything else.

I have however noted some new entities in this latest version of GivTCP around import export costs. That's fine but i think the boundaries for costs are not set right. Can only be a value between 0 & 1 GBP but doesn't accept decimals?

hoggy I think these values are set in the Givtcp ENV, but I agree that you should be able to modify them through the HA interface.

Tim I set my rates via the ENV in the docker compose file.

Should be no reason they can’t be set in the ha config and should allow decimals, mine is set to a decimal number… I never change them as my values are the default ones :-) let me double check the config.ymal in case I set it as an int by mistake…

Britkat

I have the same. Try and write in a decimal it goes red.

Hi, anybody using the Smart Home Display feature? I've tried getting it working but it remains at 0...

Thanks

You mean the GivEnergy clone web page on GivTCP at port 3000?
Works ok 4 me. Just dont use it

chickengeorge have you set up the env correctly? You have to set the ip of the host for a start.