-
Notifications
You must be signed in to change notification settings - Fork 16
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
mqtt stops cloud upload #52
Comments
I think the reason might be the update frequency. Requesting data from the inverter too often might prevent it from sending data to the cloud. We should add an option to adjust the update frequency to see if we can find a setting that works well |
Yes I think it is related to that because if you quit the docker image then it starts uploading to the cloud again. We need to find a good balance so both work together. Either that or I dump the cloud site but the cloud app is graphically nice (especially for the wife who doesn't care about all the techie stuff) |
That's an interesting thing, thanks for the report. I had experimented a bit and landed on 30.5 second as a cooperative time interval that shouldn't block the update to the cloud. I also checked and it seems to work on my side. One feature that I have planned though is to implement the five second update mode, and then an option to also forward that data into the cloud. |
I'll continue to play and investigate. Great work though - very happy someone is pushing this forward. Thanks |
One thing that just crossed my mind is that the 30.5s threshold is tight, and the inverter is running internal countdowns when to send the next update to the cloud. It is just a hunch that in case the tool is restarted shortly after it queried the inverter it might be that the internal countdowns never reaches zero. Hard to verify this hypothesis, tho. |
QQ - currently as mentioned I connect to the inverter off my main wlan. Can you connect to the inverter in the same way off the inverter's internal wifi network - maybe through this, if you can retrieve the data still, it would not interfer with uploading data to the s-miles cloud? Just a thought. |
Interesting idea. Will try. |
I changed the request delay to 60 seconds, with that the data is again also pushed to the cloud. mqtt/home assistant is still working of course. The delay of 30.5 seconds did not work for me |
I can confirm this. Switched to 60.5 seconds and the s-miles cloud is updated again. Maybe make this a config switch. |
Yeah, a mode to co-exist with the cloud makes sense. |
How do I get the coop mode to work? I've waited for the fix and created a new test vm (Ubuntu 22.04.3 LTS) This is my config.toml, which is passed to the docker container:
So coop_mode is set to true and update_interval is increased as well. But still the updates are every 30 sec, preventing s-miles cloud from updating. |
Did you try the most recent version. Do you see any output on the console when the tool starts? |
I've created the test virtual machine on Monday 2024-01-22 from scratch. The fixed version was released earlier, so I thought I'll automatically get the most recent version. But maybe the docker repository is not up to date? Anyway, here's the output when I start the container without (-d [detached]):
Docker inspect:
Also did a pull:
|
Yep. A new version is to be released some time this week to docker. |
Thank you for the support! 👍 I've now created the image from the Dockerfile. Here is what I did (maybe someone has the same problem):
|
Thanks for the software! I investigated a bit and I have a thought on this: I noticed that the S-Miles cloud updates are sent at specific times (x:00, x:15, x:30, x:45), plus-minus a few seconds. Is this the same for every HMS-800W-2T? May it be, that this is the reason? If I am correct, a workaround to keep the cloud upload working always would be to use a multiple of 60s (minus the time needed to execute the code) as the interval and making sure to start at in a "fitting" part of a minute on the clock, e.g. in the range betwen 15-20s "after the full minute". A fix in software could be to allow checking the current time and e.g. skipping an update if it clashes with the update of the cloud. |
I got it to update reliably by skipping the publishing in the S-Miles cloud update interval: Maybe something like this or any other working approach could be merged? |
Looks super interesting! Do I read this right that every 15 minutes an update is sent to the cloud? Perhaps this feature could be opt-in behind a config flag? |
From my testing it seems to be that way, although I just figured it out by trial and error, so there are no guarantees that I am right. Putting this behind a config flag sounds like a good idea! |
Looking forward to a pull request then 😉 |
hi guys, this is a great project and I have it working against my new inverter and sending mqtt data. However, I see that it seems to stop the upload to the s-miles cloud. Is this the case that you have experienced?
I'm attached to the inverter via my normal wlan and not the inverter's internal wifi.
Hope someone can shed some light on this one,
Thanks
The text was updated successfully, but these errors were encountered: