• H
    Heizelmann

    In my experience it is best to use the ESP8266 in battery powered projects only as slave for transmission and as described above with an Attiny13 or so as Master. The ESP can be switched on or off simply by the Attiny via the CH_PD pin of the ESP. Only disadvantage of the complete solution is the long on-time of the ESP due to the complex WIFI registration process and protocol. In my experience sending a simple byte of information takes mostly about 5 to 15 seconds. If this happens only once a day or every x hours it might be OK. For battery powered sensors I prefer Mysensors technology.

    posted in Support in Deutsch read more
  • H
    Heizelmann

    For me it works with the workaround from @mwittig

    max(0, subString("$traffic.traffic", "^\d\{1,3\}"))
    

    The device looks like this ( @V1per maybe you check this)

        {
          "variables": [
            {
              "name": "travelTimeMinutes",
              "expression": "max(0,subString(\"$traffic.traffic\", \"^\\d\\{1,3\\}\"))",
              "type": "number"
            }
          ],
          "xAttributeOptions": [],
          "id": "travelVariables",
          "name": "travelVariables",
          "class": "VariablesDevice"
        }
    

    posted in Rules and Scripts read more
  • H
    Heizelmann

    @V1per I see. The error message is more or less a warning. The variable is evalated correctly and also can be used in numeric operation. Pimatic distinguish only between Expression variable and Value variable but internally checks if it is a number or a string.

    Nevertheless this behaviour should be corrected by the developers.

    posted in Rules and Scripts read more
  • H
    Heizelmann

    @V1per You don’t need to search for the space, simply change the {1,2} to {1,3} then up to three digits are matched.

    posted in Rules and Scripts read more
  • H
    Heizelmann

    I am not so familiar with regular expression.Can you explain yours? Or try this "(\d{1,2}) "

    posted in Rules and Scripts read more
  • H
    Heizelmann

    @Heizelmann said in Extend Timer Device with Countdown Option:

    Setting the time seems to be a missing feature.
    E.g. I would like to setup a new timer for an operation hour counter and would start with an inital value greater zero.
    a)Editing device attributes in Variables would help but is not implemented yet.
    b)More comfortable would be to set it in device editor.
    c)Setting time attribute in rules is also not yet possible. (e.g. ‘set time of timer = 42’ )

    An option for count down is also desirable.

    I would like to add another feature request:

    • the timer should continue running when pimatic server or system has been stopped (Currently I use a workaround of a complete timer by a buttons device, a couple of rules, and the date(“u”) expression function, but integrating this into the timer device would be more comfortable.)

    posted in Feature Requests read more
  • H
    Heizelmann

    try this:

    execute "cp /home/pi/pimatic-app/config.json /mnt/Backup/Pimatic{date("YYYY-MM-DD")}.json"
    

    posted in Rules and Scripts read more
  • H
    Heizelmann

    I tested it also with homeduino devices and it is the same error.So I think it is a pimatic issue. As an alternative you can use the $id.attribute notation, this works for me. Please try

    when $door-contact-kuechenfenster.battery > $low_batterie
    

    (if the id is the ssame as the name in your example, otherwise use your device id of cause)

    posted in Rules and Scripts read more
  • H
    Heizelmann

    @mwittig Thanks for the info and the bug report to openweather.org. The alternatives you mentioned are not providing weather data nesr enough to my city. So for now I will wait and hope that openweathermap.org will correct this malfunction soon.

    If you have some news please report it here.

    posted in Troubleshooting read more

Looks like your connection to pimatic forum was lost, please wait while we try to reconnect.