rest_command: # Entfernen falls diese Zeile schon existiert bzw. du das in einer extra YAML machst
dimmer_on:
url: ‘http://[Homepilot IP]/devices/{{ did }}’ # [Homepilot IP] ersetzen
method: PUT
payload: ‘{“name”:“TURN_ON_CMD”}’
dimmer_off:
url: ‘http://[Homepilot IP]/devices/{{ did }}’ # [Homepilot IP] ersetzen
method: PUT
payload: ‘{“name”:“TURN_OFF_CMD”}’
dimmer_brightness:
url: ‘http://[Homepilot IP]/devices/{{ did }}’ # [Homepilot IP] ersetzen
method: PUT
payload: ‘{“name”:“GOTO_POS_CMD”,“value”:“{{ brightness }}”}’
i´ve added the files as shown on top of this post and get the following error when i check the config:
Invalid config for [rest]: [belt_winder_up] is an invalid option for [rest]. Check: rest->rest->0->belt_winder_up. (See /config/configuration.yaml, line 39).
You either have to create an extra yaml file and include it rest_command: !include rest.yaml
Or just put rest_command: into your configuration.yaml and add the block underneath.
Please re-read step 2.
If you’re already using rest.yaml for something different, just create a file with a different name like rest_command.yaml and include that one.
In my current project, I created a PowerShell-script to create sensors and covers for Rademacher-Covers using the device.json you can obtain from your homepilot.
Just download and store that json from http://[Homepilot IP]/devices in the script-directory.
Then open “CreateRademacherCoverInfos.ps1” in ISE or Visual Studio code.
Change the variables in the first region
# basepath - working directory
$basepath = "D:\temp\rademacher"
# Name of json-File from homepilot, get it from http://[Homepilot IP]/devices and save it
$devicesJSONFileName = "Rademacher-Devices.json"
# parts of devicenames, that should be excluded, e.g. switche, ligths, ...
$excludeNamesContaining = @("stecker", "duofern", "licht", "leucht")
# Homepilot-IP
$homepilotIP = "192.168.66.99"
The basepath should be the path, where you stored the json-file and where the yml-files will be created.
If you want to exclude some devices, like lights, you can use the excludeNamesContaining-array.
Then add you own homepilot-IP and start the script.
Hello together,
my HA 2022-2-6 is running in a Docker Container with Bridged Network.
I’ve installed HACS 1.22 and then Rademacher Homepilot Integration (peribeir) successful,
but I can’t connect to my Homepilot at Host-Network.
Error-Message in then Dialogbox “Hostname/IP-Adresse der Bridge eingeben”:
Unbekannter Fehler.
Must there more ports be accessible from outside in the HA Container?
Uli
After a fix of the Version 1.4.1 => Version 1.5.0 it works fine
Version v1.5.0-beta3 now recognise my homepilot automatically and I can add all my DuoFern und Z-Wave devices (about 42)
Thanks a lot.
Hey guys I am thinking about buying Rademacher 1550 for my window.
Does this work with Home assistant and do I need the official Rademacher bridge? Would love to do it without. Anyways, does anyone have experience with different products of this kind?
I have the exact same product, since they speak some sort of proprietary protocol on 433MHz you’ll either need a bridge (easy) or the USB stick which is hard to get and not as easy to implement (if at all)
Given that you have the same product, how does it go together with Home Assistant in terms of compatibility?
And may I ask how it works range wise, I have to cover two platforms…
The second option is much easier, and given that the repository is quite active it might be a good place to start. However the first method, while requiring more setup time, is more robust. I haven’t touched it for 2 years and it still works 100%.
Be aware that the custom integration is more likely to break when Home Assistant changes its core API between versions.
Still, the integration probably is a better place to start.
With the REST integration:
What works:
Sending commands like Open, Close, Stop, Set Position
Reading the current position
What doesn’t work:
The covers don’t have a “opening” or “closing” state, the Rademacher Hub only reports the target state while the cover is moving and the current one while it isn’t
Setting the position to 0 or 100 doesn’t close/open the covers completely (missing about 1cm), only a open/close command will
As I said, I haven’t really touched my setup for a few years, so firmware updates might resolve those issues, I just don’t really care.
If you’re starting fresh, go with the cheaper hub and install the integration from HACS.
As for the range I don’t really know, I’ve installed 8 motors, and since they form a mesh network and relay commands I haven’t had a single issue with that.