Rawshutter Device Problem

---

Re: Problem to get pimatic-wunderground running

Hello again,

beeing back home today, I found again a problem with the rawshutters.
All three respective devices didn’t show any press-buttons in the web-frontend on my iPad, but a kind of status ‘up’. Pimatic didn’t show any error message at that point of time.

Opening the config.json, I found again the line "command" : "up", as yesterday, but now in all three rawshutter devices.

To make a long story short, after additional investigations (via PC), I realized, that pimatic seems to store the last command, by pressing the button or by rule, by that line in the config.json.

That seems not to produce any errors, as long as pimatic isn’t restarted.
Restarting it without that lines in the config works fine, but with the line(s) "command" : "up/down/stopped" in, it produces an error message per device which looks like this:

error [pimatic]: Error loading device “jalo-arb02”: Protocol “rawshutter” has no property named “command”. Available properties are: “pulseCount” “pulseLengths” “pulsesUp” “pulsesDown” “pulsesStop”

… and following also in all affected rules.

Looking at the device configuration (via web frontend) shows, that there is really not such a property.
So, from this understanding, the rawshutter devices seems to have the need for a respective enhancement, or pimatic shouldn’t write back this line to the config.json.

Am I right?

I also checked an old config.json of mine, which didn’t contain such lines. So it must have been coming along with my update on pimatic 0.9.48 and node 10.15.3.

As far as I could found in the forum, @rrooggiieerr has developed the rawshutter device. Maybe he can help here?

… and please forget my impressions from yesterday, about beeing whatever plugin the reason for the problem.

Regards
Pedder

@pedder said in Rawshutter Device Problem:

error [pimatic]: Error loading device “jalo-arb02”: Protocol “rawshutter” has no property named “command”. Available properties are: “pulseCount” “pulseLengths” “pulsesUp” “pulsesDown” “pulsesStop”

Most likely it is a bug, but it does not seem to be an easy catch. I am not able to reproduce it so far. Can you please a sample configuration for the shutter device(s) you’re using.

EDIT: Does executing the stop() command causes the “command” property to be written to the config?

Hello @mwittig,

yes for sure, here comes the device:

"devices": [
    {
      "id": "ug-buero-jalo",
      "name": "Jalo Buero",
      "class": "HomeduinoRFShutter",
      "protocols": [
        {
          "name": "rawshutter",
          "options": {
            "pulseCount": 50,
            "pulseLengths": [
              622,
              1817,
              18229
            ],
            "pulsesUp": "01010110011001011010100101100101100101100110010102",
            "pulsesDown": "01010110011001011010100101100101100101100101011002",
            "pulsesStop": "01010110011001011010100101100101100101100101100102",
            "command": "up"
          },
          "rfrepeats": 15,
          "receive": false
        }
      ]
    },

And to your question:
The line is added per rawshutter, as soon as the first command is executed via button or rule, independent which command it is.
And it changes with the next command, look here at the same device, after a short ‘down’ and then ‘stop’

  "devices": [
    {
      "id": "ug-buero-jalo",
      "name": "Jalo Buero",
      "class": "HomeduinoRFShutter",
      "protocols": [
        {
          "name": "rawshutter",
          "options": {
            "pulseCount": 50,
            "pulseLengths": [
              622,
              1817,
              18229
            ],
            "pulsesUp": "01010110011001011010100101100101100101100110010102",
            "pulsesDown": "01010110011001011010100101100101100101100101011002",
            "pulsesStop": "01010110011001011010100101100101100101100101100102",
            "command": "stop"
          },
          "rfrepeats": 15,
          "receive": false
        }
      ]
    },

@pedder Thanks for the info which helped me to reproduce the problem. pimatic-homeduino-0-9-18 should fix the issue.

@mwittig
Thanks a lot again!

I did the following:

1. Deleted the "command" : "[status]" lines in the config.json
2. Executed the update to homeduino 0.9.18
3. Restarted pimatic - no error messages
4. Tested all shutters - all worked well
5. Checked the config.json - no new "command" : "[status]" lines in
6. Did an additional pimatic restart - no error messages

So successfully repaired