A Home Assistant integration for Solaredge inverters

Overview

hacs_badge

solaredge-modbus-multi

A Home Assistant integration for Solaredge inverters. Supports multiple inverters chained through RS485.

Works with 1 or more inverters - you don't need to have multiple inverters to use this integration, it will work fine with a single inverter.

This integration is for installations where you have a single Leader (Master) inverter connected to network, and one or more Follower (Slave) inverters connected behild it using one of the RS485 bus ports. This integration also supports up to three meters connected to the first inverter.

Multiple Inverter Support

Important: The inverters must have sequential unit IDs (i.e. 1, 2, 3, ...). It doesn't matter which RS485 bus your inverter chain is on as long as it's configured as Solaredge leader/follower (master/slave in older firmware). If you have meters connected to inverter unit 1 the meter IDs can overlap the inverter unit IDs because they're on different busses (the solaredge meter ships with default ID 2).

This integration is developed on a system that consists of two inverters and one meter:

  • Inverters (addressed 1 and 2) on RS485-1
  • Ethernet connected to inverter 1 with modbus/tcp enabled
  • E+I meter (address 2) connected to inverter 1 on RS485-2.
  • Ethernet is also for Solaredge comms - no wireless or cell options

Installation

Copy the contents of the custom_components folder into to your Home Assistant config/custom_components folder or install through HACS. After rebooting Home Assistant, this integration can be configured through the integration setup UI.

Enabling Modbus TCP on SolarEdge Inverter

  1. Enable wifi direct on the inverter by switching the red toggle switch on the inverter to "P" position for less than 5 seconds.
  2. Connect to the inverter access point like you would for a normal wifi network. The wifi password is published at the right side of the inverter. OR scan the QR code on the side of your inverter.
  3. Open up a browser and go to http://172.16.0.1 > Site Communication. From this page you can enable Modbus/TCP.

This only needs to be done on the Leader (Master) inverter with the IP (network) connection.

Credits

This started as a fork but things got too messy and I wasn't sure how to clean it up to get it merged upstream, so I started a new repository. It's now evolved into my "learn about python and HA" project and I've started to make larger changes.

Origional fork:

Comments
  • Export Control

    Export Control

    The export control block of registers allows control of how much power is exported from the system to the grid. This may be useful, for example, to prevent export if the export rate is negative.

    Once the select / number controls are merged, it will be relatively easy to add support for this feature which should be the last one to bring this integration up to feature parity with https://github.com/binsentsu/home-assistant-solaredge-modbus (this was merged there in https://github.com/binsentsu/home-assistant-solaredge-modbus/pull/42)

    enhancement help wanted 
    opened by mpredfearn 76
  • Find another Energymeter

    Find another Energymeter

    Hi,

    first the SE-RGMTR-1D-240C-A was found and i got the sensor values. A day later no values were available and another sensor pop up SE-MTR-3Y-400V-A (and this one is really installed)

    grafik

    bug 
    opened by thewizard-de 38
  • Error: filedescriptor out of range in select()

    Error: filedescriptor out of range in select()

    Before reporting a bug, make sure your configuration is correct and your LAN is working. https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration

    Describe the bug A clear and concise description of what the bug is. I'm using your integration for about a half year now. But now the integration stops working after a while. When I restart HA it works again for some time

    Expected behavior A clear and concise description of what you expected to happen. I expect it keeps working

    Screenshots If applicable, add screenshots of the problem and/or configuration. Schermafbeelding 2022-04-22 om 10 54 29

    Logs Copy any log messages/errors from Home Assistant from "custom_components.solaredge_modbus" and "pymodbus.client.sync".

    Deze fout is ontstaan door een aangepaste integratie.
    
    Logger: custom_components.solaredge_modbus
    Source: custom_components/solaredge_modbus/__init__.py:491
    Integration: SolarEdge Modbus Multi-Inverter (documentation, issues)
    First occurred: 10:49:17 (7 occurrences)
    Last logged: 10:55:17
    
    Error reading inverter at id 1: filedescriptor out of range in select()
    

    Home Assistant (please complete the following information):

    • Version: 2022.4.6

    Additional context Add any other context about the problem here.

    help wanted hardware 
    opened by gieljnssns 31
  • ModbusTcpClient(redacted:1502): Connection unexpectedly closed

    ModbusTcpClient(redacted:1502): Connection unexpectedly closed

    Basically there two, connected, error messages (copies from Log)

    2022-08-20 23:08:40.007 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Error fetching SolarEdge Coordinator data: Failed to update devices: Modbus Error: [Connection] ModbusTcpClient(.......:1502): Connection unexpectedly closed 0.000131 seconds into read of 8 bytes without response from unit before it closed connection

    2022-08-21 05:54:43.009 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Error fetching SolarEdge Coordinator data: Failed to update devices: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received) 2022-08-21 05:55:46.007 ERROR (SyncWorker_5) [pymodbus.client.sync] Connection to (......., 1502) failed: timed out 2022-08-21 05:56:49.006 ERROR (SyncWorker_0) [pymodbus.client.sync] Connection to (......., 1502) failed: timed out ....... continuing...

    Solaredge thru modbus is unreachable. No data is coming into HA. Solaredge entities are: not available. Getting control back by either by resetting or reinstall of the integration Solaredge. Reconfigured the WiFI connection with my LAN brought no solution. Every time within a few hours after a restart, both errors appear.

    Solaredge Support updated my Solaredge and stated that the transformer is operating ok.

    Home Assistant (please complete the following information):

    • Home Assistant Core Version: 2022.8.6 and .5
    • solaredge-modbus-multi Version: 2.1.2 also 2.1.1. The integration is standard configured.

    Please, do you have a solution?

    help wanted hardware 
    opened by bakboord4 30
  • Battery data - unknown

    Battery data - unknown

    Hi,

    I am using your integration now for a few days and it is working great. The only thing what sometimes goes wrong is the energy import and export of the Battery: image When the battery is loading it gives both import and export as unknown. When there is a bigger load it looks like that it is working. For example the battery is loading at the moment, but I see an unknown. History shows that the sensor is working: image

    The sensor looks updated 8 minutes ago.

    help wanted 
    opened by rploeg 20
  • Energy Meter with Modbus Connection not recognized

    Energy Meter with Modbus Connection not recognized

    Setup

    SE82.8K Inverter on Modbus address 2 Solaredge Energy Meter connected to Inverter on Modbus address 1 but not recognized by [solaredge-modbus-multi] as sensor.

    Screenshot 2022-08-24 132405

    opened by hoeselr 20
  • 2.2.1 to 2.2.2: grid meter now shown as two devices with different model but only one has entities

    2.2.1 to 2.2.2: grid meter now shown as two devices with different model but only one has entities

    Describe the bug On 2.2.1 I had two devices: I1 (inverter) M1 (attached meter with model SE-RGMTR-1D-240C-A). Attached meter showed as model "SE-RGMTR-1D-240C-A". Since 2.2.2. I have: I1 (inverter) M1 (SE-MTR-3Y-400V-A) <- no entities M1 (SE-RGMTR-1D-240C-A) <- has all the expected entities

    Expected behavior not sure if this is really a bug or expected, but at least physically only one meter is attached.

    Screenshots

    image image

    Home Assistant (please complete the following information):

    • Home Assistant Core Version: 2022.9.5
    • solaredge-modbus-multi Version: 2.2.2
    bug 
    opened by spali 18
  • Connection time out

    Connection time out

    I'm getting a lot of connection time out using a polling interval below 10 secs. I was getting the same problems with other component for modbus-solaredge. I think that this is related to the new HA version 7.2, and I was hoping that this component wasn't affected using a much more recent pymodbus library.

    Screenshot 2022-07-12 at 14 12 30

    Do you have the same problems?

    help wanted 
    opened by rzulian 18
  • Fronius modbus

    Fronius modbus

    I have a SolarEdge inverter and also a Fronius Galvo inverter. I've installed this component for both inverters. The sensors of the Solaredge inverter looks very good. Better then other modbus components I've tested so far. Good work!

    image

    image

    The sensors of the Fronius inverter looks good. Some small improvement could be made. As you can see the main sensor values are ok. The Fronius status codes are different and also the power factor is different. So with no modifications I can use this custom component already for both inverters!

    I think with some minor changes this component could also be interesting for other inverter brands e.g. Fronius. @WillCodeForCats are you interested? If so, I could help you with debugging/testing the Fronius inverter for sure.

    enhancement 
    opened by dhover 17
  • Language Translations

    Language Translations

    Looking for better language translations. The current translations are just the English version run through Google Translate.

    Please help by reviewing and submitting updated translations, or new ones for languages we don't have yet.

    help wanted good first issue 
    opened by WillCodeForCats 12
  • two integrations with the same file location - how to safely remove one?

    two integrations with the same file location - how to safely remove one?

    it's probably not a bug per se, but - maybe you can help me ;) I was using the Solaredge Modbus integration by bitsentsu - lets call it "A", and because I wanted to give a try to your integration (as being updated "more ecently", and I like to have my software "up-to-date") without changing anything I went full Leeroy Jenkins and additionaly installed your Solaredge Modbus Multi-Inverter integration - lets call it "B". both integrations installed via HACS.

    integration B started to work without anything additional, as it probably read all configurations from the A, with one exception: as the integration B is planned for multi-inverter setup, an "I1" was added to entity names so now I had twice as many entities. I've noticed, that entities from integration A went unknown/unavailable, but all from your integration showed all the readings correctly. so - as I wanted to keep all my readings/history/recorder/influxdb archive to be consistent, I went to the dashboard and entity by entity started to delete entity from A, and to rename entity from B (by deleting "I1" - I'm not planning multi-inverter setup anyway). everything went smooth, and is working without problems.

    BUT - after that I've noticed, that I still have the A integration listed in HACS... I've checked custom_components folder and if I'm correct, A & B use the same folder, just the files were overwritten ;)

    so now goes my question: is it safe to uninstall the A integration via HACS, or it would remove the B integration along with data? or maybe there's some other way to delete the A integration by hand, so it won't be recognized by HACS as also installed in the system?

    bug 
    opened by pejotigrek 12
  • Remote Control Charge/Discharge Limit inconsistent

    Remote Control Charge/Discharge Limit inconsistent

    Describe the bug

    This might be a display issue or it's specific to the 11.4 Hub inverter where the DC charge/discharge limit is in floating point 11.4k (0x46322000) instead of the maximum battery charge power 5000

    Expected behavior

    Maybe this is a display issue, it's showing inconstant data

    Screenshots Screenshot 2022-12-31 8 29 06 AM Screenshot 2022-12-31 8 28 52 AM

    Logs

    N/A

    Debug Logs

    2022-12-31 12:29:34.642 DEBUG (SyncWorker_3) [custom_components.solaredge_modbus_multi.hub] Inverter 1: charge_limit 0x46322000
    2022-12-31 12:29:34.643 DEBUG (SyncWorker_3) [custom_components.solaredge_modbus_multi.hub] Inverter 1: discharge_limit 0x46322000
    

    Home Assistant (please complete the following information):

    • Home Assistant Core Version: 2022.12.8
    • solaredge-modbus-multi Version: v2.2.8

    Home Assistant 2022.12.8 Supervisor 2022.12.1 Operating System 9.4 Frontend 20221213.1 - latest OS Alpine Linux v3.17 (RaspberryPi4)

    Additional context https://github.com/WillCodeForCats/solaredge-modbus-multi/blob/e6587867b73049a9f340adb6e2df8fe2902e4687/custom_components/solaredge_modbus_multi/number.py#L305

    (feel free to close this if you think it's a SolarEdge firmware issue)

    opened by rtlinux 0
  • Home Assistant Core 2023.1

    Home Assistant Core 2023.1

    Describe the current behavior Add more unit enums

    What should be updated or changed? UnitOfElectricCurrent enumerator replaces ELECTRIC_CURRENT_*** constants UnitOfElectricPotential enumerator replaces ELECTRIC_POTENTIAL_*** constants UnitOfFrequency enumerator replaces FREQUENCY_*** constants

    update 
    opened by WillCodeForCats 0
  • Release v2.2.6+ not compatible with Home Assistant core modbus integration

    Release v2.2.6+ not compatible with Home Assistant core modbus integration

    After Upgrading to v 2.2.6 with the new pymodbus version my HA internal Modbus integration is broken. Checking config says: 'Component error: modbus - No module named 'pymodbus.client.sync' and won't let me reboot. Also my manually configured Modbus sensors are unavailable.

    I'm on HA 2022.11.1. Rolling back to 2022.11.0 before the 2.2.6 upgrade didn't help.

    opened by alsFC 29
  • Updating state took X seconds

    Updating state took X seconds

    Logger: homeassistant.helpers.entity
    Source: helpers/entity.py:545
    First occurred: 4:37:46 AM (2 occurrences)
    Last logged: 7:31:35 AM
    
    Updating state for sensor.solaredge_m1_imported_a_kwh (<class 'custom_components.solaredge_modbus_multi.sensor.ACEnergy'>) took 0.658 seconds. Please report it to the custom integration author.
    Updating state for sensor.washing_machine_today_s_consumption (<class 'homeassistant.components.tplink.sensor.SmartPlugSensor'>) took 0.672 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tplink%22
    

    Originally posted by @purcell-lab in https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/137#issuecomment-1296406664

    opened by WillCodeForCats 0
Releases(v2.2.9-pre.1)
  • v2.2.9-pre.1(Dec 25, 2022)

    • Home assistant core 2022.11 by @WillCodeForCats in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/171

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.8...v2.2.9-pre.1

    Source code(tar.gz)
    Source code(zip)
  • v2.2.8(Dec 21, 2022)

    NOTE: This release uses a newer version of pymodbus that's not supported in Home Assistant core. If you are using the core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    This release adds a French translation along with some other minor updates.

    • Create fr.json by @stephanfo in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/213

    • Add integration_type to manifest by @WillCodeForCats in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/201

    • strings.json to match translations en.json by @WillCodeForCats in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/202

    • Allow command delay up to 60 seconds by @WillCodeForCats in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/203

    • Update translations by @WillCodeForCats in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/209

    • Python 3.11 StrEnum by @WillCodeForCats in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/204

    • ChangeConfDefaultFlag enum type by @WillCodeForCats in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/212

    • @stephanfo made their first contribution in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/213

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7...v2.2.8

    Source code(tar.gz)
    Source code(zip)
  • v2.2.8-pre.1(Dec 11, 2022)

    NOTE: This release uses a newer version of pymodbus that's not supported in Home Assistant core. If you are using the core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Allow command delay up to 60 seconds #203 and #209
    • Python 3.11 StrEnum #204
    • ChangeConfDefaultFlag enum type #212

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7...v2.2.8-pre.1

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7(Nov 26, 2022)

    NOTE: This release uses a newer version of pymodbus that's not supported in Home Assistant core. If you are using the core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    There's several new features in this release, but the major one is inverter controls: we now have site limit controls (export, production, external, and negative limit) and storage (battery) controls.

    We've also added a new sensor for Synergy MMPPT inverter events, an option to allow battery energy to reset to zero (needed for LG batteries), and bumped pymodbus to 3.0.2.

    New sponsors: @bertybuttface

    • Add support for StorEdge control by @mpredfearn #133
    • Updates and fixes for #133 by @WillCodeForCats in #158, #160, #173, #190
    • Inverter limit controls #179, #181, #188, #191
    • Add inverter command delay option #197
    • Option for battery energy to reset to zero #177, #198
    • Add Synergy MMPPT Events sensor #152, #182, #183
    • Advanced Power Control binary sensor #157
    • Refactor disconnect #165
    • Note depreciated sensors #166, #172
    • Bump pymodbus to 3.0.2 #170
    • Add battery power save mode #178
    • Clean up: #184, #196
    • Bug fixes: #195, #194, #193, #192

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.6...v2.2.7

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.11(Nov 19, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Add batt energy reset option to validation logic #198

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.10...v2.2.7-pre.11

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.10(Nov 16, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Battery energy in zero state behavior #195
    • Config flow cleanup #196
    • Add inverter command delay option #197

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.9...v2.2.7-pre.10

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.9(Nov 15, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Fix for inverters without limit control #193
    • Continue if dict key deletes fail #194

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.8...v2.2.7-pre.9

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.8(Nov 14, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    NOTE: Several power control entity names have been updated in this pre-release. You will need to re-select your power control options.

    • Power control UI updates #173
    • Update meter related names #181
    • Meter event bits as attribute #182
    • Pad mmppt events bit display attribute #183
    • Clean up debug logging #184
    • Updates for limit controls #188
    • Update limit control class names #191
    • Power control entity validation #190
    • Fix log message for site limit enabled #192

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.7...v2.2.7-pre.8

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.7(Nov 10, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Inverter limit controls #179
    • Add battery power save mode #178

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.5...v2.2.7-pre.7

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.5(Nov 8, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Option for battery energy to reset to zero #177
    • Log warning for depreciated sensors if enabled #172

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.4...v2.2.7-pre.5

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.4(Nov 5, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Bump pymodbus to 3.0.2 #170
    • Note depreciated sensors #166 (discussion #168)

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.3...v2.2.7-pre.4

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.3(Nov 5, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    What's Changed

    • Bump pymodbus to 3.0.1 #164
    • Refactor disconnect #165
    • Add Synergy MMPPT Events sensor #152
    • Add Advanced Power Control binary sensor #157

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.2...v2.2.7-pre.3

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.2(Nov 3, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Remove disconnect call after write #160

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.7-pre.1...v2.2.7-pre.2

    Source code(tar.gz)
    Source code(zip)
  • v2.2.7-pre.1(Nov 3, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    • Add support for StorEdge control by @mpredfearn #133
    • Updates and fixes for PR #133 by @WillCodeForCats in #158

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.6...v2.2.7-pre.1

    • @mpredfearn made their first contribution in https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/133
    Source code(tar.gz)
    Source code(zip)
  • v2.2.6(Nov 3, 2022)

    NOTE: This release will cause other core and custom integrations that rely on old versions of pymodbus to stop working. If you are using the Home Assistant core modbus integration the last compatible release is v2.2.5. Other modbus custom integrations will need to be removed. See issue #162 for updates.

    The big change for this release is we're now using pymodbus v3.0.0 to communicate with inverters.

    This release also allows battery energy import and export values to go backwards. Even though by definition they shouldn't, it's been reported by several users that they do anyway. If this happens a warning message will be logged. For more information see the known issues section in the wiki: WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues

    • Update to pymodbus v3.0.0 #143
    • Read advanced power control #138
    • keep_modbus_open as property #144
    • Coordinator timeout as property of hub #145
    • Bump limitusus/json-syntax-check from 1.0.3 to 2.0.0 #146
    • Allow battery energy to reset to zero #122
    • New config options for power control #147
    • Log warnings when advanced options are enabled #149
    • Qualify no response vs. no address #148
    • Remove battery enabled warning #151

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.5...v2.2.6

    Source code(tar.gz)
    Source code(zip)
  • v2.2.6-pre.4(Nov 1, 2022)

    • New config options for power control #147
    • Log warnings when advanced options are enabled #149
    • Qualify no response vs. no address #148
    • Remove battery enabled warning #151

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.6-pre.3...v2.2.6-pre.4

    Source code(tar.gz)
    Source code(zip)
  • v2.2.6-pre.3(Oct 24, 2022)

    • Update to pymodbus v3.0.0 #143

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.6-pre.2...v2.2.6-pre.3

    Source code(tar.gz)
    Source code(zip)
  • v2.2.6-pre.2(Oct 24, 2022)

    • Allow battery energy to reset to zero #122
    • Coordinator timeout as property of hub #145
    • Bump limitusus/json-syntax-check from 1.0.3 to 2.0.0 #146

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.6-pre.1...v2.2.6-pre.2

    Source code(tar.gz)
    Source code(zip)
  • v2.2.6-pre.1(Oct 20, 2022)

    • Read advanced power control #138
    • keep_modbus_open as property #144

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.5...v2.2.6-pre.1

    Source code(tar.gz)
    Source code(zip)
  • v2.2.5(Oct 20, 2022)

    This release contains new battery data validation and three new power control sensors: RRCR Status, Active Power Limit, and CosPhi. We've also updated setup errors to return user friendly messages, changed our entity naming to follow the latest Home Assistant requirements, and changed to our own Python lint actions that use current versions of isort, black, and flake8.

    • Global power control sensors #117
    • Increase coordinator timeout to 30 seconds #142
    • Update battery data validations in #125, #128, #129, and #130
    • Support new entity naming practices #121
    • Differentiate no response vs. not sunspec modbus #126
    • Change python code quality action #135

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.4...v2.2.5

    Source code(tar.gz)
    Source code(zip)
  • v2.2.5-pre.6(Oct 13, 2022)

    This release adds three new power control related sensors: RRCR Status, Active Power Limit, and CosPhi.

    • Global power control sensors #117
    • Change python code quality action #135

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.5-pre.5...v2.2.5-pre.6

    Source code(tar.gz)
    Source code(zip)
  • v2.2.5-pre.5(Oct 12, 2022)

    • Missed one hex() function #130
    • Differentiate no response vs. not sunspec modbus #126

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.5-pre.4...v2.2.5-pre.5

    Source code(tar.gz)
    Source code(zip)
  • v2.2.5-pre.4(Oct 10, 2022)

    • Checks using float_to_hex should be strings #129
    • Battery device attributes should be non-zero #129

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.5-pre.3...v2.2.5-pre.4

    Source code(tar.gz)
    Source code(zip)
  • v2.2.5-pre.3(Oct 9, 2022)

    Release v2.2.5-pre.2 contains loading errors fixed in PR #128.

    • Fix B_RatedEnergy reference #128

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.5-pre.2...v2.2.5-pre.3

    Source code(tar.gz)
    Source code(zip)
  • v2.2.5-pre.2(Oct 8, 2022)

    • Update battery data validations #125
    • Support new entity naming practices #121

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.5-pre.1...v2.2.5-pre.2

    Source code(tar.gz)
    Source code(zip)
  • v2.2.5-pre.1(Oct 7, 2022)

  • v2.2.4(Oct 7, 2022)

    This is an optional release (unless you are filing a bug report for batteries then it's required). It will provide a user friendly error if the inverter can't be reached during startup or after adding an inverter config that's invalid, and provide more useful debug logs for battery values.

    • Qualify read exceptions during setup #116
    • Battery log float as hex #124

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.3...v2.2.4

    Source code(tar.gz)
    Source code(zip)
  • v2.2.3(Sep 28, 2022)

    This release is quality of life updates. Extra sensors for three phase systems will be disabled by default in single or split phase systems when adding the integration, fixes cosmetic issues #100 and #101, and changed some constants to match practices in Home Assistant core. SolarEdge Synergy inverters will now have MMPPT device attributes in the device entity.

    You will see extra/empty meter and battery devices in the device list after upgrading to this version due to PR #103: delete these extra devices using the "delete" button in the Home Assistant UI. This is a cosmetic issue which does not affect function (do not open issue reports).

    • Battery state of energy device class #110
    • Check keep_modbus_open value in coordinator init #102 (@spali)
    • Use uid_base for device identifier #103
    • Support removing devices from UI #104
    • Sensor registry defaults for single vs. three phase #93
    • Create IntEnum classes for SunSpec #99
    • Add integration config debug logging #107
    • Don't add sunspec device attrs if none for device #108
    • Add synergy unit information to device attributes #109
    • Battery SOH icon #112
    • Bump actions/checkout from 1 to 3 #111

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.2...v2.2.3

    Source code(tar.gz)
    Source code(zip)
  • v2.2.3-pre.5(Sep 25, 2022)

    • Battery state of energy device class #110

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.3-pre.4...v2.2.3-pre.5

    Source code(tar.gz)
    Source code(zip)
  • v2.2.3-pre.4(Sep 23, 2022)

    • Don't add sunspec device attrs if none for device #108
    • Add synergy unit information to device attributes #109

    Full Changelog: https://github.com/WillCodeForCats/solaredge-modbus-multi/compare/v2.2.3-pre.3...v2.2.3-pre.4

    Source code(tar.gz)
    Source code(zip)
Owner
Seth
Seth
Python code written to utilize the Korlan usb2can hardware to send and receive data over the can-bus on a 2008 Nissan 350z

nissan_ecu_hacking Python code written to utilize the Korlan usb2can hardware to send and receive data over the can-bus on a 2008 Nissan 350z My goal

Liam Goss 11 Sep 24, 2022
A script and GUI for controlling stepper motors from an arduino

A script and GUI for controlling stepper motors from an arduino (nema 23 in my case but should work for others in general)

Pip 2 Aug 01, 2022
Ingeniamotion is a library that works over ingenialink and aims to simplify the interaction with Ingenia's drives.

Ingeniamotion Ingeniamotion is a library that works over ingenialink and aims to simplify the interaction with Ingenia's drives. Requirements Python 3

Ingenia Motion Control 7 Dec 15, 2022
A PYTHON Library for Controlling Motors using SOLO Motor Controllers with RASPBERRY PI, Linux, windows, and more!

A PYTHON Library for Controlling Motors using SOLO Motor Controllers with RASPBERRY PI, Linux, windows, and more!

SOLO Motor Controllers 3 Apr 29, 2022
This repo uses a stereo camera and gray-code-based structured light to realize dense 3D reconstruction.

Structured-light-stereo This repo uses a stereo camera and gray-code-based structured light to realize dense 3D reconstruction. . How to use: STEP 1:

FEI 20 Dec 31, 2022
A simple Picobot project implemented in Python

Python-Picobot A simple Picobot project implemented in Python About Explanation This is my first programming project. Picobot use rules.txt file which

Shayan Shiravani 0 Apr 03, 2022
A Macropad using the Raspberry Pi Pico, programmed with CircuitPython.

A Macropad using the Raspberry Pi Pico, programmed with CircuitPython.

15 Oct 14, 2022
Examples to accompany the

Examples to accompany the "Raspberry Pi Pico Python SDK" book published by Raspberry Pi Trading, which forms part of the technical documentation in support of Raspberry Pi Pico and the MicroPython po

Raspberry Pi 589 Jan 08, 2023
Small Robot, with LIDAR and DepthCamera. Using ROS for Maping and Navigation

πŸ€– RoboCop πŸ€– Small Robot, with LIDAR and DepthCamera. Using ROS for Maping and Navigation Made by Clemente Donoso, πŸ“ Chile πŸ‡¨πŸ‡± RoboCop Lateral Fron

Clemente Donoso Krauss 2 Jan 04, 2022
Setup DevTerm to be a cool non-GUI device

DevTerm hobby project I bought this amazing device: DevTerm A-0604. It has a beefy ARM processor, runs a custom version of Armbian, embraces Open Sour

Alex Shteinikov 9 Nov 17, 2022
Intel Realsense t265 into Unreal Engine

t265_UE Intel Realsense t265 into Unreal Engine. Windows only, and Livelink plugin is 4.26.2 only at the moment. Might recompile it for different vers

Bjarke Aagaard 30 Jan 02, 2023
The goal of this project is for anyone with an old printer to be able to double-sided printing.

Welcome to PDF-double-side! Hi! I'm 15. I have a old printer so I can't print double-sided outs. The goal of this project is for anyone with an old pr

DejaVu 4 Dec 28, 2021
ArduinoWaterHeaterIOT - IoT Probe of a solar PV water heating system - Arduino, Python, MQTT, MySQL

ArduinoWaterHeaterIOT IoT Probe of a solar PV water heating system - Arduino, Raspberry Pi, Python, MQTT, MySQL The Arduino sends the AC and DC watts

Jacques Fourie 1 Jan 11, 2022
Make your MacOS keyboard brightness fade in and out

Make your MacOS keyboard brightness fade in and out. (It's working depends on the Kbrightness file, which only works for 2015 Macs, so this will only work on 2015 Macs.)

1 Dec 16, 2021
Modi2-firmware-updater - MODI+ Firmware Updater With Python

MODI+ Firmware Updater μ‹€ν–‰ μ€€λΉ„ python3(파이썬3.9 ν˜Ήμ€ κ·Έ μ΄μƒμ˜ 버전)λ₯Ό 컴퓨터에 μ„€μΉ˜ python3 -m pip

LUXROBO 1 Feb 04, 2022
Ha-rpi gpio - Home Assistant Raspberry Pi GPIO Integration

Home Assistant Raspberry Pi GPIO custom integration This is a spin-off from the

Shay Levy 98 Dec 24, 2022
2D waypoints will be predefined in ROS based robots to navigate to the destination avoiding obstacles.

A number of 2D waypoints will be predefined in ROS based robots to navigate to the destination avoiding obstacles.

Arghya Chatterjee 5 Nov 05, 2022
Play music on Raspberry Pi Pico Without CPU involvement

MicroPython_PIO_Music_DMA Play music on Raspberry Pi Pico Without CPU involvement This is based on PIOBeep (https://github.com/benevpi/pico_pio_buzz)

3 Nov 27, 2022
A Python script to monitor the latest block on an LCD.

PiHole-Monitoring A Python script to monitor the latest block on a lcd display. The first number represents the dns queries from the last 24h, the sec

Maxi 4 Dec 05, 2022
Sleep As Android integration for Home Assistant

Sleep As Android custom integration This integration will allow you to get events from your SleepAsAndroid application in a form of the sensor states

Igor 84 Dec 30, 2022