I will, thanks for this great Sunspec integration!
1 Like
I am trying to use “DC Energy Injected” and “DC Energy Absorbed” from Sunspec model 714 (DER DC Measurement) for the Energy monitor but when I add my device those entities are not being added to HA. I started looking at the code of this integration and also the Sunspec model_714.json file. Sunspec model_714.json file does not include a “units” value for any of its values and that seems to be the problem. I tried to find the model_714.json file to edit it manually but I could not find it. Anybody knows if this can be done? Thanks again
It looks like the SunSpec folks have missed to add units to the model specification file. This file (model_714.json) is used by the pySunSpec2 library which my integration relies on.
I have created an issue with them to get this fixed, you can upvote it here:
Thanks again. Do you know if the file can be modified locally in the mean time?
I was able to modify the model_714.json file. I found it somewhere in /mnt/data/docker/overlay2 by running the command: find /mnt/data/docker -name model_714.json. Now the entities in 714 are added correctly.
1 Like
I posted in the wrong Thread ! Edit went here Custom Component: ABB/Power-One/FIMER PV Inverters - SunSpec Modbus TCP - #98 by BinGraiban
The missing units for model 714 has been added in the latest version 
1 Like
I upgraded it and works fine, thank you! It has been working great for weeks. My HA energy panel looks great. Thanks!
1 Like
Hi there, I just started with HA so my knowledge about the structure isn’t very deep yet. I tested the sunspec integration to access my Elgris 3 phase smartmeter wich supports sunspec (and many other protocols).
All (around 50) entities appear, but most of them with wrong scale ( frequency 500000hz, current, voltage… Most of them 10e4 or 10e6 too large in scale. Watts are ok for example. Any ideas where I have to look to get this fixed? I’m running the HA core image on a RPI and installed the sunspec integration via Hacs.
Thanks, Benjamin
1 Like
Hello @TWM
Welcome to HA
This sounds like a scaling factor problem, it’s possible that their implementation is not 100% correct.
Try to open an issue at https://github.com/sunspec/pysunspec2/issues , this is the library that this integration uses and the problem is either in that library or in the smart meter firmware.
Regards,
Johan
CJNE,
I have an APSystems with 5 inverters which are reporting via Zigbee to a ECU with Sunspec enabled. Looking to your integration and default settings I see one inverter, but no values. I assigned each inverter an unique address 1-5. How I’m able to add the other ones and start testing the integration in HA? Looking forward to get it work 
Hello @ahof
I’m not familiar with APSystems, 5 inverters sounds impressive though, you must have a lot of solar power there
If each inverter has it’s own address assigned then you should be able to add them each separately (add the integration 5 times) using their respective address as slave id perhaps?
Is there any documentation available for the ECU? I could take a look if don’t work.
CJNE,
I dont have realy not so much Solar capacity. A total of 22 solar panels. APSystems, is a microinverter technology. A number of panels share an inverter which is placed behind the panels. So no string where 1 large inverter is used.
I send you the link with the details which I found on the internet, for example YC600 (2 panel inverter), I have also 5 QS1 (4 panel inverters), al reachable via a unique modbus address.
https://certifications.sunspec.org/PICS/Altenergy_Power_System_Inc.___single_phase_MicroinverterAPpcs_11-12.xlsx
Example of the ECU:
Hello
Would anyone here happen to have tried getting this workig with a Fox ESS Inverter? I am trying all sorts of ways at the moment. the inverter has SunSpec MODUS, on either TCP or RS485. I can see port 502 open on the IP on my LAN but having no joy at all.
Same issue, do you have already a solution?
@CJNE I’m having this issue when I try to add a ‘Read model’ from the dropdown. Worked fine on setup (with 160), but when I back to add anything else (or change the Scan interval), I get:
User input malformed: 160 is not a valid option for dictionary value @ data['models_enabled']
I note that I actually can’t ‘unselect’ 160… even when unticked in the dropdown, it still appears in the list (though I do want to keep it).
Loving this component… has made it very easy to get string (MTPP) level data from my Fronius inverters! Thanks @CJNE !
Is anyone else using with Fronius? I’m getting everything I need at the inverter level (I have two Fronius Primo 5.0 inverters), using slave ID 1 and 2 (first and second inverters), but can’t seem to access the “system-wide” data (e.g. import/export to grid etc.). I tried slave ID 0 (just times out) and 200 (does nothing) based on reading up on MODBUS, but no luck. Any ideas?
EDIT:
After having a dig through the Fronius Modbus specs, I found my Fronius Smartmeter at slave ID 245.
1 Like
I do note that I can work around this issue by deleted the component and then re-adding with the same name (and revised setting)… but would be nice to get fixed for easier on-the-fly changes.
I have one Symo inverter and two SmartMeter → ID 240 and 241
1 Like
Hi there, thanks for your great work!
I use a fronius symo gen24 inverter. Using model 160 I have a strange behaviour with MPPT 2 and 3. They represent the battery. Fronius documents, hat while charging or discharging the other data is set to 0. This leads in invalidating the data in HA. Can that be changed, so the data stays valid in HA?
Maybe someone else has the same issue?
The other issue, not being able to reconfigure the integration is already discussed. Maybe that’s a quick one?
Thanks!
teamvc
1 Like