All things Sunsynk (Deye, Inge, etc...)

That is weird. BMS miscalculations no doubt. Which battery again?
Dyness AX48100
What's the soc for your 49.9? Although they call it a 48V on my hubble 100% is really 53.73V anything less than that is not saturated or the bms struggle. So 49.9 is around 85% for me. 50% is 47.67V on mine.
Not sure, there's a chart that shows the correlation. But it's not linear, and the drop-off is very steep.
All working 100s again?
Yeah thankfully. By the time I got everything going again the batteries were only charged to 40% by evening. And to make it worse the power never came back after LS.

Only came back at 10pm (after going out at 10am), by which time the batteries were on 20%. To say there was anxiety is an understatement. Seems like when something goes wrong, everything will go wrong...
 
I wish I'd known about the down-sides with Hubble. That warranty thing is slightly disappointing.

The depth-of-discharge thing seems to my eye to be less of an issue though: 3000 cycles at 100% depth-of-discharge, vs 6000 half-cycles, would get me to roughly the same amount of kWh over its lifespan. Or am I misunderstanding something?

Maybe I'll just work it as hard as I can and then replace it with something else in roughly 3000 days.
No need to count days. Work them until they are finished, and I mean finished, you will know when that comes around, and much to the awe, shock and horror of the Hubble bashing brigade, they will probably outlast Pylontechs and most others.
 
Dyness AX48100

Not sure, there's a chart that shows the correlation. But it's not linear, and the drop-off is very steep.

Yeah thankfully. By the time I got everything going again the batteries were only charged to 40% by evening. And to make it worse the power never came back after LS.

Only came back at 10pm (after going out at 10am), by which time the batteries were on 20%. To say there was anxiety is an understatement. Seems like when something goes wrong, everything will go wrong...
glad its all working again and definitely something to keep an eye on going forward
 
Thanks for the info.

I'm not sure if anyone noticed, or whether this issue has come up. I pulled the warranty info from Hubble's website, and it says there

I went to have a look on Solar Assistant's website but they don't have any comment on this and the "contact-us" link is just broken.

Has anyone come across this issue before?
I wouldn’t worry about the cable in the battery, as long as you don’t write anything they can’t see you’re reading it. Just try not to ever tell them you are. They know I do and have warned me but they still didn’t make a big fuss out of it.
 
No need to count days. Work them until they are finished, and I mean finished, you will know when that comes around, and much to the awe, shock and horror of the Hubble bashing brigade, they will probably outlast Pylontechs and most others.
I'm curious as to why you say this.

You're misunderstanding cycles. 6000 half cycles is only 3000 cycles.
Well yes, 6000 half-cycles is 3000 cycles.

So in the end you'd have stored and retrieved roughly the same amount of electricity from the battery. If it was more than 6000 half-cycles then I'd be more worried surely?
 
In other news, I eventually got enough contiguous free time to set Home Assistant up properly and used the Solarman integration (https://github.com/StephanJoubert/home_assistant_solarman).

Followed the directions and it seems to see my logger, but I get "Unknown" for everything:
1689423626368.png

Anyone come across this before? Where does one even start debugging?
Or is the only solution, pull out the credit card and order Solar Assistant?
 
In other news, I eventually got enough contiguous free time to set Home Assistant up properly and used the Solarman integration (https://github.com/StephanJoubert/home_assistant_solarman).

Followed the directions and it seems to see my logger, but I get "Unknown" for everything:
View attachment 1557455

Anyone come across this before? Where does one even start debugging?
Or is the only solution, pull out the credit card and order Solar Assistant?
I’ll check which integration I’m using but mines fine.

1689423736777.png
 
In other news, I eventually got enough contiguous free time to set Home Assistant up properly and used the Solarman integration (https://github.com/StephanJoubert/home_assistant_solarman).

Followed the directions and it seems to see my logger, but I get "Unknown" for everything:
View attachment 1557455

Anyone come across this before? Where does one even start debugging?
Or is the only solution, pull out the credit card and order Solar Assistant?
Only thing i can think of is that in your setup, one of the following is not correct:
  • Dongle IP
  • Dongle serial
  • Inverter Modbus
Do you get ANY values at all (if you check developer options) from the integration?
 
No need to count days. Work them until they are finished, and I mean finished, you will know when that comes around, and much to the awe, shock and horror of the Hubble bashing brigade, they will probably outlast Pylontechs and most others.
From what I've heard, the Hubble bashing brigade find the slow service / lack of response the worst.
 
Only thing i can think of is that in your setup, one of the following is not correct:
  • Dongle IP
  • Dongle serial
  • Inverter Modbus
Do you get ANY values at all (if you check developer options) from the integration?
If I look at the debug logs I see the following:

Code:
2023-07-15 15:24:04.228 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] a5170010450000f9ae648902000000000000000000000000000001030003006e3426d115
2023-07-15 15:24:04.239 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] a51000101500bc2f55e1a5020135150900271a0000bf88a9640600ec15
2023-07-15 15:24:04.240 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] invalid modbus crc
2023-07-15 15:24:04.241 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] Querying [3 - 112] failed, invalid response packet.
2023-07-15 15:24:04.241 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] Querying [3 - 112] failed, [0] retry attempts left
2023-07-15 15:24:04.241 WARNING (SyncWorker_3) [custom_components.solarman.solarman] Querying registers [3 - 112] failed, aborting.

What is the inverter modbus? I see "invalid modbus crc" there, so ... it's unhappy about something? An incompatible protocol version or something like that?


The Solarman Smart app works (I mean after a fashion, it updates occasionally). So I can only presume that from the dongle itself to the inverter's inners is working properly.
 
I'm curious as to why you say this.


Well yes, 6000 half-cycles is 3000 cycles.

So in the end you'd have stored and retrieved roughly the same amount of electricity from the battery. If it was more than 6000 half-cycles then I'd be more worried surely?
I think I may have misunderstood you. I thought you'd said 6000 half-cycles counted as 6000 cycles
 
If I look at the debug logs I see the following:

Code:
2023-07-15 15:24:04.228 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] a5170010450000f9ae648902000000000000000000000000000001030003006e3426d115
2023-07-15 15:24:04.239 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] a51000101500bc2f55e1a5020135150900271a0000bf88a9640600ec15
2023-07-15 15:24:04.240 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] invalid modbus crc
2023-07-15 15:24:04.241 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] Querying [3 - 112] failed, invalid response packet.
2023-07-15 15:24:04.241 DEBUG (SyncWorker_3) [custom_components.solarman.solarman] Querying [3 - 112] failed, [0] retry attempts left
2023-07-15 15:24:04.241 WARNING (SyncWorker_3) [custom_components.solarman.solarman] Querying registers [3 - 112] failed, aborting.

What is the inverter modbus? I see "invalid modbus crc" there, so ... it's unhappy about something? An incompatible protocol version or something like that?


The Solarman Smart app works (I mean after a fashion, it updates occasionally). So I can only presume that from the dongle itself to the inverter's inners is working properly.

What do you see on this screen? Specifically in the Modbus SN field

IMG_1727.jpg
 
maybe try the solutions in this github issue

OK I don't know what solved it, but the trick mentioned in that thread of using 0.0.0.0 and 0 for autodetect, worked!

Thank you!
 
I'm curious as to why you say this.
Because I bought 3 myself, based on my own research at the time, and they have given me zero issues?

Remember, the 3000 cycles are specified at a charge and discharge rate at 1C, which Pylontechs aren't even capable of. Reducing this to 0.5C (same as Pylontech) increases the lifetime and therefore cycles. It's been argued to death, over and over again, but a certain group of people (who may have had buyer's remorse at purchasing other batteries) keep hammering on the 3000 cycles, and the chemistry, apparently it spontaneously self-combusts. :laugh: I have both Pylontech and Hubble batteries, and haven't had any issues with either.

Would I buy the AM-2 today? Yes, if I can get the same config as I previously bought. Even if I wanted to, I cannot, because mine were based on an earlier config that isn't available today. They fiddled with the BMS and cell count, and this introduced issues that needed tweaking. So I would do my research all over again before committing to the newer models.
 
Because I bought 3 myself, based on my own research at the time, and they have given me zero issues?

Remember, the 3000 cycles are specified at a charge and discharge rate at 1C, which Pylontechs aren't even capable of. Reducing this to 0.5C (same as Pylontech) increases the lifetime and therefore cycles. It's been argued to death, over and over again, but a certain group of people (who may have had buyer's remorse at purchasing other batteries) keep hammering on the 3000 cycles, and the chemistry, apparently it spontaneously self-combusts. :laugh: I have both Pylontech and Hubble batteries, and haven't had any issues with either.

Would I buy the AM-2 today? Yes, if I can get the same config as I previously bought. Even if I wanted to, I cannot, because mine were based on an earlier config that isn't available today. They fiddled with the BMS and cell count, and this introduced issues that needed tweaking. So I would do my research all over again before committing to the newer models.
Interesting. I guess we'll see in the next 5 to 10 years what happens.

How can you tell which edition that you've got? My Hubble was installed quite recently so I would presume that it's a newer one.
 
In other news, I eventually got enough contiguous free time to set Home Assistant up properly and used the Solarman integration (https://github.com/StephanJoubert/home_assistant_solarman).

Followed the directions and it seems to see my logger, but I get "Unknown" for everything:
View attachment 1557455

Anyone come across this before? Where does one even start debugging?
Or is the only solution, pull out the credit card and order Solar Assistant?
It's not communicating correctly. Check you have set it all up correctly: wifi, serial, modus parameter.
 
Top
Sign up to the MyBroadband newsletter
X