[Feature Request]: Wallbox Integration #491
Comments
|
Please share product integration details like modbus definitions of this carcharger. |
|
I will not develop things if I cannot test it myself against the actual car charger. I'm also not sure if this needs to be part of this integration: if it needs its own Modbus connection to communicate with, a separate integration is a better idea. I'm leaving this open for now, hoping that another developer shows interest to implement it. |
|
@SvenAbels If you refer to the user manual for the chargers, they are installed either with an ethernet connection to a DDSU / DTSU-666-FE Note: Usually this is a 666H with RS485 communication, but it appears there is now an 'FE' model that has Fast Ethernet / RJ45 instead. This model however appears to be aimed at people without a Huawei inverter and allows the 666-FE to connect to your home network (and then to FusionSolar on the internet) and for the EV charger to also connect to the LAN, and then allow the EV charger to directly query the 666-FE for meter data using modbus-tcp. For sites with a Huawei inverter (and optional LUNA ESS) the EV charger is installed using "virtual meter mode", that sees the EV charger connected to the home network using the RJ-45 Ethernet port, and it then connects to the sDongle via modbus-tcp. Given the inverter (that the sDongle is connected to) has an RS485 connection to the DDSU/DTSU-666H meter, this would mean the EV charger is querying (client) the inverter for the power meter data (via modbus-tcp). Given above, I don't think that you'll be able to get any information FROM the EV charge itself. It might be worth having a look instead at the Energy Management Assistant Huawei (EMMA-A01/A02) that are coming out shortly, and look like being positioned to replace the use of DDSU / DTSU-666H meters (that are actually made by CHINT, not Huawei). These WILL combine the functions of these meters, plus the SmartLogger and it appears also the sDongle (with the EMMA having an RS485 port to communicate with the inverter(s) and via that, the LUNA ESS and then also have 2 x Fast Ethernet ports (RJ-45) with 1 x Internal (this looks like it is used to direct patch/connect to an EV charger though, and is not for "LAN" connectivity) and 1 x WAN port (connecting it to your home LAN and providing it access to FusionSolar portal, whilst also potentially providing the modbus-tcp access to the inverter [ if it replaces the sDongle]). Quick Guide – https://support.huawei.com/enterprise/en/doc/EDOC1100321602 User Manual – https://support.huawei.com/enterprise/en/doc/EDOC1100325377 FusionSolar App Quick Guide (EMMA) – https://support.huawei.com/enterprise/en/doc/EDOC1100312274?idPath=258788303|258788491|258789989|23205712|21608721 From the EMMA user guide:
Note: The EV charger will be required to have firmware 'FusionCharge V100R023C10' installed to communicate to the EMMA. However, current version released on the 28th April 2023 is 'FusionCharge V100R022C10SPC070' (see: https://support.huawei.com/enterprise/en/fusioncharge/fusioncharge-pid-254563737 ), so it would appear an EV charger firmware update will be released AFTER the EMMA is released. In summary... a) It appears there's no 'smarts' built into the EV charger itself, if you want to remotely control it at this time it might be best to look at the FusionSolar integration ( https://github.com/tijsverkoyen/HomeAssistant-FusionSolar ) and see if there's any management/reporting that is available via that integration / API. Edit: You need to keep a watch on this for the Northbound interface reference being updated, as it appears the EV charger is not (currently?) a published entity: https://support.huawei.com/enterprise/en/site-power-facility/imaster-neteco-pid-251993099?category=reference-guides b) Watch and wait and see what happens with the EMMA-A02 model and see if it adds support for managing/monitoring the EV chargers, or if its just being able to support the chargers querying the EMMA over modbus-tcp for "power meter" type data. c) Watch and wait and see what happens with the EMMA-A02 model and if it replaces the DDSU/DTSU-666H meters, and IF any additional updates are made to the Huawei inverters modbus registers to support managing/monitoring the EV chargers (same as how the inverters can manage/monitor a LUNA battery connected to them via RS485 cable....). Side Note: There is a discussion thread created re the EMMA device, to allow discussion about this and the affect on deployments and subsequent flow through affect to WLCRS's great integration (and do we need to sponsor him to fund him getting one, to allow for testing / adding support for EMMA) ;-) See Discussion Thread: #457 |
|
Hi @Roving-Ronin , first of all I'd like to thank you for the excellent and detailed information. I was not aware of the upcoming EMMA device. I purchased a Huawei Inverter which will soon be connected via the "traditional" DTSU-666H meter and a FusionSolar Smart Charger. Indeed my understanding is that the chargwer will use the virtual meter solution to communicate with Fusion Solar. This means that the charger will use a plain Wifi-connection to connect to the FusionSolar service. The interverter is connected using the com port to the DTSU-666H meter and via the sDongle to the web. As far as I can see, the charger does not need to use its FE connection as everything can be done via Wifi, which I would also prefer. Please correct me if I'm wrong. This setup allows to configure the charger via the Fusion Solar app to charge the vehicle only with solar power when it's avialable. My request for my original posting here was that I was hoping for 2 things: For the first point (a) I could also use a workacound by adding a shelly device in front of my charger power but for the second point (b) I can't find any solution. Of course I can do this from the FusionSolar app but everything else in my house is already integrated into HomeAssistant so such a switch would be nice. Best regards, Sven |
|
Just found this that covers scenarios for the EV chargers install and usage, including options for https://photomate.zendesk.com/hc/en-gb/article_attachments/10442149835805 Includes this, that says Fast Ethernet on the charger and the sDongle (No info on if an EMMA is used instead of a DDSU/DSTU-666H, given its still to hit the market) are to be used, in preferance to WiFi.
Also it advises if you have a charger and inverter talking together (to get the DTSU-666H meter data) then this will stop the sDongle supporting any other modbus-tcp access (i.e. WLCRS integration !). This may be worked around by needing to install the Modbus Proxy via HACS, so the sDongle only 'sees' one modbus-tcp connection, yet WLCRS + Charger talk to it via the Proxy. This would need to be tested and stability checked, as the proxy does take some time to start up and could see the integration and charger timeout waiting for it. Charging options and 'where' to get the power from are covered in Section 2.2.2 - https://photomate.zendesk.com/hc/en-gb/article_attachments/10442149835805#%5B%7B%22num%22%3A1120%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22XYZ%22%7D%2Cnull%2C422.16483%2Cnull%5D Reading this and re-evaluating it, and their options to install just a charger (with DSTU-666FE meter) or in certain situations where you can't connect the charger and inverter together (so the charger can access the DSTU-666 data via the sDongle and modbus-tcp) to instead install DSTU-666FE (in addition to the existing DTSU-666H that is providing data to the inverter via RS485), as per this diagram:
It looks more like the EV chargers are really a seperate device from the whole other inverter / battery environment. This (and especially being able to be installed without an inverter setup) would mean the 'smarts' / communication is all contained within the EV charger, with it appearing to be being controlled via FusionSolar / App on phone. If this is so, this would likely mean this integration would be unlikely to support it, unless the ev chargers end up supporting modbus-tcp access themselves. However this seems unlikely, as these chargers have been on the market for a while and there is no documentation or mention of modbus support from Huawei, and just the Communication Matrix (for SPC070) doesn't appear to support modbus connections to the ev chargers, instead it looks like the charger just uses modbus to query the DTSU-666FE meter or ' Virtual Meter' (i.e. sDongle on inverter, that would pass through the DTSU-666H wired to it via RS485) Traffic Flow - Charger as Destination Traffic Flow - Charger as Source Anyhow... apologies for long and rambling, as sourcing info and trying to work out how this charger works... :-( But it really looks like it is a modbus-tcp client (not server) and its controlled via mobile app and/or FusionSolar, which (if you have a PV plant setup) is where it gets the info as to how much PV capacity you have. This data then being used, in conjunction with the Power Meter (ie. Active Power) to allow the charger to determine if your PV is exporting (so a positive number in HA for Active Power) and when it reaches the minimum level of surplus power, to then turn the charger on (and off etc). This is assuming setting it up to preference PV power charging over grid. If this is correct it still goes back to there is limited chance the WLCRS integration will be able to work with the ev Charger, as it doesn't have modbus access (server) and it doesn't tie into the inverter's RS485 cascade /modbus setup, so there's no way to talk to it. As mentioned above the best option looks to be to see if the FusionSolar integration adds support for it (that would require Huawei API supporting / publishing it). Doing it this way (if/when available) would still allow you to "have a switch" in HA to allow toggling charge from PV / Grid, as the FusionSolar would provide you a sensor entity to do this, you'd just need to add it into your dashboard. Re the tracking Active Power (W) and total consumption of Energy (kWh) you would be easiest to do with with a Shelly EM3 or IoTaWatt appliance with their own CT clamps. I can't find any mention and it looks like Hauwei also haven't included support for Open Charge Point Protocol (OCPP), that allows 3rd party software to pull data from inverters (or their consumption meter data) and then use AI to work out when to charge / Grid vs PV / when cheapest. An example being https://chargehq.net/ but alas Huawei inverters aren't supported by them (yet?) |
|
Hi @Roving-Ronin , thank you for your ramblings! They were quite enlightening. I agree with your conclusions:
I'm keeping this issue open for now to aid discoverability due to all the noteworthy info in it, but I'll mark it as 'wontfix'. |
wlcrs
added
wontfix
|
First of all: Thanks alot for the detailed information and the detailed research. This is really amazing and I highly appreciate your help! :-) However, the information means that the situation is actually worse than I expected because in reality it means that I either need to rely on a proxy which might be stable or not or that I have to choose between making my charger smart or using this integration. The fact that the modbus-tcp connection of the wallbox is limited to one device was a surprise to me. I could buy this additional DTSU666-FE but it's hard to eveb buy it here in my region. Therefore, I will switch to another charger with a seperate smart meter (go-e) so that it does not impact the modbus tcp connection. However, the general problem will of course still exist for anyone who buys a Huawei charger in connection with the Huawei inverter and if you order all at the same time then it's not unlikely that you want to stay at the same manufacturer. I wonder why Huawei implemted the charger this way... |
|
I think the one to watch will be the option of the EMMA. As per the first picture / page pasted above, the logical diagram Huawei has provided shows the EV charger directed patched via Cat5/6 cable, between it and the EMMA. Conversely the EMMA is only shown connecting to the inverter(s) using RS485 serial cable.
As above, we'll still have to wait and grab the release notes and communication matrix info from when EMMA is released soon. PS. I think that looking to support EMMA would appear to be critical for the integration, giving it is being pushed as the default install and connectivity method on Huawei installs in future. Still waiting to get hands on the Modbus register definitions, but hopeful that as it's the 'next generation' of the DDSU / DTSU (& a heap more features / functions) that it will see the existing Modbus registers for the meter be used for it (& extra registers added if needed), which would mean it would be compatible with wlcrs for the existing meter data. Definitely worth every sponsoring $10 for wlcrs to upgrade his setup to a EMMA in future ;-) |
|
Good evening, I was following your very sophisicated discussion and would like to bring in 2 other facts. I have an Inverter (10kw) combined with a Luna 10kWh and a DTSU-666 smart meter installed. Your integration is connected via RPI-WIFI-Inverter -> from my point of view very stable. Trying it out at home - could connect to the wallbox via Modbus-tool: Some values arrive - but continuously - no clue what that is, but maybe you experts have an idea. |
|
@trollsoft7 So you connected the charger but you can still use the home assistant wlcrs integration? |
|
Yes - charger is connected and I see it in the fusion portal. wlcrs-integration continues to work flawlessly. As written my HA-RPi4 is connected to the Inverters WIFI (which is not recommended in WLCRS-documentation, but it works very stable for me). Though I haven't charged a car yet, as I don't have any :-(. |
|
Hi, i got pretty much the same setup as @trollsoft7 but I use a wifi-router to connect via client-mode to the inverter-Wifi, all very stable. I would also really like to get this topic forward, and I also got a car, so I could report back on actual charging. |
|
@chrissi5120 so your RPi4 has 2 x WiFi dongles and they connect to the inbuilt (commissioning) WiF AP on each inverter, whilst you have the WallCharger connected to the LAN. This is a software architecture question that falls to how WLCRS wants to add support for the wallbox. Using that method would mean requiring a method of indicating and/or detecting that your connecting directly to the WallBox whereas with the apparent move from sDongles and DDSU/DTSU-666 meters to instead using EMMA appliances (that have the meter/CT functionality, and also a direct connection LAN port for plugging in the WallBox, RS485 to talk with inverters/batteries and a WAN port to connect it to the home network (and FusionSolar / modbus-tcp support etc) that would require supporting that (default) method. EMMA Issue/Discussion - #498 |
|
Hey guys, I am also very interested in having the Wallbox integrated into home assistant mainly for tracking of power usage for the car, so read-only information gathering. I would be grateful for any kind of implementation and am willing to give feedback if needed. |
|
Hello, I would also be very interested in a solution ;) Huawei Sun 10kw SDoungel and Wallbox Connected via Wi-Fi |
|
Just wondering if anyone with a SmartCharger has managed to connect to it, using modbus and the register list above? How are your SmartChargers also connected into the Huawei Inverters / PV setup? Looking at this post (above - #491 (comment) ) it looks like you can either connect the SmartCharger to the meter using a 'virtual meter', but that uses up the single modbus-tcp connection the sDongle WiFi+FE provides, and therefore stops WCLRS being able to connect. Alternatively it looks like you have to install a second DTSU-666FE (Fast Ethernet) meter (Datasheet - https://cdn.shopify.com/s/files/1/0781/9748/9944/files/Huawei_TDS_DDSU666-FE_EV-Charger__EN.pdf?v=1708256060 ) that the SmartCharger connects to over the home FastEthernet (wired) network. Meaning you'd have a DDSU/DTSU-666H meter that is wired into the Inverter(s) via RS485 and operating seperate, just to provide Grid Power/Energy data to the SmartCharger would be this new/secondary DTSU-666-FE meter. Edit: Found this that shows an example of having Inverter/PV (optional LUNA ESS) and existing DDSU/DTSU-666H meter connected via RS485. Shows needing to add a DDSU/DTSU-666-FE meter for the SmartChargers use.
No mention if you could swap out the existing 666-H meter for a new 666-FE meter and have the Inverter(s) connect to it via RS485, whilst the SmartCharger connects via the network. I would assume the SmartCharger is connecting modbus (via FE) and the Inverters also (via RS485), that would prohibit this being possible though, as both Inverter/Charger would be thinking their the Master device in the modbus chain and conflict...? If your using something like https://qmodbus.sourceforge.net/ to query the SmartCharger and see if the modbus responds, I've just found these document that has some more 'realistic' appearing modbus numbers, but its confusing if these are for the SmartChargers or are for FusionCharge DC (i.e. commercial EV charge setup) devices. If anyone could test it would be appreciated.
From: Northbound Modbus-TCP Interconnection Protocol for AC Chargers |
|
@Roving-Ronin I tried to poll the wallbox with your "new" addresses - as soon it connects (directly to the wallbox port 502) it starts receiving (one message per second): Sending a request for example for charging control at 8198 register does not change anything. It seems to be ignored. Maybe following information is also interesting: in the setup menu of the Wallbox I can choose a 3rd-party-application with a IP-address. I used the IP of Home Assistant - but of course nothing happens, as home assistant should run a modbus-server, which it isn't. Thanks for all your efforts! |
|
I have received full documentation from Huawey Support below |
|
Previously mentioned "I can't find any mention and it looks like Hauwei also haven't included support for Open Charge Point Protocol (OCPP), that allows 3rd party software to pull data from inverters (or their consumption meter data) and then use AI to work out when to charge / Grid vs PV / when cheapest. An example being https://chargehq.net/ but alas Huawei inverters aren't supported by them (yet?)" Just looking at this again and noticed OCPP 1.6 support is "planned to be available via software upgrade in 2023.Q4" and current manual refers to it:
|
|
Joining the conversation as I just installed one of these boxes today and needed it integrated to home assistant. I have infra and comfortable with a keyboard but have little knowledge about modbus-signaling. Happy to help if anyone needs hands on the setup here to test or debug. edit They also tried reading the telemetry data directly but hit a wall with a required tls-certificate which must be trusted by huawei already so a self-signed didn't work. I think I found a third attempt which was to read the data from when a " third party nmt server " IP was added to config in charging station settings and then run a nmt server but I believe this also ended up failing due to ssl. Perhaps these two last ones were the same, either way I think the way to go is to file a report to huawei and wait for next patch. You found it listed in documentation as supported simply because it states that it should be by now but a unit test probably went missing at release and it didn't get discovered until this thread started digging. |
|
Hi, everyone, Any further developments on this end? It seems really odd that with all data available on FusionSolar and having the Scharger connected to the inverter and Sdongle, we may not be able to get some data. I am waiting for a contact in Spain to help with this and OCPP (it seems to be supported but there's no option on the menu to get it working). I believe the guy is on vacation, but as soon as I hear from him I will let you know. Cheers |
|
Please read up the thread (& also EMMA thread). ATM we are still seeking more/clarification of the Modbus registers for the SCharger. Given we've been lucky enough to get what appears to be valid register definitions for the EMMA effort (as people have time) is focused there. There are some SCharger Modbus registers in the EMMA btw, but they have to be validated, let alone they appear to o my be a subset of the overall list of registers (ie iirc doesn't have registers for setting max kW limit, or on/off?). Btw re your comment about not being able to work, but you have it connected and also an sDongle. The issue there is that the SCharger uses the sDongle to create a 'virtual meter' to provide the SCharger with power/current/energy data. However in doo g this it uses the SINGLE connection for Modbus the SDongle allows for, thereby stopping any others (such as from HomeAssistant). |
|
Hi @Roving-Ronin, Thanks for the reply. I've been reading the thread and was just not fully understanding why it was not possible to get it integrated. Anyhow, with you explanation on the Modbus single connection, I got it. Also, as promised, I heard back from Huawei on the OCCP protocol and enabling it on the SCharger. Seems like there is the need to install a "special" version (060), which I attach, along with the OCCP Commissioning manual. Hope this may help. FusionCharge_V100R023C10SPC060_FusionCharge-EU-CHARGE.zip Cheers |
|
Obviously @DNAngelX did the job for ioBroker - https://github.com/DNAngelX/ioBroker.huawei-charger/tree/main |
|
Hello all
In the inveter parameters, I says "adress of the powermeter" |
Hi, Yes, that's correct, That's exactly what happened in my case as well. Once I got the WLAN FE for the inverter, I was able to get the SCharger to get the virtual meter and have a balanced installation (means that it will not overload the power available from the network). I also hoped that Huawei managed this way better and in a different way, having a meter directly embebed on the Charger for example as many other brands. Also the OCPP connection is something that I have not been able to setup yet. Hope this helps |
|
Thanks for quick confirmation! let's order the fu**ing dongle then... There's something I'm not sure about the behaviour And the other way round: ess empty, plug car, ess will be filled up first because car charge requires 1400W (depend on the setting) to start and ess will not let this happens unless sun power > ess charging power also I didn't see a setting for time delay: start car charge if excess >1400W during xx seconds/minuts, there's probably a fixed delay coded, do you know the value? Sorry I'm a bit off topic! |
Hi again, I do not have a battery, so I am not sure on how to correctly reply to that. However, from my experience, the charger connects to the FusionSolar and the Inverter through the WLAN FE dongle. With that, it is able to know the power available and produced from the PV and balance it with the grid power available. In my case, i have a limit of 5.75kW power supply. When charging, if for example I connect home's AC, the Scharger decreases the power to charge the car to the maximum possible to balance between PV and the grid supply. With battery I understand that you may do the same. You also have an option on SCharger to be ECO mode, so you will only charge when PV is enough or when you have batteries to supply that energy, without getting power from the grid. At least, that's my understanding. Cheers |
Is this what was missing to get the SCharger included on this integration? |
|
Just to add my experience. I have this exact setup with the wlan dongle and
have not been able to ever charge the car using PV preferred despite full
battery and instead feeding 3kW back to grid.
I’m really disappointed with this product and only wish people would stop
buying this crap so they get the message.
…On Sat, Sep 7, 2024 at 23:29 Alvaro Duarte ***@***.***> wrote:
Obviously @DNAngelX <https://github.com/DNAngelX> did the job for
ioBroker - https://github.com/DNAngelX/ioBroker.huawei-charger/tree/main
I am not an expert, but it seems he decodes Modbus-messages. FYI
Is this what was missing to get the SCharger included on this integration?
—
Reply to this email directly, view it on GitHub
<#491 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGFGAGNHXTDYLG44SFWLNLZVNV3NAVCNFSM6AAAAAA5NM6EMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWGQ2TOMJVG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hi, is it possible for you @wlcrs to adopt the iobroker adapter for the huawei wallbox (https://github.com/DNAngelX/ioBroker.huawei-charger/tree/main) from @DNAngelX into this home assistant integration? This would be really nice and helpful for all the people using this wallbox! |
|
That one is not fully working yet (see here), and, unfortunately, I doubt it ever will (see my comment in that thread). IMO modbus is not the way to go, we will have to wait for OCPP to be implemented. |
I somehow have lost my faith for Huawei ever doing this. Its was announced for Q4'23 so were almost a year overdue... |
|
Hi, @passibe15 and @Kugelfang666
Do you guys mean the OCPP implementation that I referred here: #491 (comment) ?? Huawei already released this firmware, still available only for users whom request it, but is done: (although I was not able to get it working with OCPP addon from HACS on HA). |
|
Hello, i can give access via vpn to my installation of fusioncharge.
Il Gio 23 Mag 2024, 10:30 Roving Ronin ***@***.***> ha
scritto:
… @lucabacchipg <https://github.com/lucabacchipg> until someone can get
their hands upon the modbus register definitions, provide Thijs (i.e.
WLCRS) access remotely to their Huawei EV Charger to test it again, there
will be no chance of this. Step 1 all hinges on getting those modbus
definitions.
—
Reply to this email directly, view it on GitHub
<#491 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGCKYRFLTY3QCUFRG3SQBK3ZDWSK7AVCNFSM6AAAAAA5NM6EMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGUZTEMJXGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
check this report is that the implementation of OCPP is not working in this version. evcc-io/evcc#3806 (reply in thread) |
Thanks for pointing it out, although German is not ,y strongest thing, I got the idea. I have a contact in Huawei Europe and will enquire about that. Cheers |
|
@DNAngelX found a solution how to add the Huawei Wallbox via Huawei API to IOBroker. Would it be possible for you to integrate this too into your HomeAssistant Integration? You can see his documentation here: |
|
I think if someone create a HA integragtion than it would be easy to use this in combination with evcc |
Hi, I received this feed and it seems that there is all the data to be able to integrate with Fusionsolar. What do you think? Then I can be your tester on my Huawei platform. Thank you |
|
Good evening everyone, I was looking at the Huawei website to find new updates. I came across version V100R024C10. I think it's a pre-release but it looks promising. |
Looks promising. Can you share the firmware file? |
I can't find it anywhere -.- |
|
Don't get your hopes up.
That's a firmware for DC chargers (just like V100R023C10SPC070 was). See the changelog where it talks about liquid cooling, charging with 300 A and POS-terminals. |
I hate you 🤣 |
|
I usually look at one of their distributors for recent firmware, have a look yourself: https://photomate.zendesk.com/hc/en-gb/categories/4406398674589-Firmware |
|
Hello, this is last Modbus documentaion (Oct 2024) and lat Realease not for next day FW 160T upgrade of FusionCharge 22KW If someone know how to handle... Northbound Modbus-TCP Interconnection Protocol for AC Chargers.pdf |
Describe your feature request
Huawei also also offers a smart charger (FusionSolar with 7kw or 22kw) and it wouold be fantastic to integrte it as well
Proper usage
The text was updated successfully, but these errors were encountered: