Announcement

Collapse
No announcement yet.

New Energy Hub Inverter - troubles connecting

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    New Energy Hub Inverter - troubles connecting

    Hi, I have just upgraded to a new energy hub inverter (SE10000H - photos attached) and I am having trouble connecting. I have checked IP addressed; and checked and enabled the TCP port on the inverter (port 1502). In the error log I am getting the following message "Failed to get data: Unable to connect to the remote server". I have ethernet connection as per last inverter [which worked flawlessly with this plugin].

    Has anyone managed to get the plugin working with the newer energy hub inverters?
    Attached Files

    #2
    I know the plugin works for others with a SE10000H inverter. Did you follow the CPU 4.x instructions carefully?

    https://forums.homeseer.com/forum/en...u-4-x-firmware
    stefxx

    Comment


      #3
      Hi, I followed the instructions, and I am still having issues. I am connected to the inverter; however, I am not receiving data (see a sample of the log file below; and I have attached a screen shot from inverter configuration; screen shot of my plugin settings). Any tips would be greatly appreciated

      Log file:
      22/11/2022 4:08:03 PM Thread created
      22/11/2022 4:08:03 PM Thread started
      22/11/2022 4:08:03 PM Send: 3F010000000601030000006D
      22/11/2022 4:08:03 PM Connected to 192.168.0.27:502
      22/11/2022 4:08:10 PM Send: 3F010000000601030000006D
      22/11/2022 4:08:20 PM Send: 3F010000000601030000006D
      22/11/2022 4:08:30 PM Send: 3F010000000601030000006D
      22/11/2022 4:08:40 PM Send: 3F010000000601030000006D
      22/11/2022 4:08:50 PM Send: 3F010000000601030000006D
      22/11/2022 4:09:00 PM Send: 3F010000000601030000006D
      22/11/2022 4:09:10 PM Send: 3F010000000601030000006D
      22/11/2022 4:09:20 PM Send: 3F010000000601030000006D
      22/11/2022 4:09:30 PM Send: 3F010000000601030000006D
      22/11/2022 4:09:40 PM Send: 3F010000000601030000006D
      22/11/2022 4:09:50 PM Send: 3F010000000601030000006D
      22/11/2022 4:10:00 PM Send: 3F010000000601030000006D
      22/11/2022 4:10:10 PM Send: 3F010000000601030000006D
      22/11/2022 4:10:20 PM Send: 3F010000000601030000006D
      22/11/2022 4:10:30 PM Send: 3F010000000601030000006D
      22/11/2022 4:10:40 PM Send: 3F010000000601030000006D
      22/11/2022 4:10:50 PM Send: 3F010000000601030000006D
      22/11/2022 4:11:00 PM Send: 3F010000000601030000006D
      22/11/2022 4:11:10 PM Send: 3F010000000601030000006D
      22/11/2022 4:11:20 PM Send: 3F010000000601030000006D
      22/11/2022 4:11:30 PM Send: 3F010000000601030000006D
      Attached Files

      Comment


        #4
        Those settings look fine. But isn't the default Modbus port for a SE10000H not 1502? Not if it matters as long as both sides are configured to use the same port...

        Can you ping the SolarEdge from your HomeSeer server succesfully?
        stefxx

        Comment


          #5
          I can ping the IP address (ping 192.168.0.27). However, I cannot open port 502 using telnet (telnet 192.168.0.27 502)

          Comment


            #6
            Have you tried changing the port to 1502 (in both the inverter and the plugin)? I know those SolarEdge inverters run some kind of firewall, perhaps it is blocking 502?
            stefxx

            Comment


              #7
              With 1502 I can now open the port with Telnet. However, the plugin is still not reading the data (changing the values in Homeseer). The last change was from the old inverter (which is now decommissioned)

              Comment


                #8
                The plugin will have created new devices/features in HS4 for the new inverter. Did you check those?

                Also, can you please show the log again now? Is any data being received?
                stefxx

                Comment


                  #9
                  I doubled checked ... A new device/features has not be created.
                  Please find attached an updated log. It appears no data is being received

                  23/11/2022 3:37:10 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:37:00 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:36:50 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:36:40 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:36:30 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:36:20 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:36:10 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:36:00 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:35:50 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:35:40 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:35:30 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:35:20 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:35:10 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:35:00 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:34:50 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:34:48 PM SolarEdge Trace SE10: Send: 3F010000000601030000006D
                  23/11/2022 3:34:48 PM SolarEdge Warning SE10: Connected to 192.168.0.27:1502
                  23/11/2022 3:34:48 PM SolarEdge Debug SE10: Thread created
                  23/11/2022 3:34:48 PM SolarEdge Debug SE10: Thread started
                  23/11/2022 3:34:48 PM SolarEdge Info Initialization of SolarEdge version 4.0.15.0 complete
                  23/11/2022 3:34:48 PM SolarEdge Info .NET version detected: .NET Framework 4.8.4515.0​

                  Comment


                    #10
                    Maybe this helps? https://github.com/jbuehl/solaredge/...ment-593152198
                    stefxx

                    Comment


                      #11
                      Just letting you know that it is now working. As per the link you sent, I followed the steps [as per below] and then it worked
                      1. Flick the switch on SolarEdge to P and connect your mobile device to the WiFi hotspot (password on the side of the inverter, or use the QR code + mySolarEdge app)
                      2. Open the browser and visit http://172.16.0.1 5 and click on the “Communication” menu item
                      3. Select “RS485-2”
                      4. Choose Protocol “SunSpec (Non-SE Logger)”, also under that set Device ID to 1 (mine was set to 5). Now some Modbus TCP requests were responding.
                      5. Change the Protocol over to “SolarEdge Master” (now a SolarEdge logger script was getting data too)
                      6. Change back protocol to “None”
                      7. Power cycle the inverter for good measure, and it was all still working

                      Comment

                      Working...
                      X