bohdan-s / sungather Goto Github PK
View Code? Open in Web Editor NEWLicense: GNU General Public License v3.0
sungather's Introduction
sungather's People
Contributors
Stargazers
Watchers
Forkers
rark-ha benni336 manfredherrmann bg6cq lucahammer cottiac danielhin neiser eigenbaukombinat ech1965 michbeck100 bjeanes ranhiru alangibson dkies samkbel dervomsee norrland daedalist c-po eisbaeeer corneliusweiss fheck arfoll octofinger zup2 hughhalf moorgrove danpadure holiday-sunrise morph027 mk2lehe burnsy180 ddoy2277 gubbelgobbel gemx santje243 lindsted vetinari bigjools moddy anthony-spruyt apollo1987 daniel-maier jaredb7 sjlangley dixonte chrfritsch cartman10 markvdb augustinmarx knuedd n4zroth caliph9k jorghendriks xrobausungather's Issues
Random failure MQTT: Server Error; Server not configured
SunGather 0.3.7 was running happily for the past few days and then this morning I noticed Grafana was empty. On checking the Docker instance I found it had terminated and the last entries in the log were the following:
2022-05-12 06:32:21 INFO Inverter: Successfully scraped in 1.433464 secs
2022-05-12 06:32:21 WARNING MQTT: Server Error; Server not configured
MQTT: Server Error; Server not configured
Traceback (most recent call last):
File "/usr/src/sungather/sungather.py", line 566, in <module>
main()
File "/usr/src/sungather/sungather.py", line 534, in main
export.publish(inverter)
File "/usr/src/sungather/exports/mqtt.py", line 80, in publish
logging.debug(f"MQTT: Publishing: {self.mqtt_config['topic']} : {json.dumps(inverter.latest_scrape)}")
AttributeError: 'export_mqtt' object has no attribute 'mqtt_config'
There was no change to either the configuration or instance, so not sure how or why it suddenly lost the MQTT config. Started the instance again and it is working again.
2022-05-13 10:33:00 INFO Modbus client is not connected, attempting to reconnect
2022-05-13 10:33:00 INFO Connection: ModbusTcpClient(11.11.11.1:502)
2022-05-13 10:33:03 INFO Detected Model: SG8K-D
2022-05-13 10:33:03 INFO Closing Session: ModbusTcpClient(11.11.11.1:502)
2022-05-13 10:33:03 INFO Loading Export: exports\webserver
2022-05-13 10:33:03 INFO Webserver: Configured
2022-05-13 10:33:03 INFO Loading Export: exports\mqtt
2022-05-13 10:33:03 INFO Loading Export: exports\pvoutput
2022-05-13 10:33:03 INFO MQTT: Connected to mosquitto:1883
2022-05-13 10:33:04 INFO PVOutput: Configured export to 7 Eastlake Ave every 5 minutes
2022-05-13 10:33:04 INFO Modbus, Connecting new session
2022-05-13 10:33:06 INFO Inverter: Successfully scraped in 1.524352 secs
2022-05-13 10:33:06 INFO MQTT: Published
2022-05-13 10:33:06 INFO MQTT: Published Home Assistant Discovery messages
MQTT/HA - Zeroing sensors after inverter switches off
Is it possible to zero out the sensors once the inverter switches off overnight? It's causing the energy dashboard to think there is something to calculate.
The grid usage that was applicable just before the inverter switched off last night has been projected across overnight until the inverter kicked in again this morning (I also had the same with Solar Production, but with a minimal number)
SH6.0RT current/daily load (export_to/import_from grid)
Hi,
@bohdan-s thanks again for the fast reply on discord. As discussed, SunGather doesn't print out the current consumption/load. You mentioned in the chat that the hybrid model seem to use different registers which causes the missing data.
It seems 13008, 13010 and 5216, 5218 to be the data I'm searching for
Following the level 3 log with Smart Meter disabled.
I'm having a SH6.0RT connected to a BYD Battery and a external Smart Meter.
Please let me know if you need me to test or I can help in any way.
$ python3 sungather.py
2022-03-17 00:20:26 INFO Starting SunGather 0.3.7
2022-03-17 00:20:26 INFO Loaded config: config.yaml
2022-03-17 00:20:26 INFO Loaded registers: /src/github/SunGather/SunGather/registers.yaml
2022-03-17 00:20:26 INFO Registers file version: 0.2.0
+----------------------------------------------+
| Inverter Configuration Settings |
+----------------------------------------------+
| Config | Value |
+--------------------+-------------------------+
| host | 10.77.8.243 |
| port | 8082 |
| timeout | 10 |
| retries | 3 |
| RetryOnEmpty | False |
| slave | 1 |
| model | SH6.0RT |
| level | 3 |
| use_local_time | False |
| smart_meter | False |
| connection | http |
+----------------------------------------------+
2022-03-17 00:20:35 WARNING No data returned for read, 7012:25
No data returned for read, 7012:25
+----------------------------------------------------------------------+
| Address | Register | Value |
+---------+-------------------------------------+----------------------+
| 5000 | device_type_code | SH6.0RT |
| ---- | run_state | ON |
| 4950 | protocol_number | 12288 |
| 4952 | protocol_version | 4352 |
| 4954 | arm_software_version | 16722 |
| 4969 | dsp_software_version | 19780 |
| 4990 | serial_number | xxxxx |
| 5001 | nominal_active_power | 6.0 kW |
| 5002 | output_type | 3P4L |
| 5003 | daily_power_yields | 0.0 kWh |
| 5004 | total_power_yields | 0.0 kWh |
| 5006 | total_running_time | 0 h |
| 5008 | internal_temperature | 27.5 °C |
| 5009 | total_apparent_power | 0 VA |
| 5011 | mppt_1_voltage | 0.0 V |
| 5012 | mppt_1_current | 0.0 A |
| 5013 | mppt_2_voltage | 0.0 V |
| 5014 | mppt_2_current | 0.0 A |
| 5015 | mppt_3_voltage | 0.0 V |
| 5016 | mppt_3_current | 0.0 A |
| 5017 | total_dc_power | 0 W |
| 5019 | phase_a_voltage | 226.2 V |
| 5020 | phase_b_voltage | 226.2 V |
| 5021 | phase_c_voltage | 226.8 V |
| 5022 | phase_a_current | 0.0 A |
| 5023 | phase_b_current | 0.0 A |
| 5024 | phase_c_current | 0.0 A |
| 5031 | total_active_power | 0 W |
| 5033 | total_reactive_power | 0 Var |
| 5035 | power_factor | 0.0 |
| 5036 | grid_frequency | 49.97 Hz |
| 5038 | work_state_1 | 0 |
| 5049 | nominal_reactive_power | 3.0 kVar |
| 5071 | array_insulation_resistance | 695 k-ohm |
| 5077 | active_power_regulation_setpoint | 0 W |
| 5079 | reactive_power_regulation_setpoint | 0 Var |
| 5081 | work_state_2 | 0 |
| 5083 | meter_power | 0 W |
| 5085 | meter_a_phase_power | 0 W |
| 5087 | meter_b_phase_power | 0 W |
| 5089 | meter_c_phase_power | -65535 W |
| 5091 | load_power | 0 W |
| 5093 | daily_export_energy | 0.0 kWh |
| 5095 | total_export_energy | xxxx.x kWh |
| 5097 | daily_import_energy | 1.4 kWh |
| 5099 | total_import_energy | xxxx.x kWh |
| 5101 | daily_direct_energy_consumption | 0.0 kWh |
| 5103 | total_direct_energy_consumption | xxxx.1 kWh |
| 5113 | daily_running_time | 0 min |
| 5115 | mppt_4_voltage | 0.0 V |
| 5116 | mppt_4_current | 0.0 A |
| 5117 | mppt_5_voltage | 0.0 V |
| 5118 | mppt_5_current | 0.0 A |
| 5119 | mppt_6_voltage | 0.0 V |
| 5120 | mppt_6_current | 0.0 A |
| 5121 | mppt_7_voltage | 0.0 V |
| 5122 | mppt_7_current | 0.0 A |
| 5123 | mppt_8_voltage | 0.0 V |
| 5124 | mppt_8_current | 0.0 A |
| 5128 | monthly_power_yields | 0.0 kWh |
| 5130 | mppt_9_voltage | 0.0 V |
| 5131 | mppt_9_current | 0.0 A |
| 5132 | mppt_10_voltage | 0.0 V |
| 5133 | mppt_10_current | 0.0 A |
| 5134 | mppt_11_voltage | 0.0 V |
| 5135 | mppt_11_current | 0.0 A |
| 5136 | mppt_12_voltage | 0.0 V |
| 5137 | mppt_12_current | 0.0 A |
| 5146 | negative_voltage_to_the_ground | 0.0 V |
| 5147 | bus_voltage | 402.0 V |
| 5150 | pid_work_state | 0 |
| 5151 | pid_alarm_code | 0 |
| 5216 | export_power | -451 W |
| 5218 | power_meter | 452 W |
| 6100 | pv_power_of_today | 0 W |
| 6196 | daily_pv_energy_yields | 26.2 kWh |
| 6227 | monthly_pv_energy_yields | 1625 kWh |
| 6250 | yearly_pv_energy_yields | 0.0 kWh |
| 6290 | direct_power_consumption_today_pv | 0 W |
| 6386 | direct_power_consumption_pv | 5.6 kWh |
| 6417 | direct_power_consumption_monthly_pv | 106.3 kWh |
| 6429 | direct_power_consumption_yearly_pv | 0.0 kWh |
| 6469 | export_power_from_pv_today | 0 W |
| 6565 | export_power_from_pv | 10.7 kWh |
| 6596 | export_power_from_pv_monthly | 0.0 kWh |
| 6608 | export_power_from_pv_yearly | 0.0 kWh |
| 6648 | battery_charge_power_from_pv_today | 0.0 kWh |
| 6744 | battery_charge_power_from_pv | 9.9 kWh |
| 6775 | battery_charge_power_from_pv_monthly | 56.2 kWh |
| 6787 | battery_charge_power_from_pv_yearly | 0.0 kWh |
| 13000 | system_state | 8 |
| 13001 | running_state | 40 |
| 13002 | daily_pv_generation | 0.0 kWh |
| 13003 | total_pv_generation | xxxx.3 kWh |
| 13005 | daily_pv_export | 0.0 kWh |
| 13006 | total_pv_export | 1016.3 kWh |
| 13008 | load_power_hybrid | 41.5 W |
| 13010 | export_power_hybrid | -414 W |
| 13012 | daily_battery_charge_from_pv | 0.0 kWh |
| 13013 | total_battery_charge_from_pv | xxx.9 kWh |
| 13015 | co2_reduction | 1800.6 kg |
| 13020 | battery_voltage | 0.0 V |
| 13021 | battery_current | 0 A |
| 13022 | battery_power | 0 W |
| 13023 | battery_level | 0.0 % |
| 13024 | battery_state_of_healthy | 99.0 % |
| 13025 | battery_temperature | 20.0 °C |
| 13026 | daily_battery_discharge_energy | 0.0 kWh |
| 13027 | total_battery_discharge_energy | xxx.5 kWh |
| 13029 | self_consumption_of_day | 100.0 % |
| 13030 | grid_state | 0 |
| 13039 | battery_capacity | 26.1 kWh |
| 13040 | daily_charge_energy | 0.0 kWh |
| 13041 | total_charge_energy | xxx.3 kWh |
| 13043 | drm_state | 255 |
| 13050 | inverter_alarm | 0.0 |
| 13052 | grid-side_fault | 0.0 |
| 13054 | system_fault1 | 0.0 |
| 13056 | system_fault2 | 0.0 |
| 13058 | dc-side_fault | 0.0 |
| 13060 | permanent_fault | 0.0 |
| 13062 | bdc-side_fault | 0.0 |
| 13064 | bdc-side_permanent_fault | 0.0 |
| 13066 | battery_fault | 0.0 |
| 13068 | battery_alarm | 0.0 |
| 13070 | bms_alarm | 0 |
| 13072 | bms_protection | 0 |
| 13074 | bms_fault1 | 0 |
| 13076 | bms_fault2 | 0 |
| 13078 | bms_alarm2 | 0 |
| 13100 | bms_status | 0 |
| 13101 | max_charging_current | 0 A |
| 13102 | max_discharging_current | 0 A |
| 13103 | warning | 0 |
| 13104 | protection | 0 |
| 13105 | fault1 | 0 |
| 13106 | fault2 | 0 |
| 13107 | soc | 0 % |
| 13108 | soh | 0 |
| 13111 | cycle_count | 0.0 |
| 13112 | average_cell_voltage | 0 V |
| 13113 | max_cell_voltage | 0 V |
| 13114 | min_cell_voltage | 0 V |
| 13115 | battery_pack_voltage | 0 V |
| 13116 | average_cell_temp | 0 °C |
| 13117 | max_cell_temp | 0 °C |
| 13118 | min_cell_temp | 0 °C |
| 5006 | start_stop | Start |
| 5007 | power_limitation_switch | Enable |
| 5008 | power_limitation_setting | 100.0 % |
| 5010 | export_power_limitation | 0 |
| 5011 | export_power_limitation_value | 0 |
| 5012 | current_transformer_output_current | 0 A |
| 5013 | current_transformer_range | 0 A |
| 5014 | current_transformer | 0 |
| 5015 | export_power_limitation_percentage | 0.0 % |
| 5016 | installed_pv_power | 0.0 KW |
| 5019 | power_factor_setting | 0.0 |
| 5035 | night_svg_switch | 0 |
| 5036 | reactive_power_adjustment_mode | Enable Q(U) |
| 5037 | reactive_power_percentage_setting | 0.0 % |
| 5039 | power_limitation_adjustment | 0.0 kW |
| 5040 | reactive_power_adjustment | 0.0 kVar |
| 5041 | pid_recovery | 0 |
| 5042 | anti_pid | 0 |
| 5043 | fullday_pid_suppression | 0 |
| ---- | export_to_grid | 0 W |
| ---- | import_from_grid | 0 W |
| ---- | timestamp | 2022-3-17 1:20:33 |
+----------------------------------------------------------------------+
Home Assistant Addon (HACS)
Dev issue for the new HA Addon for Sungather.
Current state is working SunGather under Terminal SSH Docker Session. Working Addon install interface. To Do: Complete Dockerfile to install prerequistes for python.
[Proposal] Adding Units to Registers
In Reference to #1 I would like to continue that work and jump in.
I have a PDF showing all available registers and I would start to add missing ones to registers.yaml
But additionally I also figured out that it is hard to guess what kind of data is behind each value without knowing units.
Units might be usefull to hand them down the road (influx db tag or mqtt?) and it might make more sense to add a "unit" field instead of renaming the register by adding something like [kwh] (registername -> registername [kWh]
What do you all think about adding units?
Influx DB api token
Using the InfluxDB addon in HA, I cant find any simple way of creating the influxDB api token. Is there any way of connecting using username and password as with Solariot?
PVOutput sumbissions stop at midnight
Hello,
Thank you! Things are going well with my Home Assistant integration and I am loving this script!
I have seen some odd behaviour the past couple of days after updating my script where the PVOut sumbissions start failing after midnight and I get nothing for the next day. My logs look a little like:
Jan 25 00:00:16 [] python3[9182]: 2022-01-25 00:00:16 WARNING No data returned for read, 5000:100
Jan 25 00:00:16 [] python3[9182]: #11#011#011#011Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED
Jan 25 00:00:16 [] python3[9182]: 2022-01-25 00:00:16 WARNING No data returned for read, 5100:100
Jan 25 00:00:16 [] python3[9182]: #11#011#011#011Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED
Jan 25 00:00:16 [] python3[9182]: 2022-01-25 00:00:16 WARNING No data returned for hold, 4999:10
Jan 25 00:00:16 [] python3[9182]: #11#011#011#011Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED
Jan 25 00:00:16 [] python3[9182]: 2022-01-25 00:00:16 WARNING Data collection failed, skipped exporting data. Retying in 30 secs
Jan 25 00:02:49 [] python3[9182]: 2022-01-25 00:02:49 ERROR PVOutput: Upload Failed; 400 Message; b'Bad request 400: Moon Powered'
Jan 25 00:03:18 [] python3[9182]: 2022-01-25 00:03:18 ERROR PVOutput: Upload Failed; 400 Message; b'Bad request 400: Moon Powered'
.....
Jan 25 00:17:19 [] python3[9182]: 2022-01-25 00:17:19 ERROR PVOutput: Upload Failed; 400 Message; b'Bad request 400: Moon Powered'
...
Jan 25 00:32:20 [] python3[9182]: 2022-01-25 00:32:20 ERROR PVOutput: Upload Failed; 400 Message; b'Bad request 400: Batch size greater than 30 records [60]'
...
Jan 25 00:48:21 [] python3[9182]: 2022-01-25 00:48:21 ERROR PVOutput: Upload Failed; 403 Message; b'Forbidden 403: Exceeded 60 requests per hour'
Jan 25 00:48:51 [] python3[9182]: 2022-01-25 00:48:51 ERROR PVOutput: Upload Failed; 413 Message; b''
...
Jan 25 02:02:55 [] python3[9182]: 2022-01-25 02:02:55 ERROR PVOutput: Upload Failed; 413 Message; b''
Jan 25 02:03:25 [] python3[9182]: 2022-01-25 02:03:25 ERROR PVOutput: Upload Failed; 400 Message; b'<html><body><h1>400 Bad request</h1>\nYour browser sent an invalid request.\n</body></html>\n\n'
...
Jan 25 04:37:02 [] python3[9182]: 2022-01-25 04:37:02 ERROR PVOutput: Upload Failed; 400 Message; b'<html><body><h1>400 Bad request</h1>\nYour browser sent an invalid request.\n</body></html>\n\n'
Jan 25 04:37:32 [] python3[9182]: 2022-01-25 04:37:32 ERROR PVOutput: Failed to Upload
Jan 25 04:38:02 [] python3[9182]: 2022-01-25 04:38:02 ERROR PVOutput: Upload Failed; 400 Message; b'<html><body><h1>400 Bad request</h1>\nYour browser sent an invalid request.\n</body></html>\n
As part of my update I also moved to a new config.yaml and tried uncommenting the voltage register for PVOutput but assume thats not an issue here. After commenting the voltage registers again and restarting it all seems to be fine. I then uncommented the voltage, which seemed to work again but hit the same midnight issue last night. Any ideas?
Mapping for running_state
I started using SunGather and I'm thinking to move from modbus4mqtt. Unfortunately it seems that SunGather doesn't support a mapping for running_state.
According to the sungrow documentation this is the mapping:
So running_state actually contains 8 values.
How can I achieve such a mapping?
Support writing holding registers
I would like to be able to write registers, too.
My idea would be to listen to special mqtt topics and/or HTTP PUT on the webserver.
Support for SG5K-D
Hey mate,
I'm trying to run SunGather against a SG5K-D with a WiFi V31 dongle.
Modbus seems to not work:
2021-12-17 13:47:22 INFO Starting SunGather 0.1.0
2021-12-17 13:47:22 INFO Loaded config: config.yaml
2021-12-17 13:47:23 INFO Loaded registers: registers.yaml
2021-12-17 13:47:23 INFO Loaded Export: exports\console
2021-12-17 13:47:23 INFO Configured Console Logging
2021-12-17 13:47:23 INFO Configured export: console
2021-12-17 13:47:23 INFO Loaded Export: exports\mqtt
2021-12-17 13:47:23 INFO Configured MQTT Client
2021-12-17 13:47:23 INFO Configured export: mqtt
2021-12-17 13:47:23 INFO Connection: ModbusTcpClient(192.168.0.6:502)
2021-12-17 13:47:23 DEBUG Connection to Modbus server established. Socket ('10.0.1.249', 47621)
2021-12-17 13:47:23 DEBUG load_registers: read, 4999:1
2021-12-17 13:47:23 DEBUG Connection to Modbus server established. Socket ('10.0.1.249', 51883)
2021-12-17 13:47:23 DEBUG Current transaction state - IDLE
2021-12-17 13:47:23 DEBUG Running transaction 1
2021-12-17 13:47:23 DEBUG SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x87 0x0 0x1
2021-12-17 13:47:23 DEBUG New Transaction state 'SENDING'
2021-12-17 13:47:23 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2021-12-17 13:47:23 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2021-12-17 13:47:23 DEBUG RECV: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x84 0x4
2021-12-17 13:47:23 DEBUG Processing: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x84 0x4
2021-12-17 13:47:23 DEBUG Frame check failed, ignoring!!
2021-12-17 13:47:23 DEBUG Getting transaction 1
2021-12-17 13:47:23 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2021-12-17 13:47:23 WARNING Modbus connection failed
But it might be its failing out because I can't see the SG5K-D being supported?
Question: What is 'Inverter Power State' / run_state?
Mine is OFF most of the time.
Btw, great job, looking forward to Home Assistant support via HACS. :)
Typo in README.md
Small typo in the README ... Sungow instead of Sungrow.
... any network connected Sungow Inverter
new install module not found
I can't understand if the problem is with SunGather (I think not) or with SungrowModbusTcpClient or pymodbus
In pymodbus/client there is no sync.py file. Only sync_diag.py
Traceback (most recent call last):
File "/home/dan/SunGather/SunGather/sungather.py", line 3, in
from SungrowModbusTcpClient import SungrowModbusTcpClient
File "/usr/local/lib/python3.9/dist-packages/SungrowModbusTcpClient/SungrowModbusTcpClient.py", line 1, in
from pymodbus.client.sync import ModbusTcpClient
ModuleNotFoundError: No module named 'pymodbus.client.sync'
Please make sure mqtt.py exists in the exports folder
Hi
Still getting this error
2022-03-13 12:51:45 ERROR Failed loading export: 'NoneType' object has no attribute 'replace'
Please make sure mqtt.py exists in the exports folder
Failed loading export: 'NoneType' object has no attribute 'replace'
Please make sure mqtt.py exists in the exports folder
Checked MQTT settings ok Checked the folder exports and mqtt.py exists ?
index out of range
Hi I'm having an issue to read values from an SG40CX. I don't know if I should paste here but just be sure, this is my output on pastebin : https://pastebin.com/SqD1Ep3p
It seems to be reading some values but the output is always 0 or nothing at all. Included here the output of the webserver: https://pastebin.com/n8LkGWP2
Greetings and I hope we can work this out together!
Cron execution
If I would set up Cron execution and run sungather as one shot would it still handle the PV output rate limit even though I basically stop and rerun the script?
Huge thanks, awesome work!
New SH- Modbus Documentation
Maybe even a newer version is already out there. I personally think the layout got worse
Communication.Protocol.of.Residential.Hybrid.InverterV1.0.22_20201117.pdf
|
SG10RT
Hi everyone,
thank you very much for this great tool.
As you know I am using it for SH-Inverters and it works great.
But know I need to work with an SG-Inverter (SG10RT). The WiNetS WebInterfaces is accessable via ethernet. But I do not really get, how it works now and what I have to adapt?
I thought I need to use http instead of sungrow? Can anyone give me a push into the right direct?
pypi Release
Hi,
it would be great to have releases ready for installation on pypi. I'm in to help you there.
Home Assistant sensor setup and Energy platform
Following on from the comment in the closed item #2 (comment)
@bohdan-s the updates you've made in the past 48 hrs have fixed my initial issue as HA now generates 6 sensors. For others that would like a walk-through doc please read below.
In the SunGather config.yaml you need to set the smart_meter if you have one;
smart_meter: True
HA sensors created by the MQTT auto-discovery;
sensor.inverter_active_power
sensor.inverter_daily_generation
sensor.inverter_export_to_grid
sensor.inverter_import_from_grid
sensor.inverter_load_power
sensor.inverter_meter_power
Used the README settings for HA sensors and put the following into your sensors.yaml
sensor:
- platform: integration
source: sensor.inverter_active_power
- platform: integration
source: sensor.inverter_export_to_grid
- platform: integration
source: sensor.inverter_import_from_grid
The additional sensors then setup in HA are the following with Wh unit of measurement for the Energy platform.
sensor.sensor_inverter_active_power_integral
sensor.sensor_inverter_export_to_grid_integral
sensor.sensor_inverter_import_from_grid_integral
You need to utilise the customize.yaml manual method to get some friendly names and icons. Add the following;
sensor.sensor_inverter_active_power_integral:
icon: mdi:solar-power
friendly_name: Solar Generation
sensor.sensor_inverter_export_to_grid_integral:
icon: mdi:transmission-tower-export
friendly_name: Grid Export
sensor.sensor_inverter_import_from_grid_integral:
icon: mdi:transmission-tower-import
friendly_name: Grid Import
Navigate to the Energy platform (Configuration > Energy). Add these sensors to the following areas:
Electricity Grid > Grid Import - sensor.sensor_inverter_import_from_grid_integral
Electricity Grid > Grid Export - sensor.sensor_inverter_export_to_grid_integral
Solar Panels > Solar Production - sensor.sensor_inverter_active_power_integral
Not detecting correct inverter parameters?
Apologies if this is something a bit silly, I haven't had much of a look into it myself. I have a SG5.0RT with the WiNet-S dongle. On a run I get:
python3 sungather.py
2021-12-24 10:56:12 ERROR Failed loading export: timed out
Please make sure mqtt.py exists in the exports folder
2021-12-24 10:56:22 ERROR index out of range
2021-12-24 10:56:22 ERROR Modbus Error: [Input/Output] Unable to decode request
Traceback (most recent call last):
File "/home/..../.local/lib/python3.7/site-packages/pymodbus/transaction.py", line 210, in execute
request.unit_id)
File "/home/..../.local/lib/python3.7/site-packages/pymodbus/framer/socket_framer.py", line 153, in processIncomingPacket
self._process(callback)
File "/home/..../.local/lib/python3.7/site-packages/pymodbus/framer/socket_framer.py", line 175, in _process
raise ModbusIOException("Unable to decode request")
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] Unable to decode request
2021-12-24 10:56:22 WARNING Modbus connection failed: Modbus Error: [Input/Output] Unable to decode request
2021-12-24 10:56:22 ERROR index out of range
2021-12-24 10:56:22 ERROR Modbus Error: [Input/Output] Unable to decode request
I have tried setting:
connection: http
model: "SG5.0RT"
and it seems to work:
python3 sungather.py
Publish HTTP
Publish HTTP
Inverter Power State incorrectly OFF
After checking the terminal entries and then logging into the web page, I was logged out of the web page (presumably SunGather was doing it's next scrape).
The reading for run_state started showing OFF when it was in fact ON (confirmed via the web page). I restarted the container to get it to show ON again. Capture of the bug below.
Please make sure mqtt.py exists in the exports folder
Upon loading I get the error message "Please make sure mqtt.py exists in the exports folder"
I can confirm it exists. I've set up the config file with the correct IP for the MQTT server, unhashed the port (but use the default 1883 anyway), and added a username/password using " " to capture them.
HA_discovery
First of all, Awesome work! Also, huge thanks for the webclient. I had kind of given up hope of reading out my data for me the webclient works great. (SG10RT)
But I have some issues and I'll file them one by one so there will be 2 more.
I cant seem to get HA_discovery to work. I get a line in the MQTT log but that's the only thing that happens.
1642493332: New connection from 192.168.10.87 on port 1883. {"result": "ok", "data": {}}1642493332: New client connected from 192.168.10.87 as SunGather (p2, c1, k60, u'sungather').
It's entirely possible that this is an issue on my side.
InfluxDB: 'NoneType' object has no attribute 'write'
Is there a known hotfix to this problem?
default scan intervall changed
According to code:
"scan_interval": configfile['inverter'].get('scan_interval',15),
default scan interval has changed to 15 instead of 30 seconds.
Trouble to connect Mosquitto MQTT
Hi,
just got my SH10RT and try to implemt it to the home assistant.
Got SunGather running on eth port and getting out 39 registers. As soon i try to connect to the local Mosquitto MQTT Server SunGather quit with following faults:
Traceback (most recent call last): File "./sungather.py", line 190, in <module> main() File "./sungather.py", line 158, in main export.publish(inverter) File "/root/SunGather/SunGather/exports/mqtt.py", line 123, in publish payload = json.dumps(inverter.inverter_config | inverter.client_config | inverter.latest_scrape).replace('"', '\"') TypeError: unsupported operand type(s) for |: 'dict' and 'dict'
im running rasperryPi with python version 3.7.3
anybody lnow this issue or can support me?
Thanks in andvance!
Register Numbers in Webview
thanks for your work :)
would it be easy to show the register number alongside the name in the web view? it would make debugging a lot faster for me
Originally posted by @chainsawbike in #1 (comment)
System not recognizing SG3K-D
System not recognizing SG3K-D
admin@RT-AC68U-A2D8:/tmp/mnt/KINGSTON/entware/home/SunGather-main/SunGather# ./sungather.py -v 10 --runonce > log.txt 2022-09-12 13:19:29 INFO Starting SunGather 0.3.8 2022-09-12 13:19:30 INFO Loaded config: config.yaml 2022-09-12 13:19:37 INFO Loaded registers: /tmp/mnt/KINGSTON/entware/home/SunGather-main/SunGather/registers-sungrow.yaml 2022-09-12 13:19:37 INFO Registers file version: 0.2.0 2022-09-12 13:19:37 INFO Logging to console set to: DEBUG 2022-09-12 13:19:37 DEBUG Inverter Config Loaded: {'host': '192.168.1.208', 'port': 502, 'timeout': 10, 'retries': 3, 'slave': 1, 'scan_interval': 30, 'connection': 'sungrow', 'model': None, 'smart_meter': False, 'use_local_time': False, 'log_console': 'WARNING', 'log_file': 'OFF', 'level': 3} 2022-09-12 13:19:37 DEBUG Checking Modbus Connection 2022-09-12 13:19:37 INFO Modbus client is not connected, attempting to reconnect 2022-09-12 13:19:37 INFO Connection: ModbusTcpClient(192.168.1.208:502) 2022-09-12 13:19:37 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 44772) 2022-09-12 13:19:37 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 57834) 2022-09-12 13:19:40 DEBUG load_registers: read, 4999:1 2022-09-12 13:19:40 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 47555) 2022-09-12 13:19:40 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 50533) 2022-09-12 13:19:40 DEBUG Current transaction state - IDLE 2022-09-12 13:19:40 DEBUG Running transaction 1 2022-09-12 13:19:40 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 35795) 2022-09-12 13:19:40 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 53786) 2022-09-12 13:19:40 DEBUG SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x87 0x0 0x1 2022-09-12 13:19:40 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:40 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:40 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:40 DEBUG RECV: 0x0 0x1 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x1 0x22 2022-09-12 13:19:40 DEBUG Processing: 0x0 0x1 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0x1 0x22 2022-09-12 13:19:40 DEBUG Factory Response[ReadInputRegistersResponse: 4] 2022-09-12 13:19:40 DEBUG Adding transaction 1 2022-09-12 13:19:40 DEBUG Getting transaction 1 2022-09-12 13:19:40 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:40 WARNING Unknown Type Code Detected: 290 Unknown Type Code Detected: 290 2022-09-12 13:19:40 INFO Closing Session: ModbusTcpClient(192.168.1.208:502) 2022-09-12 13:19:40 INFO Loading Export: exports\webserver 2022-09-12 13:19:40 INFO Webserver: Configured 2022-09-12 13:19:40 INFO Loading Export: exports\pvoutput 2022-09-12 13:19:40 DEBUG PVOutput: Get System ; https://pvoutput.org/service/r2/getsystem.jsp, {'X-Pvoutput-Apikey': 'xxxxxxxxxx', 'X-Pvoutput-SystemId': '93119', 'Content-Type': 'application/x-www-form-urlencoded', 'cache-control': 'no-cache'}, 'teams': '1' 2022-09-12 13:19:40 DEBUG Starting new HTTPS connection (1): pvoutput.org:443 2022-09-12 13:19:41 DEBUG https://pvoutput.org:443 "POST /service/r2/getsystem.jsp?teams=1 HTTP/1.1" 200 None 2022-09-12 13:19:41 DEBUG PVOutput: Response; 200 Message; b'CasaFunfzehn,3630,,11,330,JA Solar,1,3000,Sungrow,N,13.0,No,20201209,-12.949314,-38.3846,5;;1618;0' 2022-09-12 13:19:41 INFO PVOutput: Configured export to CasaFunfzehn every 5 minutes 2022-09-12 13:19:41 DEBUG Checking Modbus Connection 2022-09-12 13:19:41 INFO Modbus, Connecting new session 2022-09-12 13:19:41 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 36283) 2022-09-12 13:19:41 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 46697) 2022-09-12 13:19:41 DEBUG Scraping: read, 4949:50 2022-09-12 13:19:41 DEBUG load_registers: read, 4949:50 2022-09-12 13:19:41 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 57582) 2022-09-12 13:19:41 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 59253) 2022-09-12 13:19:41 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:41 DEBUG Running transaction 2 2022-09-12 13:19:41 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 38093) 2022-09-12 13:19:41 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 41436) 2022-09-12 13:19:41 DEBUG SEND: 0x0 0x2 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x55 0x0 0x32 2022-09-12 13:19:41 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:41 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:41 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:41 DEBUG RECV: 0x0 0x2 0x0 0x0 0x0 0x67 0x1 0x4 0x64 0x30 0x0 0x41 0x52 0xf 0x0 0x1 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x41 0x31 0x39 0x30 0x38 0x30 0x35 0x32 0x37 0x35 0x35 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 2022-09-12 13:19:41 DEBUG Processing: 0x0 0x2 0x0 0x0 0x0 0x67 0x1 0x4 0x64 0x30 0x0 0x41 0x52 0xf 0x0 0x1 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x41 0x31 0x39 0x30 0x38 0x30 0x35 0x32 0x37 0x35 0x35 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 2022-09-12 13:19:41 DEBUG Factory Response[ReadInputRegistersResponse: 4] 2022-09-12 13:19:41 DEBUG Adding transaction 2 2022-09-12 13:19:41 DEBUG Getting transaction 2 2022-09-12 13:19:41 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:42 DEBUG Scraping: read, 5000:100 2022-09-12 13:19:42 DEBUG load_registers: read, 5000:100 2022-09-12 13:19:42 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 37117) 2022-09-12 13:19:42 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 55642) 2022-09-12 13:19:42 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:42 DEBUG Running transaction 3 2022-09-12 13:19:42 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 39053) 2022-09-12 13:19:42 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 39577) 2022-09-12 13:19:42 DEBUG SEND: 0x0 0x3 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x88 0x0 0x64 2022-09-12 13:19:42 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:42 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:42 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:42 DEBUG RECV: 0x0 0x3 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0x0 0x1e 0x0 0x0 0x0 0x26 0x29 0x3e 0x0 0x0 0x1e 0x4b 0x0 0x0 0x1 0xa8 0xff 0xff 0xff 0xff 0xf 0x57 0x0 0xf 0x0 0x0 0x0 0x0 0xff 0xff 0xff 0xff 0x2 0x5e 0x0 0x0 0x8 0x8e 0xff 0xff 0xff 0xff 0x0 0x1c 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x2 0x5e 0x0 0x0 0xff 0xff 0x7f 0xff 0x3 0xdf 0x2 0x58 0xff 0xff 0x81 0x0 0x7 0xd0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xff 0xff 0xff 0xff 0x0 0x64 0x0 0x9 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x0 0x1 0x0 0x0 0x7f 0xff 0x0 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 2022-09-12 13:19:42 DEBUG Processing: 0x0 0x3 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0x0 0x1e 0x0 0x0 0x0 0x26 0x29 0x3e 0x0 0x0 0x1e 0x4b 0x0 0x0 0x1 0xa8 0xff 0xff 0xff 0xff 0xf 0x57 0x0 0xf 0x0 0x0 0x0 0x0 0xff 0xff 0xff 0xff 0x2 0x5e 0x0 0x0 0x8 0x8e 0xff 0xff 0xff 0xff 0x0 0x1c 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x2 0x5e 0x0 0x0 0xff 0xff 0x7f 0xff 0x3 0xdf 0x2 0x58 0xff 0xff 0x81 0x0 0x7 0xd0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xff 0xff 0xff 0xff 0x0 0x64 0x0 0x9 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0x7f 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x0 0x1 0x0 0x0 0x7f 0xff 0x0 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 2022-09-12 13:19:42 DEBUG Factory Response[ReadInputRegistersResponse: 4] 2022-09-12 13:19:42 DEBUG Adding transaction 3 2022-09-12 13:19:42 DEBUG Getting transaction 3 2022-09-12 13:19:42 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:42 DEBUG Scraping: read, 5100:100 2022-09-12 13:19:42 DEBUG load_registers: read, 5100:100 2022-09-12 13:19:42 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 41537) 2022-09-12 13:19:42 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 52029) 2022-09-12 13:19:42 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:42 DEBUG Running transaction 4 2022-09-12 13:19:42 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 52835) 2022-09-12 13:19:42 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 38288) 2022-09-12 13:19:42 DEBUG SEND: 0x0 0x4 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0xec 0x0 0x64 2022-09-12 13:19:42 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:42 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:43 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:43 DEBUG RECV: 0x0 0x4 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0xe 0x0 0x42 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x0 0x5 0x9c 0x71 0x0 0x1 0xff 0xff 0xff 0xff 0x17 0x73 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 2022-09-12 13:19:43 DEBUG Processing: 0x0 0x4 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0xe 0x0 0x42 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x0 0x5 0x9c 0x71 0x0 0x1 0xff 0xff 0xff 0xff 0x17 0x73 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 2022-09-12 13:19:43 DEBUG Factory Response[ReadInputRegistersResponse: 4] 2022-09-12 13:19:43 DEBUG Adding transaction 4 2022-09-12 13:19:43 DEBUG Getting transaction 4 2022-09-12 13:19:43 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:43 DEBUG Scraping: read, 5200:100 2022-09-12 13:19:43 DEBUG load_registers: read, 5200:100 2022-09-12 13:19:43 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 34226) 2022-09-12 13:19:43 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 60302) 2022-09-12 13:19:43 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:43 DEBUG Running transaction 5 2022-09-12 13:19:43 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 39985) 2022-09-12 13:19:43 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 47253) 2022-09-12 13:19:43 DEBUG SEND: 0x0 0x5 0x0 0x0 0x0 0x6 0x1 0x4 0x14 0x50 0x0 0x64 2022-09-12 13:19:43 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:43 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:43 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:43 DEBUG RECV: 0x0 0x5 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xab 0x15 0x4f 0xdf 0xdf 0xcd 0xfc 0x3b 0xbb 0x4a 0x5c 0x30 0x87 0xbf 0x3f 0xff 0xda 0x4b 0x98 0xe7 0xd 0x5c 0xb2 0x2f 0x37 0x68 0xe9 0xdf 0x5f 0xf2 0xeb 0x7 0xbe 0xc3 0xac 0xc6 0xe7 0xde 0xf7 0x12 0xf8 0xbc 0xf8 0x80 0xf1 0xa6 0x74 0xb2 0x77 0x22 0x73 0x74 0xe3 0x26 0x9 0x26 0xf8 0xf3 0x48 0x80 0xc 0xa1 0xac 0x20 0x40 0xb3 0x22 0x80 0xe4 0x4e 0x2e 0x5 0x76 0x20 0x0 0xd9 0xda 0x37 0x4c 0xd5 0xd2 0x85 0xa6 0xd8 0xa2 0x1c 0x88 0x1d 0x8d 0x3a 0xcd 0x42 0x34 0xd 0xba 0x19 0x0 0x5b 0x20 0x1 0x0 0x0 0x1 0x0 0x1 0x0 0x1 0x2c 0x41 0x31 0x39 0x30 0x38 0x30 0x35 0x32 0x37 0x35 0x35 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x22 0x53 0x47 0x33 0x4b 0x2d 0x44 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x56 0x33 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 2022-09-12 13:19:43 DEBUG Processing: 0x0 0x5 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xab 0x15 0x4f 0xdf 0xdf 0xcd 0xfc 0x3b 0xbb 0x4a 0x5c 0x30 0x87 0xbf 0x3f 0xff 0xda 0x4b 0x98 0xe7 0xd 0x5c 0xb2 0x2f 0x37 0x68 0xe9 0xdf 0x5f 0xf2 0xeb 0x7 0xbe 0xc3 0xac 0xc6 0xe7 0xde 0xf7 0x12 0xf8 0xbc 0xf8 0x80 0xf1 0xa6 0x74 0xb2 0x77 0x22 0x73 0x74 0xe3 0x26 0x9 0x26 0xf8 0xf3 0x48 0x80 0xc 0xa1 0xac 0x20 0x40 0xb3 0x22 0x80 0xe4 0x4e 0x2e 0x5 0x76 0x20 0x0 0xd9 0xda 0x37 0x4c 0xd5 0xd2 0x85 0xa6 0xd8 0xa2 0x1c 0x88 0x1d 0x8d 0x3a 0xcd 0x42 0x34 0xd 0xba 0x19 0x0 0x5b 0x20 0x1 0x0 0x0 0x1 0x0 0x1 0x0 0x1 0x2c 0x41 0x31 0x39 0x30 0x38 0x30 0x35 0x32 0x37 0x35 0x35 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x22 0x53 0x47 0x33 0x4b 0x2d 0x44 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x56 0x33 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 2022-09-12 13:19:43 DEBUG Factory Response[ReadInputRegistersResponse: 4] 2022-09-12 13:19:43 DEBUG Adding transaction 5 2022-09-12 13:19:43 DEBUG Getting transaction 5 2022-09-12 13:19:43 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:43 DEBUG Scraping: read, 5600:100 2022-09-12 13:19:43 DEBUG load_registers: read, 5600:100 2022-09-12 13:19:43 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 46067) 2022-09-12 13:19:43 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 57933) 2022-09-12 13:19:43 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:43 DEBUG Running transaction 6 2022-09-12 13:19:43 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 38795) 2022-09-12 13:19:43 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 45886) 2022-09-12 13:19:43 DEBUG SEND: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x4 0x15 0xe0 0x0 0x64 2022-09-12 13:19:43 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:43 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:44 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:44 DEBUG RECV: 0x0 0x6 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:44 DEBUG Processing: 0x0 0x6 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:44 DEBUG Factory Response[132] 2022-09-12 13:19:44 DEBUG Adding transaction 6 2022-09-12 13:19:44 DEBUG Getting transaction 6 2022-09-12 13:19:44 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:44 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:44 DEBUG Exception Response(132, 4, IllegalAddress) 2022-09-12 13:19:44 DEBUG Scraping: read, 6099:100 2022-09-12 13:19:44 DEBUG load_registers: read, 6099:100 2022-09-12 13:19:44 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 46810) 2022-09-12 13:19:44 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 46614) 2022-09-12 13:19:44 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:44 DEBUG Running transaction 7 2022-09-12 13:19:44 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 54368) 2022-09-12 13:19:44 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 58718) 2022-09-12 13:19:44 DEBUG SEND: 0x0 0x7 0x0 0x0 0x0 0x6 0x1 0x4 0x17 0xd3 0x0 0x64 2022-09-12 13:19:44 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:44 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:44 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:44 DEBUG RECV: 0x0 0x7 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x43 0x0 0x9f 0x1 0x9 0x1 0x7a 0x2 0x9d 0x2 0x30 0x2 0xd8 0x7 0x74 0x2 0x1b 0x2 0xfb 0x3 0xb6 0x6 0xb6 0x4 0x26 0x4 0x25 0x2 0x7f 0x3 0xd3 0x7 0xfa 0x3 0xaa 0x2 0x6f 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x50 0x0 0x9b 0x0 0x9d 0x0 0xcb 2022-09-12 13:19:44 DEBUG Processing: 0x0 0x7 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x43 0x0 0x9f 0x1 0x9 0x1 0x7a 0x2 0x9d 0x2 0x30 0x2 0xd8 0x7 0x74 0x2 0x1b 0x2 0xfb 0x3 0xb6 0x6 0xb6 0x4 0x26 0x4 0x25 0x2 0x7f 0x3 0xd3 0x7 0xfa 0x3 0xaa 0x2 0x6f 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x50 0x0 0x9b 0x0 0x9d 0x0 0xcb 2022-09-12 13:19:44 DEBUG Factory Response[ReadInputRegistersResponse: 4] 2022-09-12 13:19:44 DEBUG Adding transaction 7 2022-09-12 13:19:44 DEBUG Getting transaction 7 2022-09-12 13:19:44 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:44 DEBUG Scraping: read, 6199:100 2022-09-12 13:19:44 DEBUG load_registers: read, 6199:100 2022-09-12 13:19:44 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 58454) 2022-09-12 13:19:44 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 51828) 2022-09-12 13:19:44 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:44 DEBUG Running transaction 8 2022-09-12 13:19:44 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 45654) 2022-09-12 13:19:44 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 39841) 2022-09-12 13:19:44 DEBUG SEND: 0x0 0x8 0x0 0x0 0x0 0x6 0x1 0x4 0x18 0x37 0x0 0x64 2022-09-12 13:19:44 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:44 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:45 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:45 DEBUG RECV: 0x0 0x8 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0x0 0xce 0x0 0xac 0x0 0x9d 0x0 0x8c 0x0 0xbd 0x0 0xbf 0x0 0xbf 0x0 0x26 0x0 0x74 0x0 0x4b 0x0 0xad 0x0 0x9c 0x0 0xd3 0x0 0xc1 0x0 0xbd 0x0 0x91 0x0 0x89 0x0 0x96 0x0 0xbc 0x0 0xba 0x0 0xbc 0x0 0xca 0x0 0xd0 0x0 0x86 0x0 0xce 0x0 0x52 0x0 0x71 0x0 0x0 0x0 0x0 0x2 0x20 0x1 0xed 0x1 0xb8 0x1 0xa3 0x1 0xde 0x2 0x2 0x0 0xbb 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x10 0x54 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1e 0x5c 0x8 0x6 0x47 0xd9 0xcc 0x54 0xcb 0xc4 0xe0 0xc1 0xde 0x6b 0x23 0xb7 0x3e 0xa0 0x12 0x72 0x30 0x0 0x41 0x52 0xf 0x0 0x1 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 2022-09-12 13:19:45 DEBUG Processing: 0x0 0x8 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0x0 0xce 0x0 0xac 0x0 0x9d 0x0 0x8c 0x0 0xbd 0x0 0xbf 0x0 0xbf 0x0 0x26 0x0 0x74 0x0 0x4b 0x0 0xad 0x0 0x9c 0x0 0xd3 0x0 0xc1 0x0 0xbd 0x0 0x91 0x0 0x89 0x0 0x96 0x0 0xbc 0x0 0xba 0x0 0xbc 0x0 0xca 0x0 0xd0 0x0 0x86 0x0 0xce 0x0 0x52 0x0 0x71 0x0 0x0 0x0 0x0 0x2 0x20 0x1 0xed 0x1 0xb8 0x1 0xa3 0x1 0xde 0x2 0x2 0x0 0xbb 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x10 0x54 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1e 0x5c 0x8 0x6 0x47 0xd9 0xcc 0x54 0xcb 0xc4 0xe0 0xc1 0xde 0x6b 0x23 0xb7 0x3e 0xa0 0x12 0x72 0x30 0x0 0x41 0x52 0xf 0x0 0x1 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 2022-09-12 13:19:45 DEBUG Factory Response[ReadInputRegistersResponse: 4] 2022-09-12 13:19:45 DEBUG Adding transaction 8 2022-09-12 13:19:45 DEBUG Getting transaction 8 2022-09-12 13:19:45 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:45 DEBUG Scraping: read, 6299:100 2022-09-12 13:19:45 DEBUG load_registers: read, 6299:100 2022-09-12 13:19:45 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 46287) 2022-09-12 13:19:45 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 50949) 2022-09-12 13:19:45 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:45 DEBUG Running transaction 9 2022-09-12 13:19:45 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 41661) 2022-09-12 13:19:45 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 51320) 2022-09-12 13:19:45 DEBUG SEND: 0x0 0x9 0x0 0x0 0x0 0x6 0x1 0x4 0x18 0x9b 0x0 0x64 2022-09-12 13:19:45 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:45 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:45 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:45 DEBUG RECV: 0x0 0x9 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:45 DEBUG Processing: 0x0 0x9 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:45 DEBUG Factory Response[132] 2022-09-12 13:19:45 DEBUG Adding transaction 9 2022-09-12 13:19:45 DEBUG Getting transaction 9 2022-09-12 13:19:45 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:45 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:45 DEBUG Exception Response(132, 4, IllegalAddress) 2022-09-12 13:19:45 DEBUG Scraping: read, 6399:100 2022-09-12 13:19:45 DEBUG load_registers: read, 6399:100 2022-09-12 13:19:45 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 49683) 2022-09-12 13:19:45 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 46306) 2022-09-12 13:19:45 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:45 DEBUG Running transaction 10 2022-09-12 13:19:45 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 39819) 2022-09-12 13:19:45 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 49968) 2022-09-12 13:19:45 DEBUG SEND: 0x0 0xa 0x0 0x0 0x0 0x6 0x1 0x4 0x18 0xff 0x0 0x64 2022-09-12 13:19:45 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:45 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:46 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:46 DEBUG RECV: 0x0 0xa 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:46 DEBUG Processing: 0x0 0xa 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:46 DEBUG Factory Response[132] 2022-09-12 13:19:46 DEBUG Adding transaction 10 2022-09-12 13:19:46 DEBUG Getting transaction 10 2022-09-12 13:19:46 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:46 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:46 DEBUG Exception Response(132, 4, IllegalAddress) 2022-09-12 13:19:46 DEBUG Scraping: read, 6499:100 2022-09-12 13:19:46 DEBUG load_registers: read, 6499:100 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 39333) 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 58141) 2022-09-12 13:19:46 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:46 DEBUG Running transaction 11 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 54212) 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 37775) 2022-09-12 13:19:46 DEBUG SEND: 0x0 0xb 0x0 0x0 0x0 0x6 0x1 0x4 0x19 0x63 0x0 0x64 2022-09-12 13:19:46 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:46 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:46 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:46 DEBUG RECV: 0x0 0xb 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:46 DEBUG Processing: 0x0 0xb 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:46 DEBUG Factory Response[132] 2022-09-12 13:19:46 DEBUG Adding transaction 11 2022-09-12 13:19:46 DEBUG Getting transaction 11 2022-09-12 13:19:46 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:46 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:46 DEBUG Exception Response(132, 4, IllegalAddress) 2022-09-12 13:19:46 DEBUG Scraping: read, 6599:100 2022-09-12 13:19:46 DEBUG load_registers: read, 6599:100 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 34651) 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 55667) 2022-09-12 13:19:46 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:46 DEBUG Running transaction 12 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 58915) 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 38667) 2022-09-12 13:19:46 DEBUG SEND: 0x0 0xc 0x0 0x0 0x0 0x6 0x1 0x4 0x19 0xc7 0x0 0x64 2022-09-12 13:19:46 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:46 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:46 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:46 DEBUG RECV: 0x0 0xc 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:46 DEBUG Processing: 0x0 0xc 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:46 DEBUG Factory Response[132] 2022-09-12 13:19:46 DEBUG Adding transaction 12 2022-09-12 13:19:46 DEBUG Getting transaction 12 2022-09-12 13:19:46 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:46 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:46 DEBUG Exception Response(132, 4, IllegalAddress) 2022-09-12 13:19:46 DEBUG Scraping: read, 6699:100 2022-09-12 13:19:46 DEBUG load_registers: read, 6699:100 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 50258) 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 57981) 2022-09-12 13:19:46 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:46 DEBUG Running transaction 13 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 58040) 2022-09-12 13:19:46 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 47945) 2022-09-12 13:19:46 DEBUG SEND: 0x0 0xd 0x0 0x0 0x0 0x6 0x1 0x4 0x1a 0x2b 0x0 0x64 2022-09-12 13:19:46 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:46 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:47 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:47 DEBUG RECV: 0x0 0xd 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:47 DEBUG Processing: 0x0 0xd 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:47 DEBUG Factory Response[132] 2022-09-12 13:19:47 DEBUG Adding transaction 13 2022-09-12 13:19:47 DEBUG Getting transaction 13 2022-09-12 13:19:47 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:47 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:47 DEBUG Exception Response(132, 4, IllegalAddress) 2022-09-12 13:19:47 DEBUG Scraping: read, 7012:25 2022-09-12 13:19:47 DEBUG load_registers: read, 7012:25 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 47282) 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 45005) 2022-09-12 13:19:47 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:47 DEBUG Running transaction 14 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 52002) 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 35481) 2022-09-12 13:19:47 DEBUG SEND: 0x0 0xe 0x0 0x0 0x0 0x6 0x1 0x4 0x1b 0x64 0x0 0x19 2022-09-12 13:19:47 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:47 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:47 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:47 DEBUG RECV: 0x0 0xe 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:47 DEBUG Processing: 0x0 0xe 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:47 DEBUG Factory Response[132] 2022-09-12 13:19:47 DEBUG Adding transaction 14 2022-09-12 13:19:47 DEBUG Getting transaction 14 2022-09-12 13:19:47 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:47 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:47 DEBUG Exception Response(132, 4, IllegalAddress) 2022-09-12 13:19:47 DEBUG Scraping: read, 12999:125 2022-09-12 13:19:47 DEBUG load_registers: read, 12999:125 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 51504) 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 49980) 2022-09-12 13:19:47 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:47 DEBUG Running transaction 15 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 45490) 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 47575) 2022-09-12 13:19:47 DEBUG SEND: 0x0 0xf 0x0 0x0 0x0 0x6 0x1 0x4 0x32 0xc7 0x0 0x7d 2022-09-12 13:19:47 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:47 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:47 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:47 DEBUG RECV: 0x0 0xf 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:47 DEBUG Processing: 0x0 0xf 0x0 0x0 0x0 0x3 0x1 0x84 0x2 2022-09-12 13:19:47 DEBUG Factory Response[132] 2022-09-12 13:19:47 DEBUG Adding transaction 15 2022-09-12 13:19:47 DEBUG Getting transaction 15 2022-09-12 13:19:47 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:47 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:47 DEBUG Exception Response(132, 4, IllegalAddress) 2022-09-12 13:19:47 DEBUG Scraping: hold, 4999:10 2022-09-12 13:19:47 DEBUG load_registers: hold, 4999:10 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 37363) 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 36001) 2022-09-12 13:19:47 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:47 DEBUG Running transaction 16 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 60785) 2022-09-12 13:19:47 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 58933) 2022-09-12 13:19:47 DEBUG SEND: 0x0 0x10 0x0 0x0 0x0 0x6 0x1 0x3 0x13 0x87 0x0 0xa 2022-09-12 13:19:47 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:47 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:48 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:48 DEBUG RECV: 0x0 0x10 0x0 0x0 0x0 0x17 0x1 0x3 0x14 0x7 0xe6 0x0 0x9 0x0 0xc 0x0 0xa 0x0 0x13 0x0 0x2e 0x0 0xcf 0x0 0xaa 0x3 0xe8 0x0 0xff 2022-09-12 13:19:48 DEBUG Processing: 0x0 0x10 0x0 0x0 0x0 0x17 0x1 0x3 0x14 0x7 0xe6 0x0 0x9 0x0 0xc 0x0 0xa 0x0 0x13 0x0 0x2e 0x0 0xcf 0x0 0xaa 0x3 0xe8 0x0 0xff2022-09-12 13:19:48 DEBUG Factory Response[ReadHoldingRegistersResponse: 3] 2022-09-12 13:19:48 DEBUG Adding transaction 16 2022-09-12 13:19:48 DEBUG Getting transaction 16 2022-09-12 13:19:48 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:48 DEBUG Scraping: hold, 5009:10 2022-09-12 13:19:48 DEBUG load_registers: hold, 5009:10 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 53655) 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 57229) 2022-09-12 13:19:48 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:48 DEBUG Running transaction 17 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 50105) 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 51668) 2022-09-12 13:19:48 DEBUG SEND: 0x0 0x11 0x0 0x0 0x0 0x6 0x1 0x3 0x13 0x91 0x0 0xa 2022-09-12 13:19:48 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:48 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:48 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:48 DEBUG RECV: 0x0 0x11 0x0 0x0 0x0 0x17 0x1 0x3 0x14 0x3 0xe8 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x3 0xe8 2022-09-12 13:19:48 DEBUG Processing: 0x0 0x11 0x0 0x0 0x0 0x17 0x1 0x3 0x14 0x3 0xe8 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x3 0xe8 2022-09-12 13:19:48 DEBUG Factory Response[ReadHoldingRegistersResponse: 3] 2022-09-12 13:19:48 DEBUG Adding transaction 17 2022-09-12 13:19:48 DEBUG Getting transaction 17 2022-09-12 13:19:48 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:48 DEBUG Scraping: hold, 5034:10 2022-09-12 13:19:48 DEBUG load_registers: hold, 5034:10 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 46920) 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 37094) 2022-09-12 13:19:48 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:48 DEBUG Running transaction 18 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 55391) 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 53064) 2022-09-12 13:19:48 DEBUG SEND: 0x0 0x12 0x0 0x0 0x0 0x6 0x1 0x3 0x13 0xaa 0x0 0xa 2022-09-12 13:19:48 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:48 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:48 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:48 DEBUG RECV: 0x0 0x12 0x0 0x0 0x0 0x17 0x1 0x3 0x14 0xff 0xff 0x0 0x55 0x0 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 2022-09-12 13:19:48 DEBUG Processing: 0x0 0x12 0x0 0x0 0x0 0x17 0x1 0x3 0x14 0xff 0xff 0x0 0x55 0x0 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 2022-09-12 13:19:48 DEBUG Factory Response[ReadHoldingRegistersResponse: 3] 2022-09-12 13:19:48 DEBUG Adding transaction 18 2022-09-12 13:19:48 DEBUG Getting transaction 18 2022-09-12 13:19:48 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:48 DEBUG Scraping: hold, 13000:100 2022-09-12 13:19:48 DEBUG load_registers: hold, 13000:100 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 54928) 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 47884) 2022-09-12 13:19:48 DEBUG Current transaction state - TRANSACTION_COMPLETE 2022-09-12 13:19:48 DEBUG Running transaction 19 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 42448) 2022-09-12 13:19:48 DEBUG Connection to Modbus server established. Socket ('192.168.1.1', 57009) 2022-09-12 13:19:48 DEBUG SEND: 0x0 0x13 0x0 0x0 0x0 0x6 0x1 0x3 0x32 0xc8 0x0 0x64 2022-09-12 13:19:48 DEBUG New Transaction state 'SENDING' 2022-09-12 13:19:48 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY' 2022-09-12 13:19:49 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY' 2022-09-12 13:19:49 DEBUG RECV: 0x0 0x13 0x0 0x0 0x0 0x3 0x1 0x83 0x2 2022-09-12 13:19:49 DEBUG Processing: 0x0 0x13 0x0 0x0 0x0 0x3 0x1 0x83 0x2 2022-09-12 13:19:49 DEBUG Factory Response[131] 2022-09-12 13:19:49 DEBUG Adding transaction 19 2022-09-12 13:19:49 DEBUG Getting transaction 19 2022-09-12 13:19:49 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE' 2022-09-12 13:19:49 WARNING Modbus connection failed Modbus connection failed 2022-09-12 13:19:49 DEBUG Exception Response(131, 3, IllegalAddress) 2022-09-12 13:19:49 INFO Scraping: 9/18 registers failed to scrape 2022-09-12 13:19:49 DEBUG Using Inverter Time: 2022-9-12 10:19:46 2022-09-12 13:19:49 INFO Inverter: Successfully scraped in 7.660853 secs 2022-09-12 13:19:49 DEBUG PVOutput: Data Logged: {'v1': 3800.0, 'v2': 606, 'v4': 33373, 'v6': 219.0, 'count': 1} 2022-09-12 13:19:49 DEBUG PVOutput: Request; https://pvoutput.org/service/r2/addbatchstatus.jsp, {'X-Pvoutput-Apikey': 'xxxxxxxxx', 'X-Pvoutput-SystemId': '93119', 'Content-Type': 'application/x-www-form-urlencoded', 'cache-control': 'no-cache'} : {'data': '20220912,10:19,3800,606,,33373,,219.0,,,,,,', 'c1': 2} 2022-09-12 13:19:49 DEBUG Starting new HTTPS connection (1): pvoutput.org:443 2022-09-12 13:19:50 DEBUG https://pvoutput.org:443 "POST /service/r2/addbatchstatus.jsp?data=20220912%2C10%3A19%2C3800%2C606%2C%2C33373%2C%2C219.0%2C%2C%2C%2C%2C%2C&c1=2 HTTP/1.1" 200 16 2022-09-12 13:19:50 INFO PVOutput: Data uploaded 2022-09-12 13:19:50 INFO Closing Session: ModbusTcpClient(192.168.1.208:502) 2022-09-12 13:19:50 DEBUG Processing Time: 8.52 secs
Very high inverter temperature
Just updated to 3.3 but this was also present in 3.1
I just noticed these temperature spikes on the inverter temperature. I also noticed that the inverter never has a negative temperature even though the outside temperature is around -6°C right now.
I turned on logging to file so I can provide the debug log file if that would help.
Two scrap values for daily datas
Hi For SH10RT and SH8.0RT I can confirm that daily values are only updated every 5 min. A scraping time below 5 minutes is therefore "useless". How ever there are othere values that are live values that one might want to scrape, like power_load (consumption of your residencial) mppt voltage, battery power or mppt current.
I want so, that's why I scrape every 30 sec.
If we could confirm this behaviour also for the other inverters, we could fix the 5 min interval for the daily values (or make another config setting for it) and keep the current scraping value for the live values.
Scraping is then performed: if $scrape_daily > $scrape_intervall: every $scrape_intervall a "current_dataset" and every $scrape_daily a daily dataset.
if $scrape_daily <= $scrape_intervall: every $scrape_intervall a full scrape including current and daily data.
Of course I could also reduce the values with an influx database task. I am not using the mqtt or the pvout. So I don't know if there could be any issues with those "plugins".
Support for SG8K-D Inverter
Hey,
Firstly thanks for this, been working on something like this personally but found yours on whirlpool.
The script seems to be working in some capacity but I don't think you directly support this model.
Traceback (most recent call last):
File "/usr/local/lib/python3.10/threading.py", line 1009, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.10/threading.py", line 946, in run
self._target(*self._args, **self._kwargs)
File "/usr/src/sungather/exports/mqtt.py", line 38, in publish
self.sensor_topic = self.sensor_topic.replace('{model}', inverter.get('device_type_code', 'unknown').replace('.',''))
AttributeError: 'int' object has no attribute 'replace'
Exception in thread Thread-72 (publish):
I have sent a request to sungrowpower for the modbus register
Hidden registers?
Not really an issue, however I have two observations:
- Looks like there are hidden registers, not provided in the documentation and not being used by SunGather
- Most values just don't add up on my SH10RT.
1: As seen on screenshots below (iSolarCloud app), there are extra registers like Total Backup Power and per-phase Backup power. I can't find this data in official register map (the PDF), and in any of modbus implementations, including SunGather.
What I need the most is per-phase power, as measured by smart meter. Yes, my hybrid inverter, SH10RT, came with DTSU666 meter in the box. Also I want to note that per-phase power, reported by the app, is offset from real values (that I have measured with other equipment) by 1/3 of Total Backup Power (actual power on grid input is zero, although some phases are positive, some negative).
2: Another issue is that numbers don't add up. For example battery power is not equal to battery current and battery voltage multiplied. Same goes for other values, like Total DC Power does not equal the sum of load, grid and battery charge. I spent a couple of days trying to understand what is what, and still ended up asking about it here.
So far I came to conclusion that these values are being faked, because, for example, if battery power is equal load power, and everything else is disconnected, there is no leftover for internal conversion losses. And inverter runs pretty hot, there should be a significant loss.
Anyone looked in to this?
Setup SH10RT/SH8RT - time out
Hi,
I am just setting up my stuff and I would like to support this work with some documentation work, coding what ever. But currently I am struggling a bit.
At first I am just happy with gathering data via Modbus. All the Database setup (mqtt/influx) can come later (if not needed), when the data is flowing. The webpanel is accessable but shows no data.
I enabled console for debug mode and saw that connection times out.
Config Value
host 192.168.10.3
connection sungrow
model SH8.0RT
2022-01-19 11:44:48 ERROR Connection to (192.168.10.3, 502) failed: timed out
2022-01-19 11:44:58 ERROR Connection to (192.168.10.3, 502) failed: timed out
2022-01-19 11:45:08 ERROR Connection to (192.168.10.3, 502) failed: timed out
2022-01-19 11:45:08 WARNING No data returned for read, 5000:100
Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.10.3:502)]
2022-01-19 11:45:18 ERROR Connection to (192.168.10.3, 502) failed: timed out
2022-01-19 11:45:18 WARNING No data returned for hold, 4999:10
Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.10.3:502)]
2022-01-19 11:45:18 WARNING Data collection failed, skipped exporting data. Retying in 30 secs
I checked other IP addresses to resulting in "no route to host". And the router states that 192.168.10.3 was given to "espressif". So I assume that the host must be there somehow. nmap and ping do not show anything. Modbus is enabled.
I am unsure which ethernet jack I have to use for modbus (Wifi Dongle or the one at the converter). And maybe it is also a problem of my firmeware of the converter version. I could see in Wifi http-page that it is V11.
By the way I also tried to connect via pymodbus.consol[erp]. I am not sure if I put everything right there but it resulted in the same problem (time out).
I would appreciate any helpful hints!
Best
Feature Request: Export to Charge HQ
ChargeHQ allows you to send solar generation data to their API, this then helps smartly control charging of EV vehicles.
https://chargehq.net/kb/push-api
Now they do support Sungrow natively, but this uses the isolorcloud website and can have data delays of up to 10 minutes.
Considering sungather has access directly to the inverter and can easily do 30 second intervals, this would allow the EV charging to be more efficient.
SG5.0RS support
Hello,
Is this guy supported? I hoped it would be very similair to SH5.0RS but unfortunately none of the settings seem to work. Tried various combination in the config file.
Running the docker container if this would be any different.
If you can tell me which config is most likely to work I can post some logging output from the container.
Thanks!
More info from the smart meter?
Is it possible to get out more info from the smart meter then just the power of the phases?
I would like to get voltage and current also
Sungrow SH10RT-112 'index out of range' error
Hi,
i received last week my SHRT10-112 with the 9,6kWh Battery. The SHRT10-112 is a SH10RT with slightly modified hardware (or suppliers of hardware). Differences and Compatibility of SHRT and SBR versions.pdf.
I'm using just ethernet connection, no WiFi connection. When connectin to the inverter with a modbus client and reading register 5000, i'm receiving 0xe0f. I extended already the registers-sungrow.yaml file to support the SHRT10-112, when receiving a 0xe0f. (see registers-sungrow.yaml.txt).
The sungather.py connects and reads the values for the console output correct. But i get many 'index out of range' errors.
Here a console log of the first output: debuglog.txt
Is this normal? I necessary i can upload more/other debug outputs.
Meter: incorrect readings
I have a Sungrow SH10RT (10kW hybrid) with battery and smart meter.
I get many values from the inverter that seem good, however meter-related numbers are way off.
I am running SunGather v0.3.7.
[suggestion] Mark calculated values
Hi all,
I would like to suggest to mark the calculated values that are not originally provided by the inverter for example with an prefix like "calc_".
This is an suggestion. I could do of course for my own version but I would prefere to development forces joined.
WARNING No data returned for read, 4999:1 - DEBUG Modbus Error: [Connection] HTTP Request failed:
Hi,
the code worked perfectly until 2022-12-13 (without changing anything), then I got this messages:
...
2022-12-13 10:47:43 INFO MQTT: Published
2022-12-13 10:47:43 INFO Next scrape in 296 secs
2022-12-13 10:52:44 INFO Inverter: Successfully scraped in 3.696175 secs
2022-12-13 10:52:44 INFO MQTT: Published
2022-12-13 10:52:44 INFO Next scrape in 296 secs
2022-12-13 10:57:50 WARNING No data returned for read, 5000:100
No data returned for read, 5000:100
2022-12-13 10:57:53 WARNING No data returned for read, 6099:100
No data returned for read, 6099:100
2022-12-13 10:57:57 WARNING No data returned for read, 6199:100
No data returned for read, 6199:100
2022-12-13 10:58:00 WARNING No data returned for read, 6299:100
No data returned for read, 6299:100
2022-12-13 10:58:03 WARNING No data returned for read, 6399:100
No data returned for read, 6399:100
2022-12-13 10:58:06 WARNING No data returned for read, 6499:100
No data returned for read, 6499:100
2022-12-13 10:58:09 WARNING No data returned for read, 6599:100
No data returned for read, 6599:100
2022-12-13 10:58:12 WARNING No data returned for read, 6699:100
No data returned for read, 6699:100
2022-12-13 10:58:15 WARNING No data returned for read, 12999:125
No data returned for read, 12999:125
2022-12-13 10:58:18 WARNING No data returned for hold, 4999:10
No data returned for hold, 4999:10
2022-12-13 10:58:18 INFO Disconnecting: SungrowModbusWebClient_0.3.2(192.168.0.135:8082)
2022-12-13 10:58:18 INFO Disconnecting: None
2022-12-13 10:58:18 WARNING Data collection failed, skipped exporting data. Retying in 300 secs
Data collection failed, skipped exporting data. Retying in 300 secs
...
After several test which all failed I have installed the newest version and running in DEBUG mode:
2022-12-15 08:51:28 INFO Starting SunGather 0.3.9
2022-12-15 08:51:28 INFO Loaded config: config.yaml
2022-12-15 08:51:29 INFO Loaded registers: registers-sungrow.yaml
2022-12-15 08:51:29 INFO Registers file version: 0.2.1
2022-12-15 08:51:29 INFO Logging to console set to: DEBUG
2022-12-15 08:51:29 INFO Logging to file set to: DEBUG
2022-12-15 08:51:29 DEBUG Inverter Config Loaded: {'host': '192.168.0.135', 'port': 502, 'timeout': 300, 'retries': 5, 'slave': 1, 'scan_interval': 300, 'connection': 'http', 'model': None, 'smart_meter': False, 'use_local_time': False, 'log_console': 'DEBUG', 'log_file': 'DEBUG', 'level': 0}
2022-12-15 08:51:29 DEBUG Checking Modbus Connection
2022-12-15 08:51:29 INFO Modbus client is not connected, attempting to reconnect
2022-12-15 08:51:29 INFO Connection: SungrowModbusWebClient_0.3.2(192.168.0.135:8082)
2022-12-15 08:51:29 DEBUG Connection to websocket server established: ws://192.168.0.135:8082/ws/home/overview
2022-12-15 08:51:29 DEBUG {'result_code': 1, 'result_msg': 'success', 'result_data': {'service': 'connect', 'token': '60581efb-1a33-4f11-99e8-dd6e4c3ab58b', 'uid': 1, 'tips_disable': 0}}
2022-12-15 08:51:29 INFO Token Retrieved: 60581efb-1a33-4f11-99e8-dd6e4c3ab58b
2022-12-15 08:51:29 DEBUG Requesting Device Information
2022-12-15 08:51:29 DEBUG {'result_code': 1, 'result_msg': 'success', 'result_data': {'service': 'devicelist', 'list': [{'id': 1, 'dev_id': 1, 'dev_code': 3585, 'dev_type': 35, 'dev_procotol': 2, 'dev_sn': 'A2162102870', 'dev_name': 'SH6.0RT(COM1-001)', 'dev_model': 'SH6.0RT', 'port_name': 'COM1', 'phys_addr': '1', 'logc_addr': '1', 'link_status': 1, 'init_status': 1, 'dev_special': '0', 'list': []}], 'count': 1}}
2022-12-15 08:51:29 DEBUG Retrieved: dev_type = 35, dev_code = 3585
2022-12-15 08:51:32 DEBUG load_registers: read, 4999:1
2022-12-15 08:51:32 DEBUG Current transaction state - IDLE
2022-12-15 08:51:32 DEBUG Running transaction 1
2022-12-15 08:51:32 DEBUG SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x87 0x0 0x1
2022-12-15 08:51:32 DEBUG New Transaction state 'SENDING'
2022-12-15 08:51:32 DEBUG param_type: 0, start_address: 5000, count: 1, dev_id: 1
2022-12-15 08:51:32 DEBUG Calling: http://192.168.0.135/device/getParam?dev_id=1&dev_type=35&dev_code=3585&type=3¶m_addr=5000¶m_num=1¶m_type=0&token=60581efb-1a33-4f11-99e8-dd6e4c3ab58b&lang=en_us&time123456=1671090692
2022-12-15 08:51:32 DEBUG Starting new HTTP connection (1): 192.168.0.135:80
2022-12-15 08:51:32 WARNING No data returned for read, 4999:1
No data returned for read, 4999:1
2022-12-15 08:51:32 DEBUG Modbus Error: [Connection] HTTP Request failed: HTTPConnectionPool(host='192.168.0.135', port=80): Max retries exceeded with url: /device/getParam?dev_id=1&dev_type=35&dev_code=3585&type=3¶m_addr=5000¶m_num=1¶m_type=0&token=60581efb-1a33-4f11-99e8-dd6e4c3ab58b&lang=en_us&time123456=1671090692 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd8e0ce1cd0>: Failed to establish a new connection: [Errno 111] Connection refused'))')
See logfile attached
Can you help me?
May be a problem with port 80?
Nmap scan report for espressif (192.168.0.135)
Host is up (0.0047s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
443/tcp open https
8082/tcp open blackice-alerts
Wrong voltage is sent to pvoutput.org - total_apparent_power instead of phase_a_voltage
The good value/variable is sent after script restart then is getting wrong:
my config:
- name: v5 # Ambient temperature see: https://forum.pvoutput.org/t/what-temperature-is-used-to-calcul>
register: internal_temperature #
- name: v6 # Voltage
register: phase_a_voltage # Read voltage from first Phase
Unsupported models from non hybrid modbus documentation
Hi @bohdan-s ,
I just went through the doc that is uploaded here and I noticed that SG85BF,SG80HV,SG80BF,SG110HV-M are not part of the supported inverters in the registers.yaml. Is there any reason why those models were excluded?
I have noticed that the models are not fully listed for all registers where needed. I also doubt it make sens to add it everywhere where needed. That would blow up the registers.yaml.
The question is: How do we want to handle it? Wait until an issue is raised to support the named model? And then take care?
I would like to suggest to change the model list for each register to a list of model series. That could reduce the listings to SGHV-Series, SGRT-Series SGCX Series and so on
This nights clock change lead to freeze sungather
Somehow sungather stopped working with the first scrape which took place after the clock change. See log:
2022-10-30 02:59:54 INFO MQTT: Published
2022-10-30 02:59:54 INFO Next scrape in 5 secs
2022-10-30 02:00:04 INFO Inverter: Successfully scraped in 82805.131784 secs
2022-10-30 02:00:04 INFO MQTT: Published
2022-10-30 02:00:04 WARNING SunGather is taking 82805.13 to process, which is longer than interval 10, Please increase scan interval
SunGather is taking 82805.13 to process, which is longer than interval 10, Please increase scan interval
There were no new log entries after the last one.
export_power / total_active_power out of range (?)
Hi,
on a cloudy day with very low power generation (like 10-20W in the WiFi App)
export_power and total_active_power seem to show "wrong" values.
total_active_power | 65493
export_power | 65076
At first I thought it's an out of range thing (like S32 vs U32). According to the guide they should be both S32. But that didn't help.
I didn't yet dive into the code to figure out where it might come from. Maybe it is also an error within the converter.
First wanted to ask if someone here saw something similar.
support for hybrid (sh) series of sungrow inverters
Here is the official docs for the hybrid range:
communication-protocol-of-residential-hybrid-inverterv1.0.20-1.pdf
I doubt I'll have time to add them myself until late Jan, so I'll leave them here incase someone else wants to add them before then
Firmware update on SH5.0RS results in many registers missing under `http` connection
I bumped firmware to try to resolve an unrelated issue:
SUNSTONE-H03011.02.15->SUNSTONE-H03011.02.22AFCI06002.01.02->AFCI06002.01.03SUNSTONE-H01011.02.16->SUNSTONE-H01011.02.26
Since then, many registers are missing when using http. Some show up under modbus, but that has other issues (like zeroed running_state).
Interestingly, the missing registers, such as grid_frequency, which I spot-checked in the Web UI manually, still can be pulled:
Consequently, I'm not sure if this is an issue for https://github.com/bohdan-s/SungrowModbusWebClient or here.
The SunGather logs have lines like, but I am not sure if these existed before update:
2022-07-12 16:59:55 DEBUG Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED ')
2022-07-12 16:59:58 INFO Scraping: 1/14 registers failed to scrape
2022-07-12 17:00:08 DEBUG Payload Dict: {'result_code': 301, 'result_msg': 'I18N_COMMON_READ_FAILED'}
and:
No data returned for read, 5000:100
No data returned for read, 12999:125
No data returned for hold, 4999:10
No data returned for hold, 5009:10
No data returned for hold, 5034:10
No data returned for read, 5000:100
Some unfiltered log lines:
2022-07-13 09:17:00 DEBUG Current transaction state - SENDING
2022-07-13 09:17:00 DEBUG Running transaction 23
2022-07-13 09:17:00 DEBUG SEND: 0x0 0x17 0x0 0x0 0x0 0x6 0x1 0x4 0x19 0xc7 0x0 0x64
2022-07-13 09:17:00 DEBUG New Transaction state 'SENDING'
2022-07-13 09:17:00 DEBUG param_type: 0, start_address: 6600, count: 100, dev_id: 1
2022-07-13 09:17:00 DEBUG Calling: http://10.10.10.219/device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=6600¶m_num=100¶m_type=0&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667820
2022-07-13 09:17:00 DEBUG Starting new HTTP connection (1): 10.10.10.219:80
2022-07-13 09:17:00 DEBUG http://10.10.10.219:80 "GET /device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=6600¶m_num=100¶m_type=0&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667820 HTTP/1.1" 200 65
2022-07-13 09:17:00 DEBUG HTTP Status code 200
2022-07-13 09:17:00 DEBUG Payload Status code 301
2022-07-13 09:17:00 DEBUG Payload Dict: {'result_code': 301, 'result_msg': 'I18N_COMMON_READ_FAILED'}
2022-07-13 09:17:00 WARNING No data returned for read, 6599:100
No data returned for read, 6599:100
2022-07-13 09:17:00 DEBUG Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED ')
2022-07-13 09:17:00 DEBUG Scraping: read, 6699:100
2022-07-13 09:17:00 DEBUG load_registers: read, 6699:100
2022-07-13 09:17:00 DEBUG Current transaction state - SENDING
2022-07-13 09:17:00 DEBUG Running transaction 24
2022-07-13 09:17:00 DEBUG SEND: 0x0 0x18 0x0 0x0 0x0 0x6 0x1 0x4 0x1a 0x2b 0x0 0x64
2022-07-13 09:17:00 DEBUG New Transaction state 'SENDING'
2022-07-13 09:17:00 DEBUG param_type: 0, start_address: 6700, count: 100, dev_id: 1
2022-07-13 09:17:00 DEBUG Calling: http://10.10.10.219/device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=6700¶m_num=100¶m_type=0&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667820
2022-07-13 09:17:01 DEBUG Starting new HTTP connection (1): 10.10.10.219:80
2022-07-13 09:17:01 DEBUG http://10.10.10.219:80 "GET /device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=6700¶m_num=100¶m_type=0&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667820 HTTP/1.1" 200 65
2022-07-13 09:17:01 DEBUG HTTP Status code 200
2022-07-13 09:17:01 DEBUG Payload Status code 301
2022-07-13 09:17:01 DEBUG Payload Dict: {'result_code': 301, 'result_msg': 'I18N_COMMON_READ_FAILED'}
2022-07-13 09:17:01 WARNING No data returned for read, 6699:100
No data returned for read, 6699:100
2022-07-13 09:17:01 DEBUG Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED ')
2022-07-13 09:17:01 DEBUG Scraping: read, 12999:125
2022-07-13 09:17:01 DEBUG load_registers: read, 12999:125
2022-07-13 09:17:01 DEBUG Current transaction state - SENDING
2022-07-13 09:17:01 DEBUG Running transaction 25
2022-07-13 09:17:01 DEBUG SEND: 0x0 0x19 0x0 0x0 0x0 0x6 0x1 0x4 0x32 0xc7 0x0 0x7d
2022-07-13 09:17:01 DEBUG New Transaction state 'SENDING'
2022-07-13 09:17:01 DEBUG param_type: 0, start_address: 13000, count: 125, dev_id: 1
2022-07-13 09:17:01 DEBUG Calling: http://10.10.10.219/device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=13000¶m_num=125¶m_type=0&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667821
2022-07-13 09:17:01 DEBUG Starting new HTTP connection (1): 10.10.10.219:80
2022-07-13 09:17:01 DEBUG http://10.10.10.219:80 "GET /device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=13000¶m_num=125¶m_type=0&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667821 HTTP/1.1" 200 65
2022-07-13 09:17:01 DEBUG HTTP Status code 200
2022-07-13 09:17:01 DEBUG Payload Status code 301
2022-07-13 09:17:01 DEBUG Payload Dict: {'result_code': 301, 'result_msg': 'I18N_COMMON_READ_FAILED'}
2022-07-13 09:17:01 WARNING No data returned for read, 12999:125
No data returned for read, 12999:125
2022-07-13 09:17:01 DEBUG Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED ')
2022-07-13 09:17:01 DEBUG Scraping: hold, 4999:10
2022-07-13 09:17:01 DEBUG load_registers: hold, 4999:10
2022-07-13 09:17:01 DEBUG Current transaction state - SENDING
2022-07-13 09:17:01 DEBUG Running transaction 26
2022-07-13 09:17:01 DEBUG SEND: 0x0 0x1a 0x0 0x0 0x0 0x6 0x1 0x3 0x13 0x87 0x0 0xa
2022-07-13 09:17:01 DEBUG New Transaction state 'SENDING'
2022-07-13 09:17:01 DEBUG param_type: 1, start_address: 5000, count: 10, dev_id: 1
2022-07-13 09:17:01 DEBUG Calling: http://10.10.10.219/device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=5000¶m_num=10¶m_type=1&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667821
2022-07-13 09:17:01 DEBUG Starting new HTTP connection (1): 10.10.10.219:80
2022-07-13 09:17:01 DEBUG http://10.10.10.219:80 "GET /device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=5000¶m_num=10¶m_type=1&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667821 HTTP/1.1" 200 65
2022-07-13 09:17:01 DEBUG HTTP Status code 200
2022-07-13 09:17:01 DEBUG Payload Status code 301
2022-07-13 09:17:01 DEBUG Payload Dict: {'result_code': 301, 'result_msg': 'I18N_COMMON_READ_FAILED'}
2022-07-13 09:17:01 WARNING No data returned for hold, 4999:10
No data returned for hold, 4999:10
2022-07-13 09:17:01 DEBUG Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED ')
2022-07-13 09:17:01 DEBUG Scraping: hold, 5009:10
2022-07-13 09:17:01 DEBUG load_registers: hold, 5009:10
2022-07-13 09:17:01 DEBUG Current transaction state - SENDING
2022-07-13 09:17:01 DEBUG Running transaction 27
2022-07-13 09:17:01 DEBUG SEND: 0x0 0x1b 0x0 0x0 0x0 0x6 0x1 0x3 0x13 0x91 0x0 0xa
2022-07-13 09:17:01 DEBUG New Transaction state 'SENDING'
2022-07-13 09:17:01 DEBUG param_type: 1, start_address: 5010, count: 10, dev_id: 1
2022-07-13 09:17:01 DEBUG Calling: http://10.10.10.219/device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=5010¶m_num=10¶m_type=1&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667821
2022-07-13 09:17:01 DEBUG Starting new HTTP connection (1): 10.10.10.219:80
2022-07-13 09:17:01 DEBUG http://10.10.10.219:80 "GET /device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=5010¶m_num=10¶m_type=1&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667821 HTTP/1.1" 200 65
2022-07-13 09:17:01 DEBUG HTTP Status code 200
2022-07-13 09:17:01 DEBUG Payload Status code 301
2022-07-13 09:17:01 DEBUG Payload Dict: {'result_code': 301, 'result_msg': 'I18N_COMMON_READ_FAILED'}
2022-07-13 09:17:01 WARNING No data returned for hold, 5009:10
No data returned for hold, 5009:10
2022-07-13 09:17:01 DEBUG Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED ')
2022-07-13 09:17:01 DEBUG Scraping: hold, 5034:10
2022-07-13 09:17:01 DEBUG load_registers: hold, 5034:10
2022-07-13 09:17:01 DEBUG Current transaction state - SENDING
2022-07-13 09:17:01 DEBUG Running transaction 28
2022-07-13 09:17:01 DEBUG SEND: 0x0 0x1c 0x0 0x0 0x0 0x6 0x1 0x3 0x13 0xaa 0x0 0xa
2022-07-13 09:17:01 DEBUG New Transaction state 'SENDING'
2022-07-13 09:17:01 DEBUG param_type: 1, start_address: 5035, count: 10, dev_id: 1
2022-07-13 09:17:01 DEBUG Calling: http://10.10.10.219/device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=5035¶m_num=10¶m_type=1&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667821
2022-07-13 09:17:01 DEBUG Starting new HTTP connection (1): 10.10.10.219:80
2022-07-13 09:17:01 DEBUG http://10.10.10.219:80 "GET /device/getParam?dev_id=1&dev_type=35&dev_code=3343&type=3¶m_addr=5035¶m_num=10¶m_type=1&token=7af476f9-9d31-4b5f-b635-8e8c2b826a84&lang=en_us&time123456=1657667821 HTTP/1.1" 200 65
2022-07-13 09:17:01 DEBUG HTTP Status code 200
2022-07-13 09:17:01 DEBUG Payload Status code 301
2022-07-13 09:17:01 DEBUG Payload Dict: {'result_code': 301, 'result_msg': 'I18N_COMMON_READ_FAILED'}
2022-07-13 09:17:01 WARNING No data returned for hold, 5034:10
No data returned for hold, 5034:10
2022-07-13 09:17:01 DEBUG Modbus Error: [Connection] Connection Failed: 301:I18N_COMMON_READ_FAILED ')
2022-07-13 09:17:01 INFO Disconnecting: SungrowModbusWebClient_0.3.2(10.10.10.219:8082)
2022-07-13 09:17:01 INFO Disconnecting: None
2022-07-13 09:17:01 WARNING Data collection failed, skipped exporting data. Retying in 15 secs
Data collection failed, skipped exporting data. Retying in 15 secs
2022-07-13 09:17:01 DEBUG Processing Time: 0.33 secs
2022-07-13 09:17:01 INFO Next scrape in 14 secs
PV Output team
The default team joining does not work if you have to few outputs. I got this response until i changed to join_team: False
2022-01-18 09:28:17 ERROR PVOutput: Team update Failed; 400 Message; b'Bad request 400: Your system must have at least 5 outputs to join a team'
Dependancy created on the config.yaml 'logger'
Hey,
Just been following the master branch and noticed that there is no longer a check on the existance of the logger parameter in the config.yaml file:
SunGather/SunGather/sungather.py
Line 438 in 1b54ae3
pvoutput values don't look right
Thanks for the rewrite @bohdan-s! I just got around to trying it today. My config is as follows:
inverter:
host: sungrow.gateway
port: 8082 # Default for modbus is 502, for http is 8082
# slave: 0x01 # Default is 0x01
# timeout: 10 # Default is 10
# scan_interval: 30 # Default is 30
connection: http # options: modbus, sungrow, http
# model: "SG7.0RT" # This is autodected on startup, only needed if detection issues or for testing
# See model list here: https://github.com/bohdan-s/SunGather#supported
smart_meter: True # Default is False, Set to true if inverter supports reading grind / house consumption
# use_local_time: False # Default False, Uses Inveter time, if try uses PC time when updating timestamps (e.g. PVOutput)
# hybrid: False # Default false, if you have a Hybrid (battery) set to True
# logging: 30 # 10 = Debug, 20 = Info, 30 = Warnning (default), 40 = Error
# level: 1 # 0 = Model and Solar Generation,
# 1 (default) = Useful data, all required for exports,
# 2 everything your Inverter supports,
# 3 Everything from every register
exports:
- name: console # Print Registers to console, good for debugging / troubleshooting
enabled: True
- name: pvoutput # Publish Registers to PVOutput
api: "<key>"
sid: "<sid>"
# 60 for regular accounts, 300 for donation accounts
rate_limit: 60
enabled: True
parameters:
- name: v1 # Energy Generation
register: daily_power_yields # Solar Generated Today (Energy)
multiple: 1000
- name: v2 # Power Generation
register: total_active_power # Current Generation (Power)
- name: v4 # Power Consumption
register: load_power # Current Home usage (Power)
- name: v5 # Temperature
register: internal_temperature # Inverter internal temperature
- name: c1 # Cumulative Flag,
value: 1 # If using v2/v4 set to 1
In pvoutput.org, I'm seeing all zero values except for temperature, which I guess makes sense based on the values of the registers:
Register Value
device_type_code SG10RT
daily_power_yields 54.0
total_power_yields 3644.9
total_running_time 1000
internal_temperature 42.4
total_apparent_power 0
total_active_power 0
work_state_1 Standby
meter_power 538
load_power 0
monthly_power_yields 1217.1
start_stop Start
export_to_grid 0
import_from_grid 538
timestamp 2021-12-23 21:01:07
I'll admit I still don't fully understand what each field in pvoutput means 😆 I expect energy/power/average to be 0 given it's 9:30PM here, but I thought "Power Used" would show how much I'm consuming from the grid (meter_power).
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.