Deye Battery Offline in Cloud - Increase the poll interval for WiFi logger to 10+ seconds

[OwlBawl]

I have problems with concurent connection to WiFi logger using Deye Cloud and Ha-solarman
With default Cloud update interval and Ha-solarman - my battery become "offline" shortly after integration start.
When disable it - Deye cloud battery ok again.
StephanJoubert's integration don't overload logger as this one. But it has ~30s update interval as i know.
The rs485 integration by kellerza with 5s update is also ok.
So, the only problem I see - serial port overflow with concurent requests...

[davidrapan]

You can change it by using custom profile and define the intervals there.

Edit: Btw you are using all three of them at the same time? 🤯

[davidrapan]

Maybe with the combination of Deye Inverter with Deye Battery.

[OwlBawl]

Yes, exactly, I saw it with Deye-Deye set on other variations

[OwlBawl]

So.... in search of unconflicted solution with poll interval )
Anyway interesting to figure it out. For now I know that you default interval (5s?) fils battery communication, while Stephan's integration with 30s interval works fine, but think it's to long

[davidrapan]

I told you, try to increase it to 10. Here is how

[OwlBawl]

Would try, thank you.
Was a bit exited that this "problem" is undiscovered by anyone before.

[davidrapan]

If there is an issue I'm pretty sure it will be about congestion. When all of the events happens at the same time which means that lower polling rate will lower the chance of it happening but won't remove the issue completely.

[OwlBawl]

So, maybe my current rs485 integration would be more stable and fault safe

[davidrapan]

I mean you should for sure prefer Sunsynk addon over this integration if you have the chance. 😉

[PV-Joe]

I recommend to use ha-solarman only as it provides all necessary information.

Or is there any other values by the other two integrations that are not taken into account by ha-solarman?

[OwlBawl]

Deye's WiFi definitely not the most reliable thing I met )
Thing wired connection it always priority for critical hardware

[davidrapan]

I would not call it Deye WIFI.

[PV-Joe]

ha-solarman by David Rapan runs since month 100% stable without any problems, so I can't confirm that the LSW3 Stick-Logger is having any problems with stability.

It is pulling the "current sensors" every 5 seconds from my Deye Hybrid.

Maybe it is a WiFi problem that could be optimized?

[OwlBawl]

I have separate 2,4Ghz network for all my iot things working just fine on UniFi.
This one work also, but definitely know that things like "bind to ap" make problems to Deye logger, it could have issues on reconnect, so canceled it. Anyways, WiFi vs wire for me personally is obvious for stability.

[davidrapan]

WiFi vs wire for me personally is obvious for stability.

Not sure about the state with WiFi 7 but in overall I agree for sure!

[OwlBawl]

Made custom yaml
For Deye hybrid - update interval 10 instead of 5 seems to be working. Battery disconnection not mentioned yet.

[FrancescoCosta78]

SET to ZERO all offline.

[davidrapan]

This shouldn't have be solution (it should just help a little). You will proly still need to increase that base update interval to 10 s or something.

[FrancescoCosta78]

Modify:

default:
update_interval: 25 #(OLD 5)
digits: 6

• group: Control
  update_interval: 25 #(OLD 5)
  items:

• group: PV
  update_interval: 25 #(OLD 5)
  items:

It's not ok definityve....

Idea?

[davidrapan]

I mean this and disable reading of additional battery sensor should be enough. It's what's always helped so far.

[FrancescoCosta78]

if insert into group battery ?

[FrancescoCosta78]

Isn't it by chance the request to some register that gives some error?
In the log there is nothing with the writing err or error or ko.
The other integration was set to default 5 and never blocked. True that it didn't have all these sensors...

Anyway I put all the intervals that were at 5 -> 15 and let's see.

[trozman]

Same problem here (Inv: Deye, batt: Deye). Then I edited in /solarman/inverter_definitions/deye_hybrid.yaml (using Studio Code Server HA addon):
...
default:
update_interval: 10 #old: 5

...

And deye cloud app/devices/battery stays online (observing for 30 minutes). Will observe if stays that way**

I also tried adding update_interval to Battery group:

• group: Battery
  update_interval:10 #added

but it didn't have an effect.

**update 1: no, increasing to 10s didn't work. Increasing poll interval and observing when it's stable...
**update 2: 15s interval mostly works ok, but I had to change const.py: TIMINGS_INTERVAL_SCALE = 3.
**update 3 (4. 3. 2026): after the firmware update (to include 'Smart devices'), I had to increase the interval TIMINGS_INTERVAL_SCALE = 3 (20 secs).

[techadrian]

Hi,
I had the same issue with partial offline in Deye Cloud/Solarman for the Battery status being offline.

Considering what was discussed above, I have done a replacement of all "update_interval: 5" values to "update_interval: 21" and solved my issue. I am using deye_p3.yaml profile.

I do not rely on such tight pull intervals, so most probably doing 30 sec intervals would offer the best stability for all platforms.

[schumixmd]

Can we add Default Update Interval as a parameter? Instead of messing up with the profiles?
The reason is that I like the 5sec pooling interval, but if I want to change some parameters from the cloud, most of the time it does not work. So, changing the parameter in HA, would be way easier than anything else.