David Rapan
David Rapan
Yeah, you also need to edit `manifest.json` of the old integration. [However, transferring history is very easy](https://github.com/davidrapan/ha-solarman/wiki/Naming-Scheme)
Hi @OneScuzzie2k, can you show the debug log?
Hi @knownout, it's a known issue and is being discussed in #208
Hi @mic-hall, it's a known issue with some loggers and there is unfortunately not much we can do about it. I was able to solve it for energy sensors, but...
Fuses and circuit breakers can usually temporarily handle ~10 times their rated current, depending on the type, but it varies a lot. I'm strongly against polluting device configuration w/ things...
I'm pretty sure this is not a problem on "our" side and only affects some Ethernet loggers. The main difference between cloud and local usage is that w/ the cloud...
I told you, Ethernet loggers are not using Solarman protocol for local communication and Modbus TCP doesn't use CRC. Edit: Wireless loggers use the Solarman protocol with a checksum, and...
So far it looks like it's more of a HW issue than a FW one. You can build your own logger using [Modbus TCP RTU bridge](https://github.com/rosenrot00/esphome_modbus_bridge) running on ESP8266/32 +...
If the bridge you are currently using correctly implements Modbus TCP then it has to work. Have you selected the appropriate transport protocol in the device configuration?
I can see one successful request.. so maybe too many clients are polling at the same time? Try to disable polling using LSW-3 while testing it out.