Homewizard 3 phase meter NodeRED venusOS #124
Unanswered
TheRaver13
asked this question in
Q&A
Replies: 3 comments 9 replies
-
|
Hi, thanks for deciding to try this driver. First thing I have to point out is that the driver only handles the registration of your device and provides you with the device id, from that point on you are dealing with Victron’s MQTT api directly. So if you have registered the device ok, then your problem is outside the driver. I would highly recommend you start with a simple example like temperature. I have a node-red example for this in the samples folder. It’s hard tell from your screen shots but are you definitely publishing to the correct W topics? You publish to W and read from N. Keep alive is required if you are using MQTT Explorer. Also the name of the nodes handling the registration appear to be device/grid/… instead of device/grid01/… but I assume the topics underneath are correct otherwise the registration would not have worked. Happy to answer any ore questions. Martin |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Martin, Thank you for the reply, I found the issue and the message on the MQTT bus was missing the string "value" there for the message was not read the right way. Now all working smoothly big thanks for this nice addition to victron system. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Thanks for the update. I'm glad you got it working. Have you had a look at the Proxy feature in the latest release? You should find that it simplifies your node-red flows a lot. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Martin, Last weekend I enabled my ESS finally but I'm running into some issues that connection to the BMS is lost multiple times a day so I did some digging and saw in HRM that the dbus-roundtrip time has large spikes every 4 to 6 hours. So i posted the question on the victron forum and they said the issue might be caused by node-red or external plugins like the dbus-mqttt-devices. When I get the error of BMS lost I also see that my grid meter disappeared in the cerbo console. Below are some pictures of the round trip and my node-red flow Is there a way to find out of this is causing the issue ? |
Beta Was this translation helpful? Give feedback.
-
|
I'm not aware of any reason why the driver might cause a spike every hours. It just connects to MQTT and does nothing until it receives a message. You should monitor two log files: Piping the output through tai64nlocal will convert the timestamps into human readable form. I used to have a problem on my old CCGX. It would randomly reboot. From the /var/log/boot log file I could see the device was running out of memory and venusos was triggering a reboot. What device are you running this all on? and How much RAM does it have? Are you running SignalK too? |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
cat /var/log/boot | tai64nlocal cat /var/log/dbus-mqtt-devices/current | tai64nlocal cat /var/log/dmesg |
Beta Was this translation helpful? Give feedback.
-
|
I can't see any problems here. The last few entries in the boot file are the install of the driver. Any reason why you installed it again this morning? I assume you need run it for a good 6 hours. You need find times in the log file that align with where you see the spikes you saw earlier. |
Beta Was this translation helpful? Give feedback.
-
|
I did not reinstall it on purpose, I will wait till I get a new error van HRM and then post the new log file. |
Beta Was this translation helpful? Give feedback.
-
|
No clue what I have done but since this morning no issues anymore 😄 will keep updated. Maybe the reinstall helped. |
Beta Was this translation helpful? Give feedback.
-
|
Good to hear you've had no further issues, but just to be clear reinstalling should have no effect. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi i'm trying to integrate an homewizard wifi 3 phase energymeter (SD630) into victron using MQTT, the meter has an HTTP API which I read in NodeRED and then send to the topics with MQTT. I followed the steps in the readme and see the device in venusOS but the values stay "null". I used the keepalive script and MQTT explorer and see the same on N bus but on the W bus I do see the correct data.
Looks like the translation from W to N is not working. I probably did something wrong.
Beta Was this translation helpful? Give feedback.
All reactions