[solved]pimatic-pilight / shutter migration

---

Hi everybody,

I’m wondering about the pimatic-pilight plugin? were is it? cannot find it in the list of available plugins to install.

also tried:

npm install pimatic-pilight

but did not work…
would like to import my pilight devices to pimatic.

regards

pascal

Pilight isnt supported anymore. You can switch to homeduino.

The only reason I still use it is that I didnt manage to control my Shutter (shutter5 / esmart) with it. I dont know where to grab id and code. Any ideas? It it possible to use pilight and homeduino with the Same sender (gpio)?

I doubt you can use pilight and pimatic with the same sender.
When you have homeduino installed, just go to messages in pimatic and turn on debug there.
You will see your code/id when sending

@incmve ok, installed the plugin on my clean pimatic installation with Raspberry Pi 3. Seems to work! Receiving debug output. Unfortunately there is no exact output like the expected “shutter5” but a lot of switch-variety.
Tried one with:

   {
      "id": "homeduino-contact",
      "name": "Shutter Controller",
      "class": "HomeduinoRFShutter",
      "protocols": [
        {
          "name": "switch14",
          "options": {
            "unit": 4,
            "id": 845056
          }
        }
      ]
    }

It shows “Down & Up”-Buttons but they don’t work very well. I have to trigger them multiple times and they behave inverted.

For my switch (brennenstuhl) i’ve added a RFSwitch-Device. It perfectly switches the lamp on. But not off.

Do I have to add multiple protocols the get UP,Down,Stop functionality?

At least this is a step in the right direction

I’ve managed to find out the different unitcode’s for up / down / stop.
Seems to work “sometimes”, means after the first rf-send, pimatic don’t send another signal for a while. I think it could be a performance issue because I’m not using an arduiono at the moment. Driver is “gpio”. After a while, I can successfully trigger another command for the shutter.

Here’s my config:

{
      "id": "rf-shutter-buttons",
      "name": "Leinwand",
      "class": "HomeduinoRFButtonsDevice",
      "buttons": [
        {
          "id": "shutter-down-button",
          "text": "▼",
          "protocols": [
            {
              "name": "switch14",
              "options": {
                "unit": 2,
                "id": 845056,
                "all": true,
                "state": false
              }
            }
          ]
        },
        {
          "id": "shutter-stop-button",
          "text": "◄►",
          "protocols": [
            {
              "name": "switch14",
              "options": {
                "unit": 3,
                "id": 845056,
                "all": true,
                "state": false
              }
            }
          ]
        },
        {
          "id": "shutter-up-button",
          "text": "▲",
          "protocols": [
            {
              "name": "switch14",
              "options": {
                "unit": 4,
                "id": 845056,
                "all": false,
                "state": false
              }
            }
          ]
        }
      ]
    }

regards

RF receiving without an arduino can keep your CPU busy but I doubt it will hang up an Pi 3.
Maybe @Icesory or @mwittig has an idea?

@incmve same behaviour with my RF Switches (Brennenstuhl) It takes some time for pimatic to actually do the action, but sometimes it reacts instantly.

short update:

after a while (after some reboots and updates), homeduino works pretty well with the RPi3.
Shutter control works quite good. Sometimes there is some lag but it performs the action I triggered.
Soon I will get an arduino nano to outsource the receiving 433 part.

I guess it causes problems sometimes when it receives it’s own commands which were send by the Pi.

I’ll give you an update.

Pascal