how to link primary and secondary switches using the API

[neckcen]

Hello,

As stated in the title, is it possible to link a primary switch (e.g. actual load bearing) to a secondary switch?

I've read the doc several time and did not see any way to associate a secondary switch to a load. I was expecting to use jobs but apparently secondary switches are not smartbuttons nor can I associate an output (job or otherwise) to a secondary switch.

Thank you for your time and thanks for creating this system, playing with it is quite fun.

[woodworm]

The interaction between jobs and smartbuttons are not yet finally documented. I hope this description helps in the meantime. https://github.com/Feller-AG/wiser-api/issues/24

[neckcen]

Hi woodworm,

Thanks a lot for the link, I somehow missed it and it did help a lot.

For anyone who would end up scratching their head -like me- on how to apply this to a dimmer switch; here is what worked for me (when associated with a secondary dimmer switch, everything seems to work as expected including press-to-dim):

POST api/jobs
{
  "button_ctrl": {
    "event": "click",
    "button": "up down",
    "loads": [
      1
    ]
  }
}

While I'm at it, if I may, a bit of general feedback regarding the API.

• When in AP mode, the API was really slow and connection often got cut by the server, no issue whatsoever in client mode. If this is expected a warning would be advisable, using the API in AP mode made for a terrible experience.
• The documentation is lacking some generic explanation of core concepts (what are devices, jobs, smartbuttons, ...). I believe a short paragraph for each would greatly help painting the whole picture.
• (probably my biggest gripe) It is weird how really similar actions are achieved differently. For example loads/findme sends feedback through the websocket whilst devices/findme replies through the api. Another example (and the origin of this issue) is how some buttons settings are set remotely through the devices endpoints, whilst others require physically assigning them to a program.

Overall though it works well and having everything run locally is great.

[woodworm]

Thanks for your feedback We are aware that more detailed information is still pending in the documentation... We're working on it! In the meantime, we can also offer you support via our Customercare Center to get more information about the core concepts. To do this, you need to write an email to our Customercare Center with the note "API request at woodworm".