Empty readings from meter #4
Comments
|
Hi, |
|
That's the procedure I followed in order to enable ModBus TCP, it's really weird that I'm not getting only part of the data 🤔 Thanks for your reply, though! |
|
What firmware level is the SolarEdge? I had some time out troubles, after a call with SolarEdgw support they updated my firmware and the troubles were solved. |
|
I’m on 3.2173, which according to the readme of this repo appears to be problematic. |
|
@LucaTNT I was just about to raise an issue for the same thing, it looks like we have the same type of export meter. Using latest version of this library. lloyd@xps13:~/Dropbox/code/sunspec-monitor$ ./sunspec-status -v 192.168.1.6
INVERTER:
Model: SolarEdge SE3680
Firmware version: 3.2016
Serial Number: ...
Status: ON (MPPT)
Power Output (AC): 884 W
Power Input (DC): 898 W
Efficiency: 98.50 %
Total Production: 2711.770 kWh
Voltage (AC): 238.90 V (49.96 Hz)
Current (AC): 3.75 A
Voltage (DC): 380.40 V
Current (DC): 2.36 A
Temperature: 33.05 C (heatsink)
METER (#1):
Model: WattNode WNC-3Y-400-MB
Option: Export+Import
Firmware version: 24
Serial Number: ...
Exported Energy: 0.000 kWh
Imported Energy: 0.000 kWh
Real Power: 0 W
Apparent Power: 0 VA
Power Factor: -0.00
Voltage (AC): 0.00 V (0.00 Hz)
Current (AC): 0.00 ADropped debug dump here, https://gist.github.com/lloydwatkin/6f99110ba1bbd9828bfa21da1e4128e9 |
|
I've read the meter data using a different library to confirm that this library isn't the issue, and can confirm that is the case (@LucaTNT if you hear anything back about this issue please do let me know - and I'll do the same). lloyd@xps13:~/Dropbox/code/sunspec-monitor$ modbus read 192.168.1.6 400190 64
400190 105
400191 32768
400192 32768
400193 32768
400194 32768
400195 32768
400196 32768
400197 32768
400198 32768
400199 32768
400200 32768
400201 32768
400202 32768
400203 32768
400204 32768
400205 32768
400206 32768
400207 32768
400208 32768
400209 32768
400210 32768
400211 32768
400212 32768
400213 32768
400214 32768
400215 32768
400216 32768
400217 32768
400218 32768
400219 32768
400220 32768
400221 32768
400222 32768
400223 32768
400224 32768
400225 32768
400226 32768
400227 0
400228 0
400229 0
400230 0
400231 0
400232 0
400233 0
400234 0
400235 0
400236 0
400237 0
400238 0
400239 0
400240 0
400241 0
400242 0
400243 32768
400244 0
400245 0
400246 0
400247 0
400248 0
400249 0
400250 0
400251 0
400252 0
400253 0 |
|
@lloydwatkin I contacted SolarEdge and they remotely updated my inverter, but nothing changed. |
|
I've emailed the installer today who have past the request to solaredge so will update with feedback. My meter is number 1 so its not your meter number. As I paid extra to have the modbus installed (for the very purpose of monitoring inside my own network) I consider this a product defect so will insist its fixed by the installer 👍 |
|
But also, I can see the data in the solaredge portal (because that's how I get import/export/production data) so its obviously has the correct information somewhere. |
|
@lloydwatkin great, thanks for keeping us posted, Lloyd! |
|
Solaredge updated my inverter today (hence readme pull request). They claim
that's fixed it, but data shows not). I'm convinced the installer hasn't
configured something correctly so I'm still chasing them.
…On Tue, 17 Apr 2018, 6:37 pm Luca Zorzi, ***@***.***> wrote:
@lloydwatkin <https://github.com/lloydwatkin> great, thanks for keeping
us posted, Lloyd!
Let me know if I can be of any help 💪
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQlBj_amzOODb4qfkkVsyRYftctQwvrks5tpihMgaJpZM4SlVKV>
.
|
|
@LucaTNT does your setup also export data to solaredge portal? Mine does. Apparently the wattnode device can either be set up to export data in a fashion suitable for the portal or sunspec, but not both. Meaning you'd need to purchase and fit an additional meter. I'm chasing this up with my installer since I specifically asked about this at the time and was told I'd be able to do both. I may experiment and switch my meter setup to see if I can get the data out, but we also like having the portal so I don't want to log data internally exclusively (and Solaredge don't have an API for pushing data). |
|
That's exactly my case: I export all the data to the SolarEdge portal (the
iPhone app is very convenient), but I'd also like to have access to the raw
data from the meter.
Thanks for your help!
|
|
I've sent more questions to solaredge about a second meter (~£250 in the
UK) and how to flip the device to log to sunspec. Will keep you updated.
…On 27 April 2018 at 14:34, Luca Zorzi ***@***.***> wrote:
That's exactly my case: I export all the data to the SolarEdge portal (the
iPhone app is very convenient), but I'd also like to have access to the raw
data from the meter.
Thanks for your help!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQlBqDTfw7hJcw_I6MlCxP5jU6ZybC1ks5tsx5SgaJpZM4SlVKV>
.
|
|
I am having the same problem, is there any solution to this? sunspec-monitor$ ./sunspec-status -v 10.1.0.101 Power Output (AC): 672 W METER (#1): Exported Energy: 0.000 kWh |
|
@mcmellow are you able to post your output? Specifically I'm interested in what meter you have installed so I can look into that. |
There is no meter installed in my situation. It is just the inverter |
|
I'm still in discussions on this. Solar installer is kicking the can down the road and has set me up for a tech call with SolarEdge direct. Looks like you might need a |
|
This the output of my inveter sunspec-status -v -m 0 192.168.xxx.xxx INVERTER: Power Output (AC): 278 W I hope this helps |
|
Wow, I am having this exact same issue. I have the same WattNode Meter as you and the exact same issue. I have had SolarEdge update the firmware, etc. and no change. In fact, after they did that a week ago, they then started to ignore my support ticket, which is very annoying. I'm gonna watch this thread very closely as I to was pretty clear with my installers about what I wanted to do and why, so very annoyed that I've been unable to get the data out for Home Automation stuff. Just in case it's of interest, here's my output, but I've used all the same scripts as you guys already to confirm through many sources that the data simply seems not to be coming out of the Mete correctly: `INVERTER: Power Output (AC): 758 W METER (#1): Exported Energy: 0.000 kWh |
|
Yeah our meter doesn't export in sunspec format. I too was very clear with
my installer about what I expected and was told it was possible (developers
🙄). I'm still awaiting a call from SolarEdge via the installers.
In the meantime I'm looking again at openelec monitor which does what we
need - I abandoned this idea after paying extra for the modbus after I was
told the functionality existed.
It seems there's many installers out there installing equipment they don't understand unfortunately. Trustpilot review in preparation and this will be one point on the list of areas where they messed up the install 😂
…On Tue, 16 Oct 2018, 11:55 am wraithrmm, ***@***.***> wrote:
Wow, I am having this exact same issue.
I have the same WattNode Meter as you and the exact same issue.
I have had SolarEdge update the firmware, etc. and no change. In fact,
after they did that a week ago, they then started to ignore my support
ticket, which is very annoying.
I'm gonna watch this thread very closely as I to was pretty clear with my
installers about what I wanted to do and why, so very annoyed that I've
been unable to get the data out for Home Automation stuff.
Just in case it's of interest, here's my output, but I've used all the
same scripts as you guys already to confirm through many sources that the
data simply seems not to be coming out of the Mete correctly:
`INVERTER:
Model: SolarEdge SE6000
Firmware version: 3.2251
Serial Number: 73163C5B
Power Output (AC): 758 W
Power Input (DC): 769 W
Efficiency: 98.49 %
Total Production: 617.070 kWh
Voltage (AC): 245.30 V (49.98 Hz)
Current (AC): 3.12 A
Voltage (DC): 389.90 V
Current (DC): 1.97 A
Temperature: 28.60 C (heatsink)
METER (#1 <#1>):
Model: WattNode WND-3Y-400-MB
Option: Export+Import
Firmware version: 25
Serial Number: 4136367
Exported Energy: 0.000 kWh
Imported Energy: 0.000 kWh
Real Power: 0 W
Apparent Power: 0 VA
Power Factor: -0.00
Voltage (AC): 0.00 V (0.00 Hz)
Current (AC): 0.00 A`
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQlBntqzOie9a9Jt9vJtxcHA7yjeJjqks5ulbsugaJpZM4SlVKV>
.
|
|
UPDATE TO KEEP THIS THREAD LIVE: The technician at SolarEdge has informed me he cannot deal with the issue and he needs to escalate the problem. After this I have yet to be contacted with anything. Currently I'm also getting my installer to apply some pressure from the 'Installer' path and if this fails, I'm going to throw all my toys of of my pram at my installer and insist they remove the defective equipment in place of something that works. They have admitted several times that they don't understand the feature of the Inverter, which is not acceptable really, as they are the people making the promises before you hand over your money. |
|
@wraithrmm I had a call from solaredge last week who said they'd follow up later the same day. I've heard nothing back. My situation is essentially the same as yours. |
|
So.... I had a reply from the Solar Edge people at long last. I read as follows: "Dear Wraith, The upshot then is that we cannot both send the data to the Solar Edge Portal AND collect said information locally over TCP with only one meter. Which is totally ridiculous, but... a fact none the less. I've told my installer this and called them out on their general lack of understanding of the products they are selling. I don't expect anything to come of it to be honest but just in case anyone else reads this and is in the market for solar panels, they are called Naked Solar and while very friendly until you pay them their money, their installers are carless, lack attention to detail and clearly make promises they cannot fulfil as they don't understand the hardware they are selling. Anyhow, all that is beside the point. I'm not sure what I can do to resolve this atm, without purchasing a second meter, which rather defeats the point of USING it to SAVE ME MONEY in the first place. :-( I've tried to packet-sniff on a hub, etc. to get the data, but have yet to find anything at all, let alone be able to decode it. As such, I think this TCP feature is a no-go for me unless I disconnect from the Solar Edge portal completely, which I don't really want to do either. If anyone finds anything more helpful then I did, please do let us know :-) |
|
@wraithrmm yes this is the information I had already - just trying to get my installer to realise it (and I've told them this information several times). You can have two meters connected at the same time, which is one bonus (I found the meter on ebay but it was around $240). Another solution would be to update the API endpoint on the inverter to send data to an internal server and then proxy this through to solaredge. The issue here is that, I assume, you'd lose the ability to receive firmware updates (although I guess you could revert to get updates). Although I seem to remember there being an issue with solaredge adding some certificate to the inverter so you'd need to decode that. I'm going to continue to push my installer to put in the correct gear. In the meantime I'm planning on getting an openelecmonitor (the cheaper 4 CT box) which pushes data over MQTT and then combine this with calls to the inverter. https://openenergymonitor.com/emontx-v3-electricity-monitoring-transmitter/ |
|
My setup is two RWND-3D-240-MB meters, 1st meter is configured "Production" (this is inside the DC disconnect box that was included with the SE11400 Inverter), 2nd meter is configured "Export+Import" and has current clamps installed at grid connection point. I have no issues reading data from both meters locally. After 2nd meter was added, this enabled seeing "Consumption" and "Self Consumption" in the SolarEdge portal automatically. One thing to try might be to put "Export+Import" meter as 2nd meter, if one doesnt have separate production meter. As it could be that inverter firmware expects first meter to be always a production meter... |
|
I have success! I've been talking to the following member of staff at solaredge [email protected]. His response today was:
....and then...
Woo hoo! I hope this is able to help others. |
|
I can also confirm that data is still being shared with the solaredge portal too. |
Connects to tjko#4
|
Another update for solaredge this morning:
|
|
OMG YES! This was it. I placed a support request with SolarEdge and they moved it to meter 1 within 2 hours and then everything just started working! I cannot BELIEVE how much effort that took and how few people actually know how the inverter is supposed to work in their own company, but am SO glad it's now working (before I spent £100 on some alternate solution). Thank you so much for sharing this solution. |
|
So I need to ask SolarEdge to update my inverter and it will automagically work? Thanks for your help guys! |
|
@LucaTNT I think so. |
|
So I’ve managed to get it all hooked up to Hass.io now using its native MODBUS support and the up to the second data is not driving my Immerssion heater :-) This is my Hass.io copy of the Solar Edge reporting app, that now works even if there is not internet access to the home :-) https://www.dropbox.com/s/6u9yd8qbjo3dj9k/2018-11-16%2020.09.02.png?dl=0 |
Hi, I'm really interested to know your hass.io configuration, the dropbox link is dead. I have got the modbus component configured but can't read the correct sensor info into from the registers. |
|
I used this modbus config to get the values originally, which kinda worked a bit: But I ran into all sorts of issues with the modbus system as it queries for each of these values in separate calls, which often resulted in things being out of sync and created allot of lag due to multiple calls to collect the ENTIRE modbus block, but then only use one register from it :-/ One of the biggest issues was it not having the correct scale factors as they would get out of sync occasionally, causing insane spikes in the reporting. As such, I ended up creating my very own component for use with this, which solves all of these problems and now I have fully replicated the Solar Edge UI in Hasss.io using the new Lovelace image card and the reporting fugures from the modbus. Here's the code, you should put it into a file called "/config/custom_components/modbus1.py" Then another file here "custom_components/sensor/modbus1.py" Then finally the config I have for this is as follows: Note: Please don't shoot me for the bad implementation. It's not the best code and is based on what I could find from the original modbus code as I'm not a very confident coder in python. But it works and so you are welcome to give it a go if you like. :-) |
Wow, this is great and works perfectly!! I had exactly the issues you described using the inbuilt modbus component. I can now reliably use the modbus data to make load control decisions in seconds... rather than waiting minutes due to the solaredge api restrictions. Also, I was never a fan of the semonitor.py solution... I tried for ages to retrieve my inverter key using rs232/485/wireshark but had no luck. If you still want per-panel data I guess there is no alternative, but for anyone with a modbus meter on a solaredge installation this is a far simpler and elegant solution to get realtime production/consumption data without breaking the existing monitoring. Thanks for your work on this! |
|
OMG yes, I know what you mean, I spent DAYS trying to sniff the packets, etc. Didn't work at all. I have to be honest, I really was NOT expecting it to work for you from my code (you know how these things usually go). :-p But you are very welcome and I hope others can also benefit from it to. :-) I love being able to have my heating etc all responding and use my excess power generation. Saves me allot of money and all told (aside from allot of effort on my part) this has saved me £800 for the Immersion Heater Power Diversion Unit :-p And just for reference, here's a re-share of the Hass.io UI I put in place: https://www.dropbox.com/s/y1rq39z17g6wj1i/2019-01-30%2009.53.17.png?dl=0 It's identical to the SolarEdge one, but way more responsive. |
|
Hi people! Just a heads-up. I updated to Home Assistant 0.87.1 the other day and everything stopped working! :-( After a few hours of crying into my pillow, I man'ed up and sorted it out. Turns out there is a dependance that is a bit old in the code, look for ['pymodbus==1.3.1']. This needs to be updated as that version of the pymodbus thing is no longer supported. Simply change this to ['pymodbus==2.1.0'] and then restart Home Assistant and it all works again. YAY! Just for all future people that come across this, I have already edited my original post with this code in it. :-) |
|
@wraithrmm The recent changes to home assistant custom component file locations have broken the modbus custom component code you posted earlier, it looks like everything now needs to reside under custom_components/modbus1. Have you had any luck getting this to work on newer versions of home assistant? |
Very interesting. I am running against the same issue with using the modbus implementation as is, being scale factor and readings out of sync. I now end up with spikes because I get a duplicate reading before the switch of scale factor. Could you explain in some kind of psuedo language how you resolved it? I am reading the modbus via loxone and this writes down every value. I am then monitoring the measurement from loxone with node red and writing it to a mysql database. The only solution I have for now is post process checking the value before and after to detect if it's a spike and if yes, delete the record. I would however like to move this somewhere before saving it to the database but I have no idea how to check if the SF and value are "in sync". |
Hi,
I'm not sure if this is the right place to ask this question, but I'll give it a shot anyway.
I have a SolarEdge SE6000 inverter + a WattNode WND-3Y-400-MB meter.
All the data coming from the inverter is correctly shown, while I can only see Model, Option, Firmware version and Serial Number of the meter.
All the other data coming from the meter is 0, it appears that the ModBUS data is empty (see below).
Do you think this could be due to a misconfiguration on the inverter? Any hint would be appreciated, thank you very much.
$VAR1 = { 'M_AC_Power_C' => -32768, 'M_AC_Voltage_LL' => -32768, 'M_Imported' => 0, 'M_AC_VA_C' => -32768, 'M_AC_PF_A' => -32768, 'M_Import_VARh_Q2B' => 0, 'M_AC_Voltage_AB' => -32768, 'M_AC_Freq' => -32768, 'M_AC_VAR_SF' => -32768, 'M_Exported_VA' => 0, 'M_Imported_VA_C' => 0, 'M_AC_Power_SF' => -32768, 'M_Exported_VA_B' => 0, 'M_AC_Power' => -32768, 'M_Import_VARh_Q2' => 0, 'M_Import_VARh_Q4' => 0, 'M_Imported_VA' => 0, 'M_Energy_W_SF' => -32768, 'M_Events' => 131072, 'M_Import_VARh_Q1C' => 0, 'M_Energy_VAR_SF' => -32768, 'M_AC_Power_B' => -32768, 'M_Exported' => 0, 'M_Exported_VA_A' => 0, 'M_Import_VARh_Q1' => 0, 'M_Exported_B' => 0, 'M_AC_Current_A' => -32768, 'M_AC_Voltage_AN' => -32768, 'M_AC_Current_B' => -32768, 'M_AC_Voltage_BC' => -32768, 'M_AC_PF_C' => -32768, 'M_AC_Voltage_CA' => -32768, 'M_AC_Current_SF' => -32768, 'M_AC_VA_B' => -32768, 'M_Import_VARh_Q3A' => 0, 'M_Import_VARh_Q3' => 0, 'M_AC_Power_A' => -32768, 'M_AC_Voltage_BN' => -32768, 'M_Imported_B' => 0, 'M_AC_Voltage_LN' => -32768, 'M_Import_VARh_Q4A' => 0, 'M_Imported_A' => 0, 'M_Imported_VA_B' => 0, 'M_AC_Current_C' => -32768, 'C_SunSpec_DID' => 201, 'M_AC_VAR_B' => -32768, 'M_Import_VARh_Q4B' => 0, 'M_AC_Current' => -32768, 'M_Imported_VA_A' => 0, 'M_AC_VA' => -32768, 'M_Import_VARh_Q1A' => 0, 'M_Exported_VA_C' => 0, 'M_AC_PF' => -32768, 'C_SunSpec_Length' => 105, 'M_Exported_C' => 0, 'M_AC_Freq_SF' => -32768, 'M_Exported_A' => 0, 'M_Import_VARh_Q2A' => 0, 'M_AC_VAR_A' => -32768, 'M_AC_VA_A' => -32768, 'M_Imported_C' => 0, 'M_Energy_VA_SF' => -32768, 'M_Import_VARh_Q4C' => 0, 'M_AC_Voltage_CN' => -32768, 'M_Import_VARh_Q3B' => 0, 'M_AC_PF_SF' => -32768, 'M_AC_VA_SF' => -32768, 'M_Import_VARh_Q3C' => 0, 'M_Import_VARh_Q1B' => 0, 'M_AC_VAR_C' => -32768, 'M_AC_PF_B' => -32768, 'M_AC_VAR' => -32768, 'M_Import_VARh_Q2C' => 0, 'M_AC_Voltage_SF' => -32768 };The text was updated successfully, but these errors were encountered: