-
Notifications
You must be signed in to change notification settings - Fork 52
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
Non-numeric serial number #213
Comments
hi! I think it was a bad design decision to model the serial number as integer, so if you would like to submit a PR fixing this, that would be great. |
This issue is stale because it has been open for 30 days with no activity. |
Same problem here. Serial number ending with F character. @MagiX13 , I'm sorry, but I wasn't able to find your fork. Can you provide the places you've edited? |
@MagiX13 I can implement this change. Could you tell me how do you encode textual serial number into the Modbus frame? I'm referring to this code
|
I use to use WVC script from @krywenko https://github.com/krywenko/WVC-inverters/blob/dfd8d103635cdf91f37f67a41c00a81fb87d6483/wvc#L21. I'm not sure how deye build its serial number to request the message. It is a modbus tcp? do I need to encode the serial number? if so, I can make some tests to find out. |
|
@kbialek and @thalesmaoa: I used this approach and it seems to work fine on my end: e: fixed a typo in the command |
@MagiX13 I have problem in understanding how this code
Can you check on your side? |
@kbialek , what about
|
@thalesmaoa So you're suggesting that the serial number is not an arbitrary string, but a hexadecimal number, right? |
Yes, since I know nothing about the communication system with the deye. How it is encoded and so on, I need to know if that makes sense.
In other words, does older versions has an int serial number and new ones hex serial number? This is the question. The code we fix it. From @MagiX13 answer, it seems that my suggestion is correct. There must be a if statement for the serial number. |
Sorry, there was a typo in there, should have been |
Thanks @MagiX13 It's clear now that the SN is hex encoded |
@thalesmaoa Imho, you can just convert your SN from hex to dec and then set |
No, perhaps is my inverter not compatible Serial: Model: Config
log
|
@thalesmaoa The SN
Bytes are reversed as expected. What is your timezone? Is there sunlight and is the inverter producing energy? |
Yes! I'm in Brazil. GMT -3. From my readings, it seems that it is getting a response. I still have a few minutes for a test.
Not sure what |
@thalesmaoa Did you try using |
Yes,
Not working. |
@kbialek , what is your suggestion for debug? |
None 😞 You may also try out the new |
I found the problem, but not sure yet how to solve it. Short answer: serial number is wrong. I was playing with awesome work from jedie https://github.com/jedie/inverter-connect and I could retrieve my serial using AT.
|
Just to add. Inverter serial number Device serial number The last one is firmware related. |
If this worked for you, then your inverter supports the |
Sorry for not making it clear. The answer for this issue is not that. What if someone has a inverter serial number with letters? Which is the correct number? The first one, called inverter serial number, is the same labelled next to the Qr code. Just ignore this number. The second one, called device serial number is the correct one and the one you should use. |
👍
That's correct. Always use device serial number aka logger serial number. |
For some reason, my Deye SUN-M80G3-EU-Q0 (obtained in Nov 2023, never upgrade the firmware thus running
MW3_16U_5406_2.27
) has a non-numeric serial number, ending with BD.I made some local changes to accommodate this, but was wondering if there are more people with this/there is a need for a pull request - I think it amounts to 3-4 lines that I had to change. I had it running with these changes since March already and it seems stable. Today I decided to update the docker repo and saw that this is still not supported and would be happy to submit a PR.
The text was updated successfully, but these errors were encountered: