The configuration options from below are common to all output devices. At the time of writing these are
the Shelly Pro3EM and the EcoTracker. The samples always show the Shelly Pro3EM configuration. For
usage with the EcoTracker please replace the shelly-pro3 property with eco-tracker.
If the physical input device is not reachable and no power values are available for a certain time, the uni-meter will not provide any output values to the storage anymore, so that the storage triggers its fallback behavior.
Without any configuration that happens after one minute. If you need a different timeout, you can configure it using the following configuration below:
uni-meter {
#...
output-devices {
#...
shelly-pro3em {
# These are the defaults used without any configuration:
forget-interval = 1m
}
}
}In some setups, it might be necessary to add a static offset to the power values. This can be the case if the real electrical meter readings are not 100% accurate to your household's electrical meter readings.
You can either configure a power offset for the single phases or a total power offset. The phase power offsets take precedence over the total power offset. If at least one phase power offset is configured, the total power offset is ignored.
Setting the power offset is done in the /etc/uni-meter.conf file:
uni-meter {
#...
output-devices {
#...
shelly-pro3em {
#...
power-offset-total =0
power-offset-l1 = 0
power-offset-l2 = 0
power-offset-l3 = 0
}
}
}uni-meter can send individual power values to different clients. This allows the usage with multiple
independent storages. This is more or less an experimental feature. Even if all storages only get a share
of the current power, over time small fluctuations of the charging/discharging power may lead to the
situation that one storage charges another one. That can be corrected by disabling the complete uni-meter
in certain intervals using the REST API to switch on/off for short periods, for instance,
through a cron job.
For each client, specified by its IP address, the MAC address and the power factor to use can be configured.
For all other clients not found in that client-contexts list a default-client-power-factor can be
set which defaults to 1.0.
uni-meter {
#...
output-devices {
shelly-pro3em {
#...
default-client-power-factor = 0.5
client-contexts = [{
# See correct data from local machine
address = "127.0.0.1"
mac = "abcdef0123456"
power-factor = 1.0
},{
# Small batterie
address = "192.168.178.30"
mac = "bcdef01234567"
power-factor = 0.3
},{
# Big batterie
address = "192.168.178.70"
mac = "cdef012345678"
power-factor = 0.7
}]
}
}
}If you are using the uni-meter in a Non-European country, which has different grid voltage and frequency standards as Europe, you can change these parameters as below.
uni-meter {
#...
output-devices {
#...
shelly-pro3em {
# North american settings
default-voltage = 115.0
default-frequency = 60.0
}
}
}If mDNS is used, the announced IP address is derived from the selected output device configuration.
If interface contains an IPv4 or IPv6 address, uni-meter uses it directly. Otherwise, it is treated as a network
interface name and uni-meter tries to resolve an IP address from it, preferring IPv4 over IPv6. If that does not
work, uni-meter falls back to the detected primary IPv4 address.
uni-meter {
#...
output-devices {
#...
shelly-pro3em {
interface = "eth0"
}
}
}