Skip to content

Latest commit

 

History

History
141 lines (105 loc) · 7.96 KB

File metadata and controls

141 lines (105 loc) · 7.96 KB

Siemens OZW672 Integration for HomeAssistant

GitHub Release GitHub Activity License

pre-commit Black

hacs Project Maintenance

Discord Community Forum

Overview

OZW672 is a Web server platform which enables remote plant monitoring for Siemens LPB/BSB Plants. This integration was built and tested using a OZW672.01 running v11.0 firmware monitoring an RVS43.345/109 with three AVS73.390/109 extension modules.

Yes - you can use this integration to WRITE values to the OZW672. Noting that:

  1. The OZW672 only supports certain datapoints to have WriteAccess
  2. This integration only supports writing for "Enumerations", "Numbers" and "Switch" domains.
  3. Some values you write are ignored by the OZW672. If that happens - test using the OZW672 UI.

Sensors Supported

Platform Description
binary_sensor Read only Show something On or Off. eg a Pump
sensor Read only sensors that don't fit in any other category
switch Read/Writ eSwitch something On or Off.
select Read/Write selectable Enumerations
number Read/Write Numbers - eg Temperature or Percentage

example

Disclaimer

This is an independent, unofficial, community-developed project. It is not affiliated with, endorsed by, sponsored by, or approved by Siemens AG or any of its subsidiaries.

"Siemens", "OZW672", "RVS43", "AVS73" and other product and model designations are trademarks or registered trademarks of Siemens AG or their respective owners. They are used here nominatively — that is, solely to identify the hardware this integration communicates with, as is permitted for accurate description of interoperability. No claim to those marks is made or implied.

The icon and logo shipped with this integration are original artwork created for this project. They are not Siemens assets, are not reproductions of any Siemens logo or wordmark, and do not represent Siemens branding or an official Siemens product.

This integration talks to the OZW672 over the local HTTP API exposed by the device itself. It contains no Siemens source code, firmware, or other proprietary Siemens material, and distributes none.

The software is provided under the MIT License without warranty of any kind — see LICENSE. You use it, and any changes it writes to your equipment, at your own risk.

If you are a rights holder and believe anything here misrepresents your brand, please open an issue on the issue tracker and it will be addressed promptly.

Installation

  1. Use HACS, in `HACS > Integrations Cick the three dots on the top right and select "Custom Repositories" and add a link to this GitHub Repository.
  2. Click "Explore & Download Repositories", Search for "Siemens OZW672" and click "Download. Skip to step 8
  3. If no HACS, use the tool of choice to open the directory (folder) for your HA configuration (where you find configuration.yaml).
  4. If you do not have a custom_components directory (folder) there, you need to create it.
  5. In the custom_components directory (folder) create a new folder called siemens_ozw672.
  6. Download all the files from the custom_components/siemens_ozw672/ directory (folder) in this repository.
  7. Place the files you downloaded in the new directory (folder) you created.
  8. Restart Home Assistant.
  9. Add Integration or in the HA UI go to "Settings" -> "Devices & Services" then click "+" and search for "Siemens OZW672 Integration".

Note: This integration will wake up your vehicle(s) during installation.

  1. Add the custom repository in HACS
  2. Install via HACS and restart HomeAssistant
  3. Go to Settings -> Devices and "Add Integration". Select "Siemens OZW672"

Configuration only supported by the UI

  1. The OZW672 is not very powerful - LIMIT polling only variables you require. You can discover entities to poll, then re-run and discover more. Only discover max 10 at a time.
  2. In my testing http was more scaleable than https - YOU MUST ENABLE THIS IN THE OZW672
  3. https implementation does NOT check for valid server certificate
  4. The component provides flexbility in naming your entities in two ways:
    a. No Prefix. eg. "Legionella function"
    b. Prefix the datapoint with the Function/MenuItem name eg. "DHW - Legionella function"
    c. Prefix the datapoint with the Operating Line number from the manual eg. "1640 Legionella function"
    d. Both Prefixes - eg: "DHW - 1640 Legionella function"

My recommendations for reliable operation:

  1. Configure the OZW672 to use http. Home > 0.x OZW672.01 > Settings > Communication > Services > We access via http = ON
  2. Configure the OZW672 to use static IP, Gateway & DNS. Home > 0.x OZW672.01 > Settings > Communication > Ethernet
  3. Discover Functions one at a time. The OZW672 is not powerful - discover one function and max 10 variables at a time.
  4. Configure a dedicated user in teh OZW672 for your home assistant polling. I used the "Service" user group.

Contributions are welcome!

If you want to contribute to this please read the Contribution guidelines Please make sure you enable debug and submit logs.

Credits

This project was created in my spare time on an OZW671.01 monitoring my home Hydronic Plant.

This project was generated from @oncleben31's Home Assistant Custom Component Cookiecutter template.

Code template was mainly taken from @Ludeeus's integration_blueprint template