David Rapan
David Rapan
Hi @cnu80, this new device may require additional implementation. Try contacting Deye and asking for Modbus documentation.
It's all done in https://github.com/davidrapan/ha-solarman/blob/7e4a59b9f87d5c395821e77737192fafc6551a05/custom_components/solarman/const.py#L76 between lines 76 to 90. You can try adding another "device" and point it to the file which you think could work, I guess? :)
> I received the reply that the Modbus information is not available for customers. This is ridiculous and BS, though. I wonder what their reasons are for doing that. We'll...
Hi @tommi1968, mhmm, maybe it's because it's reconfigured from connecting via the logger to a proxy and because it knows the logger's MAC address, it's used for matching. Have you...
Hi @ResnikSI, hmm.. this really looks like they changed the way values are stored in registers, wow.. do you know what firmware (and protocol) version you had before?
> I hope it helps, as for protocol/profile I was talking about > Protocol Version：0105 Which translates to 1.5 and mine are using 1.4 so I was wondering if this...
Well, we need to find out what exactly has changed and on which devices to be able to reliably detect when is different scaling needed. Simple "same issue" doesn't help...
For now, I'll make it configurable using a modifier (set to 2) in the device configuration. But what I don't understand yet... is that the Total Losses are correct according...
And **Total Battery (Dis)Charge** is scaled properly?
I mean, does it need *10 too?