Tegra

I note that the app went down again this morning at 06:15

I have just chatted with Sunsynk's helpdesk and they acknowledge having a data/programming problem and request 24 hours patience to fix the issue.

Still no data being reported. The Gateways are online but the Inverter still shown as being offline. Random varying disparate reporting times as recently as 06h50 this morning. Anybody elses problem persisting?

Hi. Same issue here. App last reported data at 06h42 today Sat 02 Mar 2024. Both inverters are showing as being online but no data on the app. Also the Master inverter to which the panels are connected is showing no PV kWp on the inverter, but the battery is charging from the sun, and I'm not using grid. Sunsynk App monitoring system is FUBAR. The same happened about a month on 6 Feb 2024 where no solar PV or grid stat reported. Problem resolved itself overnight. Suspect in chief .... Sunsynk. I was never able to elucidate the real cause or determine what fixed the issue. Ironically the inverter still did it's job correctly despite the reported data being absent. Two other independent Sunsynk systems that I monitor went offline at 08h32 and 11h37. Very strange.

I have four geysers each fitted with CBi Astute geyser timers. They were installed in Sept 2022, and thus far I have had two units fail after 10 months, in that the relay fails to switch through power to the geyser thermostat/element. CBi swapped out the first failed unit and I trust they will similarly swap the 2nd unit. Both failed in July 2023 after 10 months of use. I guess it won't be ling before the remaing two original units fail as well. Having had similar issues with CBi timers on swimming pool pumps, I am now going to install Onesto 25A Contactors and forgo the data I would normally have if directly connected. Its cheaper to replace a contactor than the CBi geyser timer. Anybody else with similar experience?

Latest issue is the Sunsynk/PV Pro application not resetting itself at midnight. According to the app I receive 27kW of solar power by 03:28 in the morning. The system only reset itself for the day around 9am. It seems to be carrying over the PV and Charge values from the previous day. Anybody else noticed this?

The data logger with ETH+Wi-Fi is the E-Linter Goldfinch DB9. The one most likely supplied with a Sunsynk inverter is the Magpie variant which is Wi-Fi only.

Good morning. Confirmation was received from [email protected] that 4790122C26R is in fact the latest version of the software for the E-Linter Magpie data logger (Model EESW-D205 Hardware Version AEW2-0005-03). The software can be updated from the 10.10.10.1 browser webpage. I have done this. Just be patient while it updates, it takes a while. An update success popup will appear. Also make sure that the internet is switched off for the update process. You don't want the update being interrupted by the PC switching Wi-Fi networks automatically. Also, a good idea to forget all Wi-Fi network connections that the PC can connect to at your home. If using a mobile phone, make sure that data is off. Hope that this helps. Tegra assumes no responsibility for the use or outcome of the attached zip file. 4790122C26R.zip

Just reset my static IP address to unchecked and et voila I'm back online on both inverters. Thanks. Fixed IP addressing for my network clearly not the way to go. Its now randomly choosing its own IP on my network. This has also fixed the duplicate IP address issue I previously had and could not explain (4x IP addresses for 2x loggers). Have also updated the logger software. Don't see any difference.

The following response has been received from Sunsynk: QUOTE The problem with the data loggers has been firmware and server related. As discussed, it was escalated to the factory and they are currently doing the best to sort it out ASAP. We are awaiting their feedback. Apologies for the inconvenience this has caused. UNQUOTE Now we sit back and wait. No point in any more fiddling.

Join the club. Definitely something incompatible between the inverter with its updated software and the loggers with their legacy software,which can't be updated by Sunsynk OTA.

Morning Gary, I think you may well be into something. What model of data logger do you have? Mine is EESW-D205 with hardware AEWZ-0005-03. I note that your software/firmware version is subsequent to mine (4790122A12R). I also see that your logger is also still online, while both of mine are offline. The conundrum now is how to update the data logger firmware myself since Sunsynk will have no access with the data loggers offline. Does anybody have the firmware update file for Gary's version?

Hi. My two loggers are still dead. No adult response from Sunsynk. They remain in denial. Suggest you email [email protected] to complain about your issue. You are only one of a multitude having this same dead logger problem. Its not your wifi network. Its all Sunsynk's fault. An update they pushed must have caused this to happen. Good luck. I've had no joy from Sunsynk thus far.

We all need to email this issue to [email protected] I spoke with him yesterday and he was totally unaware of this problem. His only suggestion/solution was to courier the loggers to him in JNB for them to verify the failure(s) for replacement. I have two inverters and two dead loggers. When I suggested that the problem was caused by the Master inverter, he had no answer. Sunsynk need to act responsibly and promptly to this failure as it is becoming steadily more widespread.

Several folks are having the same issue. Statistically this can't be coincidental.

Sunsynk wifi dongle.

What service from Sunsynk, multiple emails to them unanswered. JNB based technical staff 'unaware' of the problem. Service is non-existent.

Switch off your home wifi. Then physically disconnect the logger and after 30 seconds reinsert. Then connect directly to the dongle via wifi to EAP_*****. Once connected use your browser to connect via IP 10.10.10.1. You should then be able to set it to your phone's hotspot instead of the home wifi network. Regrettably, this has not mitigated the issues I have with the dead loggers.

Lets stay in touch.

Good evening, Yellow_TapeMeasure, I too have an Ubiquiti Unifi AP-AC-LR network in my home (multiple access points and dedicated 2.4GHz and 5GHz outputs). The network was installed long before the Sunsynk system and is extremely stable with a fibre connection to the www. The Unifi network also happily runs IDS HYYP for my alarm system (2.4Ghz), multiple CBI Astute devices without any issues, also Google home, my Yamaha hifi, multiple Xiaomi TV devices and Samsung TVs. The Sunsynk system was installed in September 2022 and ran smoothly on the Unifi 2.4 GHz wifi network until this past Monday. No devices have ever had connection issues. Even Sunsynk, until Monday 16 Jan. The only thing that has changed in the entire solar system is the firmware update from Sunsynk. The logger for the Master inverter failed to connect, while the logger for the Slave sustained its connection. On swapping the two loggers (on the advice of Sunsynk) the functional logger from the Slave inverter survived 28 minutes on the Master inverter and then exhibited the same failure mode. Now both loggers are dead. Of course, I also tried the trick of trying to connect via a mobile phone hotspot, with the home unifi network switched off. The logger was able to be set to the android 2.4GHz hotspot but still failed to connect to the internet. Status 'not connected' and Cloud 'initializing' The second failed logger now has the same failure and is also not able to connect. The logger(s) just show a constant green light. Sunsynk's advice at this time is for me to courier the two failed loggers to them to investigate the failure. The contact person at Sunsynk JNB is [email protected] Simply replacing non-functional loggers is not going to solve this problem. Another two loggers will simply die. My installer is going to give me a 3rd logger and I fully suspect that it will die as well. Sunsynk will receive a courier package with 3 dead loggers next week. I have already advised Dino @ Sunsynk of at least three other people concurrently experiencing the same problem. I reiterate that this problem will multiply as I fully suspect a firmware update being implicated. Zero feedback has been received from Sunsynk (UK).

My master units logger also went down Monday morning 07h18. Tried everything to get it back online. Remained dead except for steady green light. Logger on the Slave stayed connected Sunsynk suggested swapping loggers. Did so. Now I have two dead loggers. The Master seems to be killing the loggers. Sunsynk have no answer. Unaware of any problem. I suspect this may be more widespread. Perhaps recent firmware update corrupted the loggers via the Master? Anybody else with similar issues or resolutions?

I have two Sunsynk 8kW units. The logger for the Master went down Monday 16 Jan at 07:10 and nothing I have tried had managed to bring it back online. The logger for the Slave continued to work. Both units worked per perfectly until Monday morning. I can't believe that it's pure coincidence that two independent user's Sunsynk loggers have both 'died' at the same time on the same day. I can find the logger via 10.10.10.1 via a browser, and also it's IP and MAC address on my network by using Angry IP Scanner. The crazy thing is that one of the faulty loggers seems to be occupying two IP addresses at the same time (192.168.5.195 and 192.168.5.252 both with the same MAC). The functioning logger only has one IP address (192.168.5.251). As per Sunsynk's advice I tried swapping the loggers around on the slave and master inverters and the failure has now been caused to happen on the remaining functional logger, when it was attached to the master. I now have two kaput loggers. I fully suspect that the new firmware (M 6.0.2.2 / S 1.7.2.4 / C E.4.2.) that was installed about a week ago on the Master and Slave inverters has somehow corrupted the loggers via the Master inverter. I have contacted Sunsynk but have had no real response from them to resolve the issue.

Perhaps the title of this thread should be fixed: Data not Datal

The dongle I have is the Sunsynk wifi version with no RJ45 LAN connection. I can find the logger via 10.10.10.1 via a browser, and also it's IP and MAC address on my network by using Angry IP Scanner. The crazy thing is that the faulty logger seems to be occupying two IP addresses at the same time (192.168.5.195 and 192.168.5.252 both with the same MAC). The functioning logger only has one IP address (192.168.5.251). As per Sunsynk's advice I have tried swapping the loggers around on the slave and master inverters and the failure has now been caused to happen on the remaining functional logger. I now have two kaput loggers. Anybody out there who can tell me how to institute a warranty claim with Sunsynk? The faulty loggers is just over three months old. I fully suspect that the new firmware that was installed about a week ago has somehow corrupted the loggers via the Master inverter.