Announcement

Collapse
No announcement yet.

RGB Feature control

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    RGB Feature control

    I have been trying to control a Hue light via the RGB feature via the plugin. It appears that you cannot send the command to set the RGB to a hex string via the control ascii interface and the only way I have been able to send a Hex string and control a hue light is via the JSON interface using the controldevicebyindex JSON API. It works, but with a side effect that when you change the color via this API then it will also reset the dimming level of the light. In my research I ran across your documentation regarding setting the RGB and that you have a default value of "NOTHING" in your plug in that will reset the brightness / dimming level to what is given for the XY coordinates of the light mapping ....your example shows a way to override this from a script.. there is a way to override this if you are using the JSON interface to HomeSeer?

    I cannot see where calling into the system via the JSON that this can be done...

    Is there anyway via a JSON or direct ascii control that we can talk to the HS system and have the JowiHue plug in and set the color and not have it reset the brightness level of the light?

    #2
    The plugin gets a device change of HS, but does not know where the request was triggered, Device control, device trigger, Json or Ascii, they all come in at the same point. So the plugin cannot distinguish between the different methods through the call.

    A user can change this behavior on general level in the settings of the plugin BTW, by enabling the option "Skip changing dim value when using color voice commands", which in fact is active for all color commands. not only voice commands (*note to self: remove the voice command part from this option)

    Wim
    -- Wim

    Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

    1210 devices/features ---- 392 events ----- 40 scripts

    Comment


      #3
      Thanks Wim, That setting was not set on my HS4 system, so I can try that again.

      I have tried to send the hex color string via the ascii control interface and have never gotten it to work seeing it the way.. I checked the reference ID was correct and I've tried it both with the "#" prefix on the hex string and without it... would prefer the ascii control over using the JSON if I could get it to work. Do you know of any reason the ascii control for this would not work?

      Comment


        #4
        No, I am not using anything of the ascii or Json interface here myself. The plugin only checks on the control string or the colorpicker controltype, nothing else. These are send by HS. How they interpret your ascii string is not known to me..
        -- Wim

        Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

        1210 devices/features ---- 392 events ----- 40 scripts

        Comment


          #5
          Thanks Wim, I tried setting that skip changing dim value option... I restarted HomeSeer after I made that change to make sure that everything was right... and still when I send the hex string via the JSON api the light gets dimmed down when the color changes. So I will abandon the idea of using the color picker for now and use a different approach.

          Comment


            #6
            Hello Guys,

            I have posted a follow up to this https://forums.homeseer.com/forum/hs...46#post1522746

            Comment

            Working...
            X