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

Problems reading out data Deye 600 #9

Closed
renfie opened this issue Aug 5, 2024 · 5 comments
Closed

Problems reading out data Deye 600 #9

renfie opened this issue Aug 5, 2024 · 5 comments

Comments

@renfie
Copy link

renfie commented Aug 5, 2024

Are there any problems when reading out the Deye 600 or how can I avoid the problem that neither voltage nor current are displayed?
Is there anything known?

# Solar Exporter watt 332 today_e 0.9 total_e 891.7 online 1 voltage{panel="1"} -99 current{panel="1"} -99 voltage{panel="2"} -99 current{panel="2"} -99 temperature -19.9 executiontime 46

@BoneBunny
Copy link

Seems it's related to a OTA update. For me it's also not working since the last Update. (SUN-M80G3-EU)
https://dy-support.org/community/deye-micro-inverter/port-48899-nach-ota-firmwareupdate-gesperrt/

@ToWipf
Copy link
Owner

ToWipf commented Aug 25, 2024

The exporter returns -99 if someone cannot retrieve data

Look like this problem: s10l/deye-logger-at-cmd#6

@renfie renfie closed this as completed Jan 13, 2025
@renfie renfie reopened this Jan 14, 2025
@renfie
Copy link
Author

renfie commented Jan 14, 2025

Hello,

I have downgraded to MW3_16U_5406_1.63 and can access the port again. Unfortunately, no data is still being transmitted. What could be the reason?

The exporter returns data
image

but prometheus says the solar-exporter is down!

image

@renfie
Copy link
Author

renfie commented Jan 15, 2025

Hi,

ok, I have deleted everything again and recreated it. Now it works again.

@renfie renfie closed this as completed Jan 15, 2025
@ToWipf
Copy link
Owner

ToWipf commented Feb 9, 2025

The problem here was that a new Prometheus version (3) was used, but the exporter sources were not yet up to date. Updating the exporter would have been sufficient in this case. I have already implemented the fix there.

Nice to hear that it is working again

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

3 participants