Jaloezie

Nicky WesselsNicky Wessels Gebruiker
December 2017 aangepast in Pairot
Hoe zet je de jaloezie goed op ?

Ik zie slechts 2 verzend adressen en verwacht er 3 ?

ik heb de volgende adressen
- Up/Down
- Stop
- Position
- Position Status
- Direction Status
- Movement Status

ik het volgende geconifureerd
eerste regel: zend(up/down ) + status (direction status)
tweede regel geen mogelijkheid voor zend ?? dus status(stop)
derde regel: zend(position) + status (position status)

Het werkt maar niet goed,
- de screens gaan op of neer, maar ik kan geen stop uitvoeren
- positie lijkt te werken, maar mijn timings van de screens staan nog niet goed om dit te controleren

Al vast bedankt

Reacties

  • Freddy van GeelFreddy van Geel xxter medewerker
    December 2017 aangepast
    Hoi Nicky,

    De Jaloezie werkt op deze manier:
    Een jaloezie vereist een één bit schakeling (DPT 1.x) als zendende groep voor de op/neer beweging en één byte dimwaarde (DPT 5.001) als zendende groep voor waarden van 0-100 voor de positie. Beiden vereisen een of meer status groepsadressen van dezelfde types en aanvullend een één bit schakeling (DPT 1.x) als statusgroep voor de start/stop status.
    Zie ook het document voor: Projectbewerking
    Als je op de tegel tikt in HomeKit app zal de jaloezie volledig dicht of open gaan. Lang drukken op de tegel geeft een percentage sturing, waarbij direct de gekozen waarde wordt uitgestuurd.

    HomeKit ondersteunt geen ”stop” om handmatig te stoppen, en geen lamellen verstelling.
  • As far as I can understand dutch :), the answer above seems incomplete.

    I will use the english version of the doc but it's just a translation from the dutch version Freddy copy/pasted above:
    "A blind requires a one bit switching (DPT 1.x) sending group for up/down movement and a one byte scaling (DPT 5.001) sending group for 0-100 values for the position."

    So far so good, this maps quite nicely with what most blind actuators have ("move up/down" and "setPos").

    "Both require one or more similar type status group addresses and an additional one bit switching (DPT 1.x) for the start/stop status"

    This where it gets more complicated. There are 3 status requested here, and only one is obvious and commonly found in actors AFAIK: position status (aka "isPos").
    I suppose "start/stop" status means some form of "blind is moving" status ? I don't have these on my actors, what should I put (it's mandatory) ?
    And I imagine the last "status" (matching move up/down sending group) is the "moving up" or "moving down" status ? I haven't seen this often in actors (newer MDT have it, I think, any other?)


    For the moment, I have configured the blind with the 2 "rare" statuses having the same GA than move up/down. With this, all the Pairot is doing is sending a "setPos", followed shortly by a read on "isPos".

    Some extra clarity is needed as to the Pairot logic here? Is it somehow detecting strange GA usage in my config and falling back on just "setPos" and "isPos", or do we have to indicate many mandatory GAs only for fun ?

    How does the thing work?


  • Hoi Nicky,
    HomeKit ondersteunt geen ”stop” om handmatig te stoppen, en geen lamellen verstelling.

    The latest HAP specs seems to hint at stop support ("Hold Position" characteristics). Is this implemented in Pairot and not working in Homekit?
  • Freddy van GeelFreddy van Geel xxter medewerker

    Hoi Nicky,
    HomeKit ondersteunt geen ”stop” om handmatig te stoppen, en geen lamellen verstelling.

    The latest HAP specs seems to hint at stop support ("Hold Position" characteristics). Is this implemented in Pairot and not working in Homekit?
    Thanks for the heads-up! Our developers will look into the (probably renewed) specs and answer below.
    Due to the holidays this will maybe take a bit longer than what you're used to at xxter ;)
  • Harm ElzingaHarm Elzinga xxter medewerker
    This is indeed correct. The stop command is currently not supported in the Pairot.
    This will be implemented in an update. So currently only direct position control is supported. The status GA's of the start/stop and up/down are not "read" but can be used with actuators which do not support exact position.

    Personally I have never seen a blind-actuator which does not support start/stop (short press) and up/down (long press), because this is the normal way of using these kind of actuators with pushbuttons. Could this be a parameter setting? And does this clarify your question?
  • @Freddy van Geel Clear re. support of "stop" in Pairot. Thanks.

    @Harm Elzinga Yes, all actuators have "move up/down" and "step/stop" COMMANDS. However, Pairot currently asks for:

    * a "move up/down" COMMAND (fine)
    * a "move to position" COMMAND (fine)
    * a "isPosition" STATUS (fine)
    * a "move up/down" STATUS (what is this? see above for my interpretation "isMoving")
    * a "start/stop" STATUS (same question)

    In other terms, yes all actors have these two commands but Pairot only asks for one of them and for the other, it asks for a STATUS...




  • Harm ElzingaHarm Elzinga xxter medewerker
    Hi Fred,

    Sorry for the delayed answer.
    * a "move up/down" STATUS (what is this? see above for my interpretation "isMoving")
    * a "start/stop" STATUS (same question)

    These are status groups for when you also control the actuator with for example with buttons.
    Some actuators will also have optional status objects for this.
    * a "move up/down" STATUS (what is this? see above for my interpretation "isMoving")
    0 = is moving up
    1 = is moving down
    * a "start/stop" STATUS (same question)
    0 = stop

    We will make these status fields optional, if you supply the isPosition GA.
  • Udo KellerUdo Keller Gebruiker, Specialist

    Some actuators will also have optional status objects for this.
    * a "move up/down" STATUS (what is this? see above for my interpretation "isMoving")
    0 = is moving up
    1 = is moving down
    * a "start/stop" STATUS (same question)
    0 = stop

    We will make these status fields optional, if you supply the isPosition GA.

    Are there any news regarding these two status objects becoming optional? In v1.1.35 beta, both still are mandatory.

    Aside from this, just to be sure: You are saying that "start/stop STATUS" = 0 means the blinds are not moving, and "start/stop STATUS" = 1 means they are moving.

    Thank you for clarification.
  • Harm ElzingaHarm Elzinga xxter medewerker
    Hi Udo,

    The on the beta site, these fields are not optional.
    Aside from this, just to be sure: You are saying that "start/stop STATUS" = 0 means the blinds are not moving, and "start/stop STATUS" = 1 means they are moving.
    Yes, but most actuators do not send the "start" 1, only the stop one.
Log In of Registreer om te reageren.