Silla Prism Solar wallbox

[MarcoVg1980]

Could be possible to integrate the wallbox in object. It have MQTT support. I can share the document obout MQTT protocol.

Thanks

DOC-Manuale_Prism_MQTT-rel.2.0_rev.-20220105-IT.pdf
FLYER-Prism_Solar_20230308-EN.pdf

[andig]

You can integrate it using a custom charger and the MQTT plugins. Core team does not plan to work on this.

[MarcoVg1980]

Dear Andig, I have try to use custom MQTT charger.. but seems i wrong some setup.. here....

chargers:

name: Carport
type: custom # or default
status: # charger status A..F
source: mqtt
topic: prism/1/state/ #carport/lp/1/ChargeStatus
timeout: 10m
enabled: # charger enabled state (true/false or 0/1)
source: mqtt
topic: prism/1/mode
timeout: 10m
enable: # set charger enabled state (true/false or 0/1)
source: mqtt
topic: prism/1/state/
payload: ${enable:%d}
timeout: 10m
maxcurrent: # set charger max current (A)
source: mqtt
topic: prism/1/command/set_current_user
timeout: 10m
LOG:

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2025/01/25 12:03:39 evcc 0.133.0
[main ] INFO 2025/01/25 12:03:39 using config file: /config/evcc.yaml
[mqtt ] INFO 2025/01/25 12:03:39 connecting evcc-1534863626 at tcp://core-mosquitto.local.hass.io:1883
[main ] INFO 2025/01/25 12:03:40 listening at :7070
[main ] FATAL 2025/01/25 12:03:41 failed configuring loadpoints: failed configuring loadpoint: not found: charge
[main ] FATAL 2025/01/25 12:03:41 will attempt restart in: 15m0s

Log

[MarcoVg1980]

Dear Andig, I have try to use custom MQTT charger.. but seems i wrong some setup.. here....

chargers:

• name: Carport
  type: custom # or default
  status: # charger status A..F
  source: mqtt
  topic: prism/1/state/ #carport/lp/1/ChargeStatus
  timeout: 10m
  enabled: # charger enabled state (true/false or 0/1)
  source: mqtt
  topic: prism/1/mode
  timeout: 10m
  enable: # set charger enabled state (true/false or 0/1)
  source: mqtt
  topic: prism/1/state/
  payload: ${enable:%d}
  timeout: 10m
  maxcurrent: # set charger max current (A)
  source: mqtt
  topic: prism/1/command/set_current_user
  timeout: 10m

LOG:

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2025/01/25 12:03:39 evcc 0.133.0
[main ] INFO 2025/01/25 12:03:39 using config file: /config/evcc.yaml
[mqtt ] INFO 2025/01/25 12:03:39 connecting evcc-1534863626 at tcp://core-mosquitto.local.hass.io:1883
[main ] INFO 2025/01/25 12:03:40 listening at :7070
[main ] FATAL 2025/01/25 12:03:41 failed configuring loadpoints: failed configuring loadpoint: not found: charge
[main ] FATAL 2025/01/25 12:03:41 will attempt restart in: 15m0s

[mfuchs1984]

meter: charge # charge meter

Das meter hast du weiter oben auskommentiert.

[MarcoVg1980]

I still have same error....

network:

schema is the HTTP schema

setting to https does not enable https, it only changes the way URLs are generated

schema: http

host is the hostname or IP address

if the host name contains a .local suffix, the name will be announced on MDNS

docker: MDNS announcements don't work. host must be set to the docker host's name.

host: evcc.local

port is the listening port for UI and api

evcc will listen on all available interfaces

port: 7070

interval: 30s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval

database configuration for persisting charge sessions and settings

database:

type: sqlite

dsn:

sponsor token enables optional features (request at https://sponsor.evcc.io)

sponsortoken:

telemetry enables aggregated statistics

Telemetry allows collecting usage data (grid and green energy, charge power).

Data is aggregated, no individual charging sessions are tracked. The collected,

anonymous data can be retrieved using https://api.evcc.io.

See #4343 or details.

For time being, this is only available to sponsors, hence data is associated with

the sponsor token's identity.

telemetry: true

log settings

log: info
levels:
site: debug
lp-1: debug
lp-2: debug
cache: error
db: error

modbus proxy for allowing external programs to reuse the evcc modbus connection

each entry will start a proxy instance at the given port speaking Modbus TCP and

relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)

modbusproxy:

- port: 5200

uri: solar-edge:502

# rtu: true

# readonly: true # use deny to raise modbus errors

meter definitions

name can be freely chosen and is used as reference when assigning meters to site and loadpoints

for documentation see https://docs.evcc.io/docs/devices/meters

meters:

• name: my_pv
  type: template
  template: huawei-dongle
  usage: pv

  Modbus TCP

  modbus: tcpip
  id: 1
  host: 192.168.1.191 # Hostname
  port: 502 # Port
  timeout: 15s # optional

charger definitions for generic charger via MQTT

name can be freely chosen and is used as reference when assigning charger to vehicle

for documentation see https://docs.evcc.io/docs/devices/chargers

chargers:

• name: Carport
  type: custom # or default
  status: # charger status A..F
  source: mqtt
  topic: prism/1/state/ #carport/lp/1/ChargeStatus
  timeout: 10m
  enabled: # charger enabled state (true/false or 0/1)
  source: mqtt
  topic: prism/1/mode
  timeout: 10m
  enable: # set charger enabled state (true/false or 0/1)
  source: mqtt
  topic: prism/1/state/
  payload: ${enable:%d}
  timeout: 10m
  maxcurrent: # set charger max current (A)
  source: mqtt
  topic: prism/1/command/set_current_user
  timeout: 10m

vehicle definitions

name can be freely chosen and is used as reference when assigning vehicle to loadpoint

for documentation see https://docs.evcc.io/docs/devices/vehicles

vehicles:

• name: car1
  type: renault
  title: Twingo
  capacity: 22 # kWh
  user: [email protected] # user
  password: Ferrari-80
  vin: # .WREN.Car ID..
  onIdentify: # set defaults when vehicle is identified

mode: pv # enable PV-charging when vehicle is identified

phases: 1
icon: car
cache: 15m

minCurrent: 8

maxCurrent: 16

site describes the EVU connection, PV and home battery

site:
title: Home # display name for UI
meters:
grid: grid # grid meter
pv:
- pv # list of pv inverters/ meters
battery:
- battery # list of battery meters

aux:

- aux # list of auxiliary meters for adjusting grid operating point

residualPower: 200 # additional household usage margin in W
maxGridSupplyWhileBatteryCharging: 1 # ignore battery charging if AC consumption is above this value

loadpoint describes the charger, charge meter and connected vehicle

loadpoints:

• title: Carport Charger # display name for UI
  charger: Carport # charger
  meter: charge # charge meter
  mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available

  remaining settings are experts-only and best left at default values

  priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
  soc:

  polling defines usage of the vehicle APIs

  Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery

  or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.

  poll:
  # poll mode defines under which condition the vehicle API is called:
  # charging: update vehicle ONLY when charging (this is the recommended default)
  # connected: update vehicle when connected (not only charging), interval defines how often
  # always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
  mode: charging
  # poll interval defines how often the vehicle API may be polled if NOT charging
  interval: 60m
  estimate: true # set false to disable interpolating between api updates (not recommended)
  enable: # pv mode enable behavior
  delay: 1m # threshold must be exceeded for this long
  threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
  disable: # pv mode disable behavior
  delay: 3m # threshold must be exceeded for this long
  threshold: 0 # maximum import power (W)

tariffs are the fixed or variable tariffs

tariffs:
currency: EUR # three letter ISO-4217 currency code (default EUR)
grid:
# either static grid price (or price zones)
type: fixed
price: 0.294 # EUR/kWh
zones:
- days: Mon-Sun
hours: 7-21
price: 0.19 # EUR/kWh
- days: Mon-Sun
hours: 21-0
price: 0.12 # EUR/kWh
- days: Mon-Sun
hours: 0-7
price: 0.12 # EUR/kWh

mqtt message broker

mqtt:
broker: core-mosquitto.local.hass.io
topic: evcc # root topic for publishing, set empty to disable
user: mqttuser
password: ferrari

influx database

influx:

url: http://localhost:8086

database: evcc

user:

password:

eebus credentials

eebus:

uri: # :4712

interfaces: # limit eebus to specific network interfaces

- en0

certificate: # local signed certificate, required, can be generated via evcc eebus-cert

public: # public key

private: # private key

push messages

messaging:
events:
start: # charge start event
title: Charge started
msg: Started charging in "${mode}" mode
stop: # charge stop event
title: Charge finished
msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
connect: # vehicle connect event
title: Car connected
msg: "Car connected at ${pvPower:%.1fk}kW PV"
disconnect: # vehicle connected event
title: Car disconnected
msg: Car disconnected after ${connectedDuration}
soc: # vehicle soc update event
title: Soc updated
msg: Battery charged to ${vehicleSoc:%.0f}%
guest: # vehicle could not be identified
title: Unknown vehicle
msg: Unknown vehicle, guest connected?
services:

- type: pushover

app: # app id

recipients:

- # list of recipient ids

- type: telegram

token: # bot id

chats:

- # list of chat ids

- type: email

uri: smtp://:@:/?fromAddress=&toAddresses=

- type: ntfy

uri: https:///

priority:

tags:

[mfuchs1984]

Sure, you still have the line meter: charge # charge meter in your loadpoint config.

Btw., to format the config properly here, copy it to the input files, mark it and then press <>.

[MarcoVg1980]

Now seems to read somthing, but I can't read the SOC from batteries and Other values

[MarcoVg1980]

network:
  # schema is the HTTP schema
  # setting to `https` does not enable https, it only changes the way URLs are generated
  schema: http
  # host is the hostname or IP address
  # if the host name contains a `.local` suffix, the name will be announced on MDNS
  # docker: MDNS announcements don't work. host must be set to the docker host's name.
  host: evcc.local
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 30s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval

# database configuration for persisting charge sessions and settings
# database:
#   type: sqlite
#   dsn: <path-to-db-file>

# sponsor token enables optional features (request at https://sponsor.evcc.io)
# sponsortoken:

# telemetry enables aggregated statistics
#
# Telemetry allows collecting usage data (grid and green energy, charge power).
# Data is aggregated, no individual charging sessions are tracked. The collected,
# anonymous data can be retrieved using https://api.evcc.io.
#
# See https://github.com/evcc-io/evcc/pull/4343 or details.
#
# For time being, this is only available to sponsors, hence data is associated with
# the sponsor token's identity.
#
# telemetry: true

# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error

# modbus proxy for allowing external programs to reuse the evcc modbus connection
# each entry will start a proxy instance at the given port speaking Modbus TCP and
# relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)
modbusproxy:
  #  - port: 5200
  #    uri: solar-edge:502
  #    # rtu: true
  #    # readonly: true # use `deny` to raise modbus errors

# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for documentation see https://docs.evcc.io/docs/devices/meters
    
meters:
  #- name: my_pv
  #  type: template
  #  template: huawei-dongle
  #  usage: pv
    
  - name: my_pv
    type: template
    template: huawei-dongle
    usage: pv
    
    modbus: tcpip
    id: 1
    host: 192.168.1.191 # Hostname
    port: 502 # Port
    timeout: 15s # optional

  - name: my_grid
    type: template
    template: huawei-dongle
    usage: grid
    
    modbus: tcpip
    id: 1
    host: 192.168.1.191 # Hostname
    port: 502 # Port
    timeout: 15s # optional
    
  - name: my_battery
    type: template
    template: huawei-dongle
    usage: battery
    
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.1.191 # Hostname
    port: 502 # Port
    timeout: 15s # optional
    

    

# charger definitions for generic charger via MQTT
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
  - name: Carport
    type: custom  # or default
    status: # charger status A..F
        source: mqtt
        topic:  prism/1/state/  #carport/lp/1/ChargeStatus
        timeout: 10m
    enabled: # charger enabled state (true/false or 0/1)
        source: mqtt
        topic: prism/1/mode
        timeout: 10m
    enable: # set charger enabled state (true/false or 0/1)
        source: mqtt
        topic: prism/1/state/
        payload: ${enable:%d}
        timeout: 10m
    maxcurrent: # set charger max current (A)
        source: mqtt
        topic: prism/1/command/set_current_user
        timeout: 10m


# vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:
  - name: car1
    type: renault
    title: Twingo
    capacity: 22 # kWh
    user: -----------
    password: ----------
    vin:    # .WREN.Car ID..
    onIdentify: # set defaults when vehicle is identified
#    mode: pv # enable PV-charging when vehicle is identified
    phases: 1
    icon: car
    cache: 15m
#    minCurrent: 8
#    maxCurrent: 16


# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: my_grid # grid meter
    pv:
      - my_pv # list of pv inverters/ meters
    battery:
      - my_battery # list of battery meters
#    aux:
#      - aux # list of auxiliary meters for adjusting grid operating point
  residualPower: 200 # additional household usage margin in W
  maxGridSupplyWhileBatteryCharging: 1 # ignore battery charging if AC consumption is above this value

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Carport Charger # display name for UI
    charger: Carport # charger
    meter: my_pv # charge meter
    vehicle: car1
    mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly availab


    # remaining settings are experts-only and best left at default values
    priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    soc:
      # polling defines usage of the vehicle APIs
      # Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
      # or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
      poll:
        # poll mode defines under which condition the vehicle API is called:
        #   charging: update vehicle ONLY when charging (this is the recommended default)
        #   connected: update vehicle when connected (not only charging), interval defines how often
        #   always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
        mode: charging
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 60m
      estimate: true # set false to disable interpolating between api updates (not recommended)
    enable: # pv mode enable behavior
      delay: 1m # threshold must be exceeded for this long
      threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
    disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)

# tariffs are the fixed or variable tariffs
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type:  fixed
    price: 0.294 # EUR/kWh
    zones:
      - days: Mon-Sun
        hours: 7-21
        price: 0.19 # EUR/kWh
      - days: Mon-Sun
        hours: 21-0
        price: 0.12 # EUR/kWh
      - days: Mon-Sun
        hours: 0-7
        price: 0.12 # EUR/kWh


# mqtt message broker
mqtt:
  broker: core-mosquitto.local.hass.io
  topic: evcc # root topic for publishing, set empty to disable
  user: -------
  password: -----

# influx database
influx:
  # url: http://localhost:8086
  # database: evcc
  # user:
  # password:

# eebus credentials
eebus:
  # uri: # :4712
  # interfaces: # limit eebus to specific network interfaces
  # - en0
  # certificate: # local signed certificate, required, can be generated via `evcc eebus-cert`
  #   public: # public key
  #   private: # private key

# push messages
messaging:
  events:
    start: # charge start event
      title: Charge started
      msg: Started charging in "${mode}" mode
    stop: # charge stop event
      title: Charge finished
      msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
    connect: # vehicle connect event
      title: Car connected
      msg: "Car connected at ${pvPower:%.1fk}kW PV"
    disconnect: # vehicle connected event
      title: Car disconnected
      msg: Car disconnected after ${connectedDuration}
    soc: # vehicle soc update event
      title: Soc updated
      msg: Battery charged to ${vehicleSoc:%.0f}%
    guest: # vehicle could not be identified
      title: Unknown vehicle
      msg: Unknown vehicle, guest connected?
  services:
  # - type: pushover
  #   app: # app id
  #   recipients:
  #   - # list of recipient ids
  # - type: telegram
  #   token: # bot id
  #   chats:
  #   - # list of chat ids
  # - type: email
  #   uri: smtp://<user>:<password>@<host>:<port>/?fromAddress=<from>&toAddresses=<to>
  # - type: ntfy
  #   uri: https://<host>/<topics>
  #   priority: <priority>
  #   tags: <tags>