-
Notifications
You must be signed in to change notification settings - Fork 5
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
[Idea] The data packets look like modbus over ethernet #1
Comments
I am using modbus2tcp in home assistant to get data from solar inverter as well. |
If it is modbus then the length field is a bit odd. This should be two bytes and it seems only the first byte is the length with the value of 0x53 in the second half. The type 1/2 fields before the data would be a unit identifier and function code if it was modbus. This might make sense if using the harvi to communicate between devices. I'm tempted to buy the ethernet adapter for the zappi and have a go. If I can intercept and spoof spare energy going out to the grid then I could finally control the damn thing. |
I don't have the knowledge needed for this, bu I think this is the only way to save the product. With current cloud-only approach it is really bad and I would love any progress in this field. |
Update: Just note that I don't care about server side, I want to interface with the v2.1 zappi directly. As for cloud, I'd like to cut off internet access altogether. |
@ajaxharg - you could spoof this by sending a signal of your choice in place of the grid CT. I'm also really interested in intercepting the comms locally though - I need to brush up on this stuff, but it's on the do list. |
The data packets that are being intercepted look like modbus packets.
I do also use this for intercepting the data from my SolarEdge Inverter.
For this I use Node-red with modbus-node and JavaScript.
Don't know if this works the same, but thought I could share.
The text was updated successfully, but these errors were encountered: