What about the LAN port? (Now enabled)

[mdt3k]

My H1-5.0-E inverter has a LAN port, in addition to the RS485 port that the WiFi logger dongle connects to.

I decided to connect a computer to it, and discovered the port hosts a ModbusTCP server. I doesn't appear fussy about what equipment address you poke it with (I tried 1 and 247), it will respond to requests for modbus input registers 300-399, and holding registers 30,000-30,027, 31,000-31,038 and 44,000-44,002 (it is possible it will respond to other registers, I only tried every 100th register). The server responds straight away, and the solar-related values change at least every 5 seconds (I have not logged data for a long period at a faster rate than this, when register scanning I queried every 0.25 seconds and this didn't seem to cause any problems). It is interesting (to me at least) that these are not the same register numbers that everyone else is reporting, and they do not seem to contain exactly the same information as available via the WiFi dongle. I have not yet worked up the enthusiasm to create an RS485 break out box, but for now I assume my dongle is working the same as everyone elses.

The registers return the following information:

• 300-399: the values 1-11 and then zeros. I am unclear on the purpose of these registers
• 30,0000-30,027: 16 characters consisting of the model number (H1-5.0-E in my case) followed by some spaces to make up the 16 characters; then the firmware version numbers (138, 102 and 129 in my case), and then some zeros
• 31000-31038: Solar-related information (see decode below). I don't currently have a battery connected so I expect some of the registers I haven't decoded are related to that.
• 44,000-44,002: So far these have always contained the values 0; 0; 25,704 (=0x6468 or b0110 0100 0110 1000). It's not clear to me what this is, I would guess configuration settings, but I have not beeen able to map it on to any of the tables in the various manuals I have found floating around on the internet. I am interested in whether anyone can shed any light on this. Perhaps someone has the correct protocol manual for my inverter?

My decode of registers 31,000-31,038:
All the values appear to be signed, and where a multiplier is listed they are fixed point values (x10 means a reported value of 2 should be interpreted as 0.2, x100 means 2 -> 0.02)
31000 PV1 Voltage x10
31001 PV1 Current x10
31002 PV1 Watts
31003 PV2 Voltage x10
31004 PV2 Current x10
31005 PV2 Watts
31006 Grid Voltage x10
31007 Generated AC Current x10
31008 Generated AC WattsCurrent x10
31009 Grid Frequency Hz x100
31010 unknown_1
31011 unknown_2
31012 unknown_3
31013 unknown_4
31014 Export Watts (negative = importing)
31015 unknown_5
31016 House Usage Watts
31017 unknown_6
31018 Ambient Temperature degrees C x10
31019 Inverter Temperature degrees C x10 (the fox cloud has these values transposed, but that makes no sense)
31020 Inverter Battery Voltage x10
31021 Inverter Battery Current x10
31022 unknown_8
31023 unknown_9
31024 unknown_10
31025 unknown_11
31026 unknown_12
31027 Inverter State (0 = Standby, 1 = (attempting to) Start Generation, 2 = On Grid, other values = ?)
31028 Possibly the “Inverter Mode” from the Fox protocol manuals
31029 Possibly the CT meter type from the Fox protocol manuals
31030 unknown_13
31031 unknown_14
31032 unknown_15
31033 unknown_16
31034 unknown_17
31035 unknown_18
31036 unknown_19
31037 unknown_20
31038 unknown_21
(there is no unknown_7 as I worked out what that was).

Can anyone shed any light on any of the unknown values? In particular the use of registers 300+ and 44000+?

[spmaid]

What software are you using to poke the MODBUS LAN interface, I tried a few things, but guessing I didnt know what to do.

[mdt3k]

I started with Simply Modbus TCP Client (trial version). It's a bit painful (in particular lots of the settings change themselves when you change other settings), but with the following settings I can make it work. I ended up writing some python scripts using modbus-tk. I can share those if there is interest?

Simply modbus settings:
IP stuff - defaults but with the box's IP entered
First register 30,000 (or any valid number from my list above)
No of registers 1, or however many you want to retrieve
Function code: 3 (or 4 for registers 300-399)
Minus offset: 0
16 bit registers (it likes to change this)
ticked the boxes for high byte first, high word first

[StealthChesnut]

I did try the LAN port first, but couldn't get any data from it. I've just retried with your suggestions and I'm getting the same. I'll do some more digging in this to switch over to prefer a TCP/IP based approach, and have the direct wired connection as a backup.

Thanks for raising this @mdt3k - I'd written it off as a bad implementation/interface!

[spmaid]

would be great if we could get LAN working

[mdt3k]

@StealthChesnut it sounds like you've made it go, so I guess my basic python scripts (using modbus-tk) are probably not of interest?

[StealthChesnut]

I was also using Simply client at first, but I find it much easier to use NodeRed (there's modbus and modbusTCP nodes). It's not as easy to scan for new addresses, but trying the addresses you suggested has worked and given some data.

I don't think I'll need the scripts as Home Assistant should handle everything, but I may come back to you! Also, as the register addresses appear to be different feel free to share any findings. I'll be updating the reference guide as you've suggested.

This will likely take a little time to get in, but it'll be a much preferable approach (i.e. no additional wiring into the connector) and just a simple network cable to attach. Good to have the non-network option for those with their network security paranoia level set to high!

[mdt3k]

Today I have been hammering the LAN port a little. The inverter's registers are updated every 0.5 seconds; I have not seen a register updated faster than that (the fastest poll rate I have achieved is 100ms between requests).

If you want to record 'all' the data the inverter produces, setting the time between polls to something slightly lower than 0.5 seconds will make sure nothing is missed.

[mdt3k]

Overnight I did see some other values in the 44k registers. They were only present for single 15-second periods, and they look a lot like bit-fields, so I'm now pretty confident that they are status information. It's possible the box latches them until they're read rather than them being fleeting, this also begs the question whether them being read by the wifi-dongle resets them.

The other values I saw in the 44k registers were:

• 02:19:45 - 0x0 0x803 0x4000 - Nothing leaps out at me about this, it was dark, the inverter was in its 'standby' mode and I don't have a battery (yet)
• 04:47:15 - 0x0 0x803 0x0 - This is more interesting as it was 2 minutes into an aborted attempt by the inverter to start generating (the panels were just waking up, but there was not enough sun to get things going - the inverter continued in startup for about another minute before going back to standby )

[mdt3k]

I have tried reading the 44k registers at different rates (up to once every 5-seconds so far), and reading them more frequently yields more non-0x6468 codes. It has also lead to some new (to me) codes and codes being generated during the day. I have now (just) set the logging for these registers to every second, I will let this run for a day or two, attempt to analyse the results and report back if I can decode anything extra.

It would be interested to see the 44k codes anyone else has (or has managed to decode) along with matching data from the 31k registers, as I suspect the more data points I have the easier it will be to decode/infer things.

[spmaid]

really interested in helping here, I guess I need to get a NodeRed setup and the ModbusTCP node going? Any pointers on how to start?

[StealthChesnut]

Import this into NodeRed to get you started, then update the IP address of your inverter in the modbustcp node. Be aware - my inverter has stopped responding once, so not sure if it doesn't like how this node (or the global connection node) communicates with it?

Once imported you should have a dashboard at https://:1880/endpoint/ui/

[{"id":"5adc9ded69c0f7aa","type":"modbustcp-read","z":"8656fb0e95416d5d","d":true,"name":"","topic":"","dataType":"HoldingRegister","adr":"31000","quantity":"32","rate":"15","rateUnit":"s","server":"bdab53fd719e2963","ieeeType":"off","ieeeBE":true,"x":150,"y":160,"wires":[["b7df39a9c492d895","d8b2fd19a06b1dcb"]]},{"id":"d8b2fd19a06b1dcb","type":"split","z":"8656fb0e95416d5d","name":"","splt":"\\n","spltType":"str","arraySplt":1,"arraySpltType":"len","stream":false,"addname":"","x":350,"y":180,"wires":[["37f6dc4216e327f5"]]},{"id":"37f6dc4216e327f5","type":"switch","z":"8656fb0e95416d5d","name":"","property":"parts.index","propertyType":"msg","rules":[{"t":"eq","v":"0","vt":"num"},{"t":"eq","v":"1","vt":"num"},{"t":"eq","v":"2","vt":"num"},{"t":"eq","v":"3","vt":"num"},{"t":"eq","v":"4","vt":"num"},{"t":"eq","v":"5","vt":"num"},{"t":"eq","v":"6","vt":"num"},{"t":"eq","v":"7","vt":"num"},{"t":"eq","v":"8","vt":"num"},{"t":"eq","v":"9","vt":"num"}],"checkall":"false","repair":false,"outputs":10,"x":510,"y":180,"wires":[["b2038aee5b3c6033"],["d27d0429717ba5af"],["1476e9c37760334d"],["435c66e222ee2298"],["6ff1dc6292b4e15e"],["065e49d28ec0d98f"],["6541286773332914"],["c4c5d4492d16d234"],["4d7f456fe4b3e127"],["42ae3d3ae432aec5"]]},{"id":"bdb73bce01b69189","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"e62fb0a5.a7689","order":2,"width":0,"height":0,"label":"PV1 Volts","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":880,"y":40,"wires":[[]]},{"id":"b2038aee5b3c6033","type":"function","z":"8656fb0e95416d5d","name":"Scale","func":"msg.payload = msg.payload / 10;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":690,"y":40,"wires":[["bdb73bce01b69189"]]},{"id":"93856bd67a006ce3","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"e62fb0a5.a7689","order":2,"width":0,"height":0,"label":"PV1 Current","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":890,"y":80,"wires":[[]]},{"id":"d27d0429717ba5af","type":"function","z":"8656fb0e95416d5d","name":"Scale","func":"msg.payload = msg.payload / 10;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":690,"y":80,"wires":[["93856bd67a006ce3"]]},{"id":"1476e9c37760334d","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"e62fb0a5.a7689","order":2,"width":0,"height":0,"label":"PV1 Power","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":890,"y":120,"wires":[[]]},{"id":"435c66e222ee2298","type":"function","z":"8656fb0e95416d5d","name":"Scale","func":"msg.payload = msg.payload / 10;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":690,"y":160,"wires":[["6c2eb381eaee5f72"]]},{"id":"6ff1dc6292b4e15e","type":"function","z":"8656fb0e95416d5d","name":"Scale","func":"msg.payload = msg.payload / 10;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":690,"y":200,"wires":[["500fcc3d5b6a226d"]]},{"id":"6c2eb381eaee5f72","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"07bfcf34e2328d99","order":2,"width":0,"height":0,"label":"PV2 Volts","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":880,"y":160,"wires":[[]]},{"id":"500fcc3d5b6a226d","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"07bfcf34e2328d99","order":2,"width":0,"height":0,"label":"PV2 Current","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":890,"y":200,"wires":[[]]},{"id":"065e49d28ec0d98f","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"07bfcf34e2328d99","order":2,"width":0,"height":0,"label":"PV2 Power","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":890,"y":240,"wires":[[]]},{"id":"6541286773332914","type":"function","z":"8656fb0e95416d5d","name":"Scale","func":"msg.payload = msg.payload / 10;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":690,"y":280,"wires":[["27ba8dca084f5c86"]]},{"id":"27ba8dca084f5c86","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"9393fe97d1b60194","order":2,"width":0,"height":0,"label":"Grid Voltage","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":890,"y":280,"wires":[[]]},{"id":"c4c5d4492d16d234","type":"function","z":"8656fb0e95416d5d","name":"Scale","func":"msg.payload = msg.payload / 10;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":690,"y":320,"wires":[["cc1b3d328cc5542b"]]},{"id":"cc1b3d328cc5542b","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"9393fe97d1b60194","order":2,"width":0,"height":0,"label":"Generated AC Current ","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":920,"y":320,"wires":[[]]},{"id":"42ae3d3ae432aec5","type":"function","z":"8656fb0e95416d5d","name":"Scale","func":"msg.payload = msg.payload / 100;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":690,"y":400,"wires":[["48dcc20d866fb6dc"]]},{"id":"48dcc20d866fb6dc","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"9393fe97d1b60194","order":2,"width":0,"height":0,"label":"Grid Freq","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":880,"y":400,"wires":[[]]},{"id":"4d7f456fe4b3e127","type":"function","z":"8656fb0e95416d5d","name":"Scale","func":"msg.payload = msg.payload / 10;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":690,"y":360,"wires":[["68dad8dc9806422e"]]},{"id":"68dad8dc9806422e","type":"ui_chart","z":"8656fb0e95416d5d","name":"","group":"9393fe97d1b60194","order":2,"width":0,"height":0,"label":"Generated AC Power","chartType":"line","legend":"false","xformat":"HH:mm:ss","interpolate":"linear","nodata":"","dot":false,"ymin":"","ymax":"","removeOlder":1,"removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"className":"","x":920,"y":360,"wires":[[]]},{"id":"bdab53fd719e2963","type":"modbustcp-server","d":true,"name":"Inverter","host":"192.168.1.1","port":"502","unit_id":"247","reconnecttimeout":"15"},{"id":"e62fb0a5.a7689","type":"ui_group","name":"Array 1","tab":"67b4579.231fda8","order":1,"disp":true,"width":"6","collapse":false,"className":""},{"id":"07bfcf34e2328d99","type":"ui_group","name":"Array 2","tab":"67b4579.231fda8","order":2,"disp":true,"width":"6","collapse":false,"className":""},{"id":"9393fe97d1b60194","type":"ui_group","name":"Unknown","tab":"67b4579.231fda8","order":3,"disp":true,"width":"6","collapse":false,"className":""},{"id":"67b4579.231fda8","type":"ui_tab","name":"Home","icon":"dashboard","disabled":false,"hidden":false}]

[spmaid]

great, will give it a try and report back any issues

[StealthChesnut]

Thread to capture identified registers:

31022 unknown_8 - Battery draw / discharge, in W. wraps around from 0 to 65535 to go negative indicating charge rate in W
31023 unknown_9 - Think this is battery temp, or ambient temp. With the nearby registers being battery related, likely battery temp
31024 unknown_10 - Battery SoC (state of charge), in %

[JamesWJPS]

Just to check I assume that the wifi dongle supplied by fox can’t be interfaced yet?

If I want that to stay in can I add another so I can keep the wifi dongle in place and us RS232?

James

[ajmayers]

Hi

I have just had an H1 inverter installed and really keen to be able to get the data from it locally, as I want to be able to use the data in my own dashboards.

Ultimately I want it in Home Assistant, but I haven't been able to access the data at all yet.
Has anyone had any luck in getting the data via the LAN cable successfully? I have plugged into my LAN and assigned it a static IP, but nothing seems to talk to it - should I instead have a direct connection to a PC?

I tried the Node-Red code on a docker version on my network above and got error messages, so not sure I am doing it correctly.

Any help much appreciated, otherwise I will look at the WIFI/LAN RS485 module, but not sure how I connect the cables to the COM port..?

Thanks

[mdt3k]

I can't speak to the Node Red related stuff, but if you were getting Modbus error-responses (e.g. illegal address), rather than just being ignored, then you are on the right track and you can try some different register & function values. If you were having Node Red related issues then the free trial version of Simply Modbus works sufficiently well (with some persuasion) to let you test out the modbus side. To be clear, I can't say I'm recommending Simply Modbus, but I was able to make it work...

[StealthChesnut]

@ajmayers Did you update the global modbustcp node IP address?

I am now getting data from the LAN port, so if you can wait a little there should be a LAN version.

[ajmayers]

I have not managed to get it working yet, so probably doing something wrong - more than happy to wait for a proper written up solution if you have managed to get it working - amazing work! :)

Just out of curiosity? Do you direct connect Ethernet to a PC or can it go via a network switch? Also if direct to PC - do you have to use a cross over cable?

[StealthChesnut]

I'm going from Inverter, through a switch to a server.

[ajmayers]

Thanks for confirmation - I had been having issues with anything connecting at all - and I have been playing with some settings.

After enabling "Remote Control" in the menu on the inverter I now seem to be able access data by polling through a modbus program on my PC. Not sure if enabling this is what got it working, or not, but I am happy I can now see something!

I now look forward to your implementation when you are able to do it :)

[smiffy6969]

Hi, New here, had a fox system for a year now, and the software/cloud is a total joke...

Im reading this as i have been looking for something local, and because i dont like the idea of the setup being tweakable from the net (its chinese and the way things are right now i would rather it be disconnected form the net).

Now i read this and notice you are talking to registers through the rs485, which i had thought of playing with, but then i would have to reverse engineer codes and such as you have done...

thinking about this, this whole setup is not running on http sockets, two expensive to maintain... its not working via incomming http requests, as most routers would block incomming and a handshake would be needed to grab the IP which will more than likely be dynamic from provider. So the only way it can be working and in a way thats scalable without costs for socket servers, would be polling. Long polling is more than likely how its working, wiht a preset DNS/IP to send its poll to. I would guess the setting of settings then happens this way too, the system polls, gets a response for any cached settings updates (this could be verified by changing battery settings and seeing how long it takes for the settings to change on the inverter.

I really think this could be handled all via http over lan, I also guess that the data long polling to a server would be more readable in data form more than likely JSON or a bespoke serialzed dataset of an object/array.

Now i have tried sniffing the traffic on the net, looking for the ping and isolating the ip of the wifi dongle, but ive been having trouble finding it.

I had a thought, i can hit the wifi dongle on the inverter, and i can access the page to change the connection details it uses to connect to my virgin router, i have done this before. So why not use a proxy? Raspberry PI configured as an wireless access point...

then sniff the traffic, should be easier, you could even change the /etc/hosts file to divert all traffic to whatever.com to 127.0.0.1 local address. which you could setup a small API based local server running (i have an MVC stack i could use locally)... this would then have all incomming requests to the access point pi diverted from the preset address/ip it was going to at fox cloud and we could then see whats coming in and work out how to respond, as well how to respond with cached settings updates. I know i can only update battery levels from fox cloud but i also know the installer can change way more remotely.

Any thoughts on this? it may allow for a lan based connection over wifi or ethernet and would open up a lot for caching all data, maybe settings changes if thats how its working and connection to the ev setup outside the home through automated pushes of dynamic ip change of the service provider with something like noip and a few incomming network routing options on your router.

I do have a few pis lying around, i can butcher my syncthing pi4 to do some tests (foxcloud is going down for a bit my provider told me, and to be honest its up and down like a meerkat looking for trouble on the best of days).

ta

Paul

[StealthChesnut]

Hi Paul, sorry for the long delay in replying!

When I was looking on how to get the data there were a few options:

• RS485 comms pins
• LAN port
• Wifi Dongle hack

I did try the LAN port, but didn't get anything from it. After reading up on how RS485 and modbus work I assumed it was a non-starter, and went for the comms port pins. I did see another project where someone had soldered connections onto the inside of the wifi-dongle to intercept the modbus traffic before it was sent over TCP/IP, but that was a step too far for me.

You might be able to MITM the traffic with a proxy, but given there's an accurate, configurable way to get the data over modbus and put it into home assistant I'm not sure what any other method would gain by home-brewing all of that. HA now does long term statistics for energy use & generation, so you have a locally hosted fox cloud replacement. By all means, expand on what your end goal is!

I'm looking to reverse out the addresses for the LAN connection when I get my workstation rebuilt. So far I can get NodeRed to talk to the LAN port, but not HomeAssistant iteself, so some more work to be done just yet.

[art103]

Thank you for all of the inputs and matching up of values.

I tweaked the modbus.yaml file in the repo to use the LAN ModBus addresses, and it is working great with HA.
Eventually I want to be able to control the charge / export settings to take advantage of Octopus Agile Export, but getting LAN based data is a good start!
modbus_lan.yaml

BTW, for very simple command line prodding, I used mbpoll.
./mbpoll 192.168.1.218 -a 247 -0 -1 -t 4 -r 31000:31040

My batteries should be arriving early August, so hoping to make more progress once those are installed.

[spmaid]

So can you force discharge/export the FoxESS Inverter? I've not seen any settings on the device or in app to do this? Although, it'd be great if you could do it via MODBUS!

[art103]

I may have been overly hopeful when reading the manual!

Force time use
Priority: battery>load>grid (when charging)
Priority: load>battery>grid (when discharging)
This mode applies the area that has electricity price between peak and valley. User can use off-peak electricity to charge the battery. The charging and discharging time can be set flexibly, and it also allows to choose whether charge

It looks like you can only force charging and not discharging through the menu on the inverter.
That's a pain because grid export at peak time was the main driver for getting a battery!

Plan B: Reverse engineer the RS485 Meter protocol to trick it into thinking the local load has gone up?

Edit:
Maybe not so crazy?
Compatible Meter type: DDSU666

[Daibutt]

@art103 See this post; https://www.facebook.com/groups/foxessownersgroup/permalink/1628380637544112/

[art103]

Thanks @Daibutt, unfortunately it is a private group and I do not have a FB account.
Is there any chance you could summarise?
Many thanks!

[JamesWJPS]

I was using the modbus_lan and it was working perfectly. I reset my ha to try and get the dashboard runnibg, and stupidly didnt take a copy of modbus_lan, and now the link isnt working :). Anyone able to send me it, or give me a new link?

James

[Daibutt]

@art103 Here you go Richard

[Richard Sharpe]
Hi there.
Just managed controlled battery dump to grid.
I wired an intermediate switch on the CT grid clamp. Works as normal. When switch reverses wires. Inverter thinks power coming in and dumps to grid.
I'm not an expert in these things but seams to work. Must be conscious of amount of power going into grid. (Set max discharge rate).
I just wanted to see if it would work.
Hopefully you tech guys and get it so we can dump battery at higher price, to help level grid usage.

[William Eccles]
Very interesting, assume this would mess your app stats up but who cares if you generate £££

[Richard Sharpe]
unless they offer£2 on outgoing I don't think I'll bother. But just wanted to see if it worked.

[William Eccles]
yeh the cost of the cycle on the battery would cancel out any gains

[art103]

Many thanks, much appreciated.
I think the default export limit is 60KW, so that would be fun :D

When my prototype emulated DDSU666 meter gets off the ground, I'll start another thread and link there.

[StealthChesnut]

Quick update - LAN access is being worked on. In addition to the folks above I've got access as well so will be putting this in as an option.

[StealthChesnut]

LAN access now available. If you swap from USB to LAN then your sensors and energy dashboard should continue to work. The same sensor names have been used to make it all work the same way regardless of the connection method choice.

[C00K50N]

Perfect timing for the LAN access to become available! Not long after my PV install and just as I'm getting my head around HA and how I can get FoxESS to integrate with it.

I was using the Fox Cloud integration for the last week or two, but I'd prefer the Modbus / LAN integration to get more like real-time data. So... I've got some sensors working via the LAN now, but not all. I'm afraid my coding ability is next to zero, so I'm not sure what to look for to see if I've done anything wrong.

My grid_daily and feedin_daily figures are both 0kWh. My Grid consumption and FeedIn power are both 0kW. Can anyone help?

Separately, once I've got the LAN integration working, how do I delete the previous Fox Cloud integration? I've removed it from HACS but the sensors are still hanging around, albeit all listed as Unavailable.

[StealthChesnut]

This was a bug, and has been fixed. Just released v1.2.1 to include the fix.

One of the sensor names (Grid CT) in the USB connection setup had been renamed when looking at the LAN connection addresses. That's now been aligned (i.e. sensor.grid_export is now sensor.grid_ct), so the sensors that relied on that will now work.

[art103]

Regarding removing the old sensors, you can go to Settings, Devices, Entities and delete them from there. You may also need to remove it from your .yaml file if you added it manually (I did). It can take an hour (or two) for the statistics to update, but if you still get zero then there may be some more debugging... Do you get updates if you add the sensor to a dashboard?

On 6 Aug 2022, 17:21, at 17:21, C00K50N ***@***.***> wrote: Perfect timing for the LAN access to become available! Not long after my PV install and just as I'm getting my head around HA and how I can get FoxESS to integrate with it. I was using the Fox Cloud integration for the last week or two, but I'd prefer the Modbus / LAN integration to get more like real-time data. So... I've got some sensors working via the LAN now, but not all. I'm afraid my coding ability is next to zero, so I'm not sure what to look for to see if I've done anything wrong. My grid_daily and feedin_daily figures are both 0kWh. My Grid consumption and FeedIn power are both 0kW. Can anyone help? Separately, once I've got the LAN integration working, how do I delete the previous Fox Cloud integration? I've removed it from HACS but the sensors are still hanging around, albeit all listed as Unavailable. -- Reply to this email directly or view it on GitHub: #25 (comment) You are receiving this because you were mentioned. Message ID:

***@***.***>

[C00K50N]

Thank you! That's the old sensors cleared via Settings > Devices > Entities.

It's been around 7 hours now, and still nothing on those particular sensors. Nothing when I add a gauge or anything to a dashboard either. Other sensors are fine - e.g. PV1-Power, PV2-Power, Load Power all seem to be working fine and have been since I installed the LAN integration.

[StealthChesnut]

Fixed bug - see this comment:
#25 (reply in thread)

[C00K50N]

Ah, thank you. Will take a look at the new release now.

[art103]

Depending on how HA has coped with the move to the new sensors (and when the old ones were deleted), you may need to modify the integrations. My guess is that you now have a grid_consumption2 and feed_in_power2 sensors, which are not used by the grid_consumption_sum and feedin_sum integrations. This means the old statistics are still trying to use the old Fox Cloud sensors, which are now deleted. I didn't use HACS (I manually edited the .yaml files), so I'm not sure how to get from where you are now to a working system. If you can find those entries in configuration.yaml, then it should be an easy update to the _2 versions, otherwise I'll need to defer to a HACS expert :) August 6, 2022 8:11 PM, "C00K50N" ***@***.*** ***@***.******@***.***>)> wrote: Thank you! That's the old sensors cleared via Settings > Devices > Entities. It's been around 7 hours now, and still nothing on those particular sensors. Nothing when I add a gauge or anything to a dashboard though. Others are fine - e.g. PV1-Power, PV2-Power, Load Power all seem to be working fine and have been since I installed the LAN integration. — Reply to this email directly, view it on GitHub (#25 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAQPYXJXEL5AN4CLIAS6YR3VX22GHANCNFSM5YIAPM3A). You are receiving this because you were mentioned.Message ID: ***@***.***>

[C00K50N]

Thanks again for your suggestions. I don't appear to have any _2 sensors unfortunately. The previous integration I was using was the Fox Cloud one (written by someone else I think), not an earlier non-LAN version of this Modbus integration. So the sensors had different names.

It's not the end of the world just now, I can get the grid activity from our MyEnergi (Zappi), but that's every 15sec or so. It would be nice to have it real-time like the generation is now.

Another query to add to it... I'm using a Statistics Graph card to trace power usage for the previous 24hrs (generation, house load, car charging, grid import/export), and I'd like total generation to be one line rather than split into PV1 and PV2. Is that possible?

[StealthChesnut]

Can you check if you have a sensor called pv_total_power? That should be present and will show both pv1 and pv2 added together. I have 2 pv panel arrays so have included this.

[C00K50N]

It doesn't look like I have a sensor called that... I have PV Power Now, which I'm using with a Gauge card, but only the separate ones mentioned above seem to be available to use in the Statistics Graph card, as far as I can see. I'm conscious that there's every chance I'm doing something wrong here, I'm very much just muddling through so please bear with me!

[C00K50N]

(not sure if this image upload will work, but this is a screenshot of my dashboard)

[C00K50N]

@StealthChesnut Thank you for the updated code. I now have Grid Consumption and FeedIn gauges working. And they broadly match the values from the CTs feeding our MyEnergi Zappi which I've used as my measuring stick up to now. Spot on!

I see I also now have a Grid CT sensor which I can use to chart grid use, although it seems to be the inverse... See screenshot below - if you look at the right hand end the lilac Grid CT is the inverse of the Load Power:

[C00K50N]

Same chart but showing the MyEnergi grid rather than the Fox Grid CT...

[Daibutt]

Yeah you could just make a template sensor that is something like ;

• platform: template
  sensors:
  my_grid_ct:
  friendly_name: "Grid CT backwards"
  unit_of_measurement: 'kW'
  device_class: power
  value_template: >
  {{ states('sensor.grid_ct') | float(default=0) * -1 }}

Syntax might not be entirely correct but you get the drift hopefully

[C00K50N]

Thanks again. I gave this a try but my lack of understanding of the coding has left me stuck... I entered the above (syntaxed to match other sensors) to my configuration.yaml, but it didn't like it - failed the "check configuration". I notice that there's no reference to sensor.grid_ct in the configuration.yaml, only in the modbusLAN.yaml. But I presume I shouldn't edit the modbusLAN.yaml? Is there somewhere else the sensor.grid_ct is referenced, and therefore somewhere else I should be adding that template sensor?

Sorry for my lack of knowledge.

[StealthChesnut]

Investigating this in a new issue - #34

I'll set up my test environment and see what figures I get. It looked OK with a brief test (at least, it looked better than just zeros!) but I'll see what it shows. I see you've got a template sensor set up - if I change this sensor then it'll likely mess up your template, so make sure you remember where the template is / how you made it.

[C00K50N]

Will do. Thanks so much!

[Daibutt]

No worries, I'm guessing you have the grid_ct sensor but only based on your screenshot;

You can check you have it by looking at system/entities;

Did you add the new template sensor after existing ones in configuration.yaml? (It does not need changes to modbus.yaml)
The errors could be indent/spaces as this is important. Paste a screenshot of relevant part of your config file (not a copy/paste as that messes up the indents) and I can take a look

[C00K50N]

Thank you. Yes, I do indeed have the grid_ct sensor, it's listed in System / Entities, and also on the Overview dashboard.

I first added the new template sensor after the existing ones, and therefore not repeating the '- platform: template' or ' sensors:' lines. But I've tried again including those two lines, still no luck. Here's what I've added so you can see if I've messed up the indentation or anything:

and this is the error message I get when checking the configuration:

Thank you for your help, it's much appreciated.

[C00K50N]

Found it! Sorry, silly error, I added a further closed bracket. That's my mistake with what I copy / pasted to try and get the syntax right. D'oh!

[C00K50N]

Hmm... OK, the new inverse template sensor is definitely working. But the next challenge is getting it into my graph...

If I'm reading things correctly it may need to have a measurement state_class in order to be usable in a statistics graph, but I can't seem to add that state_class to the sensor. Is there another way?

[StealthChesnut]

your my_grid_ct sensor may not be showing in that graph as you've defined it with different units. Your graph is in W, but the sensor is in kW. If I define your (W based) sensor in my (kW based) config I get this where the W values are put into a different graph:

Try this as your sensor template and see if it comes into your graph:
my_grid_ct: friendly_name: "Grid CT Inverse" unit_of_measurement: 'W' device_class: power value_template: > {% if (states('sensor.grid_ct') | float(default=0) ) < 0 %} {{ states('sensor.grid_ct') | float(default=0) * -1000 }} {% else %} 0 {% endif %}

For the measurement class, this might be because there's two syntax for defining template sensors and the old method doesn't support setting state class. At the moment these templates are all in the old method. I'll open an issue to convert them to the new syntax.

If you want to have a go at making your own in the meantime the documentation page is here: https://www.home-assistant.io/integrations/template/

[StealthChesnut]

Closing this discussion thread as access via the LAN port has now been enabled. Any problems please open an issue.

[StealthChesnut]

I'll be updating the integration to use this, but the default refresh rate will be at lowest 5s. If you go faster than that home assistant complains in the logs that you might see performance issues.

…

On Sat, 11 Jun 2022, 19:22 mdt3k, ***@***.***> wrote: Today I have been hammering the LAN port a little. The inverter's registers are updated every 0.5 seconds; I have not seen a register updated faster than that (the fastest poll rate I have achieved is 100ms between requests). If you want to record 'all' the data the inverter produces, setting the time between polls to something slightly lower than 0.5 seconds will make sure nothing is missed. — Reply to this email directly, view it on GitHub <#25 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALFO3FHLK2DRQIB77I6SLMDVOTKODANCNFSM5YIAPM3A> . You are receiving this because you were mentioned.Message ID: <StealthChesnut/HA-FoxESS-Modbus/repo-discussions/25/comments/2929692@ github.com>