H3-PRO series #516
Replies: 26 comments 96 replies
-
|
I hadn't heard it was coming out. With a bit of help, I'm sure we can get it working. What error message do you get when you try to connect? If you send that to me, I can release a beta version which tries to talk to it as if it was a normal H1, see whether that works. Alternatively if you happen to have documentation of the list of registers it supports, we can work through that. |
Beta Was this translation helpful? Give feedback.
-
|
Did not recognise inverter model '' ([8224, 18483, 11600, 29295, 11570, 12334, 12320, 8224, 1, 63232, 0, 5130, 256, 0, 0]) |
Beta Was this translation helpful? Give feedback.
-
|
I guess using the H3 model isn´t going to work. I have that now but getting this error: I have managed to find some addresses with help of modbus poller but I guess it´s best to wait until I get the documents. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, that looks completely different to what we've seen so far! |
Beta Was this translation helpful? Give feedback.
-
|
It actually worked the first day with the old H3 registers but when FoxESS updated the firmware due another issue these modbus registers stopped to work. I now find values on other register addresses manually. I have been promised a document but I think they still are working on changes in the firmware. |
Beta Was this translation helpful? Give feedback.
-
|
I´m still waiting for documents but have made som address scans and begin to find vaules that I think is OK. Will continue to find more :) |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone, now I also have an H3-Pro inverter. My first attempts to read the device via Modbus largely confirm @MattiasLindahl 's statements regarding the changed memory addresses. The name of the inverter is still at address 30000, but there are only 8 registers, with each register containing 2 characters (highbyte, lowbyte). 30016 is followed by the serial number, which also has 8 registers (15 characters + 0x1). In the next few days I will try to read out all accessible registers, although it will certainly be difficult to recognize the meaning of each cell. I hope that we will manage to get the new FoxESS flagship into the great foxess_modbus integration. Thanks and regards |
Beta Was this translation helpful? Give feedback.
-
|
Great thanks! I just used modpoll, but the interface that @MattiasLindahl used looks like it's probably easier to work with for mapping things out. |
Beta Was this translation helpful? Give feedback.
-
|
I am working on it ... |
Beta Was this translation helpful? Give feedback.
-
|
Here is the register assignment for the H3-Pro, as far as I found out (green: almost certainly correct, gray: probably, red: no idea). Some values (battery temperature, type and serial numbers of the battery modules, ...) I cannot locate at all. Maybe the new H3-Pro also partially communicates not via tcp, but via udp? Since Fox ESS will soon be sending me the official registry plan - and I have to sign an NDA for it - I unfortunately cannot publish any further information here. I hope that enough people now own an H3-Pro and will help decrypt it. Best regards |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Looks like there's some similarities with the G2, so it probably make sense to get to get #585 in first. |
Beta Was this translation helpful? Give feedback.
-
|
Yes I think both inverters are based on G2 generation so it should be the same registers.
…________________________________
Från: Antony Male ***@***.***>
Skickat: Saturday, April 6, 2024 4:46:40 PM
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Looks like there's some similarities with the G2, so it probably make sense to get to get #585<#585> in first.
—
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your patience! I've finally got an initial stab at H3-Pro support into the pre-release v1.12.0b1. Would you mind just doing a sanity-check of all of the entities? The main thing I'm concerned about is the same (whether the value is 10x what it should be, or 1/10th of what it should be, etc) -- the H3-Pro differs from prevoius inverter models quite a bit here. Also the sign of some of the data wasn't clear from the spec, so for example it might show that the battery is charging when it's actually discharging, etc. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi!
I get this error message when connecting:
Details: unbalanced parenthesis at position 17
…________________________________
Från: Antony Male ***@***.***>
Skickat: Saturday, April 27, 2024 12:51:04 PM
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Thanks for your patience! I've finally got an initial stab at H3-Pro support into the pre-release v1.12.0b1.
Would you mind just doing a sanity-check of all of the entities? The main thing I'm concerned about is the same (whether the value is 10x what it should be, or 1/10th of what it should be, etc) -- the H3-Pro differs from prevoius inverter models quite a bit here. Also the sign of some of the data wasn't clear from the spec, so for example it might show that the battery is charging when it's actually discharging, etc.
Thanks!
—
Reply to this email directly, view it on GitHub<#516 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MMZCNNJU6J56DPOVVYLY7N7JRAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENBUGYYDQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Best regards
Mattias Lindahl
IT Manager
____________________________________________________
ProfilGruppen Extrusions AB
Box 36, 364 21 Åseda
E-mail: ***@***.***
Tel: +46 474 55039
Mob: +46 73 230 05 90
www.profilgruppen.se
____________________________________________________
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed.
If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited.
If you have received this communication in error, please notify the author by replying to this e-mail immediately.
|
Beta Was this translation helpful? Give feedback.
-
|
Damnit. That should be fixed in v1.12.0b2. |
Beta Was this translation helpful? Give feedback.
-
|
Hi!
Now it’s better 😅 some registers seems to not be good but I’l send some screenshots tomorrow if it’s just temporary since there is no sun now.
…________________________________
Från: Antony Male ***@***.***>
Skickat: Saturday, April 27, 2024 9:55:45 PM
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Damnit. That should be fixed in v1.12.0b2.
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM64EMS22Z2PWFALB23Y7P7EDAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENBXGY2TI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Best regards
Mattias Lindahl
IT Manager
____________________________________________________
ProfilGruppen Extrusions AB
Box 36, 364 21 Åseda
E-mail: ***@***.***
Tel: +46 474 55039
Mob: +46 73 230 05 90
www.profilgruppen.se
____________________________________________________
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed.
If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited.
If you have received this communication in error, please notify the author by replying to this e-mail immediately.
|
Beta Was this translation helpful? Give feedback.
-
|
Cheers! In fully expecting there to be issues - it was a chunk of (error prone) manual work, and the spec was fairly unclear in parts. |
Beta Was this translation helpful? Give feedback.
-
|
Yes of course… I found it to be very good, about 95% correct I think without having checked everything yet.
…________________________________
Från: Antony Male ***@***.***>
Skickat: Sunday, April 28, 2024 9:44:28 PM
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Cheers! In fully expecting there to be issues - it was a chunk of (error prone) manual work, and the spec was fairly unclear in parts.
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MMZW27T45DQZJZ3LIALY7VGRZAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENJVGM3TS>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Best regards
Mattias Lindahl
IT Manager
____________________________________________________
ProfilGruppen Extrusions AB
Box 36, 364 21 Åseda
E-mail: ***@***.***
Tel: +46 474 55039
Mob: +46 73 230 05 90
www.profilgruppen.se
____________________________________________________
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed.
If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited.
If you have received this communication in error, please notify the author by replying to this e-mail immediately.
|
Beta Was this translation helpful? Give feedback.
-
|
As you mentioned it’s hard to know about the division of those values by 10 or what it said.
But now I have seen that todays charge of batteries are one tenth in your integration so it should be changed. You are showing 2,57kWH but my values are 25,7 kWh
Other values that are unknown/not readed are:
Battery 2 Discharge (W)
Inverter Battery 2 Power (W)
Inverter Current R, S and T
All other seems OK for now.
…________________________________
Från: Antony Male ***@***.***>
Skickat: Sunday, April 28, 2024 9:44:28 PM
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Cheers! In fully expecting there to be issues - it was a chunk of (error prone) manual work, and the spec was fairly unclear in parts.
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MMZW27T45DQZJZ3LIALY7VGRZAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENJVGM3TS>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Best regards
Mattias Lindahl
IT Manager
____________________________________________________
ProfilGruppen Extrusions AB
Box 36, 364 21 Åseda
E-mail: ***@***.***
Tel: +46 474 55039
Mob: +46 73 230 05 90
www.profilgruppen.se
____________________________________________________
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed.
If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited.
If you have received this communication in error, please notify the author by replying to this e-mail immediately.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks! I'll tweak that.
What precisely do you mean by "Unknown / not readed? |
Beta Was this translation helpful? Give feedback.
-
Does that apply to all of the other "xxx today" and "xxx total" sensors as well? |
Beta Was this translation helpful? Give feedback.
-
|
It’s simply no value being read. It’s all values of Battery 2 that’s weird. I read for example address 39235 for Battery 2 power and it’s working for both charge and discharge with just using “inverted negative” values as charge.
…________________________________
Från: Antony Male ***@***.***>
Skickat: Monday, April 29, 2024 7:11:15 PM
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Thanks! I'll tweak that.
Other values that are unknown/not readed are
What precisely do you mean by "Unknown / not readed?
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM3P7CINKHFHYSB7MMTY7Z5LHAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENRVHA4DI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Best regards
Mattias Lindahl
IT Manager
____________________________________________________
ProfilGruppen Extrusions AB
Box 36, 364 21 Åseda
E-mail: ***@***.***
Tel: +46 474 55039
Mob: +46 73 230 05 90
www.profilgruppen.se
____________________________________________________
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed.
If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited.
If you have received this communication in error, please notify the author by replying to this e-mail immediately.
|
Beta Was this translation helpful? Give feedback.
-
|
What does the actual entity show? Can you take a screenshot? When you read 39235, is that using something like modpoll, or are you looking at the corresponding entity? What does "inverted negative" mean? The opposite of negative? |
Beta Was this translation helpful? Give feedback.
-
|
("Unknown" typically means the value is being read, but we think that the value is invalid for some reason. In this case, there will be error messages in the log) |
Beta Was this translation helpful? Give feedback.
-
|
Ok, here is some rows of the log.
```
2024-04-30 09:17:17.889 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4800: 480.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:17.890 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3328000: -3328.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:17:17.890 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-165412865: 165412.865) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:33.154 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:33.155 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4700: 470.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:33.155 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-160956417: -160956.41700000002) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:17:33.155 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4600: 460.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:33.155 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3148000: -3148.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:17:33.155 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-160956417: 160956.41700000002) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4600: 460.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-161742849: -161742.84900000002) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:17:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4600: 460.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:17:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3185000: -3185.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:17:47.895 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-161742849: 161742.84900000002) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:03.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4700: 470.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:03.150 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4800: 480.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:03.150 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-170655745: -170655.745) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:18:03.150 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4800: 480.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:03.150 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3359000: -3359.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:18:03.150 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-170655745: 170655.745) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:17.899 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4600: 460.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:17.900 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4700: 470.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:17.900 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-165937153: -165937.153) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:18:17.900 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4700: 470.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:17.900 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3246000: -3246.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:18:17.900 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-165937153: 165937.153) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:33.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4900: 490.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:33.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (5100: 510.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:33.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-173735937: -173735.937) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:18:33.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (5000: 500.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:33.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3459000: -3459.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:18:33.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-173735937: 173735.937) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:47.904 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4600: 460.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:47.904 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4800: 480.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:47.904 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-164167681: -164167.681) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:18:47.904 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4700: 470.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:18:47.904 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3269000: -3269.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:18:47.904 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-164167681: 164167.681) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:03.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4400: 440.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:03.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:03.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-163315713: -163315.71300000002) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:19:03.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4600: 460.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:03.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3149000: -3149.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:19:03.149 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-163315713: 163315.71300000002) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:17.899 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4600: 460.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:17.899 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4700: 470.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:17.899 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-163250177: -163250.177) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:19:17.900 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4700: 470.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:17.900 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3255000: -3255.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:19:17.900 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-163250177: 163250.177) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:33.234 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4400: 440.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:33.234 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:33.234 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-159252481: -159252.481) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:19:33.234 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:33.234 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3115000: -3115.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:19:33.234 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-159252481: 159252.481) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (4800: 480.0) for entity 'sensor.foxh3pro_inv_current_r' address(es) '[39127, 39126]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (5000: 500.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-174522369: -174522.369) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:19:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (5000: 500.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
2024-04-30 09:19:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-3446000: -3446.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
2024-04-30 09:19:47.894 WARNING (MainThread) [custom_components.foxess_modbus.entities.modbus_entity_mixin] Value (-174522369: 174522.369) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
```
Best regards
[User photo]
Mattias Lindahl
IT Manager, ProfilGruppen Extrusions AB
***@***.***+46 474 55039 | ***@***.*** +46 73 230 05 90 | ***@***.*** www.profilgruppen.se<https://www.profilgruppen.se/>
***@***.*** ***@***.******@***.***>
***@***.***Box 36, 364 21 Åseda
[Logo]
[LinkedIn icon]<https://www.linkedin.com/company/profilgruppen-extrusions-ab>
[Instagram icon]<https://www.instagram.com/profilgruppen/>
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. If you have received this communication in error, please notify the author by replying to this e-mail immediately.
Från: Antony Male ***@***.***>
Skickat: den 29 april 2024 19:32
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
("Unknown" typically means the value is being read, but we think that the value is invalid for some reason. In this case, there will be error messages in the log)
-
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM5CVZ7HVLX6JS5X63TY7Z7Z5AVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENRWGA4DO>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Maybe this would be enough… 😊
Logger: custom_components.foxess_modbus.entities.modbus_entity_mixin
Källa: custom_components/foxess_modbus/entities/modbus_entity_mixin.py:177
integration: FoxESS - Modbus (dokumentation<https://github.com/nathanmarlor/foxess_modbus>, ärenden<https://github.com/nathanmarlor/foxess_modbus/issues>)
Inträffade först: 28 april 2024 kl. 20:51:09 (52326 händelser)
Senast loggade: 09:19:33
* Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
* Value (-159252481: -159252.481) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
* Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_t' address(es) '[39131, 39130]' failed validation against rule (Range : {'_min': 0, '_max': 100})
* Value (-3115000: -3115.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
* Value (-159252481: 159252.481) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
Best regards
[User photo]
Mattias Lindahl
IT Manager, ProfilGruppen Extrusions AB
***@***.***+46 474 55039 | ***@***.*** +46 73 230 05 90 | ***@***.*** www.profilgruppen.se<https://www.profilgruppen.se/>
***@***.*** ***@***.******@***.***>
***@***.***Box 36, 364 21 Åseda
[Logo]
[LinkedIn icon]<https://www.linkedin.com/company/profilgruppen-extrusions-ab>
[Instagram icon]<https://www.instagram.com/profilgruppen/>
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. If you have received this communication in error, please notify the author by replying to this e-mail immediately.
Från: Antony Male ***@***.***>
Skickat: den 29 april 2024 19:32
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
("Unknown" typically means the value is being read, but we think that the value is invalid for some reason. In this case, there will be error messages in the log)
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM5CVZ7HVLX6JS5X63TY7Z7Z5AVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENRWGA4DO>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
That's my mistake, I'll fix.
Weird. The values we're reading from "Battery 2 Power" and "Battery 2 Charge" are completely nonsensical. I'm not sure what to do about that. Do you have a second battery connected to your H3?
Odd. Do you know what you actual inverter output power was at the time? I suspect it wasn't 3MW... |
Beta Was this translation helpful? Give feedback.
-
|
Yes it seems like so
…________________________________
Från: Antony Male ***@***.***>
Skickat: Wednesday, May 1, 2024 3:25:26 PM
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
But now I have seen that todays charge of batteries are one tenth in your integration so it should be changed. You are showing 2,57kWH but my values are 25,7 kWh
Does that apply to all of the other "xxx today" and "xxx total" sensors as well?
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM2HLOEOSQ6EBOWLYBTZADUMNAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEOBVGIYTM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Best regards
Mattias Lindahl
IT Manager
____________________________________________________
ProfilGruppen Extrusions AB
Box 36, 364 21 Åseda
E-mail: ***@***.***
Tel: +46 474 55039
Mob: +46 73 230 05 90
www.profilgruppen.se
____________________________________________________
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed.
If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited.
If you have received this communication in error, please notify the author by replying to this e-mail immediately.
|
Beta Was this translation helpful? Give feedback.
-
|
Från: Antony Male ***@***.***>
Datum: onsdag, 1 maj 2024 15:36
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>, Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
That's my mistake, I'll fix.
Value (-159252481: -159252.481) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Value (-159252481: 159252.481) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
Weird. The values we're reading from "Battery 2 Power" and "Battery 2 Charge" are completely nonsensical. I'm not sure what to do about that. Do you have a second battery connected to your H3? Yes, I have two batteries connected. My own reading is OK.
Are you reading this exactly the same way as Battery 1 Power and Charge? Because those two is OK in your integration.
Value (-3115000: -3115.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Odd. Do you know what you actual inverter output power was at the time? I suspect it wasn't 3MW...
My reading is OK and here is my node-red screenshot.
***@***.***
***@***.***
***@***.***
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM4SAOMWJQDBS4ZJRQLZADVVFAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEOBVGMYTK>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Please use the github web interface rather than replying to emails. Attachments are not supported in emails, so I cannot see what you tried to send. |
Beta Was this translation helpful? Give feedback.
-
|
I also notice this in the log:
Logger: homeassistant
Källa: custom_components/foxess_modbus/modbus_controller.py:356
integration: FoxESS - Modbus (dokumentation<https://github.com/nathanmarlor/foxess_modbus>, ärenden<https://github.com/nathanmarlor/foxess_modbus/issues>)
Inträffade först: 30 april 2024 kl. 22:03:38 (4426 händelser)
Senast loggade: 16:29:57
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/foxess_modbus/modbus_controller.py", line 356, in _refresh
if self._remote_control_manager is not None:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ModbusController' object has no attribute '_remote_control_manager'. Did you mean: 'remote_control_manager'?
Från: Antony Male ***@***.***>
Datum: onsdag, 1 maj 2024 15:36
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>, Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
That's my mistake, I'll fix.
Value (-159252481: -159252.481) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Value (-159252481: 159252.481) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
Weird. The values we're reading from "Battery 2 Power" and "Battery 2 Charge" are completely nonsensical. I'm not sure what to do about that. Do you have a second battery connected to your H3?
Value (-3115000: -3115.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Odd. Do you know what you actual inverter output power was at the time? I suspect it wasn't 3MW...
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM4SAOMWJQDBS4ZJRQLZADVVFAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEOBVGMYTK>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Logger: homeassistant.components.select
Källa: helpers/entity_platform.py:356
integration: Välj (dokumentation<https://www.home-assistant.io/integrations/select>, ärenden<https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+select%22>)
Inträffade först: 30 april 2024 kl. 22:03:21 (1 händelser)
Senast loggade: 30 april 2024 kl. 22:03:21
Error while setting up foxess_modbus platform for select
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_setup_platform
await asyncio.shield(awaitable)
File "/config/custom_components/foxess_modbus/select.py", line 24, in async_setup_entry
async_add_devices(create_entities(SelectEntity, controller))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/foxess_modbus/inverter_profiles.py", line 337, in create_entities
return inverter_connection_type_profile_from_config(controller.inverter_details).create_entities(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/foxess_modbus/inverter_profiles.py", line 95, in create_entities
entity = entity_factory.create_entity_if_supported(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/foxess_modbus/entities/modbus_work_mode_select.py", line 26, in create_entity_if_supported
return ModbusWorkModeSelect(controller, self, address) if address is not None else None
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/foxess_modbus/entities/modbus_work_mode_select.py", line 40, in __init__
if controller.remote_control_manager is not None:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/foxess_modbus/modbus_controller.py", line 146, in remote_control_manager
return self._remote_control_manager
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ModbusController' object has no attribute '_remote_control_manager'. Did you mean: 'remote_control_manager'?
Från: Antony Male ***@***.***>
Datum: onsdag, 1 maj 2024 15:36
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>, Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
That's my mistake, I'll fix.
Value (-159252481: -159252.481) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Value (-159252481: 159252.481) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
Weird. The values we're reading from "Battery 2 Power" and "Battery 2 Charge" are completely nonsensical. I'm not sure what to do about that. Do you have a second battery connected to your H3?
Value (-3115000: -3115.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Odd. Do you know what you actual inverter output power was at the time? I suspect it wasn't 3MW...
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM4SAOMWJQDBS4ZJRQLZADVVFAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEOBVGMYTK>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Value (-3115000: -3115.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100}) This value has to be divided by 1000 to get kW.
Odd. Do you know what you actual inverter output power was at the time? I suspect it wasn't 3MW...
Från: Antony Male ***@***.***>
Datum: onsdag, 1 maj 2024 15:36
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>, Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
That's my mistake, I'll fix.
Value (-159252481: -159252.481) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Value (-159252481: 159252.481) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
Weird. The values we're reading from "Battery 2 Power" and "Battery 2 Charge" are completely nonsensical. I'm not sure what to do about that. Do you have a second battery connected to your H3?
Value (-3115000: -3115.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Odd. Do you know what you actual inverter output power was at the time? I suspect it wasn't 3MW...
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM4SAOMWJQDBS4ZJRQLZADVVFAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEOBVGMYTK>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
It's not clear whether you were trying to write anything here. Please do use the github interface, rather than replying to emails. The email interface is bad, and it makes it hard for me to see what you're trying to write. It also doesn't support threads, so your replies end up in the wrong place. |
Beta Was this translation helpful? Give feedback.
-
|
Hi!
Did you get some time to look at what’s left to make all sensors working?
…________________________________
Från: Antony Male ***@***.***>
Skickat: Wednesday, May 1, 2024 3:36:18 PM
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Value (4500: 450.0) for entity 'sensor.foxh3pro_inv_current_s' address(es) '[39129, 39128]' failed validation against rule (Range : {'_min': 0, '_max': 100})
That's my mistake, I'll fix.
Value (-159252481: -159252.481) for entity 'sensor.foxh3pro_invbatpower_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Value (-159252481: 159252.481) for entity 'sensor.foxh3pro_battery_charge_2' address(es) '[39236, 39235]' failed validation against rule (Range : {'_min': 0, '_max': 100})
Weird. The values we're reading from "Battery 2 Power" and "Battery 2 Charge" are completely nonsensical. I'm not sure what to do about that. Do you have a second battery connected to your H3?
Value (-3115000: -3115.0) for entity 'sensor.foxh3pro_inv_power' address(es) '[39135, 39134]' failed validation against rule (Range : {'_min': -100, '_max': 100})
Odd. Do you know what you actual inverter output power was at the time? I suspect it wasn't 3MW...
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MM4SAOMWJQDBS4ZJRQLZADVVFAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEOBVGMYTK>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Best regards
Mattias Lindahl
IT Manager
____________________________________________________
ProfilGruppen Extrusions AB
Box 36, 364 21 Åseda
E-mail: ***@***.***
Tel: +46 474 55039
Mob: +46 73 230 05 90
www.profilgruppen.se
____________________________________________________
Disclaimer: The content of this e-mail is intended solely for the use of the Individual or entity to whom it is addressed.
If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited.
If you have received this communication in error, please notify the author by replying to this e-mail immediately.
|
Beta Was this translation helpful? Give feedback.
-
|
Sorry, been busy. I'll have some time on Weds. |
Beta Was this translation helpful? Give feedback.
-
|
OK 😊 I understand…
Thanks!
Från: Antony Male ***@***.***>
Skickat: den 13 maj 2024 11:08
Till: nathanmarlor/foxess_modbus ***@***.***>
Kopia: Mattias Lindahl ***@***.***>; Mention ***@***.***>
Ämne: Re: [nathanmarlor/foxess_modbus] H3-PRO series (Discussion #516)
Sorry, been busy. I'll have some time on Weds.
—
Reply to this email directly, view it on GitHub<#516 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANR2MMY6NQK4FHYRZFT4DUTZCB7GNAVCNFSM6AAAAABB4LEMTSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TIMJWHEYDA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
👍
It's hard for me to test and iterate when I don't have a H3-Pro to test against! I'm afraid I'm reliant on you (or other H3-Pro owners) to help figure out how to talk to it.
Yep. If you look at the spec, you can see the different meanings of bits 0, 1 and 2 for this register.
That's how bitfields work, yes.
Yeah, that's what I'm interested in. Other inverters use positive / negative Active Power values for force charge / discharge. I'm not sure how that relates to having different force charge / force discharge modes set in the Enable register.
Well, ish. 5000 converted to bytes as big-endian is [0x00, 0x00, 0x13, 0x88] (higher-order bits first). So You're then creating an array of two values: values[0]: 0x00 * 256 + 0x00 = 0x0000 You're then giving these two 16-bit values to the node-red modbus library, which should be writing them big-endian, as the modbus spec specifies that 16-bit registers are big-endian. When a value is split over 2 registers, the lower-order bits normally go in the higher register (you've found one exception to this). I'll get that fixed when I'm next at a computer, which will probably be at the weekend. |
Beta Was this translation helpful? Give feedback.
-
|
I tried to just reverse the array and it does the thing and writes in correct order. But you may change the way you want :)
|
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the delay, this should be fixed in v1.12.0b8. Was there anything else outstanding for the H3-Pro? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Now I can’t find any outstanding errors or values for the H3-Pro. Feels ready for release and everything is OK so far. |
Beta Was this translation helpful? Give feedback.
-
|
As a questionen from beside... To those who got the official register dokumentation... Thanks |
Beta Was this translation helpful? Give feedback.
-
|
I have an H3 Pro with 1 battery and I finally got my modbus adaptor, keen to test but assume I should be using a beta version? |
Beta Was this translation helpful? Give feedback.
-
|
Odd! I got mine from the foxess website, I'm in south africa so selected that as my region. Let me know how it goes. EDIT: Just saw your edit |
Beta Was this translation helpful? Give feedback.
-
|
@mrksdiehl @timsdrew did you end up using the From the manual I was wondering whether it is also possible to use the |
Beta Was this translation helpful? Give feedback.
-
|
Or maybe @MattiasLindahl or @vip-klaus can tell me which pins/connector they ended up using. I'm happy to add the H3 Pro to the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
I use pin 17 (485A) and pin 18 (485B) from the 20 pin connector. Works well for the last 7 month. |
Beta Was this translation helpful? Give feedback.
-
|
I've added the instructions for the H3-Pro to the wiki. |
Beta Was this translation helpful? Give feedback.
-
|
So I managed to wire it up and install it but this is what I get in the "Log Book"
I guess I have connected it correctly, because the inverter shows as |
Beta Was this translation helpful? Give feedback.
-
|
You probably need a firmware upgrade on your H3 - FoxESS switched things around |
Beta Was this translation helpful? Give feedback.
-
|
@mrksdiehl will let you know what I get when I try this weekend. My installers have done several software updates, so hopefully I'm on a recent version - according to this it's 1.31 |
Beta Was this translation helpful? Give feedback.
-
|
This is what the log says: I hope you have more luck. This is my first time playing with Modbus so it's hard for me to make any sense out of that. Is there maybe a way I could "ping" my ew11 to see if it actually receives data from the inverter? |
Beta Was this translation helpful? Give feedback.
-
|
I´ve found a possible error in value for inverter power sum. I looks like this is divided. Can you look into that?
|
Beta Was this translation helpful? Give feedback.
-
|
I thought you said that was working, back here: #516 (reply in thread). Has something changed? |
Beta Was this translation helpful? Give feedback.
-
|
I´m not sure but now it´s not working. The changes in 516 did make a difference but I didn´t notice that it was divided. It should show -5,494kW and not -0,005494 in my example image. |
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing this too in v1.12.2 - maybe a Fox firmware change? 
|
Beta Was this translation helpful? Give feedback.
-
|
I´m also missing a sum for EPS power:
We have SUM of Feed-In and Grid consumption so a SUM of EPS Power would be appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
The inverter does not expose a register with the sum of EPS power. It doesn't even expose an ESP power (just the individual phases) for me to sum manually. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, yes please, if you can sum the R, S and T power for EPS it would be nice. |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, I've had an H3-Pro-20 installed and connected via Modbus on a USR-TCP232-410s. Using v1.12.1 and v1.12.2 a connection is initially made, but it times out after a minute or so with the error: Error reading registers. Type: RegisterType.HOLDING; start: 37609; count: 92; slave: 247 from tcp://192.168.68.222:502: Exception Response(131, 3, IllegalAddress) I can connect using v1.12.0, but all of the sensors are unavailable. The controls section is however operational. Happy to help fix this if there's anything I can do. My firmware versions are: H3-Pro-20.0 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @lewisjspencer, would you mind creating a new issue for this and then we can pick up on that, the responses will get lost in this thread. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone, |
Beta Was this translation helpful? Give feedback.
-
|
see #696 |
Beta Was this translation helpful? Give feedback.
-
|
@nathanmarlor Do you have a timeline for the next release? |
Beta Was this translation helpful? Give feedback.
-
|
FoxEss has fixed this issue in firmware so now you would have to reverse this bug-fix and set read order to this again. See this comment: |
Beta Was this translation helpful? Give feedback.
-
Hi!
Do you have any plans on support for the new H3-PRO series? I now have a H3-PRO-20 installed but no support in your integration.
Beta Was this translation helpful? Give feedback.
All reactions