search

mkaiser / Sungrow-SHx-Inverter-Modbus-Home-Assistant

Sungrow SH Integration for Home Assistant for SH3K6, SH4K6, SH5K-20, SH5K-V13, SH3K6-30, SH4K6-30, SH5K-30, SH3.RS, SH3.6RS, SH4.0RS, SH5.0RS, SH6.0RS, SH5.0RT, SH6.0RT, SH8.0RT, SH10RT, SH5.0RT-20, SH6.0RT-20, SH8.0RT-20, SH10RT-20, SH5.0RT-V112, SH6.0RT-V112, SH8.0RT-V112, SH10RT-V112, SH5.0RT-V122, SH6.0RT-V122, SH8.0RT-V122, SH10RT-V122, SH4.6R
304 stars 79 forks source link

retries` configuration key is being removed #234

Closed JensPohl69 closed 5 months ago

JensPohl69 commented 5 months ago

Describe the bug A clear and concise description of what the bug is.

Your Sungrow inverter:

Home Assistant : Core 2024.1.0 Supervisor 2023.12.0 Operating System 11.2 Frontend 20240103.3

modbus_sungrow.yaml:

Inverter Firmware Status:

Since 4 days i get the following warning from the system. No update by now. 1 repair retries configuration key is being removed This stops working in version 2024.7.0. Please address before upgrading. Please remove the retries key from the modbus entry in your configuration.yaml file and restart Home Assistant to fix this issue. The maximum number of retries is now fixed to 3.

Result by checking the configuration in the developer tools

Configuration warnings Invalid config for 'scene' at configuration.yaml, line 15: 'sungrow_modbus_host_ip' is an invalid option for 'scene', check: states->0->sungrow_modbus_host_ip Invalid config for 'scene' at configuration.yaml, line 15: 'sungrow_modbus_port' is an invalid option for 'scene', check: states->0->sungrow_modbus_port Invalid config for 'scene' at configuration.yaml, line 15: 'sungrow_modbus_slave' is an invalid option for 'scene', check: states->0->sungrow_modbus_slave Invalid config for 'scene' at configuration.yaml, line 15: required key 'entities' not provided Invalid config for 'scene' at configuration.yaml, line 15: required key 'name' not provided

In line 15 of the configuration.yaml you find

scene: !include scenes.yaml This is the line you recomend in your manual The data exchange with the sungrow converter is still running fine. I'm afraid when I do the pending upgrade it won't work anymore.

Any advice for me?

Thanks in advanced

Jens

Louisbertelsmann commented 5 months ago

Update to the newest yaml.

JensPohl69 commented 5 months ago

Got it. Thanks

Von: Louis Bertelsmann @. Gesendet: Montag, 8. Januar 2024 20:20 An: mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant @.> Cc: JensPohl69 @.>; Author @.> Betreff: Re: [mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant] retries` configuration key is being removed (Issue #234)

Update to the newest yaml.

— Reply to this email directly, view it on GitHub https://github.com/mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant/issues/234#issuecomment-1881685082 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A6HSDZ7KWWIOFGJEMTRYVXLYNRBFFAVCNFSM6AAAAABBR4DSZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRGY4DKMBYGI . You are receiving this because you authored the thread. https://github.com/notifications/beacon/A6HSDZ7KKSTB2X72DXTGKQ3YNRBFFA5CNFSM6AAAAABBR4DSZ6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTQFA6FU.gif Message ID: @. @.> >

JensPohl69 commented 5 months ago

Thanks a lot and I got it and reworked the yaml. Was easy.

But in the developer tools after check configuration the following warnigs are still exisiting.

Invalid config for 'scene' at configuration.yaml, line 15: 'sungrow_modbus_host_ip' is an invalid option for 'scene', check: states->0->sungrow_modbus_host_ip Invalid config for 'scene' at configuration.yaml, line 15: 'sungrow_modbus_port' is an invalid option for 'scene', check: states->0->sungrow_modbus_port Invalid config for 'scene' at configuration.yaml, line 15: 'sungrow_modbus_slave' is an invalid option for 'scene', check: states->0->sungrow_modbus_slave Invalid config for 'scene' at configuration.yaml, line 15: required key 'entities' not provided Invalid config for 'scene' at configuration.yaml, line 15: required key 'name' not provided

Do you have any ideas what else I can do? I suspect this warning is older.

Thanks Jens

Louisbertelsmann commented 5 months ago

There’s something wrong with your installation. THis integration doesn’t use the scene.yaml.

JensPohl69 commented 5 months ago

Hi, I have removed the entries from Sense.yaml and restarted HA. The Integration runs as ususal and the warning is gone. Many thanks for your support. Kind regards JensVon meinem iPhone gesendetAm 09.01.2024 um 12:09 schrieb Louis Bertelsmann @.***>: There’s something wrong with your installation. THis integration doesn’t use the scene.yaml.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Louisbertelsmann commented 5 months ago

So, I can close this issue.

JensPohl69 commented 5 months ago

Yes 🙌 Von meinem iPhone gesendetAm 09.01.2024 um 14:46 schrieb Louis Bertelsmann @.***>: So, I can close this issue.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>