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

SlowChgWatts not being displayed correctly in HA #143

Open
walderston opened this issue Aug 29, 2024 · 5 comments
Open

SlowChgWatts not being displayed correctly in HA #143

walderston opened this issue Aug 29, 2024 · 5 comments

Comments

@walderston
Copy link

using v1.0.2 with HA. I'm able to set the SlowChgWatts however the value is not stored within HA so when I revisit the page it retains the old previous value. If I make the change via the app, the correct value is displayed in HA

@walderston walderston changed the title D2M - SlowChgWatts not being displayed correctly in HA SlowChgWatts not being displayed correctly in HA Aug 29, 2024
@foxthefox
Copy link
Owner

I have tested several thing on my DM and could not reproduce the problem.
Can you do another check and change the value from the iobroker object list and verify the change in the APP, it could be the case that the given command is not having the right information in it (similiar to one issue with r2max).
If this is the case then I would needt to have a debug log (device and msgSet/Get, msgCMD enabled) and changes via APP performed. Then I can see the original command string.

PS.
What device is concerned?

@walderston
Copy link
Author

Its a Delta 2 Max

It is able to set the charging speed correctly, however it doesn't seem to update the value within HA so it continues to display the old value. This only happens when the value is set via HA, if I set the value via the app, HA updates correctly.

Noticed permanentWatts on the powerstream (inverter_hearbeat) also sometimes seems to stick with the old value.

Shows that permanentWatts value is at 370 despite it being set to 380. The app correctly shows 380.
image
image

@walderston
Copy link
Author

@foxthefox happy to continue on this thread as you rightly said, the other issue has been resolved.

@walderston
Copy link
Author

@foxthefox do you think this is a HA issue for not persisting the state or is it expected behaviour and we should get ioBroker to send an update?

@foxthefox
Copy link
Owner

I have not investigated too much on that issue. I saw the change within the mqtt broker. I also found some HA issues related to non memorized states, but they were all related to HA restart. I have the feeling that it is a HA issue or an issue of the browser or a combination of both. So far I have not checked if clearing browser cache helps or how the HA app is behaving.

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