Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

psurplus value wrong #751

Open
danickel opened this issue Aug 15, 2024 · 6 comments
Open

psurplus value wrong #751

danickel opened this issue Aug 15, 2024 · 6 comments

Comments

@danickel
Copy link

Since some days psurplus value is wrong. Dont know, may SMA made an update?

Here the values from iobroker and sunny portal:
image

It is the half, i think because the adapter calculates everything with wrong voltage:
image

Regards,
danickel

@pdbjjens
Copy link
Contributor

@danickel
This looks like the issue described in the release notes under the headline: "Selectable own network device IP to listen for multicast messages". Please check if your adapter listens to multiple own network IPs, and if so select only the IPs on which the SMA multicasts are received. If that daoes not help, please post a log of the adapter start-up sequence.
Best Regards
pdbjjens

@danickel
Copy link
Author

hm...I did not change anything at the settings.
This are my settings (already for a long time):
image

And this is the startup sequence:
image

@pdbjjens
Copy link
Contributor

@danickel
your adapter network configuration looks o.k.
The start-up sequence as well. However the message rate of 2/sec seems quite unfamiliar. Did you change the message rate of your SHM2.0 recently in Sunny Portal? "Messintervall internes Energy Meter:" normally is 200ms which should give a message rate of 5/sec.

@danickel
Copy link
Author

No never changed here something. Maybe the worker did that at installation. I can set it to 200ms, currently it is set to 1000ms.

But why is the voltage at 119V? I also have a Victron setup that also intercepts the multicast message. The voltage there is correct and everything is fine.
image

@pdbjjens
Copy link
Contributor

@danickel
If you are sure that the Messintervall is currently at 1000ms and has been that way all the time, then do not change it. The adapter should detect 1/sec as opposed to 2/sec. That is why it halves all realtime values (power and voltage).
I currently have no explanation why it receives 2 messages per second. I still suspect some network problem.
Please switch off the averaging in the adapter by setting the realtime interval to 0 (instead of 1). Leave the non-Realtime Interval at 30 or higher. Then everything should be fine.

@pdbjjens
Copy link
Contributor

@danickel
Did you solve the problem meanwhile? If yes, I would like to know how you fixed it and to close this issue.

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

No branches or pull requests

2 participants