Deye Microinverter is sending the same data with update period of 60s or 5m

[Steinbichler]

First thank you for this fine solarman integration! Great Job!

I am running homeassistant in actual version. My converter is a Deye 600. Relais is installed.

I have your ha-slarman up an running installed via HACS. Nearly everthing works fine but:

I have requested at Deye support to set the update interval for my Deye 600 to 1 Minute.
They agreed to have it done. I see in the Homepage of the converter the update time is set to 1.

But nothing changed in the ha-solarman. I changed the number in the definition file: deye_2mppt.yaml.
After the installation the update_interval: 5 was set.
What ever the number I enter, and for sure I did a restart after the change, nothing happens.
The update interval is always 5 Minutes.

Can you help please?

Thank you an regards Roland

[davidrapan]

Hi @Steinbichler, I'm little bit worried that you are mixing different things here together.

I have requested at Deye support to set the update interval for my Deye 600 to 1 Minute.
They agreed to have it done. I see in the Homepage of the converter the update time is set to 1.

This integration and HA has nothing to do with Deye and their support and is completely separated thing. No configuration from Deye side won't affect this integration at all.

And at the same time nothing set in this integration will affects Deye Cloud nor Solarman App. Again it is completely separate thing from those.

But nothing changed in the ha-solarman. I changed the number in the definition file: deye_2mppt.yaml.
After the installation the update_interval: 5 was set.
What ever the number I enter, and for sure I did a restart after the change, nothing happens.
The update interval is always 5 Minutes.

What are you trying to achieve? update_interval: 5 in the 2mppt.yaml means 5 seconds not 5 minutes.

[Steinbichler]

Hi if set to 5 as ist should be 5 seconds I have this:

Update was 6 Minutes before.

[davidrapan]

What shows Update Interval sensor in diagnostic card in device detail view?

Edit: Please enable debug logging, let it run for a while and then post the log file here please.

[CrazyUs3r]

@Steinbichler
Wie gut ist das wlan Signal
Mein m80 macht auch nur alle 5min ist aber auch auf 1min gestellt. In der solarman app kommen die Signale aber auch nur im 5min intervall an

[Steinbichler]

@davidrapan

do you mean this one

@CrazyUs3r
Das Wlan kann das Problem nicht sein es ist sehr gut und in der Solarman App kommt der update nach einer Minute

[Steinbichler]

I started debug and I will upload the file later later

[Steinbichler]

home-assistant_solarman_2024-08-15T17-36-23.029Z.log

I hope it helps.Thank you an Regards Roland

[davidrapan]

What the actual f*ck is happening in there!

Do you have it updated to v24.08.14 version? If no please do the update.

And could I please ask you to do the following please:

1. Disable debug logging (if you have it enabled)
2. Restart Home Assistant
3. Remove the device from the integration
4. Enable debug logging
5. Add your device back again and go through configuration
6. Let it run for some time
7. Disable debug logging and post here the log file again

Thank you for your cooperation! 😉

[PV-Joe]

I remember this behavior after my first installation.

The Update information in seconds or minutes from Home Assistant was showing wrong values but the sensors updates as expected.

I haven’t done anything about it and wondered. The problem desolved by itself after a while.

[Steinbichler]

Sorry about the confusion in the deleted comment.
It was a problem with my HO installation everything woks fine I will upload the log asap.
Regards Roland

[CrazyUs3r]

My log
home-assistant_solarman_2024-08-16T08-13-04.070Z.log

[Steinbichler]

Here is my log
home-assistant_solarman_2024-08-16T08-23-58.631Z.log

[davidrapan]

@Steinbichler and when you are observing the value does it really update with such a long period? Or just the HA shows it incorrectly?

[davidrapan]

Maybe fix: Proper implementation of sensor platform will do something about that strange update behavior.

[CrazyUs3r]

I test it also

[Steinbichler]

@davidrapan.

I did a test to cover my pannels. And yes ist last at least the 5 to 6 Minutes till I see the change in HA.

A question to my understanding: Even if the content of the register in my inverter did not change, the update in HA-solarman should read the unchanged content after the interval time? Is it not in this way?

And for the link in your comment to the definition file? Should I change it like it is in the description? and clear all the names?

[davidrapan]

I did a test to cover my pannels. And yes ist last at least the 5 to 6 Minutes till I see the change in HA.

Fuu, that is really strange :-/

A question to my understanding: Even if the content of the register in my inverter did not change, the update in HA-solarman should read the unchanged content after the interval time? Is it not in this way?

It will be read from the inverter. BUT! Ha won't update it's "Last updated" until the value really changes.

So the value just stays the same without any visible update trigger and soon as the new values differs from displayed it updates the state. And refreshes "Last changed/updated"

And for the link in your comment to the definition file? Should I change it like it is in the description? and clear all the names?

It was link to a commit, it affects whole source code not just definition profile.

[CrazyUs3r]

I now it. But slow wifi. So my ha view

[davidrapan]

@CrazyUs3r, you did not wait long enough for the file to finish uploading, hehe.

You have to wait few seconds until the "Uploading" from the name does not disappear. That indicates that the upload finished.

[davidrapan]

@Steinbichler Try v24.08.17 and see if it won't fix your issue.

[bjoernmayer]

Heyho,
I am on 24.08.17 and I can see the same behaviour. Data is updated around every 5ish minutes

[davidrapan]

Hey @bjoernmayer. Please enable debug logging and post the log here.

[davidrapan]

You can check through debug logging that data are fetched every 5 seconds but microinverter sends the same data (for PV sensors and some other) for duration of 5m (in some cases 1m). So this is not something which can be solved from the integration (or at least I don't know yet how could be device influenced in this matter).

[Adminius]

that's weird. I can't really check if cloud's 1 min really 1 min or also 5... hm.
This makes all my logics fail on cloudy days (EV charging on PV)

[davidrapan]

I totally understand! It doesn't make sense at all but I currently do not have any microinverter unit to test things out and maybe find a solution. I do plan to acquire some as soon I'll have some spare funds to "waste" to do exactly that. 😉

[Adminius]

Can I somehow help?
Theoreticaly I can provide VPN to one of my inverters

[davidrapan]

Not really sure if VPN would be enough as my idea is to sniff out traffic between the device and the internet in MITM style and ask support to reconfigure that update interval. It could hopefully reveal something if they change anything on the device.

[Adminius]

Maybe?
https://github.com/Hypfer/deye-microinverter-cloud-free/tree/master/dummycloud

[davidrapan]

That is for disconnecting the device from the cloud and not losing time synchronization in the process (can be done using this integration + HA automation to set time too).

[davidrapan]

Can someone try feat: Implemented response to V5 HEARTBEAT?

It should solve time synchronization for cloudless setup.

[terzo33]

Can someone try feat: Implemented response to V5 HEARTBEAT?

It should solve time synchronization for cloudless setup.

@davidrapan how can I do?

[davidrapan]

Just run the latest code.

Meaning you have to manually update the code as it's not part of any release yet.

[terzo33]

Just run the latest code.

Meaning you have to manually update the code as it's not part of any release yet.

Perfect. I did changes. Need to wait tomorrow morning, when microinverter will start to works

[davidrapan]

@terzo33, I had to do some fixes already fix: Sequence number for response to V5 HEARTBEAT 😉

[terzo33]

Done 💪

[davidrapan]

One more fix: Run response to HEARTBEAT in asyncio.ensure_future 😉😆

[terzo33]

Today is a rainy day... i can't try :(

[terzo33]

One more fix: Run response to HEARTBEAT in asyncio.ensure_future 😉😆

@davidrapan it doesn't seem to work

Edit: @davidrapan doesn't work

[davidrapan]

The purpose of this feature is not to anyhow help w/ update period of those entities but to enable time synchronization in cloudless environment!

I just used this thread to find someone with microinverter to test the functionality.

[terzo33]

The purpose of this feature is not to anyhow help w/ update period of those entities but to enable time synchronization in cloudless environment!

I just used this thread to find someone with microinverter to test the functionality.

@davidrapan yes but it doesn't seem to work because the data is updated every 5 minutes as it happens via cloud. is there anything I can do to help you?

EDIT: @davidrapan maybe need to disconnect my microinverters from the cloud? (solarman app)

[davidrapan]

yes but it doesn't seem to work because the data is updated every 5 minutes as it happens via cloud. is there anything I can do to help you?

You do not understand. It has nothing to do with this.

[davidrapan]

@terzo33, show me please your debug log (hope you recorded some or still have chance to).

[terzo33]

@terzo33, show me please your debug log (hope you recorded some or still have chance to).

@davidrapan

[davidrapan]

Looks like it does work:

2024-12-20 09:34:06.435 DEBUG (MainThread) [custom_components.solarman.api] [38????????] V5_HEARTBEAT: a5 01 00 10 47 02 d7 cb ea 91 e6 00 5d 15
2024-12-20 09:34:06.436 DEBUG (MainThread) [custom_components.solarman.api] [38????????] V5_HEARTBEAT RESPONSE: a5 0a 00 10 17 03 cb ea 91 e6 00 01 fe 2b 65 67 00 00 00 00 56 15

[terzo33]

Looks like it does work:

2024-12-20 09:34:06.435 DEBUG (MainThread) [custom_components.solarman.api] [38????????] V5_HEARTBEAT: a5 01 00 10 47 02 d7 cb ea 91 e6 00 5d 15
2024-12-20 09:34:06.436 DEBUG (MainThread) [custom_components.solarman.api] [38????????] V5_HEARTBEAT RESPONSE: a5 0a 00 10 17 03 cb ea 91 e6 00 01 fe 2b 65 67 00 00 00 00 56 15

@davidrapan great, but what purpose will this thing you're doing serve? What improvement will it bring?

[davidrapan]

I told you, time synchronization for installations in a cloudless (disconnected from solarman servers) environment.

[terzo33]

I told you, time synchronization for installations in a cloudless (disconnected from solarman servers) environment.

yes I understood this, but by disconnecting from the solarman cloud can we also have improvements on the data or extrapolate more data?

[davidrapan]

It should prevent timeouts but this functionality has nothing to do w/ subject of this thread. I already said it, that I just used this thread to announce this feature. 😉

[github-actions]

This issue is stale because it has been open for 30 days with no activity.