No Connection with SMA Integration / SMA Integration Login failed

[Jogiarea]

The problem

Hello
Have a problem with the SMA integration, I can not log in.
I have already gone through all log invariants, always "Unexpected error".
Have also already changed the system password without success, always brings errors.

My installation:

Modbus is on

Plant location DE
Both inverters have a static IP
Speedwire encryption is off
Inverter with the latest firmware

Have tried to log in for half a year again and again but without success

Do someone have any Idea what I ve done wrong?

With Modbus i can connect to the Inverter but not to the Battery-Inverter

What version of Home Assistant Core has the issue?

2022.3.2 and other

What was the last working version of Home Assistant Core?

2022.3.2

What type of installation are you running?

Home Assistant Container

Integration causing the issue

SMA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/sma/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant]

sma documentation
sma source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @kellerza, @rklomp, mind taking a look at this issue as it has been labeled with an integration (sma) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[rklomp]

The SMA integration does not support modbus, only web interface.

[Jogiarea]

Sorry yes I know meant to say that I used the modbus to test the connection, i.e. a connection is there.
Do I what beachtren must be activated for the web interface something?

[rklomp]

I've never tested of heard of anyone using the sunny island with this plugin. Maybe this device is running different code for webconnect.

Can you share debug logging of the SMA integration and pysma?

Turn on debug in the configuration.yaml and than restart HA.

logger:
  default: info
  logs:
    homeassistant.components.sma: debug
    pysma: debug

Make sure you remove credentials etc. from the logs.

[labros-zotos]

Did you find a solution? I am trying to add the integration but I get "Failed to connect".

The only thing I get on the log is
2022-03-13 23:39:03 DEBUG (MainThread) [pysma] Sending POST request to /dyn/login.json: {'data': '{"right": "usr", "pass": "secret"}', 'headers': {'content-type': 'application/json'}}

[Jogiarea]

Hi all,
Sorry for late answer, had any to do This Weekend

Here are my log Error handling request:

Logger: aiohttp.server
Source: core.py:1043
First occurred: 05:48:09 (2 occurrences)
Last logged: 05:48:18

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 79, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 219, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 137, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/api/__init__.py", line 223, in post
    hass.states.async_set(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1363, in async_set
    state = State(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1043, in __init__
    raise InvalidEntityFormatError(
homeassistant.exceptions.InvalidEntityFormatError: Invalid entity id encountered: sma. Format should be <domain>.<object_id>

And Unexpected exception:

Logger: homeassistant.components.sma.config_flow
Source: components/sma/config_flow.py:33
Integration: SMA Solar (documentation, issues)
First occurred: 05:52:01 (3 occurrences)
Last logged: 05:53:03

Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/sma/config_flow.py", line 68, in async_step_user
    device_info = await validate_input(self.hass, user_input)
  File "/usr/src/homeassistant/homeassistant/components/sma/config_flow.py", line 33, in validate_input
    await sma.new_session()
  File "/usr/local/lib/python3.9/site-packages/pysma/__init__.py", line 247, in new_session
    body = await self._post_json(URL_LOGIN, self._new_session_data)
  File "/usr/local/lib/python3.9/site-packages/pysma/__init__.py", line 177, in _post_json
    return await self._request_json(hdrs.METH_POST, url, **params)
  File "/usr/local/lib/python3.9/site-packages/pysma/__init__.py", line 118, in _request_json
    async with self._aio_session.request(
  File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 1138, in __aenter__
    self._resp = await self._coro
  File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 634, in _request
    break
  File "/usr/local/lib/python3.9/site-packages/aiohttp/helpers.py", line 721, in __exit__
    raise asyncio.TimeoutError from None
asyncio.exceptions.TimeoutError

I dont know what this say to me

[Jogiarea]

One More Information

:

[CyborgNL]

Same for me. I have tried all combination. Still got the message: Unexpected Error. With an other app (SunSpec) it works but I prefer to use the SMA app.

[skyluker]

Same for me. I have tried all combination. Still got the message: Unexpected Error. With an other app (SunSpec) it works but I prefer to use the SMA app.

it is undergoing fix: kellerza/pysma#98

[kellerza]

The fix addresses the TimeoutError - #68999

My suspicion is that TimeoutError typically occur when you are connected via wifi.

But if your inverter has no support for the webconnect protocol it will still timeout, but the HA setup will just gracefully retry forever.

As @rklomp mentioned no-one has reported a working sunny island, so very likely it is NOT webconnect based. The first test is always, what can you access/see when you point your own browser to the inverter…

[ghost]

@Jogiarea, are you redirected to the https version when you access it in the browser? Then check the first checkbox (uses an SSL certificate), but not the second one (verify SSL certificate), like this:

[CyborgNL]

I have updated Home Assistant to: 2022-4.0
Then I try to add SMA I get the the message that no connection can be made.

[rklomp]

I have updated Home Assistant to: 2022-4.0
Then I try to add SMA I get the the message that no connection can be made.

What kind of device are you trying to connect to?

[CyborgNL]

I try to connect to my SMA Sunny boy 4000TL. I know the passwords for user and installer.

[kellerza]

Do you have an external webconnect on the 4000TL?

From the datasheet the 4000TL only supports RS485 and bluetooth

Can you please post a screenshot of Chrome when you open the page at http:// or https://?

[skyluker]

I have a SMA Sunny Tripower 6.0 | SMA STP6.0-3AV-40] and it doesn't work one the newest 2022.04 core. Although there was a time (January '22 I think) it worked.

[CyborgNL]

Do you have an external webconnect on the 4000TL?

From the datasheet the 4000TL only supports RS485 and bluetooth

Can you please post a screenshot of Chrome when you open the page at http:// or https://?

@kellerza The web connect module is installed on the 4000TL-21
I can retrieve data when using SunSpec in HomeAssistant. Is does not work when using the SMA app.

[asimar75]

Same issue for my Sunnyboy 3.0, in the integration description say is for SMA(US), I’m in Europe, wondering if it is a geographic issue.

[jimverte]

As my old Home Assistant instence is crashed i'm building a new Home Assistant. Currently i'm facing the same issue as not able to connect to the webconnect.

does anybody still have the older way by adding the code in the configuration.yaml file ourself

than we could try that way to get connected to the sma webconnect. I have a sunnyboy 3.0 @ home

[rklomp]

I am using a sunnyboy 3.6, so I assume a sb 3.0 should also work.

Are you using correct settings to connect?

[jimverte]

Succes now bu using the following settings

USE SSL Certification

Unselect Validate SSL Certification

Use the Installer account and his password

[CyborgNL]

Does anybody know if this will work with my Sunnyboy 4000TL-21?
I make use of the Webconnect.
Always the same error: Cannot connect. I have the username and password for user and installer.

What is the minimum requierment to the the SMA app in HA? It works with SunPac but not with the SMA app in HA.

.

[Jogiarea]

Ive tested all but nothing works;-(

[xzaz]

I'm having the same problem with Sunny boy 1.5. It can't just connect. I had it working with old versions of HA though.

[rklomp]

For all people having issues connecting. Please share more details about your installation:

• SMA Device details:
  • Hardware Type
  • Firmware version
  • Webconnect Software version (See SMA GUI -> Device parameters -> External Communication -> Webconnect)
  • URL used to connect to SMA GUI in browser
• Home Assistant Details:
  • Version currently used
  • If working with old version, the last version it was still working
  • Screenshot of your settings used in HA.
  • Debug logging of HA when trying to connect.

To get debug logging, turn on debug in the configuration.yaml and than restart HA.

logger:
  default: info
  logs:
    homeassistant.components.sma: debug
    pysma: debug

[skyluker]

For all people having issues connecting. Please share more details about your installation:

• SMA Device details:

  • Hardware Type
  • Firmware version
  • Webconnect Software version (See SMA GUI -> Device parameters -> External Communication -> Webconnect)
  • URL used to connect to SMA GUI in browser

• Home Assistant Details:

  • Version currently used
  • If working with old version, the last version it was still working
  • Screenshot of your settings used in HA.
  • Debug logging of HA when trying to connect.

To get debug logging, turn on debug in the configuration.yaml and than restart HA.

logger:
  default: info
  logs:
    homeassistant.components.sma: debug
    pysma: debug

SUNNY TRIPOWER 6.0 - STP6.0-3AV-40 370
firmware: 3.11.3.R
Webconnect ver: 1.5.2.R
https://192.168.0.108/

Home Assistant 2022.4.7

LOG from Core:
2022-05-17 14:42:38 DEBUG (MainThread) [pysma] Sending POST request to /dyn/login.json: {'data': '{"right": "usr", "pass": "***"}', 'headers': {'content-type': 'application/json'}}

When I try to add integration:

where should I take the screenshot with HA setting?

[xzaz]

Do we need more information? I got the same as above with the same message:
2022-06-20 19:44:55 DEBUG (MainThread) [pysma] Sending POST request to /dyn/login.json: {'data': '{"right": "usr", "pass": "pass"}', 'headers': {'content-type': 'application/json'}}

Edit:
I'v checked it in Postman and it goes correct:

First: http://192.168.178.14/dyn/login.json with content JSON {"pass" : "pass", "right" : "usr"}
Second: http://192.168.178.14/dyn/getValues.json?sid=nBak2UwgQaogwUgh with content {"destDev":[],"keys":["6400_00260100","6400_00262200","6100_40263F00"]} here 6100_40263F00 is current Watt output.

So it does not continue connecting:
_LOGGER.debug("Sending %s request to %s: %s", method, url, kwargs)
https://github.com/kellerza/pysma/blob/e38cf758912fabc2ad4f75ab5df827b3c06a5fab/pysma/__init__.py#L114

Fixed
I fixed it with some help from Tweakers.net. I messed up with the port. It's just port 80, so http. Put my forwarding the correct way and tada; connection.

[cedricdelecole]

Hi desperate guys from the last days.

Use a password not longer than 12 characters

Have you made sure to use a password not longer than 12 characters? The crazy things is that I had initially created a password of 20 characters! SMA accepted this in the login registration screen (html front-end) and truncated it by itself to 12 characters without making the user aware of it.

I use KeePass for managing all my passwords (creation and storage of passwords). Guess what happens: copy&paste 20 characters from KeePass into the SMA front-end login screen => successful login, because SMA uses again the first 12 characters only - and you keep believing, the 20-character password is fine.

Proof: I used the first 12 characters of the original password in the SMA Integration => successfully logged in! This worked for user and installer, with and without SSL etc.

Shame on SMA for this "silent" truncation of the password. Absolutely bad programming style.

This is correct, I remember that issue with password length on SMA ... but my passwords are less than 12 characters, and I have tried different combinations numerical / special characters / up and lowercases etc ....

... no luck
;-(

[garyr2w]

Having same login issues. In my case I think it might be due to the ancient Sunny Webbox I have (circa 2012). I tried sending the contents of the POST from pysma shown in the log directly to the Webbox through curl. Using the "dyn/login.json" URL does not work. Using the URL that the Webbox web page connection uses (culture/login) does seem to work. Not sure if this helps anybody but thought I'd post it just in case. Example output is below (with the password changed to xxxxxxxxx).

From the log:

2023-06-13 16:57:04.185 DEBUG (MainThread) [pysma] Sending POST request to /dyn/login.json: {'data': '{"right": "istl", "pass": "xxxxxxxxx"}', 'headers': {'content-type': 'application/json'}}

Curl using dyn/login.json:

[core-ssh ~]$ curl -v -i -d '{"right": "istl", "pass": "xxxxxxxxx"}' http://192.168.1.254/dyn/login.json

• Trying 192.168.1.254:80...
• Connected to 192.168.1.254 (192.168.1.254) port 80 (#0)

POST /dyn/login.json HTTP/1.1
Host: 192.168.1.254
User-Agent: curl/8.0.1
Accept: /
Content-Length: 41
Content-Type: application/x-www-form-urlencoded

• Empty reply from server
• Closing connection 0
  curl: (52) Empty reply from server

Curl using culture/login:

[core-ssh ~]$ curl -v -i -d '{"right": "istl", "pass": "xxxxxxxxx"}' http://192.168.1.254/culture/login

• Trying 192.168.1.254:80...
• Connected to 192.168.1.254 (192.168.1.254) port 80 (#0)

POST /culture/login HTTP/1.1
Host: 192.168.1.254
User-Agent: curl/8.0.1
Accept: /
Content-Length: 41
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 200
HTTP/1.1 200
< Server: WebBox-20
Server: WebBox-20

<?xml version="1.0"?><?xml-stylesheet type='text/xsl' href='style_en.xslt'?><Page xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd=http://www.w3.org/2001/XMLSchema deviceKey="109:155010870:p" languageCode="en" name="Login" xsi:noNamespaceSchemaLocation="PageDefinition.xsd" isDefUserPwd="false" isDefInstallerPwd="false" isUser="false"><Content deviceKey="109:155010870:p"><Element xsi:type="Login" deviceKey="109:155010870:p"><Language displayType="StateTags" obsolete="true" itemType="Value" name="Language of the user interface" address="6800837880" parameterJobStatus="OK" tagName="CntrySettings.Lang" timeStamp="11/10/2011 04:06:39 AM"><Items><XmlItem itemType="SubValue" name="Deutsch" tagName="LangDE"><Items /><Value>0</Value></XmlItem><XmlItem itemType="SubValue" name="English" tagName="LangEN"><Items />
etc.
This seems to indicate a successful login. If I'm already logged in through a browser, it returns an error here saying already logged in.

[garyr2w]

FYI for anyone else with a WebBox. This integration seems to work: https://github.com/jpcornil-git/HA-sma

[cedricdelecole]

I had the exact same issue as described here ... here is how I solved it (not on purpose) .... I had installed Ha couple of weeks ago, connected to the SMA SB5.0 to test my user / installer, then tried to integrate it using the HA integration for SMA ... FAILED as a lot of people are experiencing below ...

My Synology crashed, so I had to reinstall the complete HA couple of days ago, and I directly tried to integrate the SMA SB 5.0 **and it directly worked **!!****, so without having tested the password on the SMA web interface first.

I ASSUME the issue is that if you connect to the SMA web interface first, the connection somehow stays active (even if you log off), which makes HA integration unable to log in the SMA inverter web interface at his turn.
It looks to me like only 1 connection at the time is allowed ...

Anycase, it is working for me now ...

[gb1320]

Another success story, also on the fresh HA install, worked like a charm on the first try:
Hardware Type SB3.8-1SP-US-40
Firmware version 2.4.92.R

Webconnect Software version (See SMA GUI -> Device parameters -> External Communication -> Webconnect) there's none visible, only word 'Activated' The next part has couple versions:
Main Processor: 2.3.41.R
Communication Assembly: 2.4.91.R

URL used to connect to SMA GUI in browser: https://sma1990024609/ Inverter is connected over Ethernet to LAN. LAN DHCP server assigned it that host name. The same host name sma1990024609 worked in HA integration.

Home Assistant Details: HA Core only + MariaDB + Mosquitto MQTT running on Ubuntu 18.04.5 LTS
Version currently used: 2023.6.3 (just installed few days ago) This is the only integration I added there so far.
Browser to open inverter UI or HA UI is Microsoft Edge Version 114.0.1823.58 (Official build) (64-bit) running on a separate computer, Windows 10 VM, wired Ethernet everywhere.

[monester]

I have this https://www.sma.de/en/products/monitoring-control/webconnect module installed in my inverter Sunny Boy 5000TL-21 but this module don't expose any local ports.
It is possible to register this module on portal via https://www.sunnyportal.com/register with PIC and RID values which are coming with the module.
You can monitor on performance via https://www.sunnyportal.com .
Sma module for home assistant working only with local access so if module don't expose local interface there is no way to connect.
In #67953 (comment) there is mentioned that you should enable local access somehow but I wasn't been able to find "External Communication -> Webconnect" anywhere.

Webconnect Software version (See SMA GUI -> Device parameters -> External Communication -> Webconnect) there's none visible, only word 'Activated'

[JunoGregoire]

I'm having this issue too, with the newest version of HA. My password is 12 chars long. I've logged in directly into my SMA inverter and that works. I used to have an RPi on which this worked perfectly, though that was about a year ago.
I'm running HA on a Proxmox VM now. Could that be the issue?

[gb1320]

module installed in my inverter Sunny Boy 5000TL-21 but this module don't expose any local ports.

If you can see inverter's UI and its production numbers over LAN in the browser then it exposes at least ports 80 / 443. I believe HA integration uses the very same connection. My inverter is newer model so there's possibility that SMA changed Web API methods for this series and HA cannot 'understand' the previous version. I think post #67953 (comment) above provides a method how to check login / connectivity outside HA.

[JunoGregoire]

I'm having this issue too, with the newest version of HA. My password is 12 chars long. I've logged in directly into my SMA inverter and that works. I used to have an RPi on which this worked perfectly, though that was about a year ago. I'm running HA on a Proxmox VM now. Could that be the issue?

An update: I just tried pinging my SMA inverter, which works perfectly. So HA can definitely talk to the inverter.

EIDT: just tried again with the first checkbox enables and the 2nd disabled. Logged in in a second.

[gravidigit]

Hi all, same problem here. No login is proberly. I have tried all combies. user or installer, with and withoud ssl checkboxes. Login on the webinterface with my user account is no problem. have a user here any idea? thanks a lot!

HomeAssistant:
Home Assistant 2023.8.4 Supervisor 2023.08.1 Operating System 10.5
SMA:
SMA X12 Wechelrichter / Sunny Tripower X 12
Firmware-Version
03.02.08.R

Home Assistant Log:
Logger: pysma
Source: components/sma/config_flow.py:33
First occurred: 29. August 2023 um 19:58:27 (12 occurrences)
Last logged: 15:39:21

Request to /dyn/login.json did not return a valid json.
Could not start session: Session ID expected [result.sid]

[Carsten90]

login problem solved!!!

at first you have to use the sunny explorer and set in the inverter and battery inverter the external communication web connect to on.
Now you dont use the IP in the sunny explorer, go to your fritzbox or router and search for the actual network ip.
Use the IP adress set the first hook with the ssl and uncheck the second hook!!! thats priority!
now click on installer and use the sunny explorer password..

works like a charme!

also you have to do it for both inverters if you habe two like me

[TheChatty]

I also had this problem (SUNNY TRIPOWER 6.0 SE on firmware 3.4.16.R).

Important like told 1000x: [x] Uses an SSL certificate, [ ] Verify SSL certificate.

What's strange: example.py https://sma301560xxxxx.local/ user mysecretpw is working (from here).

[juite]

Hi everybody,

Used the intergration always without problems. Since 2 weeks entities not available anymore. Tried to reinstall the integration but now login issues. Tried al kind of combinations nothing works anymore.

HA version 10.5
SMA STP6.0-3AV-40 Firmware version: 4.0.8.R

Any ideas?

[rozsap]

I also have the problem that I cannot log in to Sonny Home Manager 2.0 on the WebUI interface. Thus, the Home Assistant cannot set the SMA integration either.
I added the device on Sunny Portal, it works great. I know the IP address, you can ping it, and the legal_notices.txt page comes up. Port scanner says ports 80 and 4712 are open. I can't access the device on either of them.
What might be the problem?

[nelsongraca]

Having this error as well, it was working a few days ago
DEBUG (MainThread) [pysma] Sending POST request to /dyn/login.json: {'data': '{"right": "istl", "pass": "SECRET"}', 'headers': {'content-type': 'application/json'}}

[heereb]

hi, this is how I fixed the error:

• apparently the HA to SMA is done via MODBUS
• this function was not activeted on my SunnyBoy 3.0 -> after activating the MODBUS, the communication with HA worked directly.
  So how to activate:
• log-on to the SMA wifi of your device (start with SMA###), after connecting to the SMA wifi go to the standard IP adres for the web interface (in my case: 192.168.12.3)
• in the webinterface is logged in with the installer user (you easily reset the password with the WPA key which can be found on the inverter)
• move to Device settings and the to Communications -> you have 3 tabs: WLAN, LAN and MODBUS
• go to the MODBUS and select "yes" to activate it, I did not change any settings...press save.
• then logout
• you can also go to this website: https://www.sma-benelux.com/kenniscentrum/tech-tips-monitoring/sma-omvormers-niko-home-control-verbinden

[Sakamoto2215]

I have the same problem, not being able to connect to the sma integration.
No matter what I try, I get invalid authentication.
I tried user and installer. I even created a new installer profile and changed the PW, didnt work either.

What bothers me is when I log into my inverter using the browser / IP I have to log in with a username and PW

The HA integration never asks for an username? Is that the problem?
I think my inverter runs in the new ennexOS.

Can someone with a working HA connection confirm their login to the inverter looks the same?

Cheers
Sakamoto

[gb1320]

That login page doesn't look like inverter's login. Please make sure you're logging into inverter itself, not SunnyPortal site. My inverter page looks like this: From: Sakamoto2215 ***@***.***> Sent: Tuesday, December 26, 2023 1:19 PM To: home-assistant/core ***@***.***> Cc: gb1320 ***@***.***>; Comment ***@***.***> Subject: Re: [home-assistant/core] No Connection with SMA Integration / SMA Integration Login failed (Issue #67953) I have the same problem, not being able to connect to the sma integration. No matter what I try, I get invalid authentication. I tried user and installer. I even created a new installer profile and changed the PW, didnt work either. What bothers me is when I log into my inverter using the browser / IP I have to log in with a username and PW The HA integration never asks for an username? Is that the problem? I think my inverter runs in the new ennexOS. Can someone with a working HA connection confirm their login to the inverter looks the same? grafik.png (view on web) <https://github.com/home-assistant/core/assets/154930231/61bab3d9-29f0-426f- 8232-ad744774c5fd> Cheers Sakamoto - Reply to this email directly, view it on GitHub <#67953 (comment)

, or unsubscribe

<https://github.com/notifications/unsubscribe-auth/AMWH7HEOORY4O7HDB42OX4DYL M5LDAVCNFSM5QMX7ZEKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWHE3TONRYG44Q> . You are receiving this because you commented. <https://github.com/notifications/beacon/AMWH7HFL5UJDQAOU6L76MOLYLM5LDA5CNFS M5QMX7ZEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGON5ZIP3Y .gif> Message ID: ***@***.*** ***@***.***> >

[rklomp]

Maybe a new tripower X device? #90313

[Sakamoto2215]

Thanks,

I just found out that the new SMA TRIPOWER X Inverter run on a completely new system.
HA Integrations does not work on TRIPOWER X.

[Batum78]

It's working with a Sunny Boy 5.0.
Had to check "use an ssl certificate"

[TQRT]

I was having the same issue trying to connect a SMA Energy Meter, tinkering with Home Assistant (first time user) I ended up in

/homeassistant/home-assistant.log

there I saw the next message:

2024-01-10 17:45:26.341 ERROR (MainThread) [pysma] Could not start session: Session ID expected [result.sid]
2024-01-10 17:45:34.838 WARNING (MainThread) [pysma] Password should not exceed 12 characters

As I'm using a password manager I had set up a 20 characters password, after changing to a 12 characters password it is now conected and working perfect.
I hope this can help other people too.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[littleyoda]

Thanks,

I just found out that the new SMA TRIPOWER X Inverter run on a completely new system. HA Integrations does not work on TRIPOWER X.

You can test my integration:
https://community.home-assistant.io/t/support-for-more-sma-devices-e-g-tripower-x/713737

[frederikvoGIT]

SMA Device details:
    -Sunny Boy Smart Energy 5.0
    -Firmware version: 03.08.03.R
    -Webconnect functionality switched on Software version not found
    -URL used to connect to SMA GUI in browser: https://192.168.129.12/webui/Plant:1/dashboard
Home Assistant Details:
    -Versions:
         Core 2024.5.4
         Supervisor 2024.05.1
         Operating System 12.3
         Frontend 20240501.1
   -Debug logging not available because can't succeed connecting

And next to my own login for the webinterface, i have this page delivered with the invertor with serial numbers and codes: