første upload
This commit is contained in:
Thomas
2024-05-29 23:35:23 +02:00
parent 0f942f18c9
commit fbfec9457f
7 changed files with 197 additions and 1 deletions

BIN
Energi.JPG Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 76 KiB

BIN
MQTT · Integration.pdf Normal file

Binary file not shown.

BIN
MQTTExplore.JPG Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

198
README.md
View File

@@ -1,2 +1,198 @@
# HomeAssistant_Saveeye # HomeAssistant_Saveeye
Har samlet lidt om opsætning af, SAVEEYE+ FOR ECHELON - SAVEEYE+ FOR ECHELON
<br>
# Forord
Har samlet lidt om opsætning af<br>
Jeg har efter lang tid, fået min SaveEye til at virke med HomeAssistant MQTT <br>
det har været en rejse jeg gerne vil se om jeg kan spare andre for<br><br>
# Udfordringer
Første udfordring var at jeg skulle have data ud af enheden, der er ikke mange informationer<br>
fra den pdf MQTT som SaveEyekan sende ud hvis man har udfordringer, (Den ligger også her)<br><br>
- Password: Det er vigtigt at man laver et password til sin MQTT broker der er under 25 tegn (ingen spesialtegn)<br>
dette kan gøres ved at oprette en ny bruger på sin HomeAssistant, da alle bruger har adgang til MQTT<br>
når du så har lavet en ny bruger: dette gøres i /config/users her kan du lave en bruger der kun har<br>
adgang fra lokalt netnærk, denne kan så sættes på i SaveEye appen på din smartphone/tablet<br>
nu kan din SaveEye enhed komme i kontakt med din MQTT broker<br><br>
- Test: Hvis du gerne vil vide om der kommer data fra SaveEye, kan du med fordel hente et lille program<br>
der hedder "mqtt explorer" (se links) med denne kan du også se hvilken data den sender<br>
- Data: Dette er de data strange der kommer med over fra SaveEye enheden, det næste er at omsætte det<br>
til noget vi faktisk kan bruge.<br>
saveeyeDeviceSerialNumber<br>
meterType<br>
meterSerialNumber<br>
timestamp<br>
activeActualConsumption<br>
total<br>
activeActualProduction<br>
total<br>
activeTotalConsumption<br>
total<br>
activeTotalProduction<br>
total<br>
reactiveActualConsumption<br>
total<br>
reactiveActualProduction<br>
total<br>
rmsVoltage<br>
L1<br>
L2<br>
L3<br>
rmsCurrent<br>
L1<br>
L2<br>
L3<br>
powerFactor<br>
L1<br>
L2<br>
L3<br><br>
# MQTT
For at få de nødventige data ind i vores MQTT skal vi have dem tilføjet manuelt, dette gøres ved at redigere<br>
filen "configuration.yaml" denne finder du enten i den SAMBA Share eller ved at installere et AddOn "Studio Code Server"<br>
her kan du redigere filen og efterfølgene teste om din konfikuration er korekt.<br><br>
- Sensor entity:<br>
device_class: VOLTAGE<br>
unit_of_measurement: V<br>
Der ligger et link længere nede der forklare "Sensor entity" hvilken type af sensor der kan bruges i de ovennævntte.<br><br>
#YAML
- yaml:<br><code>
template:
sensor:
- name: "saveeye"
unit_of_measurement: W
state: >
{{ 3600000000 / (states('sensor.saveeye_latestInterval') | float(0) * 1000)}}
<\code>
Dette er den første del af enheden, her fortæller vi hvad det er for en sensor, og hvilken parameret den har<br>
<code>
mqtt:
sensor:
- name: saveeyeDeviceSerialNumber
unique_id: saveeyeDeviceSerialNumber
state_topic: "saveeye/telemetry"
value_template: "{{value_json.saveeyeDeviceSerialNumber}}"
- name: meterType
unique_id: meterType
state_topic: "saveeye/telemetry"
value_template: "{{value_json.meterType}}"
- name: meterSerialNumber
unique_id: meterSerialNumber
state_topic: "saveeye/telemetry"
value_template: "{{value_json.meterSerialNumber}}"
- name: timestamp
unique_id: timestamp
state_topic: "saveeye/telemetry"
value_template: "{{value_json.timestamp}}"
- name: activeActualConsumption
unique_id: activeActualConsumption
state_topic: "saveeye/telemetry"
value_template: "{{value_json.activeActualConsumption.total}}"
device_class: power
unit_of_measurement: W
state_class: measurement
- name: activeActualProduction
unique_id: activeActualProduction
state_topic: "saveeye/telemetry"
value_template: "{{value_json.activeActualProduction.total}}"
device_class: power
unit_of_measurement: W
state_class: measurement
- name: activeTotalConsumption
unique_id: activeTotalConsumption
state_topic: "saveeye/telemetry"
value_template: "{{value_json.activeTotalConsumption.total}}"
device_class: ENERGY
unit_of_measurement: Wh
state_class: total_increasing
- name: activeTotalProduction
unique_id: activeTotalProduction
state_topic: "saveeye/telemetry"
value_template: "{{value_json.activeTotalProduction.total}}"
device_class: ENERGY
unit_of_measurement: Wh
state_class: total_increasing
- name: reactiveActualConsumption
unique_id: reactiveActualConsumption
state_topic: "saveeye/telemetry"
value_template: "{{value_json.reactiveActualConsumption.total}}"
device_class: power
unit_of_measurement: W
state_class: measurement
- name: reactiveActualProduction
unique_id: reactiveActualProduction
state_topic: "saveeye/telemetry"
value_template: "{{value_json.reactiveActualProduction.total}}"
device_class: power
unit_of_measurement: W
state_class: measurement
- name: rmsCurrentL1
unique_id: rmsCurrentL1
state_topic: "saveeye/telemetry"
value_template: "{{value_json.rmsCurrent.L1}}"
device_class: CURRENT
unit_of_measurement: mA
state_class: measurement
- name: rmsCurrentL2
unique_id: rmsCurrentL2
state_topic: "saveeye/telemetry"
value_template: "{{value_json.rmsCurrent.L2}}"
device_class: CURRENT
unit_of_measurement: mA
state_class: measurement
- name: rmsCurrentL3
unique_id: rmsCurrentL3
state_topic: "saveeye/telemetry"
value_template: "{{value_json.rmsCurrent.L3}}"
device_class: CURRENT
unit_of_measurement: mA
state_class: measurement
- name: powerFactorL1
unique_id: powerFactorL1
state_topic: "saveeye/telemetry"
value_template: "{{value_json.powerFactor.L1}}"
device_class: POWER_FACTOR
unit_of_measurement: "%"
state_class: measurement
- name: powerFactorL2
unique_id: powerFactorL2
state_topic: "saveeye/telemetry"
value_template: "{{value_json.powerFactor.L2}}"
device_class: POWER_FACTOR
unit_of_measurement: "%"
state_class: measurement
- name: powerFactorL3
unique_id: powerFactorL3
state_topic: "saveeye/telemetry"
value_template: "{{value_json.powerFactor.L3}}"
device_class: POWER_FACTOR
unit_of_measurement: "%"
state_class: measurement
- name: rmsVoltageL1
unique_id: rmsVoltageL1
state_topic: "saveeye/telemetry"
value_template: "{{value_json.rmsVoltage.L1}}"
device_class: VOLTAGE
unit_of_measurement: V
state_class: measurement
- name: rmsVoltageL2
unique_id: rmsVoltageL2
state_topic: "saveeye/telemetry"
value_template: "{{value_json.rmsVoltage.L2}}"
device_class: VOLTAGE
unit_of_measurement: V
state_class: measurement
- name: rmsVoltageL3
unique_id: rmsVoltageL3
state_topic: "saveeye/telemetry"
value_template: "{{value_json.rmsVoltage.L3}}"
device_class: VOLTAGE
unit_of_measurement: V
state_class: measurement
<\code>
# Links
- MQTT Explore - https://mqtt-explorer.com/ <br>
- SaveEye - https://saveeye.dk/produkt/saveeye-for-echelon/ <br>
- Sensor entity - https://developers.home-assistant.io/docs/core/entity/sensor/#available-state-classes <br>

BIN
card.JPG Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

BIN
data.JPG Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 52 KiB

BIN
mqtt.JPG Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 52 KiB