Huawei FusionCharge Wallbox #10262
Replies: 23 comments 200 replies
-
|
That needs a custom module to implement the awkward steering by power. Would you want to attempt a PR? /cc @premultiply by power is already implemented in ocpp |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @andig. I could try. Which keys are required for a custom wallbox? |
Beta Was this translation helpful? Give feedback.
-
|
See api.Charger for the required interface |
Beta Was this translation helpful? Give feedback.
-
|
I am reading the inverter data via modbus with nodered and parse it to evcc via a mqtt broker. All tools are running as seperate docker containers on a NAS. For the wallbox I tried to use the modbusproxy function with evcc and also added the respective port (5021) to the evcc container. When I tried to read the registers from the NAS/evcc (192.168.1.3:5021) there seems to be nothing there. Shouldnt I be able to get the inverter data?
|
Beta Was this translation helpful? Give feedback.
-
|
@hauke-ruehs Can you please attach the full document or download link? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi, I got nothing additional to the documentation in the thread mentioned above or the screenshot I was send from the Huawei support and which I have posted in the first place. |
Beta Was this translation helpful? Give feedback.
-
|
Your screenshot differs from the linked PDF. |
Beta Was this translation helpful? Give feedback.
-
|
What are the contents of 0x100e ? |
Beta Was this translation helpful? Give feedback.
-
|
this is the original screenshot I received from Huawei with no further documentation. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for providing the updated version containing the huawei-ac template. As mentioned above (#10262 (comment)) I only get time-outs when I try to address the wallbox. Further the charger shows some error messages with regard to signal quality from the meter and is only charging with reduced power. It seems as if it doesn't want to "talk" to other devices than the inverter. |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that its not working. Do we maybe need an external modbus server? |
Beta Was this translation helpful? Give feedback.
-
|
After some intense discussions with the Huawei support I still cannot read any registers from the Charger's Modbus. For some reason they are investigating in the clinets connection to the inverter at the moment. The integration and also the surplus charging with the Huawei software works fine. I can also ping the Charger but if I want to read a Modbus register (in the same way I read from the inverter) either direct or via Modbus proxy I get a time out error. |
Beta Was this translation helpful? Give feedback.
-
|
Did you ever get clarity on this and whether a separate modbus-server would be necessary? |
Beta Was this translation helpful? Give feedback.
-
|
Well, "clarity" in that sense that it is not possible. The inverter is the Master and no external communication is allowed. I was observing network traffic of the Wallbox and there were only UDP but no ModBus TCP packages though. |
Beta Was this translation helpful? Give feedback.
-
|
But this guy seems to have gotten some data out: #10262 (reply in thread) or is that other telemetry data? Also the changelog for the latest release seems to indicate it should be same to send data to external NMS. If I haven't misunderstood this part at least it changes the situation from not possible to "it works but has a bug". And then there was another sub-thread where they got a package but it was malformed and instead of an array of data it contained a parsing error from server. It was read only telemetry and no control support of any kind but that's all I'm looking for anyway. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, any News on the integration of the Fusioncharge? Just updated mine on the latest firmware. As "Installer" I can see now the option "3rd party NMS via TCP Modbus" as mentionnend above. This setting seems only allow to connect the Fusioncharge as Client-Device on a NMS Server-Device. In any case on the IP-Address of my Fusioncharge the port 502 is not listening for any connection. |
Beta Was this translation helpful? Give feedback.
-
|
Which version did you install? Mine is V100R023C10SPC020. As I recently learned from the Huawei support the feature is not supported at all, wich is quiet contradicting to previous statements: |
Beta Was this translation helpful? Give feedback.
-
|
Wenn ich diese Matrix richtig verstehe, würde das die Aussage des Supports untermauern. Da erkenne ich mit meinem geringen Verständnis wenig Möglichkeiten als „Ziel“: |
Beta Was this translation helpful? Give feedback.
-
|
The installed Firmware Version is the same like yours. Let me know if I can help you with some testing on my charger. |
Beta Was this translation helpful? Give feedback.
-
|
Same here today. Happy to debug my environment for clues but need someone to help me make sense of the findings. |
Beta Was this translation helpful? Give feedback.
-
|
I would strongly advice against purchasing any equipment that is not fully integrated already. |
Beta Was this translation helpful? Give feedback.
-
|
Today I setted up an modbus-slave logger and I inserted the slave IP in the Fusioncharge "NMS-Option", resulting in a packet stream every 2 minutes coming from the Fusioncharge to my logger. 
|
Beta Was this translation helpful? Give feedback.
-
Is this not the ten or so decimal registers that the documentation referenced? If so, there's our data! |
Beta Was this translation helpful? Give feedback.
-
|
How did you set it up? Is your Huawei Charger connected to a Huawei Inverter? I was monitoring network traffic with wireshark and could not detect any TCP packages from the charger. |
Beta Was this translation helpful? Give feedback.
-
|
In my setup I have the Huawei Charger connected to a Huawei Inverter. To use the Modbus output from the inverter I use the Modbus-Proxy from evcc so the registers are available via port 502 from the same IP as evcc. This works fine for e.g. Node-Red. Still I did not succeed in substituting the current grid-meter IP address (provided by the inverter) in the Charger's setup for the proxy IP as it was refused repeatedly. |
Beta Was this translation helpful? Give feedback.
-
|
I'm confused. I also have the huawei inverter and chargebox. Has nobody gotten this integrated to home assistant at all? |
Beta Was this translation helpful? Give feedback.
-
|
regarding to https://support.huawei.com/enterprise/en/doc/EDOC1100355823 V100R023C10SPC060 will bring OCPP1.6J so as soon as the new FW will be released full Evcc support should be possible |
Beta Was this translation helpful? Give feedback.
-
|
As a long time Huawei customer: „will bring…“ the main Huawei slogan SCNR |
Beta Was this translation helpful? Give feedback.
-
|
Is the ocpp protocol not just for the communication between car and Wallbox? |
Beta Was this translation helpful? Give feedback.
-
|
@smoki3 no: https://docs.evcc.io/docs/devices/chargers/#ocpp-16j-kompatible-wallbox-mit-smart-charging-profil |
Beta Was this translation helpful? Give feedback.
-
|
I do not have this Huawei charger but I plan purchasing it since I also have Huawei inverters. Some Huawei inverters were listening to port 6607 instead of 502 for modbus tcp. Has anyone tried port 6607? Has anyone done a port scan? |
Beta Was this translation helpful? Give feedback.
-
|
i tried evcc configure: seems port 502 is doing something, but wrong? Port 6607 doesn't answer... i have installed newest firmware V100R023C10SPC020
|
Beta Was this translation helpful? Give feedback.
-
|
Have to say, even with the ocpp firmware V100R023C10SPC060 it is bot working. Really annoying |
Beta Was this translation helpful? Give feedback.
-
|
numberPhases maybe doesn't work because ConnectorSwitch3to1PhaseSupported is false, although the default value should be true according to the protocol messages and commisioning guide. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to manually force single phase charging in the UI and have OCPP respect that, or will it start three phase charging anyway? Asking because I find single phase charging more useful, since it covers the wider range 1.2-7.4kW (assuming you have 32A breakers). Especially now in winter I doubt most of us have lots of days with 8kW+ solar surplus. |
Beta Was this translation helpful? Give feedback.
-
|
Just disconnect phase L2 and L3 at the charger |
Beta Was this translation helpful? Give feedback.
-
|
FYI check this out, another user reports that there is a new FW in the making addressing the OCPP wlcrs/huawei_solar#491 (comment) Anyone seen this in the wild: V100R023C10SPC160T |
Beta Was this translation helpful? Give feedback.
-
|
@Kugelfang666 And see this: #10262 (comment) There are no resolved issues mentioned. |
Beta Was this translation helpful? Give feedback.
-
|
Here are some sample messages which are sent if you set up a "third-party NMS" in the wallbox and then listen on that port (first column is byte count, rest is hexadecimal): Perhaps someone know what protocol this is? Ping @tryinit6 since you seem to have explored the same thing above. |
Beta Was this translation helpful? Give feedback.
-
|
@henrikssn I would also be interested to know if anyone has succeeded to control the wallbox? |
Beta Was this translation helpful? Give feedback.
-
|
Long story short: no |
Beta Was this translation helpful? Give feedback.
-
Also not via OCPP? I've read that there are some firmware versions with OCPP Support? |
Beta Was this translation helpful? Give feedback.
-
|
No not working actually |
Beta Was this translation helpful? Give feedback.
-
|
Heißt das, dass EVCC auf absehbare Zeit nicht mit der HUAWEI Wallbox funktionieren wird? Warum ist diese Huawei Wallbox dann in der EVCC Doku aufgeführt https://docs.evcc.io/docs/devices/chargers#huawei-fusioncharge-ac ? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Don't know if it helps but have been trying to get this working for 2 days. Finally found that I had to log in to the fusionsolar via computer and go to monitoring > monitoring > choose the dongle > go to configuration > scroll down to bottom and enable Modbus-TCP and choose unrestricted or choose restricted but then add the ip of the service that needs data. And sorry if I missed something, might at least help someone if they where looking for the answer I was :) |
Beta Was this translation helpful? Give feedback.
-
|
I did exactly that: I only allowed connection to the Modbus-Proxy relaying the inverter/smart meter but it was not accepted by the charger. Communicating with the inverter is not a problem but somehow all attempts to establish a connection to the charger are failing. |
Beta Was this translation helpful? Give feedback.
-
|
Are you connecting to the inverter over the IP given to the dongle or do you have a cat-cable with reversed cabling from the inverter to your router? I'm trying to understand exactly what I have to do to just get the inverter properly connected to use energy Dashboard in home assistant |
Beta Was this translation helpful? Give feedback.
-
|
You need to specify the IP of the Inverter/dongle (see below). |
Beta Was this translation helpful? Give feedback.
-
|
Ok. If that's all it takes I'll give it another go. But connecting from the huawei solar integration to the IP and port after opening it up in the inverter config did not work out of the box for me. Do I need a modbus-proxy in between or something then or did I just not do it correctly the first time around? |
Beta Was this translation helpful? Give feedback.
-
|
Probably not. Only if you have other requests in parallel. |
Beta Was this translation helpful? Give feedback.
-
|
Good morning, I apologize for asking this question but I have a problem. Inverter Sun2000 6ktl - fw:141 In the last few weeks, using the Huawei Solar integration, I have had constant disconnections. Until a month ago I never had any problems. Help 😅 |
Beta Was this translation helpful? Give feedback.
-
|
Yeah separate issue but I'm keen to learn what you needed to do to get the integration running. I have the exact same setup but the integration says it can not connect to the server on the dongle ip on port 502. I have enabled modbus over tcp in the inverter already. Is there anything else I need to do? |
Beta Was this translation helpful? Give feedback.
-
|
It was stable for a year without any issues, or until the HA pymodbus update months ago. Now it is clearly conflicting with the charger. It works some days, and not others. |
Beta Was this translation helpful? Give feedback.
-
|
I found a temporary solution. |
Beta Was this translation helpful? Give feedback.
-
|
Test failed!!! I tried to install version 1.3.3 and as of this morning it has no disconnects. Now I'm connected via dongle IP /port 502/slave 1. Let's see what happens in the next few hours, but it seems very stable |
Beta Was this translation helpful? Give feedback.
-
|
I use the evcc modbus-proxy, thus I can read the registers directly for evcc but also access via e.g. node-red. |
Beta Was this translation helpful? Give feedback.
-
|
So you think they compete about the slave 0 slot?
…On Wed 26. Jun 2024 at 13:35, Criaga ***@***.***> wrote:
Test failed!!! I tried to install version 1.3.3 and as of this morning it
has no disconnects. Now I'm connected via dongle IP /port 502/slave 1.
Let's see what happens in the next few hours, but it seems very stable
—
Reply to this email directly, view it on GitHub
<#10262 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGFGAEGQPD766L5FGG2J2LZJKRRPAVCNFSM6AAAAAA52KTHOGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOBRG4ZDQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Could you please contact the Huawei support ([email protected]) and ask for the release date of OCPP 1.6? It is officially announced for Q4/2023 and still not available. For quick processing of your service requests it is advised to put your devices serial number into the email. Maybe this will eventually help to integrate the wallbox to evcc. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
I sent a question to support ocpp 1.6. Can someone tell me how to tell the charger to connect to the address of the modbus proxy and not the address of the sdongle. |
Beta Was this translation helpful? Give feedback.
-
|
That did not work for me. I also tried to replace the true smartmeter IP with the modbus proxy. Somehow the wallbox knows its not the meter. I suspect there is some communication between the two beyond modbus. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, it seems version V100R023C10SPC120 is now available on the support page, does it help with this issue and OCCP? |
Beta Was this translation helpful? Give feedback.
-
To be honest, the internal PV charging feature is quite limited. Here's my setup:
Ideally, the charger should only start charging the car when the Huawei battery is fully charged or when solar production exceeds the household's consumption by at least 5 kW. Unfortunately, this isn’t happening. The charger kicks in as soon as solar production exceeds household consumption, even if the battery is still empty. Additionally, it's important for me to have the energy data integrated into my smart home system so I can accurately invoice the charging costs to my company, as it's a company car. Overall, without these basic features, I wouldn’t choose this device again. |
Beta Was this translation helpful? Give feedback.
-
|
Very interesting, I don't get a readout from the registers at all and if I try to read a register from the Charger via Modbus I see an error message in the app indicating poor connection to the meter. How did you address the registers? Are you using the Huawei Fusion Solar App? |
Beta Was this translation helpful? Give feedback.
-
I think this is specifically an issue if you have two inverters. If there is only one, setting "Max Charging Power from Grid" to 0.0 kW and "Surplus Power to Start Charging" to 5.0 kW should do exactly what you want it to do … It's a really odd/stupid limitation. Also very unfortunate that Huawei is still not delivering, especially regarding the long-announced support for OCPP. By the way: I don't really see a future for any modbus-based integration, unless Huawei makes some larger changes, which is not very likely given their focus (if you can call it that) on OCCP.
|
Beta Was this translation helpful? Give feedback.
-
|
@DNAngelX : were you able to solve the 65 seconds issue? I would be Really happy to get the Huawei charger supported in EVCC and so far it seems you made the most progress on this front. |
Beta Was this translation helpful? Give feedback.
-
No, only auto reconnect all 65 sec. I added the support to set the interval into my adapter, this works 1/2 but the Huawai PV is not able to connect then to the Wallbx while the conenction is active. |
Beta Was this translation helpful? Give feedback.
-
|
You can not set it lower than 0.5 but even if you do, it never uses pv only
even with a full battery. This product is so flawed I wish I could just
send it back and go with something actually built for the purpose.
…On Mon, Sep 9, 2024 at 17:18 Passi Be ***@***.***> wrote:
Ideally, the charger should only start charging the car when the Huawei
battery is fully charged or when solar production exceeds the household's
consumption by at least 5 kW. Unfortunately, this isn’t happening. The
charger kicks in as soon as solar production exceeds household consumption,
even if the battery is still empty.
I think this is specifically an issue if you have two inverters. If there
is only one, setting "Max Charging Power from Grid" to 0.0 kW and "Surplus
Power to Start Charging" to 5.0 kW should do exactly what you want it to do
… It's a really odd/stupid limitation.
Also very unfortunate that Huawei is still not delivering, especially
regarding the long-announced support for OCPP.
By the way: I don't really see a future for any modbus-based integration,
unless Huawei makes some larger changes, which is not very likely given
their focus (if you can call it that) on OCCP.
- Because of the charger's weird concurrent connection limit you would
need to fully substitute the data delivered by the virtual dongle meter and
- make sure that the networks of charger and dongle are completely
separated as the charger is very aggressive in scanning for the dongle and
always trying to make a connection to it. This might not even be possible
for people with consumer-grade networking hardware. (Btw, the charger is
also generating loads and loads of broadcast traffic, it is really quite an
annoying network device.)
- In addition, I am not sure what is going on with the whole
certificate thing that you can see in the charger's settings; from some
poking around with wireshark I did a while back, I believe there is some
form of certificate-based trust establishment before a modbus connection is
successfully established.
TL;DR: I believe we'll have to wait for OCPP.
—
Reply to this email directly, view it on GitHub
<#10262 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGFGAF3OI7GL5AJJDH4T2DZVW35LAVCNFSM6AAAAAA52KTHOGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJZGI3DSNI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
What did you write and where? With this a bunch of us lurking and waiting
for progress can help to put pressure on them. We’re many more than the few
brave of you who can do something about it, are least we can use our voice.
…On Mon, Oct 7, 2024 at 14:46 Kugelfang666 ***@***.***> wrote:
I also wrote a mail to the Huawei support to help escalate this topic a
little bit.
—
Reply to this email directly, view it on GitHub
<#10262 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGFGAAYU4QHAVZ3PAPVAFLZ2J7DDAVCNFSM6AAAAAA52KTHOGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBWG4ZDIOA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Currently I am testing which paramValues are required to control the charger via evcc. I found that the URLs https://uni002eu5.fusionsolar.huawei.com:32800/rest/neteco/web/homemgr/v1/charger/charge/start-charge and https://uni002eu5.fusionsolar.huawei.com:32800/rest/neteco/web/homemgr/v1/charger/charge/stop-charge are required for starting and stopping the charging process. The Power can be set via paramValue 20001. Unfortunately this seems to work only for 3 Phases, because I cannot set the power lower than 4.3 kW. Switching to just 1 Phase via 20010 also did not work. Also setting the maximum current (paramValue 20003) did not help. Any suggestions from the community? |
Beta Was this translation helpful? Give feedback.
-
|
@hauke-ruehs: |
Beta Was this translation helpful? Give feedback.
-
|
I also tested that (changing 20004 and/or 20010 after stop of charging) but I always get an exceptionId response when setting paramValue 20001 to a value lower than 4.3 kW. |
Beta Was this translation helpful? Give feedback.
-
|
Can confirm, even with the ioBroker script you cannot change the value below 4.3 kw. When i tried to change the automatic phase-switching the wallbox stopped also to respond on changes for the maximum power value (4.3 cannot be changed with the script anymore. Had to restart the whole script. Wallbox seems not to accept the value 0 for disabled phase switching. |
Beta Was this translation helpful? Give feedback.
-
|
The lowest allowed value in the fusionapp itself is also 4.1kw |
Beta Was this translation helpful? Give feedback.
-
|
We are mortals. We are many. Holding my breath while waiting for the answer
to this :-)
…On Wed, Oct 23, 2024 at 14:06 Criaga ***@***.***> wrote:
Hi, I've been following the discussion for a while because I'm interested
in the project. Do you think it will soon be possible to integrate it for
ordinary mortals 😂? Thanks
—
Reply to this email directly, view it on GitHub
<#10262 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGFGAERIGATTCLT6YZSK6TZ46GMVAVCNFSM6AAAAAA52KTHOGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBSHA2TQOI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hey Guys, been lurking here for the last few weeks looking for solutions to the lack of basic features of the charger / app. I am mostly looking for a way to get an export of my charge sessions.. I asked my supplier and they sent me a reply describing how to enable and setup the ocpp protocol. Couldn't remember if i'd seen the pdf here so i figured i'd share to be sure. It's dated 2024-03-14 cheers, and thank you for the good work! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, have you checked if there is an OCPP section? From memory I don't think so 😅 |
Beta Was this translation helpful? Give feedback.
-
|
I believe OCPP is only available in V100R023C10SPC060. Download see here #10262 (reply in thread) So if you install 060 you should see the menu they mention in the guide (but also see the following discussion re Huawei's implementation of OCPP). |
Beta Was this translation helpful? Give feedback.
-
Not yet, but it should be there with the installer account.. though... with the Romanian language barrier I'd not be surprised if they are once again clueless... I'll check tonight and let you know.
Well, i did, but the pdf references authentication and tls version
I couln'd see that referenced there iirc. |
Beta Was this translation helpful? Give feedback.
-
|
Please check this discussion: #10262 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
Yep, saw all that. I was mostly just wondering if you guys tried the different auth settings the ocpp manual shows. I could not check OCPP settings last night as the installer password they mentioned did not work. Waiting for a reply now. |
Beta Was this translation helpful? Give feedback.
-
|
There was a new release of a firmware version: FusionCharge V100R023C10SPC160T Somebody has access and can check what has changed in the changelog? https://support.huawei.com/enterprise/de/fusioncharge/fusioncharge-pid-254563737 |
Beta Was this translation helpful? Give feedback.
-
|
New Features: None. There is nothing about OCPP. All very sad. |
Beta Was this translation helpful? Give feedback.
-
|
There is a new version which should support OCPP FusionCharge V100R024C10. Heres the link: https://support.huawei.com/enterprise/my/fusioncharge/fusioncharge-pid-254563737 Maybe somebody can download and share the firmware? |
Beta Was this translation helpful? Give feedback.
-
|
It's weird. No model is named in the release document |
Beta Was this translation helpful? Give feedback.
-
|
There is a new firmware version available (V100R024C10SPC100T). Somebody has access to the Release Notes? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Do you already have the changelog for version FusionCharge V100R023C10SPC190T? |
Beta Was this translation helpful? Give feedback.
-
|
If I'm not mistaken the 190T version is only for the DC Wallbox and not for the AC box we all have at our homes |
Beta Was this translation helpful? Give feedback.
-
|
So nothing on OCPP but redundant feature update regarding automated start
based on EVID. Also a good feature but not what was promised since long
and certainly not of higher importance :(
…On Fri, Dec 20, 2024 at 10:23 Criaga ***@***.***> wrote:
There is a new firmware version available (V100R024C10SPC100T). Somebody
has access to the Release Notes?
FusionCharge V100R024C10SPC100T Release Notes.pdf
<https://github.com/user-attachments/files/18208612/FusionCharge.V100R024C10SPC100T.Release.Notes.pdf>
—
Reply to this email directly, view it on GitHub
<#10262 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGFGAC2EATJHHI35ZGVRWL2GPOXNAVCNFSM6AAAAAA52KTHOGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRSGY3DGOA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
and others
-
I tried to setup the evcc.yaml for the Huawei FusionCharge AC 22 kW Wallbox according to the Modbus documentation I was supplied with. It seems as if I need to provide specific keys for the Modbus registers. Could anyone help to modify my definition of the charger in order to make it work? Thank you!
chargers:
type: custom
power:
source: modbus
id: 1
uri: XXX.XXX.XXX.XXX:502
register:
address: 4108
type: holding
decode: uint32
status:
source: modbus
id: 1
uri: XXX.XXX.XXX.XXX:502
register:
address: 4110
type: holding
decode: uint32
Beta Was this translation helpful? Give feedback.
All reactions