Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time Discrepancy in Growatt Graphs Despite Correct Timezone Settings #86

Closed
LightMoon opened this issue Aug 19, 2024 · 1 comment
Closed

Comments

@LightMoon
Copy link

Hi @egguy!

I've noticed that the graphs on the Growatt website are showing data that's one hour ahead of the actual current time. I wanted to check if this is expected behaviour.

Even after explicitly setting the timezone in the config file, the issue remains unchanged.

data_path: /config/grott
gmode: proxy
grott_mqtt: true
ginvtype: min
ginvtypemap: ""
retain: true
verbose: true
ha_plugin: false
mqtt: {}
gnoipf: true
gblockcmd: true
gpvoutput: true
gpvsystemid: 103487
gpvapikey: *********
gpvdisv1: false
gtime: server
gtimezone: Australia/Sydney
- Grott server date/time used
	 - Grott values retrieved:
		 -  datalogserial        :  XGD6CM31UN
		 -  pvserial             :  SPM2DBE044
		 -  voltage_l1           :  248.9
		 -  voltage_l2           :  0.0
		 -  voltage_l3           :  0.0
		 -  Current_l1           :  2.7
		 -  Current_l2           :  0.0
		 -  Current_l3           :  0.0
		 -  act_power_l1         :  420.4
		 -  act_power_l2         :  0.0
		 -  act_power_l3         :  0.0
		 -  app_power_l1         :  584.6
		 -  app_power_l2         :  0.0
		 -  app_power_l3         :  0.0
		 -  react_power_l1       :  -389.7
		 -  react_power_l2       :  0.0
		 -  react_power_l3       :  0.0
		 -  powerfactor_l1       :  0.7
		 -  powerfactor_l2       :  0.0
		 -  powerfactor_l3       :  0.0
		 -  pos_rev_act_power    :  420.4
		 -  pos_act_power        :  420.4
		 -  rev_act_power        :  420.4
		 -  app_power            :  584.6
		 -  react_power          :  -389.7
		 -  powerfactor          :  0.7
		 -  frequency            :  50.0
		 -  L1-2_voltage         :  0.0
		 -  L2-3_voltage         :  0.0
		 -  L3-1_voltage         :  0.0
		 -  pos_act_energy       :  2644.1
		 -  rev_act_energy       :  8582.5
	 - MQTT jsonmsg: 
			 {"device": "XGD6CM31UN", "time": "2024-08-19T17:34:35", "buffered": "no",
			 "values": {"datalogserial": "XGD6CM31UN", "pvserial": "SPM2DBE044",
			 "voltage_l1": 2489, "voltage_l2": 0, "voltage_l3": 0, "Current_l1": 27,
			 "Current_l2": 0, "Current_l3": 0, "act_power_l1": 4204, "act_power_l2": 0,
			 "act_power_l3": 0, "app_power_l1": 5846, "app_power_l2": 0, "app_power_l3":
			 0, "react_power_l1": -3897, "react_power_l2": 0, "react_power_l3": 0,
			 "powerfactor_l1": 737, "powerfactor_l2": 0, "powerfactor_l3": 0,
			 "pos_rev_act_power": 4204, "pos_act_power": 4204, "rev_act_power": 4204,
			 "app_power": 5846, "react_power": -3897, "powerfactor": 737, "frequency":
			 500, "L1-2_voltage": 0, "L2-3_voltage": 0, "L3-1_voltage": 0,
			 "pos_act_energy": 26441, "rev_act_energy": 85825}}
	 - Grott MQTT topic used : energy/growatt
	 - MQTT message message sent
	 - PVOut: Update refused for SPM2DBE044 due to time limitation
@LightMoon
Copy link
Author

The issue I was having was due to a misconfiguration with the time zone settings on the Growatt website. The problem was resolved once I set the correct time zone at Growatt website > Energy > Modify Information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant