[NealCarney]

Some nice deals to be had here if you need to stock up. RGBW2 is one of the 50% off items.

 

[gregoryx]

Well, shoot... turns out there is an EASY way to handle multi-select in MQTT.

select:
  - unique_id: mvictron_ac_multiplus_mode
    name: "mVictron AC Multiplus Mode Select"
    command_topic: "venus-home/W/d4124333c8d6/vebus/276/Mode"
    command_template: '{"value": {{ value }} }'
    state_topic: "venus-home/N/d4124333c8d6/vebus/276/Mode"
    value_template: "{{ value_json.value }}"
    options:
      - "1"
      - "2"
      - "3"
      - "4"

🤯

I /think/ there's a way to set a different text display for the four options (Charger/Inverter/On/Off) but I haven't figured that out yet. It's supposed to be same/similar as the standard select, so... 🤔


Turns out there's also MQTT switches and buttons as well as a bunch of other integration types. I've got more learning to do. 🤔

 

[eranrund]

Well, shoot... turns out there is an EASY way to handle multi-select in MQTT.

select:
  - unique_id: mvictron_ac_multiplus_mode
    name: "mVictron AC Multiplus Mode Select"
    command_topic: "venus-home/W/d4124333c8d6/vebus/276/Mode"
    command_template: '{"value": {{ value }} }'
    state_topic: "venus-home/N/d4124333c8d6/vebus/276/Mode"
    value_template: "{{ value_json.value }}"
    options:
      - "1"
      - "2"
      - "3"
      - "4"

🤯

I /think/ there's a way to set a different text display for the four options (Charger/Inverter/On/Off) but I haven't figured that out yet. It's supposed to be same/similar as the standard select, so... 🤔


Turns out there's also MQTT switches and buttons as well as a bunch of other integration types. I've got more learning to do. 🤔
View attachment 199337

Thanks for diving into this. I also need to make the switch, given how flaky the modbus stuff is but am waiting patiently so that I can just grab the full config from you

 

[brío]

Quick question:
As I flesh out my system, I have come to realize that there are many places where I would like a binary sensor to sense whether a 12v or 24v signal is currently "on" or "off". Examples include whether the van's ignition is currently on, whether the a device like the Espar is currently receiving power, determining the positions of the upfitter switches, whether the "no charge" output from the BMS is currently active, whether a binary thermostat is currently on or off, and so on. Many of these examples are handy for supporting fault detection automations. So, for example, if the Espar controller is calling for heat, is the furnace actually producing any? If the answer is "no", I want an immediate notification.

My question is whether anybody has a standard way to do this? It isn't a particularly difficult problem, but I want to standardize on an approach. Is there something simple I should buy? My current default plan is to build an ESPhome node that interfaces to such circuits via a current-limiting resistor and the same opto-isolator boards I used in my UndermountAC prototype. A single node could handle lots of inputs cheaply and easily. Does anybody have a better way to do this kind of thing?

 

[Tuckie]

The price isn't great, but this might get you going in the right direction for a plug and play solution: 8-Channel I2C MCP23008 Optically Isolated Digital Input with I2C Interface

I'm currently using this board (along with an esp32 relay board they sell) in the workshop for a few different automations.

 

[brío]

The price isn't great, but this might get you going in the right direction for a plug and play solution: 8-Channel I2C MCP23008 Optically Isolated Digital Input with I2C Interface

I'm currently using this board (along with an esp32 relay board they sell) in the workshop for a few different automations.

Thanks!

Nice board.
What do you have it talking to? If I have to build an ESPhome node anyway for the I2C interface, I would have to think whether it is buying me enough to be worthwhile.

 

[gregoryx]

Thanks!

Nice board.
What do you have it talking to? If I have to build an ESPhome node anyway for the I2C interface, I would have to think whether it is buying me enough to be worthwhile.

Glad you asked it. I was thinking the same: that WITH an ESP module and it's in MY category of do-able. 🤣

 

[Tuckie]

What do you have it talking to?

Maybe I don't fully understand your question, but for the ESP interface, basically any of their "IOT interface" boards (aka has a socket for the esp32, such as this one) plus their esp32 board would work. In my case, I'm using this board (found someone selling for cheap on eBay). You could also just hand wire it to any ESP32 chip.

While I'm not fond of their prices, I'm using it for a workshop dust collection system with pneumatic blastgates so I wanted to know that it would stand up to abuse. I know I'm not getting knockoff components and all of the terminals are high quality. All that being said, it was still way cheaper than buying a commercial automatic blastgate system. (My sense circuits are just cheap sonoff power sensing smartplugs with the relay removed).

My system is running all esphome nodes connected with home assistant and a custom AppDaemon app to handle the state machine / automations. If you haven't looked into AppDaemon, and you prefer python coding over home assistant's repetitive automation interface, please give it a look!

What I really like about the ecosystem that they built out is that everything connects over i2c, so I don't have to think: "do I have enough pins? How are these going to connect?" Adafruit's featherwing platform is another one I'm considering for the van.

 

[brío]

Ah, I see. I just wasn't sure whether you were going through ESPhome, connecting directly to RPI pins, or ?
At this point, I am so used to building one-off ESPhome nodes that I will probably continue down that path. But if I were starting out, I can see the appeal of the approach you have taken. Your comment about quality parts and especially connectors is well-taken.

 

[gregoryx]

As in the MaxxFan thread, I'm finally actually USING ESPHome and I now understand y'all's attraction. I'll probably keep paying for other people's pre-assembled board 'cause I really don't like soldering things - I used to do that but I have to wear magnifying glasses to do that work and it irritates me.

I'm sure I wouldn't have appreciated it until getting more accustomed to Home Assistant; but now that I'm mildly comfortable with "seeing" the HASS YAML, the configs for ESPHome don't seem as intimidating as they would have a few months ago. I still struggle with anything logic-based... but I appreciate the way the basics work.

Finally got MaxxFan ON and OFF working. Going to require a LOT of IR learning to make it really work the way I want; but I don't expect to do /everything/ with it... just basic "in sync" status and basic "on/off/settings" with HASS. Generally, about as time-consuming and trial-and-error as the MQTT integration has been; but very rewarding as it works.

 

[mototreks]

Another MaxxFan option is via the RJ45 connector

 

[Scalf77]

I have been using 4 extremal relays with the RJ45 connector, ( I need a 5th if I want to use "auto" mode). Works great, I also found that be measuring the voltage lines to actual fan motor, you can determine on/off, fan speed, and direction.

 

[gregoryx]

Another MaxxFan option is via the RJ45 connector

Agreed. But I wanted to figure out how to use this thing - IR and RF - and this seems like a good application. Part of what I'm hoping to see is two-way communication with Home Assistant - meaning that since I can sense / detect an IR signal from the remote, it should be possible to use the remotes interchangeably with Home Assistant and have an accurate picture of the state of the fan from Home Assistant.

I think that's possible with the wired connection, but requires a different type of detection (as @Scalf77 shows with his example - each element is electrical and needs to be translated).

But maybe there IS a simpler way to do that. Let's face it... if there were a simple control board I could buy that does everything and integrates with Home Assistant, I'll probably buy it. 😁 🤷‍♀️


I'm hoping to use the device to get /some/ coordination with the Air Lift system (RF) as well as the soundbar (LG now, soon to be Roku) and we'll see what else is possible. I was never a fan of IR controls BITD but in a space as small as the van, it might work okay.


BTW, @Scalf77 did a killer job with the RJ45 route outlined here.

 

[vanchitect]

I am going to try and build my own ESP IR Blaster. Are these the only two ESP related items that I need to buy?

IR Blaster: HiLetgo 2pcs ESP8285 ESP-01M IR Infrared Transmitter Receiver Module Digital Infrared Transceiver Sensor WiFi Remote Control Switch

For Programming/USB Connection: HiLetgo CP2102 USB 2.0 to TTL Module Serial Converter Adapter Module USB to TTL Downloader with Jumper Wires https://a.co/d/1DEpq7i

 

[gregoryx]

I am going to try and build my own ESP IR Blaster. Are these the only two ESP related items that I need to buy?
...

This article might help. Basically, does the full walk-through from raw parts to building the ESP connections, etc.

 

[Captadv]

I am going to try and build my own ESP IR Blaster. Are these the only two ESP related items that I need to buy?

OR
Overview | Infrared Receive and Transmit with Circuit Playground Express | Adafruit Learning System

 

[eranrund]

I am going to try and build my own ESP IR Blaster. Are these the only two ESP related items that I need to buy?

IR Blaster: HiLetgo 2pcs ESP8285 ESP-01M IR Infrared Transmitter Receiver Module Digital Infrared Transceiver Sensor WiFi Remote Control Switch

For Programming/USB Connection: HiLetgo CP2102 USB 2.0 to TTL Module Serial Converter Adapter Module USB to TTL Downloader with Jumper Wires https://a.co/d/1DEpq7i

I recently ran into ESP 360 Remote, you might want to consider that.

 

[gregoryx]

I recently ran into ESP 360 Remote, you might want to consider that.

That's what I'm using. But I see now that it's a hardware assembly of parts that /could/ be done for about $10-20 or so - and still be more than adequate for a van. I'd still buy it. I like well-designed and well-executed hardware.

 

[mototreks]

So... after lots of reading, I'm going to try MQTT. I haven't done anything truly functional with MQTT yet - just tinkered. But after a few hours and defaulting the Mosquitto server a couple times, I've finally got it all working on the MQTT side.

The main thing driving me this direction is that the Victron developers said they're reliant on MQTT in the back-end of their implementation and thus it's likely to be pretty stable. Also, it alleviates the polling from Modbus - Cerbo/Venus pushes changes to the local MQTT, and I've got my Mosquitto server bridging the Cerbo Mosquitto. Weird to see everything just flashing updates in MQTT Explorer.

@gregoryx Thanks for doing all the legwork on the MQTT/Victron connection. I just set down and thought I'd give it a try. I was having some broken link messages in Mosquito when trying to connect to my CCGX but after a reboot of the CCGX everything worked great. I do like looking at those flashing updates in MQTT Explorer.

 

[gregoryx]

@gregoryx Thanks for doing all the legwork on the MQTT/Victron connection. I just set down and thought I'd give it a try. I was having some broken link messages in Mosquito when trying to connect to my CCGX but after a reboot of the CCGX everything worked great. I do like looking at those flashing updates in MQTT Explorer.

Cool. Glad you got it working.

I've still got more work to do; but so far it's 100% stable and I'm slowly getting every piece that worked in sfstar's Modbus working. For example, the "energy" dashboard is partial: currently incorporates battery in/out and solar but not the "grid" or inverter/AC portion yet.

One major change I made is to go back and make every component show up as a "device" in Home Assistant. Previously, these were all "entities" but not "devices." Now, there are "devices" that include their relevant entities.

One possible annoyance that anyone who uses my YAML may or may not like is I'm keeping with "mvictron" in everything, which was initially to differentiate from the previous "victron" stuff. I'm fine with it, so I'm leaving it that way.

Also, I've got a few things that are using Automations and Helpers to work that I'd like to move over into YAML so they're plug-and-play for anyone who wants to use the MQTT YAML. Eventually...

Here's the latest mqtt.yaml that's in play. I suspect there's some way to apply the "device" code to all the devices in a block, rather than adding the identical code to each entity. Feel free to point me in the right direction if anyone has that skill.

sensor:
#====================================================================
# Battery, Cerbo, DC
#====================================================================

  # Battery percentage
  - unique_id: mvictron_battery_soc
    name: "mVictron Battery SOC"
    state_topic: "venus-home/N/d4124333c8d6/system/0/Batteries"
    device_class: battery
    value_template: '{{ value_json.value[0].soc | round(0) }}'
    unit_of_measurement: "%"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}
    
  # DC Loads
  - name: "mVictron Battery DC Loads"
    device_class: power
    unique_id: mvictron_battery_dc_loads
    state_topic: "venus-home/N/d4124333c8d6/system/0/Dc/System/Power"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "W"
    icon: mdi:power
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}

  # Net load going in/out of battery
  - name: "mVictron Battery Load"
    unique_id: mvictron_battery_load
    device_class: power
    state_topic: "venus-home/N/d4124333c8d6/system/0/Batteries"
    value_template: '{{ value_json.value[0].power|float(0)|round(0) }}'
    unit_of_measurement: "W"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}

  # Battery Voltage
  - name: "mVictron Battery Voltage"
    unique_id: mvictron_battery_voltage
    device_class: voltage
    state_topic: "venus-home/N/d4124333c8d6/system/0/Dc/Battery/Voltage"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}

  # Starter Battery Voltage
  - name: "mVictron Battery Starter Voltage"
    unique_id: mvictron_battery_starter_voltage
    device_class: voltage
    state_topic: "venus-home/N/d4124333c8d6/battery/278/Dc/1/Voltage"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}

  # Battery Discharged Energy History
  - name: "mVictron Battery Discharged Energy"
    unique_id: mvictron_battery_discharged_energy
    device_class: energy
    state_class: total_increasing
    state_topic: "venus-home/N/d4124333c8d6/battery/278/History/DischargedEnergy"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "kWh"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}

  # Battery Charged Energy History
  - name: "mVictron Battery Charged Energy"
    unique_id: mvictron_battery_charged_energy
    device_class: energy
    state_class: total_increasing
    state_topic: "venus-home/N/d4124333c8d6/battery/278/History/ChargedEnergy"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "kWh"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}

  # Estimated Time until battery is empty based on current load.
  # These calculations were copied from victrons code to mimic how they display it
  - name: "mVictron Battery Remaining"
    unique_id: mvictron_battery_remaining
    icon: mdi:timer-sand
    state_topic: "venus-home/N/d4124333c8d6/system/0/Dc/Battery/TimeToGo"
    value_template: >
      {% if value == '{"value": null}' %}
        ∞
      {% else %}

        {% set seconds = value_json.value | round(0) | int %}
        {% set days = (seconds / 86400) | round(0, 'floor') | int %}
        {% set hours = ((seconds - days * 86400) / 3600) | round(0, 'floor') | int %}
        {% set minutes = ((seconds - hours * 3600) / 60) | round(0, 'floor') | int %}

        {% if 2 > days >= 1 %}
          {{days}} Day
        {% elif days >= 2 %}
          {{days}} Days
        {% elif hours > 0 %}
          {{hours}} Hours
        {% elif minutes > 0 %}
          {{minutes}} Minutes
        {% else %}
          ∞
        {% endif %}
      {% endif %}
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}


#====================================================================
# AC / Inverter / Multiplus
#====================================================================
  # AC Loads
  - state_topic: "venus-home/N/d4124333c8d6/system/0/Ac/Consumption/L1/Power"
    name: "mVictron AC Loads"
    unique_id: mvictron_ac_loads
    device_class: power
    unit_of_measurement: "W"
    icon: mdi:power-socket-uk
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    device: {
      identifiers: [
      "Victron Multiplus"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Multiplus 24/3000/70",
      name: "Victron Multiplus"}

  # AC Input
  - name: "mVictron AC Input"
    device_class: power
    unique_id: mvictron_ac_input
    state_topic: "venus-home/N/d4124333c8d6/system/0/Ac/ActiveIn/L1/Power"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "W"
    icon: mdi:power    
    device: {
      identifiers: [
      "Victron Multiplus"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Multiplus 24/3000/70",
      name: "Victron Multiplus"}
      
  # Current State of Multiplus Inverter
  - name: "mVictron AC Inverter State"
    unique_id: "mvictron_ac_inverter_state"
    state_topic: "venus-home/N/d4124333c8d6/system/0/SystemState/State"
    value_template: >
      {% if value_json.value == 0 %}
        Off
      {% elif value_json.value == 2 %}
        VE.Bus Fault condition
      {% elif value_json.value == 3 %}
        Bulk
      {% elif value_json.value == 4 %}
        Absorption
      {% elif value_json.value == 5 %}
        Float
      {% elif value_json.value == 6 %}
        Storage
      {% elif value_json.value == 7 %}
        Equalize
      {% elif value_json.value == 9 %}
        Inverting
      {% elif value_json.value == 10 %}
        Assisting
      {% elif value_json.value == 256 %}
        Discharging
      {% elif value_json.value == 257 %}
        Sustain
      {% else %}
        Error - No Data
      {% endif %}
    device: {
      identifiers: [
      "Victron Multiplus"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Multiplus 24/3000/70",
      name: "Victron Multiplus"}
      

#====================================================================
# Solar
#====================================================================
  # Solar Production Current
  - name: "mVictron Solar Output"
    unique_id: mvictron_solar_output
    device_class: power
    state_topic: "venus-home/N/d4124333c8d6/system/0/Dc/Pv/Power"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "W"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
      
  # Solar Yield Today
  - name: "mVictron Solar Yield Today"
    unique_id: mvictron_solar_yield_today
    device_class: energy
    state_class: total
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/History/Daily/0/Yield"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "kWh"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
      
  # Solar Yield Yesterday
  - name: "mVictron Solar Yield Yesterday"
    unique_id: mvictron_solar_yield_yesterday
    device_class: energy
    state_class: total
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/History/Daily/1/Yield"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "kWh"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
      
  # Solar Max Today
  - name: "mVictron Solar Max Today"
    unique_id: mvictron_solar_max_today
    device_class: power
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/History/Daily/0/MaxPower"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "W"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
      
  # Solar Max Yesterday
  - name: "mVictron Solar Max Yesterday"
    unique_id: mvictron_solar_max_yesterday
    device_class: power
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/History/Daily/1/MaxPower"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "W"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
      
  # Solar PV Voltage
  - name: "mVictron Solar PV Voltage"
    unique_id: mvictron_solar_pv_voltage
    device_class: voltage
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/Pv/V"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
          
  # Solar Charger Voltage
  - name: "mVictron Solar Charger Voltage"
    unique_id: mvictron_solar_charger_voltage
    device_class: voltage
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/Dc/0/Voltage"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
      
  # Current state of solar charge controller
  - name: "mVictron Solar Charger State"
    unique_id: "mvictron_solar_charger_state"
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/State"
    value_template: >
      {% if value_json.value == 0 %}
        Off
      {% elif value_json.value == 2 %}
        Fault
      {% elif value_json.value == 3 %}
        Bulk
      {% elif value_json.value == 4 %}
        Absorption
      {% elif value_json.value == 5 %}
        Float
      {% elif value_json.value == 6 %}
        Storage
      {% elif value_json.value == 7 %}
        Equalize
      {% else %}
        Error - No Data
      {% endif %}
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
      
#====================================================================
# Temp, humidity, etc
#====================================================================

# Battery temp (24)
#------------------------------------------

  # Battery Temp
  - name: "mVictron Temp Battery"
    unique_id: mvictron_temp_battery
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/system/0/Dc/Battery/Temperature"
    value_template: '{{ ((value_json.value * 9/5) + 32) | round(0) }}'
    unit_of_measurement: "°F"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}
    


# Main Cabin Ruuvi Tag (28 - Ruuvi C3B4)
#------------------------------------------

  # Main Cabin Temp
  - name: "mVictron Temp Main Cabin"
    unique_id: mvictron_temp_main
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/28/Temperature"
    value_template: '{{ ((value_json.value * 9/5) + 32) | round(0) }}'
    unit_of_measurement: "°F"
    
  # Main Cabin Humidity
  - name: "mVictron Temp Humidity Main"
    unique_id: mvictron_temp_hum_main
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/28/Humidity"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "%"
    
  # Main Cabin Temp Ruuvi Battery
  - name: "mVictron Temp Main Cabin Ruuvi Battery"
    unique_id: mvictron_temp_main_ruuvi_battery
    state_topic: "venus-home/N/d4124333c8d6/temperature/28/BatteryVoltage"
    device_class: voltage
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"


# Outside Ruuvi Tag (30 - Ruuvi 08DA)
#------------------------------------------

  # Outside Temp
  - name: "mVictron Temp Outside"
    unique_id: mvictron_temp_outside
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/30/Temperature"
    value_template: '{{ ((value_json.value * 9/5) + 32) | round(0) }}'
    unit_of_measurement: "°F"
    
  # Outside Humidity
  - name: "mVictron Temp Humidity Outside"
    unique_id: mvictron_temp_hum_outside
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/30/Humidity"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "%"
    
  # Outside Ruuvi Battery
  - name: "mVictron Temp Outside Ruuvi Battery"
    unique_id: mvictron_temp_outside_ruuvi_battery
    state_topic: "venus-home/N/d4124333c8d6/temperature/30/BatteryVoltage"
    device_class: voltage
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"

    
# Dash Ruuvi Tag (29 - Ruuvi 3A98)
#------------------------------------------

  # Dash Temp
  - name: "mVictron Temp Dash"
    unique_id: mvictron_temp_dash
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/29/Temperature"
    value_template: '{{ ((value_json.value * 9/5) + 32) | round(0) }}'
    unit_of_measurement: "°F"
    
  # Dash Ruuvi Battery
  - name: "mVictron Temp Dash Ruuvi Battery"
    unique_id: mvictron_temp_dash_ruuvi_battery
    state_topic: "venus-home/N/d4124333c8d6/temperature/29/BatteryVoltage"
    device_class: voltage
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"


# Rear Ruuvi Tag (33 - Ruuvi 2A24)
#------------------------------------------

  # Rear Temp
  - name: "mVictron Temp Rear"
    unique_id: mvictron_temp_rear
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/33/Temperature"
    value_template: '{{ ((value_json.value * 9/5) + 32) | round(0) }}'
    unit_of_measurement: "°F"
    
  # Rear Humidity
  - name: "mVictron Temp Humidity Rear"
    unique_id: mvictron_temp_hum_rear
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/33/Humidity"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "%"
    
  # Rear Ruuvi Battery
  - name: "mVictron Temp Rear Ruuvi Battery"
    unique_id: mvictron_temp_rear_ruuvi_battery
    state_topic: "venus-home/N/d4124333c8d6/temperature/33/BatteryVoltage"
    device_class: voltage
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"
    

# Fridge Ruuvi Tag (31 - Ruuvi 937A)
#------------------------------------------

  # Fridge Temp
  - name: "mVictron Temp Fridge"
    unique_id: mvictron_temp_fridge
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/31/Temperature"
    value_template: '{{ ((value_json.value * 9/5) + 32) | round(0) }}'
    unit_of_measurement: "°F"
    
  # Fridge Humidity
  - name: "mVictron Temp Humidity Fridge"
    unique_id: mvictron_temp_hum_fridge
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/31/Humidity"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "%"
    
  # Fridge Ruuvi Battery
  - name: "mVictron Temp Fridge Ruuvi Battery"
    unique_id: mvictron_temp_fridge_ruuvi_battery
    state_topic: "venus-home/N/d4124333c8d6/temperature/31/BatteryVoltage"
    device_class: voltage
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"
    

# Freezer Ruuvi Tag (32 - Ruuvi 08DA)
#------------------------------------------

  # Freezer Temp
  - name: "mVictron Temp Freezer"
    unique_id: mvictron_temp_freezer
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/32/Temperature"
    value_template: '{{ ((value_json.value * 9/5) + 32) | round(0) }}'
    unit_of_measurement: "°F"
    
  # Freezer Humidity
  - name: "mVictron Temp Humidity Freezer"
    unique_id: mvictron_temp_hum_freezer
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/32/Humidity"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "%"
    
  # Freezer Ruuvi Battery
  - name: "mVictron Temp Freezer Ruuvi Battery"
    unique_id: mvictron_temp_freezer_ruuvi_battery
    state_topic: "venus-home/N/d4124333c8d6/temperature/32/BatteryVoltage"
    device_class: voltage
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"
    
    
# Hot Water Ruuvi Tag (34 - Ruuvi 4623)
#------------------------------------------

  # Hot Water Temp
  - name: "mVictron Temp Hot Water"
    unique_id: mvictron_temp_hotwater
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/34/Temperature"
    value_template: '{{ ((value_json.value * 9/5) + 32) | round(0) }}'
    unit_of_measurement: "°F"
    
  # Hot Water Humidity
  - name: "mVictron Temp Humidity Hot Water"
    unique_id: mvictron_temp_hum_hotwater
    device_class: temperature
    state_topic: "venus-home/N/d4124333c8d6/temperature/34/Humidity"
    value_template: '{{ value_json.value|float(0)|round(0) }}'
    unit_of_measurement: "%"
    
  # Hot Water Ruuvi Battery
  - name: "mVictron Temp Hot Water Ruuvi Battery"
    unique_id: mvictron_temp_hotwater_ruuvi_battery
    state_topic: "venus-home/N/d4124333c8d6/temperature/34/BatteryVoltage"
    device_class: voltage
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "V"
    

#====================================================================
# Water tanks
#====================================================================

  # Fresh Water Level
  - name: "mVictron Water Fresh Level"
    unique_id: mvictron_water_fresh_level
    device_class: water
    state_topic: "venus-home/N/d4124333c8d6/tank/21/Level"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "%"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}
    
  # Reserve Water Level
  - name: "mVictron Water Reserve Level"
    unique_id: mvictron_water_reserve_level
    device_class: water
    state_topic: "venus-home/N/d4124333c8d6/tank/22/Level"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "%"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}
    
  # Gray Water Level
  - name: "mVictron Water Gray Level"
    unique_id: mvictron_water_gray_level
    device_class: water
    state_topic: "venus-home/N/d4124333c8d6/tank/20/Level"
    value_template: '{{ value_json.value|float(0)|round(1) }}'
    unit_of_measurement: "%"
    device: {
      identifiers: [
      "Victron Cerbo GX"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Cerbo GX",
      name: "Victron Cerbo GX"}
    

#====================================================================
#====================================================================


number:
  - unique_id: mvictron_ac_input_limit
    name: mVictron AC Input Limit
    min: 0
    max: 18
    step: 1
    mode: box
    command_topic: "venus-home/W/d4124333c8d6/vebus/276/Ac/ActiveIn/CurrentLimit"
    command_template: '{"value": {{ value }} }'
    state_topic: "venus-home/N/d4124333c8d6/vebus/276/Ac/ActiveIn/CurrentLimit"
    value_template: "{{ value_json.value }}"
    device_class: current
    unit_of_measurement: A
    icon: mdi:current-ac
    device: {
      identifiers: [
      "Victron Multiplus"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Multiplus 24/3000/70",
      name: "Victron Multiplus"}
      
  - unique_id: mvictron_ac_multiplus_mode
    name: "mVictron Multiplus Mode"
    min: 1
    max: 4
    step: 1
    mode: slider
    command_topic: "venus-home/W/d4124333c8d6/vebus/276/Mode"
    command_template: '{"value": {{ value }} }'
    state_topic: "venus-home/N/d4124333c8d6/vebus/276/Mode"
    value_template: "{{ value_json.value }}"
#    device_class: none
    icon: mdi:current-ac
    device: {
      identifiers: [
      "Victron Multiplus"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Multiplus 24/3000/70",
      name: "Victron Multiplus"}    
    
  - unique_id: mvictron_solar_charger_mode
    name: "mVictron Solar Charger Mode"
    min: 1
    max: 4
    step: 1
    mode: slider
    command_topic: "venus-home/W/d4124333c8d6/solarcharger/279/Mode"
    command_template: '{"value": {{ value }} }'
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/Mode"
    value_template: "{{ value_json.value }}"
#    device_class: none
    icon: mdi:current-ac    
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}    
    
    
#====================================================================
#====================================================================
switch:
  - unique_id: mvictron_solar_charger_switch
    name: mVictron Solar Charger Switch
    state_topic: "venus-home/N/d4124333c8d6/solarcharger/279/Mode"
    command_topic: "venus-home/W/d4124333c8d6/solarcharger/279/Mode"
    payload_on: '{"value": 1 }'
    payload_off: '{"value": 4 }'
    state_on: "On"
    state_off: "Off"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron MPPT"
      ],
      manufacturer: "Victron Energy",
      model: "Victron SmartSolar Charger MPPT 150/35",
      name: "Victron MPPT"}
      
  - unique_id: mvictron_ac_multiplus_switch
    name: mVictron AC Multiplus Switch
#    availability_topic: "venus-home/R/d4124333c8d6/availability"
#    availability_template: '{"value": {{ value }} }'
#    payload_available: 'online'
#    payload_not_available: offline
    state_topic: "venus-home/N/d4124333c8d6/vebus/276/Mode"
    command_topic: "venus-home/W/d4124333c8d6/vebus/276/Mode"
    payload_on: '{"value": 3 }'
    payload_off: '{"value": 4 }'
    state_on: "On"
    state_off: "Off"
    icon: mdi:solar-power
    device: {
      identifiers: [
      "Victron Multiplus"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Multiplus 24/3000/70",
      name: "Victron Multiplus"}      
    
    
    
#====================================================================
#====================================================================
select:
  - unique_id: mvictron_ac_multiplus_mode 
    name: "mVictron AC Multiplus Mode Select"
    command_topic: "venus-home/W/d4124333c8d6/vebus/276/Mode"
    command_template: '{"value": {{ value }} }'
    state_topic: "venus-home/N/d4124333c8d6/vebus/276/Mode"
    value_template: "{{ value_json.value }}"
    options:
      - "1"
      - "2"
      - "3"
      - "4"
    device: {
      identifiers: [
      "Victron Multiplus"
      ],
      manufacturer: "Victron Energy",
      model: "Victron Multiplus 24/3000/70",
      name: "Victron Multiplus"}