• BiGnOsE
    • 5releases
    • 17comments
Comments made
  • Feature request : Ability to backup configuration 1 year ago

    Any update on if this is being considered ?

  • Bug assign key screen 1 year ago

    Need some more info, or did you guys figure out what I was saying ?

  • Feature request : Device level macro 1 year ago

    Any update on this ?

  • Bug assign key screen 1 year ago

    Not device specific. When you click on the buttons, on screen, they open the opposite dialog to actually set the keys.

  • IFTTT Support? 1 year ago

    I second a request for IFTTT integration as a trigger. It would allow endless possibility for automation Example. When I turn on my system, I could trigger IFTTT to close my curtains and then turn off the light. When I turn off my system, I could trigger IFTTT to open the curtains and turn on the light. I'm sure there are plenty other cases, like getting the projector screen down, setting room temperature and what not. This is the one smart home integration that makes sense. Please consider it seriously,.

  • Projector not turning off with the rest of the devices. 1 year ago

    TLDR : Changing the order of execution of the codes to turn off the PJ before the AVR fixed it.

  • Projector not turning off with the rest of the devices. 1 year ago

    Thank you for suggesting the activity, it sparked me to try a few different things. I created an activity that would use the projector only, nothing else. That activity would turn on and off the projector as expected. (Although useless) Then I created a new activity with my projector and AVR only. Both would turn on properly, but projector would stay on when turning it off. Basically same problem I was facing. What I decided to try next is what matters. I went into the activity turn off sequence and changed the order to turn off the projector before the AVR, and that solved it. So basically, if the controller tries to turn off my AVR immediately followed by my projector it does not work, but the other way around works as expected. My best guess would be that the projector would not interpret the codes as being different by maybe more like a continuity, and does not make sense of the signal, then does nothing in that case ? I would be interested to compare the codes of the POWER_OFF (Yamaha RX-A2080) and POWER_OFF (Epson Powerlite Home Cinema 5040UB) to see if part of the sequences overlap, causing this kind of issue. Anyways, at least I have a work around the issue and I am content with the basic features for now. Thank you for your help.