WazzaCPT

Hello Peeps,

I have created a device config for the Geyserwise MWS units for the tuya-local integration of Home Assistant.

There are still some general bugs with the Geyserwise device itself.

This config has been tested briefly to get it operational at a site with two unit.

I would appreciate if some more users could test it out before I create a pull request to the main repository.

https://github.com/Waz-Cpt/tuya-local

If you want to just add the single file to the custom_components folder them you can download the file and upload it directly for testing.

https://github.com/Waz-Cpt/tuya-local/blob/55581ae9ef1992e677adb7287400f2f6a1ca437f/custom_components/tuya_local/devices/geyserwise_mws_water_heater.yaml

Once uploaded, restart HA and you can go through the process of adding a Tuya Device in the Tuya-Local integration. It will detect the device type for you and you will have a water_heater device and entity along with the corrected error messages and other settings.

Please DM me with feedback of questions. Or comment on this thread.

Can u pm it to me again ?
or send to my email : [email protected]

I have been working on the next iteration of Solar Monitoring
High level it will Consist of the following addons:
Scraper that gets the solar information and populates it in MQQT
I have allready completed a bare bones of this one running under : https://github.com/gdwaterworth/sunsynkmqqt
I forked SunsynkV3 and changed it 90% to do what I want
Only prerequisite is the MQQT addon


Processor which then take the MQQT data and creates topics in MQQT that will then be processed as MQQT discovery and create entities in Home Assistant
TBD
A MQQT listener that will look at changes coming from topics in HA and then set those topics back on the inverter
TBD
I have chosen this route to be modular so in the future I can add in modules that talk to various inverters and you just implement the modules needed.

The API is working. There were more changes to the token and authentication processes.

The crew for the SolarSynkv3 add-on implemented an update yesterday. That solution is currently working for sunsynk and other generic pv.inteless dongle setups.

All of these solutions are all still so fundamentally flawed relying on the cloud for data access.

I need to start moving my friends and family over to direct local connections.

ok got mine working . Looks like changes on gzip and some header stuff as well
In this


Change the variable headers_with_bearer to ( I changed encoding - removed gzip , referrer and origin )

    var headers_with_bearer = {
        "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0",
        "Accept": "application/json",
        "Accept-Language": "en-US, en; q=0.5",
        "Accept-Encoding": "deflate",
        "Content-Type": "application/json;charset=UTF-8",
        "Authorization": "Bearer " + global.get("SS.Bearer"),
        "Origin": "https://api.sunsynk.net",
        "Connection": "keep-alive",
        "Referer": "https://api.sunsynk.net/",
        "Sec-Fetch-Dest": "empty",
        "Sec-Fetch-Mode": "cors",
        "Sec-Fetch-Site": "same-site",
        "TE": "trailers"
    }

I may need to make changes on the setting one , but will try work that out later
Will update the git repo when I get some time

Unfortunatly not. I havent realy given it thought yet, I dont use this addon anymore I make use of modbus over serial. 

Hi All, many thanks for all the knowledge I found here. It helped me a lot with my Deye setup.
As a small thanks from my side please check this 3d design of case for SmartDeyeDongle V4 from SmartHomeIntegrations.co.za. I made STL files available on Printables. I hope you guys will find it useful. Cheers :).
https://www.printables.com/model/1048061-mak-housing-for-smart-home-integrations-deye-dongl

Not that I am aware of. If you want the Sunsynk dashboard, you are stuck with their firmware. At least they updated it to turn off the default access point after it was connected to your own WiFi!

Sure, that's why you take a backup, and can reinstall it if you ever need to do an upgrade. And while doing so, log all the data written out on the serial port to see how it is done 😛

@HowserMD you need to add a unit of measurement or setup your own daily energy meter within HA using the total energy sensors.
  - sensor:       - name: "Sunsynk Battery Daily Charge 70"         state: >           {{state_attr('sensor.sunsynk_battery', 'etodayChg')|float(0)|round(1)}}         unit_of_measurement: kWh       - name: "Sunsynk Battery Daily Discharge 71"         state: >           {{state_attr('sensor.sunsynk_battery', 'etodayDischg')|float(0)|round(1)}}         unit_of_measurement: kWh  

@WazzaCPT As long as one connects the TX signal of the inverter to another serial port RX signal and the same for the Dongle, it should not interfere with the existing communications taking into account the cable length limits for RS232 which is dependent on the baud rate but generally stated as around 15m. 
I have not looked at the protocol to know if only TX or both TX/RX data packets are needed to implement monitoring but am sure other forum/internet members already reversed engineer it so the info will be available somewhere.  
If you are prepared to open the Dongle, yes.
Not sure how the ESP32 is powered and if another ESP32 or similar can be powered from the same source, but this information should also be available on the forum / internet.
The diagram attached in previous post was really more to indicate sniffing should be possible without modifying the stock Dongle by just using a breakout sniffing cable 😃
 

So, it wasn't as simple as I thought it would be to get ESPHome running on the Sunsynk dongle.
Flashing is not too tricky, although I do end up contorting my fingers a little, holding 3 jumper wires for G,R,T and a pair of header pins with a jumper on them to bridge GPIO0 (aka "short for ISP" - edit: turns out this is GPIO8 on the C3) with one finger, and holding 3v3 against the capacitors to the left of the C3-Mini module to power it.
I used:
esptool.py -p /dev/cu.usbserial-01E7DF5F -b 230400 read_flash 0 $((4*1024*1024)) sunsynk2.bin to take a backup (it's a 4MB part, so you can do the calculation manually if you are using Windows).
Flashing a minimal config ended up in a boot loop when powered as above via a 3v3 supply, held against the decoupling caps. I guess it wasn't enough to power the WiFi when it initialises. So, using a DE9 breakout, and feeding 12V on the RI (pin 9), and ground on pin 5, I was able to get it running stably. It took me an AGE to figure out what pins to use for the uart! I first thought I'd be clever and use the ESPHome kickstart firmware to dynamically adjust the pins, and wasted a few hours trying to get that to work, firstly making changes for the ESP32C3, and then just iterating through the pins and looking for behaviour on the RX and TX pins of the DE9 connector. All for naught, the kickstart firmware just wasn't working properly for some reason.
BTW, I did test restoring the backup firmware, and it worked perfectly (when powered using 12V). It was actually the stock firmware boot loop when powered via 3v3 to the capacitors that clued me in to checking for power problems.
In the end, my diff to slip06x's config on github was pretty minimal:
diff -w ESPHome-1P-Sunsynk-Deye.yaml sunsynk_dongle.yaml 12c12 < board: nodemcu-32s --- > board: airm2m_core_esp32c3 14a15 > variant: esp32c3 60,61c61,62 < tx_pin: GPIO1 < rx_pin: GPIO3 --- > tx_pin: GPIO5 > rx_pin: GPIO6 67d67 < flow_control_pin: GPIO16 I did also figure out the GPIOs for the LEDs (3 and 7 for the red and green LEDs, respectively), but haven't yet bothered adding those to the config.
With that, you can now flash ESPHome onto your Sunsynk dongle, and detach yourself from the cloud entirely.

Would still be amazing to get into the orignal firmware and see if it is possible to retain the original communications but add in a stream server of the RS323 (modbus).

The error is a SSL cert that cannot be checked . This is their api website. 
You could change the https to http ( so there are no certs ) , but couldnt be bothered to be honest unless they really mess up on that front . Not sure if their api support plain http

The problem is not whether there is a data value or not ( available/unavailable ) the problem is when a data value of 0 is returned by Sunsynk. That is why I use teh forever totals and not the today totals in the energy graphs. The today totals never seem to reset at the same time and if I use teh forever totals then it is easy as they can never be 0 and also teh energy graphs will "catch up" when there is an outage
 
There is probably a use case for it in some of teh other values, but will see when I have time. 

To be honest, not sure if you would need to ESP32 or one. But you can have a look at the following GitHub repo ESPHome Stream Server, it is possible that this might work with KellerZa integration.

Alternatively, the following is some ESPHome things for Sunsynk Sunsynk ESPHome.

There may be more up to date code somewhere.

You will need two RS485 converters. There is ESPHome Yaml floating around for that method.

Otherwise there is the option of running a TCP Modbus gateway device and use tyhe KellerZA integration.
Alternatively you can direct connect to the HA machine with the WaveShare RS485 USB adaptors using the KellerZA integration. I believe there may be some limitations on the RS485 cable length.

Another option is to use the KellerZA integration with the Solarman dongles. Not sure if this would work with parallel inverters though.
A third option is using the Sunsynk API and the Node-Red flows from this guide if you are using the Sunsynk connect app:
E-Linter Logger API access
and the forum post: Sunsynk Logger Integration

Version 2.x was a complete rewrite and methology change as V1 had severe limitations due to the logic flow framework used.
The video was created by someone else and quite frankly I don't have the correct software or time to do a new one. 
The short guide is available on : https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/wiki
It does not make sense for me to try work remotely on someone else's system as you are not setup for me to look at the real data coming in and to set you up for that is time consuming.
My solution is a 2 pv string , so there may be something incorrect with the code for pv3/4. The only way i can check that is if someone "lends" me their login details or share their plant to [email protected]
That way I can setup my test environment and check with those details.
I know I did put in some fixes for pv3/4, and again this morning but again I cant test them.

Utility use, we would have to look at as I am not sure where it is shown or even if it is shown on sunsynk.net, but again I cannot use my system to check as I dont use that or aux power.
People must remember this is not a paid product and I am doing this free and gratis, so it get looked at when I have spare time and it takes LOTS of time. Sometimes it may go for 2 or 3 weeks where I dont look at it.
Sunsynk recently has been particularly painful with their changes to Region 2 and they are still having fairly major teething problems.
There is no API manual from sunsynk ( that is anywhere near up to date and that what is available is wrong/incomplete in a lot of places), so everything is reverse engineered and that takes time. 
ATM my focus is adding in some of the extra settings to be changable , but having some issues around it. Also being focused on is the bad data coming from Sunsynk and their API response time challenges  although the current fixes appear to be handling that correctly ( if not very smartly )

v4.15.0
🚀 Exciting New Features
feat: This release introduces `dynamic_colour` and `linear_gradient` options for the battery. These are two optional visual enhancements. `dynamic_colour` changes the colour of the battery icon based on the % contribution of the power source (grid, solar). `priority_load_243` will determine whether the battery or the load is prioritized when generating solar power. By default the battery is prioritized.                                                          If `linear_gradient: true` the blocks inside the battery icon that represent SOC will be coloured using a linear gradient that ranges from red to green           You can use these settings independently or in combination to achieve various affects. Some examples below


locale: add Brazilian Portuguese translation. closes #250 Thanks @R0DRIG0MEL0  chore: update copyright year. closes #251  **Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v4.14.0...v4.15.0

Lots to unpack here
The amount of sensors varies per device and I believe by hardware revision as well.  So your mileage will vary for sure
CBI switches regardless of model  run out 100% of the Cloud.  Nothing is local :(   So the ability to switch on or off, view live status or history is all done on the other end of the internets !
For full local control, Tuya Local is what you're after,not Local Tuya.  You've largely done the tricky bits already ( the dev account ).  The rest should be a breeze
The only hassle I had was that sometimes after a load shed, HA couldn't see my geyser ( Smart Controller ) or the pool devices ( Smart Isolator ) and their respective entities. So two extra steps I add to my automations is to "Reload config entry" for the geyser/pool device, wait 30 seconds for that to happen, then turn on

OK I hate you now
I looked at ESP's in the past and didnt take them tooo seriously.
Ordered a bunch of them and a robo car project and a few other things to do with my youngest son.
R4500 later, thanks for that lol

@Gary Waterworth The BLE proxy works well and all you need is a power source and wifi signal. I shared my config and setup in this post. 
 
 

Was trying to get arround having another hardware device . But yes that works as well

I dont like putting documentation in one forum where not all users come from. Anyone can branch the code and develop and then ask for a merge. My time is available on a free time basis as and when I have it. I have a fairly demanding job, so cannot allways be available and a lot of what has been done here has been through a lot of reverse engineering.  There is VERY little official documentation and that what there is is years out of date and incomplete. 
As far a Pi4 goes I cant help with teh basic config. I own a few Pi3's but they are in a box gathering dust. I moved to mini pc's a long time ago. Tiny bit more money, but far more usable. For the base install of any of the options there are far better guides available on the internet. 
Back to your problem:=
You have'nt followed all the steps here. You are missing the extra palette in node red 
https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/wiki
V2 is very new and I still need to put up more detailed information
 
V1 had a very specific use case ( ie was designed around my installation at home ) , so without more examples and data extracts I cannot comment further. It was not designed for multi invertor plants. The data was all there, but you had to setup the sensors manually.
V2 was a full rewrite to try cater for the shortfall and limitations in V1 , it was designed as the base that could be built on, but atm is still specific, so depending on your plant/invertor setup there may be some work to do. 
I dont have a lab and I refuse to change my implementation at home  , so the only way I can cater for other setups is for someone to give me access to their system so I can see how teh data extract and plant looks or for them to get more knowlegable in node red. One kind gent did that and that is now the reason that we can populate the generator data. One missing bit of information gathering is still the mini invertor data which is still a big (?).
What I dont have time for is someone who says, ok you can look at my system but you only have 4 days ( and yes that has happened ). I was actually on a business trip in Germany, so I just shrugged my shoulders. 

Shot thanks, yea caught those initial SOC in the config after a while but luckily before I got this to work so set them to my defaults 👍
Just one more thing as I'm not sure if it is mentioned in your notes and I just missed it but might need to point out the custom card used for the below needs to be installed as well
custom:multiple-entity-row 😉