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

[SMAEnergyMeter] no longer working with OH 4.0.3 #15690

Closed
pjgregory opened this issue Oct 2, 2023 · 8 comments
Closed

[SMAEnergyMeter] no longer working with OH 4.0.3 #15690

pjgregory opened this issue Oct 2, 2023 · 8 comments
Labels
awaiting feedback bug An unexpected problem or unintended behavior of an add-on stale As soon as a PR is marked stale, it can be removed 6 months later.

Comments

@pjgregory
Copy link

I have just upgraded from OH 3.3 to OH 4.0.3 running on a raspberry pie. I have both an SMA Energy Meter and an SMA Home Controller 2.0 on my house network. Both worked correctly under 3.3. Following the upgrade, both things were marked as GONE. I have reinstalled the binding, (version 4.0.3), deleted the existing two things and installed them again with the default parameters. The thing for the Home Controller starts INITIALISING, but then goes to GONE after some 30 seconds. The thing for the Energy Meter changes to ONLINE for about a minute and then goes to GONE.

Has the distributed binding been tested with 4.0.3 or is there a newer version?

PJG

@pjgregory pjgregory added the bug An unexpected problem or unintended behavior of an add-on label Oct 2, 2023
@lolodomo lolodomo changed the title SMA Energy Meter Binding no longer working with OH 4.0.3 [SMAEnergyMeter] no longer working with OH 4.0.3 Dec 11, 2023
@lsiepel
Copy link
Contributor

lsiepel commented Dec 27, 2023

It might help if you put the binding in debug logging and show the logged entries when the thing is initialised.

@cambronf
Copy link

smaenergymeter is working in openhab 4.1.1 but is useless due to:
1/ broadcast frames disturbing the reading of power and energy values
2/ mixing the readings in case of serveral SMA meters in the network (homemanager 2.0 and energymeter 20)

2024-01-30 10:57:03.362 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 10:57:03.363 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:1b03d949af'
2024-01-30 10:57:14.697 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:cfdb5f9581'
2024-01-30 10:58:03.698 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:1b03d949af'
2024-01-30 10:58:03.700 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 10:58:15.166 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:cfdb5f9581'
2024-01-30 10:59:01.411 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Disposing SMAEnergyMeter handler 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 10:59:04.157 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:1b03d949af'
2024-01-30 10:59:15.335 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:cfdb5f9581'
2024-01-30 10:59:19.401 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Initializing SMAEnergyMeter handler 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 10:59:19.650 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Found a SMA Energy Meter with S/N '1901411959'
2024-01-30 10:59:19.650 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 10:59:19.651 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Polling job scheduled to run every 60 sec. for 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 10:59:45.893 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Disposing SMAEnergyMeter handler 'smaenergymeter:energymeter:cfdb5f9581'
2024-01-30 10:59:52.062 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Initializing SMAEnergyMeter handler 'smaenergymeter:energymeter:cfdb5f9581'
2024-01-30 10:59:52.138 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Found a SMA Energy Meter with S/N '1901412043'
2024-01-30 10:59:52.139 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:cfdb5f9581'
2024-01-30 10:59:52.140 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Polling job scheduled to run every 60 sec. for 'smaenergymeter:energymeter:cfdb5f9581'
2024-01-30 11:00:03.672 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Disposing SMAEnergyMeter handler 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 11:00:04.158 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:1b03d949af'
2024-01-30 11:00:13.045 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Initializing SMAEnergyMeter handler 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 11:00:13.142 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Found a SMA Energy Meter with S/N '1901412043'
2024-01-30 11:00:13.143 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Polling job scheduled to run every 60 sec. for 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 11:00:13.143 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:b33a5eb6'
2024-01-30 11:00:22.255 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Disposing SMAEnergyMeter handler 'smaenergymeter:energymeter:1b03d949af'
2024-01-30 11:00:26.272 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Initializing SMAEnergyMeter handler 'smaenergymeter:energymeter:1b03d949af'
2024-01-30 11:00:26.312 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Found a SMA Energy Meter with S/N '-1288020298'
2024-01-30 11:00:26.313 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Update SMAEnergyMeter data 'smaenergymeter:energymeter:1b03d949af'
2024-01-30 11:00:26.313 [DEBUG] [ternal.handler.SMAEnergyMeterHandler] - Polling job scheduled to run every 60 sec. for 'smaenergymeter:energymeter:1b03d949af'

Schermafbeelding 2024-01-30 110906

@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/sma-energy-meter-binding-yields-unplausible-values/128180/130

@lsiepel
Copy link
Contributor

lsiepel commented Feb 4, 2024

smaenergymeter is working in openhab 4.1.1 but is useless due to:
1/ broadcast frames disturbing the reading of power and energy values
2/ mixing the readings in case of serveral SMA meters in the network (homemanager 2.0 and energymeter 20)

1 => #3429 PR-pending
2 => #11497 PR-pending

@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/sma-energy-meter-binding-yields-unplausible-values/128180/146

@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/sma-energy-meter-binding-yields-unplausible-values/128180/151

Copy link

stale bot commented Apr 20, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale As soon as a PR is marked stale, it can be removed 6 months later. label Apr 20, 2024
@lsiepel
Copy link
Contributor

lsiepel commented Jun 1, 2024

As both related PR’s are merged I close this. If there is still a problem with 4.2 snapshot this can be re-opened.

@lsiepel lsiepel closed this as completed Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting feedback bug An unexpected problem or unintended behavior of an add-on stale As soon as a PR is marked stale, it can be removed 6 months later.
Projects
None yet
Development

No branches or pull requests

4 participants