6
629658
Guest
Can you shed any step by step or tips to get the VenusOS loaded on the pi? Merry Christmas!!!
Victron SmartShunt / Home Assistant integration
- Thread starter Oakyz
- Start date
Archerite
New Member
sure, it works just like nearly every other rpi image that you download and flash to an SD card.
https://www.victronenergy.com/blog/2017/09/06/raspberry-pi-running-victrons-venus-firmware/
https://github.com/victronenergy/venus/wiki/raspberrypi-install-venus-image
That should point you in the right direction of the instructions. Then it depends on if you have a rpi2,rpi3 or rpi4 which image you need to download. There is a version called venusos-large that includes node-red but I am not sure how well that runs. My install is from before this was available so I don't have that on my venusos rpi. Node-red runs on the same NUC as HA does.
no problem. The NUC is just a really small PC not much bigger than a Victron MPPT in my case. Just remember that Home assistant runs on a system with SSD storage and has enough RAM. That might be a challenge with some thin-clients depending on how old they are.
Merry Christmas
Quattrohead
Solar Wizard
I am using an old Dell desktop for HA, not the best power consumption but it was just hanging around waiting to be used. Bonus is loads of USB ports.
6
629658
Guest
The thin client I bought has 8gb ram and 32gb SSD hope that’s big enough.sure, it works just like nearly every other rpi image that you download and flash to an SD card.
https://www.victronenergy.com/blog/2017/09/06/raspberry-pi-running-victrons-venus-firmware/
https://github.com/victronenergy/venus/wiki/raspberrypi-install-venus-image
That should point you in the right direction of the instructions. Then it depends on if you have a rpi2,rpi3 or rpi4 which image you need to download. There is a version called venusos-large that includes node-red but I am not sure how well that runs. My install is from before this was available so I don't have that on my venusos rpi. Node-red runs on the same NUC as HA does.
no problem. The NUC is just a really small PC not much bigger than a Victron MPPT in my case. Just remember that Home assistant runs on a system with SSD storage and has enough RAM. That might be a challenge with some thin-clients depending on how old they are.
Merry Christmas
Attachments
Archerite
New Member
That should be enough. I would be suspicous of the SSD though because of it's size it's either really old or a special type for thin clients. The specs say 32GB SATA so that might mean it's replaceable. I am not saying you have to replace it but it might not be designed for a lot of writes that HA does, and it would be just as bad as an SD card on a rpi.
6
629658
Guest
Well I don’t have much in it. Ended up paying $37 shipped. Worth a go at least.
Archerite
New Member
That's a great deal! For that price and for just testing you can't go wrong. Let me know when your setup with VenusOS on a Rpi and Home Assistant with Node-Red on your thin-client. Then I'll try giving the steps to integrate the SmartShunt values into HA with the help of node-red and VenusOS.
But the minimum setup you need working is:
- on the VenusOS Rpi:
- VE.Direct connected SmartShunt
- MQTT on local lan (not sure if it's called exactly that...but really close)
- on HomeAssistant:
- the HACS repository for community plugins
- if using the OS image, node-red is just another plugin but not sure how it integrates automatically.
- inside node red
- an MQTT server configuration pointing at your VenusOS rpi
- you can give this a name and use it for later
- the node-red-contrib-home-assistant-websocket plugin
I did not say it was going to be easy did I
When you have these installed and configured we can continue with building the flow in node-red.
To make things easier and to know what values are available you can use MQTT Explorer to connect to the rpi directly and it should show you the messages and a tree structure which among other things contains your installation ID. NEVER SHARE THIS! It's an identifier that "might" give others access to your installation remotely. At least that is what I understood about it...just treat it like a password you can't change.
And it's this installation ID that we will later need inside node-red to subscribe to the right messages.
I really hope I am not boring anyone at this point...but for now I will stop until you confirm you are ready with all of the above.
EDIT: Just to make it clear...I am not saying node-red is the only way to do this. It can be done directly in HA with configuration of the yaml configuration, I just have not got around to figuring out how exactly. for me node-red was a little more flexible and it seems stable enough for my usage.
Last edited:
6
629658
Guest
So my first step I think is to get HA onto the thin client and activate MQTT on Solar Assistant since I have that up and running. I’ll get the integrations working in HA. Once I have my feet wet on that. I have another Pi here and at first I’ll install VenusOS on that use the Victron USB adapter cable from the Smart Shunt to the Pi running VenusOS. Once I get that done then I’ll be in uncharted waters. I’ll reach out once I get to that point. I appreciate all your advice. I see there are lots of integrations available for HA. I have several systems I should be able to bring in like Hue, Yolink, Pentair etc. if it all works like I think it should it will be a great front end for all our automations.
Archerite
New Member
True, the screenshot does not specify it's an SSD. But since these were intended as thin clients they normally are really silent...meaning no HDD and possibly not even a noisy fan. Looking up the specs for a Dell Wyse 5020 Thin Client reveals that it's even worse.....it's FLASH memory!!
source: https://objects.icecat.biz/objects/mmo_33718413_1480059440_475_23478.pdf
The good thing though is that is a DiscOnModule apparently (read that somewhere else) that plugs directly into a SATA port on the motherboard. So it should not be that difficult to replace it with a good SSD.
Sid Norman
New Member
Hello,
it very good idea to use NodeRED.
Could you please explain what kind of functions you used in this flow?
Sid
StuartV
New Member
Well, I've bought me a Raspberry Pi 3 B off fleabay, £51 ? Ordered some usb to ttl serial cables and some jst plugs. Just got to wait for it all to arrive then I can venture in to the Venus OS ?
My solar set up is at the back of the house, I work from the front of the house (typical old 3 bedroom terraced UK house) and I want to see what my solar is doing now the sunnier weather is coming ?
If I get stuck, I'll be back ??
My solar set up is at the back of the house, I work from the front of the house (typical old 3 bedroom terraced UK house) and I want to see what my solar is doing now the sunnier weather is coming ?
If I get stuck, I'll be back ??
6
629658
Guest
Come back and share I’m looking at doing the same thing. I’m going to tackle home Assistant first.
Archerite
New Member
Thanks. I was going to post that but I wanted to give @jfpetesn some time to get VenusOS and Home Assistant running before overwhelming everyone with all that technical stuff ?
On the left are MQTT blocks that output a "parsed JSON object". And the topic they subscribe to is in the following format:
SoC = N/{vrm-portal-id}/battery/+/Soc
Voltage = N/{vrm-portal-id}/battery/+/Dc/0/Voltage
Current = N/{vrm-portal-id}/battery/+/Dc/0/Current
Power = N/{vrm-portal-id}/battery/+/Dc/0/Power
ConsumedAmphours = N/{vrm-portal-id}/battery/+/ConsumedAmphours
TimeToGo = N/{vrm-portal-id}/battery/+/TimeToGo
To get your "{vrm-portal-id}" there are three ways that I know of:
- On your VenusOS device go into "menu -> settings -> VRM Online Portal" and your VRM Portal ID is shown there
- Go into the VRM portal -> settings -> general and the VRM Portal ID is shown here
- Connect to your VenusOS device with MQTT explorer and whait a little while for the messages to come in. After a few seconds click on the N topic...and you will see your VRM Portal ID.
Then what I do in the "ReFormat" function block is this:
JavaScript:
// Reformat and normalize the VenusOS values
var topic = msg.topic;
topic = topic.replace("N/{vrm-portal-id}/", "");
if (topic.startsWith("solarcharger")) {
//venus_handle_scc(topic.replace("solarcharger/", ""), msg);
} else if (topic.startsWith("battery/")) {
venus_handle_battery(topic.replace("battery/", ""), msg);
}
return msg;
function venus_handle_battery(topic, message) {
var id = topic.substring(0, 3);
topic = topic.replace(id + "/", "");
switch (topic) {
case "Soc":
message.payload.value = parseFloat(message.payload.value).toFixed(2);
message.payload.sensor = "victron_battery_soc";
break;
case "Dc/0/Voltage":
message.payload.value = parseFloat(message.payload.value).toFixed(2);
message.payload.sensor = "victron_battery_voltage";
break;
case "Dc/0/Current":
message.payload.value = parseFloat(message.payload.value).toFixed(2);
message.payload.sensor = "victron_battery_current";
break;
case "Dc/0/Power":
message.payload.value = parseFloat(message.payload.value).toFixed(2);
message.payload.sensor = "victron_battery_power";
break;
case "ConsumedAmphours":
message.payload.value = parseFloat(message.payload.value).toFixed(2);
message.payload.sensor = "victron_battery_consumed_amp_hours";
break;
case "TimeToGo":
if (message.payload.value===null) {
message.payload.value = NaN;
//message.payload.data = message.payload;
} else {
message.payload.value = parseFloat(message.payload.value).toFixed(2);
}
message.payload.sensor = "victron_battery_time_to_go";
break;
}
}Next is a delay node to limit the number of messages and updates that go to Home Assistant.
I had hoped it would be possible to use a single output for each value and just put the name of the HA entity in the payload. But I could not find a way. As a workaround I put in a switch node that takes the reformatted values and has an output for each one. Those are then connected to the individual HA Sensor Node's. I can explain the configuration for each of them later if required, but it should be obvious I think
Since I figured out a way to calculate the remaining charge time for the current going into the battery I also wanted that in home assistant. So I take the values for Voltage, Current, Power and ConsumedAmpHours and send those to a second function block:
JavaScript:
switch(msg.payload.sensor) {
case "victron_battery_voltage": flow.set("charge_voltage", msg.payload.value); break;
case "victron_battery_current": flow.set("charge_current", msg.payload.value); break;
case "victron_battery_power": flow.set("charge_power", msg.payload.value); break;
case "victron_battery_consumed_amp_hours": flow.set("charge_consumed", msg.payload.value); break;
}
var voltage = flow.get("charge_voltage");
var current = flow.get("charge_current");
//var power = flow.get("charge_power");
var consumed = flow.get("charge_consumed");
var time = Math.abs(consumed) / current;
if(time>0) {
msg.payload.sensor = "victron_battery_charge_time"
msg.payload.time = (time * 3600).toFixed(2);
} else {
msg.payload.sensor = "victron_battery_charge_time"
msg.payload.time = NaN
}
return msg;This basically stores the incoming values as flow variables to "remember" earlier values of other sensors. Then with some math this is calculated into "seconds remaining to charge" and HA will show actual hours and minutes based on this. If the value is negative a NaN is outputed (Not A Number) so HA will not freak out over the value. This also goes into a limiter to only send a value to HA every 5 seconds
And that for the most part is what my flow is doing to get this data into Home Assistant. ?
Hope that helps.
6
629658
Guest
Thank you I’m peddling just a little behind.Thanks. I was going to post that but I wanted to give @jfpetesn some time to get VenusOS and Home Assistant running before overwhelming everyone with all that technical stuff ?
On the left are MQTT blocks that output a "parsed JSON object". And the topic they subscribe to is in the following format:
SoC = N/{vrm-portal-id}/battery/+/Soc
Voltage = N/{vrm-portal-id}/battery/+/Dc/0/Voltage
Current = N/{vrm-portal-id}/battery/+/Dc/0/Current
Power = N/{vrm-portal-id}/battery/+/Dc/0/Power
ConsumedAmphours = N/{vrm-portal-id}/battery/+/ConsumedAmphours
TimeToGo = N/{vrm-portal-id}/battery/+/TimeToGo
To get your "{vrm-portal-id}" there are three ways that I know of:
- On your VenusOS device go into "menu -> settings -> VRM Online Portal" and your VRM Portal ID is shown there
- Go into the VRM portal -> settings -> general and the VRM Portal ID is shown here
- Connect to your VenusOS device with MQTT explorer and whait a little while for the messages to come in. After a few seconds click on the N topic...and you will see your VRM Portal ID.
Then what I do in the "ReFormat" function block is this:
JavaScript:// Reformat and normalize the VenusOS values var topic = msg.topic; topic = topic.replace("N/{vrm-portal-id}/", ""); if (topic.startsWith("solarcharger")) { //venus_handle_scc(topic.replace("solarcharger/", ""), msg); } else if (topic.startsWith("battery/")) { venus_handle_battery(topic.replace("battery/", ""), msg); } return msg; function venus_handle_battery(topic, message) { var id = topic.substring(0, 3); topic = topic.replace(id + "/", ""); switch (topic) { case "Soc": message.payload.value = parseFloat(message.payload.value).toFixed(2); message.payload.sensor = "victron_battery_soc"; break; case "Dc/0/Voltage": message.payload.value = parseFloat(message.payload.value).toFixed(2); message.payload.sensor = "victron_battery_voltage"; break; case "Dc/0/Current": message.payload.value = parseFloat(message.payload.value).toFixed(2); message.payload.sensor = "victron_battery_current"; break; case "Dc/0/Power": message.payload.value = parseFloat(message.payload.value).toFixed(2); message.payload.sensor = "victron_battery_power"; break; case "ConsumedAmphours": message.payload.value = parseFloat(message.payload.value).toFixed(2); message.payload.sensor = "victron_battery_consumed_amp_hours"; break; case "TimeToGo": if (message.payload.value===null) { message.payload.value = NaN; //message.payload.data = message.payload; } else { message.payload.value = parseFloat(message.payload.value).toFixed(2); } message.payload.sensor = "victron_battery_time_to_go"; break; } }
Next is a delay node to limit the number of messages and updates that go to Home Assistant.
View attachment 130075
I had hoped it would be possible to use a single output for each value and just put the name of the HA entity in the payload. But I could not find a way. As a workaround I put in a switch node that takes the reformatted values and has an output for each one. Those are then connected to the individual HA Sensor Node's. I can explain the configuration for each of them later if required, but it should be obvious I think
Since I figured out a way to calculate the remaining charge time for the current going into the battery I also wanted that in home assistant. So I take the values for Voltage, Current, Power and ConsumedAmpHours and send those to a second function block:
JavaScript:switch(msg.payload.sensor) { case "victron_battery_voltage": flow.set("charge_voltage", msg.payload.value); break; case "victron_battery_current": flow.set("charge_current", msg.payload.value); break; case "victron_battery_power": flow.set("charge_power", msg.payload.value); break; case "victron_battery_consumed_amp_hours": flow.set("charge_consumed", msg.payload.value); break; } var voltage = flow.get("charge_voltage"); var current = flow.get("charge_current"); //var power = flow.get("charge_power"); var consumed = flow.get("charge_consumed"); var time = Math.abs(consumed) / current; if(time>0) { msg.payload.sensor = "victron_battery_charge_time" msg.payload.time = (time * 3600).toFixed(2); } else { msg.payload.sensor = "victron_battery_charge_time" msg.payload.time = NaN } return msg;
This basically stores the incoming values as flow variables to "remember" earlier values of other sensors. Then with some math this is calculated into "seconds remaining to charge" and HA will show actual hours and minutes based on this. If the value is negative a NaN is outputed (Not A Number) so HA will not freak out over the value. This also goes into a limiter to only send a value to HA every 5 seconds
And that for the most part is what my flow is doing to get this data into Home Assistant. ?
Hope that helps.
StuartV
New Member
So the Pi arrived a day earlier than expected, that was nice ?
I followed off grid garages tutorial on how to set it all up (google his website). Was very easy to follow too. I had 1 issue, the Pi I got, the wifi doesnt work on it ?
Luckily I’ve got a spare TP Link wifi extender with ethernet port, so its connected with ethernet to the wifi extender.
Venus OS is ok, its just the app but bigger graphs for example. I am happy I can monitor my PV Yield and battery levels from my works laptop now ? Venus OS also works through the Victron App, just swipe to VRM, tap on the GX, and it’s the devices I already have using the Bluetooth connection. Only difference tho, you can scroll back through history in the trends tab.
I’ve only got 2 panels connected to my 100/30, the other 2 panels are connected to my Iconica AIO, so I cant monitor their usage. So what have I gone and done? Bought another 100/30! ? Was on offer too, £169.00 on amazon.co.uk. I can then use the AIO as just the inverter. Needs must hey! ?
Its 404'ing out again Kaleb, could you repost please
Kaleb is there any way to connect the SmartShunt directly to a RPI using Home Assistant? (ve.direct to USB cable)
I've had two RPI's in my off grid cabin, one running Venus OS and one HA. But I just screwed up trying to update my Venus OS and can't get it to work (surely some crap with the partitions of my SD card). I tried to plug in my Victron devices directly to the HA RPI, but nothing shows up.
etschste
New Member
Please Kaleb, I would be very interested in your project as well, but still 404'ing. Maybe the github project ist set to private? BTW, I can't see any of your projects there... ?Its 404'ing out again Kaleb, could you repost please
Similar threads
