Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received) / No Response received from the remote unit/Unable to decode response BUT INTEGRATION IS WORKING #62

Closed
Vato9394 opened this issue Nov 23, 2022 · 26 comments
Closed

[Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received) / No Response received from the remote unit/Unable to decode response BUT INTEGRATION IS WORKING #62

Vato9394 opened this issue Nov 23, 2022 · 26 comments
Assignees
@rsaemann

Comments

@Vato9394
Copy link

I get 2 errors in the home assistant log:

  • [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)
  • [Input/Output] No Response received from the remote unit/Unable to decode response

But the integration is working fine and all my data is filled in.
is this a bug in the integration or do I do something wrong?
@Vato9394 Vato9394 changed the title [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received) / No Response received from the remote unit/Unable to decode response [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received) / No Response received from the remote unit/Unable to decode response BUT INTEGRATION IS WORKING Nov 23, 2022
@StealthChesnut
Copy link
Owner

Hi @Vato9394
How are you connecting to your inverter?
Are you using Lan or Modbus?

@Vato9394
Copy link
Author

Vato9394 commented Dec 1, 2022

I am using Modbus (specifically a serial to usb)

@StealthChesnut
Copy link
Owner

StealthChesnut commented Dec 1, 2022 via email

@Vato9394
Copy link
Author

Vato9394 commented Dec 1, 2022

1.36

@Vato9394
Copy link
Author

Vato9394 commented Dec 1, 2022 •
edited
Loading

I am using the fork for the h3 tho. (https://github.com/rsaemann/HA-FoxESS-H3-Modbus)
I have an AIO H3 8.0 E

@StealthChesnut
Copy link
Owner

@rsaemann - are you able to help?

@rsaemann
Copy link

rsaemann commented Dec 2, 2022

I am getting the same error. I will check if it is a bad register. Maybe it is just too many sensors read out in the update loop. I used 30 seconds for every register. Maybe that is not enough.
First guess for troubleshooting: Disable some sensors that you do not need by commenting the lines. Or increase the update interval.

@rsaemann
Copy link

rsaemann commented Dec 2, 2022

I found for my installation (island mode), that the sensors for the inverter current, battery current and battery voltage are responsible for the error. If I comment them out, no modbus errors are thrown.

If you have only the main grid or both (grid+eps) connected: please report if disabling the sensors work for you.

@Vato9394
Copy link
Author

Vato9394 commented Dec 2, 2022

I have disabled (commented) following sensors:

  • Battery Voltage
  • Battery Current

Now, I don't get an error thrown.

Thanks for the help!

@StealthChesnut
Copy link
Owner

Ok - closing this issue as it seems to be resolve. Thanks for helping out @rsaemann!

@kevinverelst
Copy link

@Vato9394 Could you help me setup my Integration? I'm seeing the same errors except my integration isn't working. The values stay "unavailable". I'm doing exactly the same except I have a H3-5.0-E inverter. How did you connect your cable to the RS485 port? If I understand correctly, I need pin 1&2?
image

@Vato9394
Copy link
Author

Vato9394 commented Dec 6, 2022

Yes, pin 1 and 2 (I got the RS485 to usb, I first tried with the USR W610, but didn't get it to work, I don't know why, maybe my incompetence?) Connect 1 to A and 2 to B, don't switch this.
I also used the fork for the H3 specifically. https://github.com/rsaemann/HA-FoxESS-H3-Modbus
I copied it manually to home assistant, don't use hacs for this (the locations in the yaml code are different if you use hacs, do yourself a favor and just do it manually)
And my firmware is the latest 1.36 (just send foxess support an email, they can update it remotely)

@rsaemann
Copy link

rsaemann commented Dec 6, 2022 •
edited
Loading

Did you check the Inverter's RS485 Slave ID? The sensors use standard address 247. However due to installation this might have changed. I encountered an accidential reset once that changed the address to 000.
Invertermenu -> settings -> communication -> RS485 -> slaveID

Check the dongle and connection with a tool like GModbus for Windows.

@Vato9394
Copy link
Author

Vato9394 commented Dec 6, 2022

You can check this in the menu on the inverter itself.

@tagware
Copy link

tagware commented Dec 6, 2022 via email •
edited by StealthChesnut
Loading

@Daibutt
Copy link
Contributor

Daibutt commented Dec 6, 2022 •
edited
Loading

When I connected using RS485 back in April, the (H1-5.0E) firmware wasn't supporting access via the LAN port .
As it's working fine there's no real push for me to swap over to LAN.
If my RS485 converter packs in I'll probably do it then.

@Vato9394
Copy link
Author

Vato9394 commented Dec 6, 2022 •
edited by StealthChesnut
Loading

Guys, Girls & Others, Is there a reason why you guys are using the RS485 port? Rather than plugin a CAT5(RJ45) cable into the inverter Ethernet port (F) and running it back to the router? As a CAT5 shield cable run can be up to 100 meters and still be in spec. Save Electrons. :o) Regards David Vincent

on the H3 inverters, modbus over ethernet is not (yet) enabled. thats the reason we use the RS485 port.

@kevinverelst
Copy link

kevinverelst commented Dec 6, 2022 •
edited
Loading

@Vato9394 I'm an idiot. It was working from the start but I was looking at the foxess entities (I used to have the foxess cloud integration installed) instead of the modbus entities. I also was under the impression that it was not working due to the error in the logs and just looking at the wrong entities. I cleaned everything up and started from scratch. This is when I noticed that it was working.

@rsaemann the default address was working fine and I can confirm your fork is working on a H3-5.0-E inverter.

@tagware My inverter has a USB wifi dongle connected to port F. I would rather just plug in an ethernet cable but since the fork I'm using tells me that port 502 is closed. It seems I cannot connect over network. I'm also confused because it says I can connect LAN on port F while that has a USB interface.
image

@tagware
Copy link

tagware commented Dec 6, 2022 via email

@tagware
Copy link

tagware commented Dec 6, 2022 via email

@kevinverelst
Copy link

Why bother? The USB RS485 stick I bought was € 3...

@tagware
Copy link

tagware commented Dec 6, 2022 via email

@Daibutt
Copy link
Contributor

Daibutt commented Dec 6, 2022 •
edited
Loading

Hi Kevin, You in theory can swap over the WiFi with a LAN port for £67 ish. The trouble is finding one. Regards David Vincent

Do you mean the FoxESS Smart LAN module? I think this just replaces your WiFi Cloud connection with hardwired Cloud connection, rather than allowing you local access.

@tagware
Copy link

tagware commented Dec 6, 2022 via email

@StealthChesnut
Copy link
Owner

@Vato9394 I'm an idiot. It was working from the start but I was looking at the foxess entities (I used to have the foxess cloud integration installed) instead of the modbus entities. I also was under the impression that it was not working due to the error in the logs and just looking at the wrong entities. I cleaned everything up and started from scratch. This is when I noticed that it was working.

@rsaemann the default address was working fine and I can confirm your fork is working on a H3-5.0-E inverter.

@kevinverelst, @Vato9394 - are your problems solved? If so I will close this discussion. :)

@Vato9394
Copy link
Author

Vato9394 commented Dec 6, 2022

yes, mine was resolved some time ago, you can close this discussion ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rsaemann rsaemann

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@kevinverelst @rsaemann @Vato9394 @tagware @StealthChesnut @Daibutt