diff --git a/Energi.JPG b/Energi.JPG
new file mode 100644
index 0000000..2d03f04
Binary files /dev/null and b/Energi.JPG differ
diff --git a/MQTT · Integration.pdf b/MQTT · Integration.pdf
new file mode 100644
index 0000000..7b50cfb
Binary files /dev/null and b/MQTT · Integration.pdf differ
diff --git a/MQTTExplore.JPG b/MQTTExplore.JPG
new file mode 100644
index 0000000..61e3f86
Binary files /dev/null and b/MQTTExplore.JPG differ
diff --git a/README.md b/README.md
index 472580c..e16046a 100644
--- a/README.md
+++ b/README.md
@@ -1,2 +1,198 @@
# HomeAssistant_Saveeye
-Har samlet lidt om opsætning af, SAVEEYE+ FOR ECHELON
+ - SAVEEYE+ FOR ECHELON
+
+# Forord
+Har samlet lidt om opsætning af
+Jeg har efter lang tid, fået min SaveEye til at virke med HomeAssistant MQTT
+det har været en rejse jeg gerne vil se om jeg kan spare andre for
+
+# Udfordringer
+Første udfordring var at jeg skulle have data ud af enheden, der er ikke mange informationer
+fra den pdf MQTT som SaveEyekan sende ud hvis man har udfordringer, (Den ligger også her)
+
+ - Password: Det er vigtigt at man laver et password til sin MQTT broker der er under 25 tegn (ingen spesialtegn)
+ dette kan gøres ved at oprette en ny bruger på sin HomeAssistant, da alle bruger har adgang til MQTT
+ når du så har lavet en ny bruger: dette gøres i /config/users her kan du lave en bruger der kun har
+ adgang fra lokalt netnærk, denne kan så sættes på i SaveEye appen på din smartphone/tablet
+ nu kan din SaveEye enhed komme i kontakt med din MQTT broker
+ - Test: Hvis du gerne vil vide om der kommer data fra SaveEye, kan du med fordel hente et lille program
+ der hedder "mqtt explorer" (se links) med denne kan du også se hvilken data den sender
+ - Data: Dette er de data strange der kommer med over fra SaveEye enheden, det næste er at omsætte det
+ til noget vi faktisk kan bruge.
+ saveeyeDeviceSerialNumber
+ meterType
+ meterSerialNumber
+ timestamp
+ activeActualConsumption
+ total
+ activeActualProduction
+ total
+ activeTotalConsumption
+ total
+ activeTotalProduction
+ total
+ reactiveActualConsumption
+ total
+ reactiveActualProduction
+ total
+ rmsVoltage
+ L1
+ L2
+ L3
+ rmsCurrent
+ L1
+ L2
+ L3
+ powerFactor
+ L1
+ L2
+ L3
+# 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
+filen "configuration.yaml" denne finder du enten i den SAMBA Share eller ved at installere et AddOn "Studio Code Server"
+her kan du redigere filen og efterfølgene teste om din konfikuration er korekt.
+ - Sensor entity:
+ device_class: VOLTAGE
+ unit_of_measurement: V
+Der ligger et link længere nede der forklare "Sensor entity" hvilken type af sensor der kan bruges i de ovennævntte.
+ #YAML
+ - yaml:
+ 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
+
+ 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/
+ - SaveEye - https://saveeye.dk/produkt/saveeye-for-echelon/
+ - Sensor entity - https://developers.home-assistant.io/docs/core/entity/sensor/#available-state-classes
+
\ No newline at end of file
diff --git a/card.JPG b/card.JPG
new file mode 100644
index 0000000..f71abc2
Binary files /dev/null and b/card.JPG differ
diff --git a/data.JPG b/data.JPG
new file mode 100644
index 0000000..bbde1f5
Binary files /dev/null and b/data.JPG differ
diff --git a/mqtt.JPG b/mqtt.JPG
new file mode 100644
index 0000000..ed312c5
Binary files /dev/null and b/mqtt.JPG differ