Announcement

Collapse
No announcement yet.

Dimming

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

  • Dimming

    This has probably already been discussed, although I can't find it.
    But I have noted Rob Mason mentioning that he is working on a "dimming issue".

    I'll just note my experience here anyway, in case I am doing something wrong.

    I have set up my HAI OmniPro II using Rob's brilliant plugin. Everything works, including Google Home integration. The only snag is dimming.

    So my experience is
    - if I increase a dimming slider to any higher percentage, the OmniPro responds by dimming one notch (1%) higher.
    - if I decrease the dimming slider to any lower percentage, the OmniPro responds by dimming one notch (1%) lower
    - of course this temporarily moves the OmniPro and Homeseer statuses out of sync, as Homeseer will report the dim value I input whereas the panel would just have the 1% increased or decreased value

    Is this the issue Rob mentioned he is working on in other threads?
    I just want to make sure I did not do something wrong on my side.

  • #2
    Yep - I need to look into this a little more...
    What OmniPro version are you running on the panel?
    What lighting technology are you using? UPB, Z-Wave, ALC, HLC?
    Finally, post the log file of the device you are controlling - that will tell me what is being sent/received.

    Thanks!
    Rob
    HS3Pro Running on a Raspberry Pi3
    64 Z-Wave Nodes, 168 Events, 280 Devices
    UPB modules via OMNI plugin/panel
    Plugins: Z-Wave, BLRF, OMNI, HSTouch, weatherXML, EasyTrigger
    HSTouch Clients: 3 Android, 1 Joggler

    Comment


    • #3
      Thanks for your response Rob!

      I'm on 4.0b - I assume that's the latest?

      So for lighting I'm using what used to be called ClickOn until Leviton acquired ClickOn somwhere in 2014 - I'm not sure what it is currently called under Leviton? I assume it is this?

      Regardless, if I use the native Snaplink app or the NQLink android app (both of which talk directly with the OmniPro Panel) then dimming works correctly - so I don't think it is an issue between the panel and the lighting system.

      I'll look for log files and post them here.

      On a different/related point, when I integrate with Google Home I see all devices end up registering as "Lights" even if the "Is Light" checkmark is not ticked in the HomeSeer interface. Based on the information in this post I want to infer this is because "dimmable" is always checked by default in your plug-in, and "dimmable" overrides "is light" (at least as far as Google Home is concerned).

      So as an example the downside of this is, let's say I have a bathroom with two lights and two heated towel rails. I want to keep the towel rails on in the winter, but if I tell Google Home to turn off all Lights in the Bathroom it treats all four of those as lights - ideally one would want Google Home to know which are lights and which are devices. I'm guessing that having control over both the "Dimmable" and "Is Light" unit properties will achieve that. Hope I'm making sense.

      Thanks!
      Christoff

      Comment


      • #4
        You can change the device types in HS to see if that will help - it wont hurt anything unless you have a lot of events tied to them.

        When you post the logs, it will tell me what type of devices you have. You might stop/restart the plugin, then control some devices, then post the log file.
        HS3Pro Running on a Raspberry Pi3
        64 Z-Wave Nodes, 168 Events, 280 Devices
        UPB modules via OMNI plugin/panel
        Plugins: Z-Wave, BLRF, OMNI, HSTouch, weatherXML, EasyTrigger
        HSTouch Clients: 3 Android, 1 Joggler

        Comment


        • #5
          Hi Rob

          To continue this post, on dimming, I have manipulated the dimming of one my my lights and captured the details in the attached log.

          I would really appreciate it if you could have a look. To recap, my issue is that dimming behaviour is erratic.
          For example, if I drag the Homeseer dimming slider to 50%, the unit would dim to 95%. If I drag it down to 50% again, it would dim to 91%.

          In the attached log please have a look at Unit 141 ("Lounge2 Corr").
          This is a dimmable light.

          Here is what I have done to produce the log.
          Note that you'll find all kinds of other automated activity in the log but for now we are only concerned with unit 141.

          2019-03-23 11:22:14 AM:
          1. Turned unit 141 ON using Homeseer. (this works fine)
          2. Turned unit 141 OFF using Homeseer. (this works fine)
          3. Turned unit 141 ON.
          2019-03-23 11:22:34 AM:
          4. Set unit 141 DIM to about 60% using the slider in Homeseer. Result: unit dimmed to 94% (instead of 60%)
          5. Set unit 141 DIM to about 20% using the slider in Homeseer. Result: unit dimmed to 91% (instead of 20%)
          6. Set unit 141 DIM to about 40% using the slider in Homeseer. Result: unit dimmed to 88% (instead of 40%)
          7. Set unit 141 to DIM to level 55% using the OmniPro panel directly. Result: unit dimmed to 55% as desired, and status in Homeseer updates correctly to 55%
          8. Set unit 141 to DIM to about 80% using the slider in Homeseer. Result: unit dimmed to 47% (instead of 80%)
          9. Turned unit off.

          I hope you can make sense of all this.
          Thank you so much!!
          Attached Files

          Comment


          • #6
            Rob, I think I partially figured this out but some work still to be done.

            So OmniPro has three commands that are at play here (I think these are related HLC but not sure)
            DIM which reduces light level a few notches
            BRIGHTEN which increases light level a few notches
            SET LEVEL (or something like that) which sets to a specific percentage

            Based on my limited understanding of the logs, the OMNI plugin sends a DIM 6 message if a move the slider to 60%
            ...so the OP2 interprets this as reducing the dimming level by 6% instead of setting it to 60%

            Not sure if that makes sense, hope it helps.

            Comment


            • #7
              Thanks - you have summarized my knowledge of OMNI dimming and frustration
              Leviton says to just always use LEVEL, but it has undesired effects, such as 'snapping' a device to 0% or 99% instead of ramping.
              I'm on another project at the moment, but would like to finish up my dimming changes for the next version.
              Stay tuned for future updates.
              HS3Pro Running on a Raspberry Pi3
              64 Z-Wave Nodes, 168 Events, 280 Devices
              UPB modules via OMNI plugin/panel
              Plugins: Z-Wave, BLRF, OMNI, HSTouch, weatherXML, EasyTrigger
              HSTouch Clients: 3 Android, 1 Joggler

              Comment


              • #8
                Thanks Rob, let me know if I can run some more tests on this side. If you have like a beta version that uses LEVEL I'd be happy to give it a go and experiment and report back to you. If it would help.

                Comment


                • #9
                  Just updated to OMNI 3.0.2.20
                  The dimming does not seem to be addressed in this update. ON/OFF commands slam the light to 0% or 100%. Setting any other level works fine using a slider in the HS interface.
                  Trying to slide to 100% slams the light on, sliding to 0% ramps is down but all the way to off.

                  Just updating my observations.

                  Comment


                  • #10
                    Still messing around with the dimming. Posting a log below. The log read from the bottom upwards (obviously) and shows changes to dimmable light unit no 141.

                    First, I turned the light on from an external client (not Homeseer) and dimmed and undimmed it from the external client, leaving the light at 100%.
                    After this I issued two dimming commands through Homeseer:
                    1. First I asked Homeseer to dim the light to 60%. Homeseer through Rob's plugin sent a DIM 6 command which OP2 interpreted as "dim the light by 6 notches" so the dimming went down to 94% instead of to 60%.
                    2. Second I asked Homseer to dim the light to 20% -> DIM 2 command received by OP2 -> dimming went to 92% instead of 20%.

                    Rob I think you said you tried this before(?) but it was before my time...
                    So my interpretation is the Plugin should issue a SET LEVEL command (not a DIM command) and the SET LEVEL should be an integer between 0 and 100. You may need to multiply the number current DIM parameter being sent by 10
                    - so what I mean is instead of sending DIM 6 when I move the HS3 slider to 60%, you need to send SET LEVEL 60.

                    Sorry if I'm being patronising, I'm guessing you already know this...just sharing my limited understanding here.

                    If you have a test build you want me to experiment with feel free to let me know! Would be more than happy to try and help you figure this out.

                    Here's the log


                    2019-06-05 09:43:32 PM [2] [--> Unit 141 changed status. Updating Homeseer...]
                    2019-06-05 09:43:32 PM [2] [-->Unsolicited: Unit=[141] status=[0]/[OFF] type=[2] / []]
                    2019-06-05 09:43:32 PM [2] [-->UNIT: desc=[] number=[141] name=[Lounge2 Corr]]
                    2019-06-05 09:43:32 PM [2] [---->Unit]
                    2019-06-05 09:43:32 PM [2] [UNSOLICITED: ExtendedStatus]
                    2019-06-05 09:43:32 PM [2] [Unit_Off: unitId=141 ]
                    2019-06-05 09:43:32 PM [2] [SetIOMulti: CC.Ref=[133] CC.ControlValue=[0]]
                    2019-06-05 09:43:26 PM [2] [--> Unit 141 changed status. Updating Homeseer...]
                    2019-06-05 09:43:26 PM [2] [-->Unsolicited: Unit=[141] status=[192]/[LEVEL 92%] type=[2] / []] light went to 92% after the DIM 2 command below was sent
                    2019-06-05 09:43:26 PM [2] [-->UNIT: desc=[] number=[141] name=[Lounge2 Corr]]
                    2019-06-05 09:43:26 PM [2] [---->Unit]
                    2019-06-05 09:43:26 PM [2] [UNSOLICITED: ExtendedStatus]
                    2019-06-05 09:43:26 PM [2] [--> Unit 141 changed status. Updating Homeseer...]
                    2019-06-05 09:43:26 PM [2] [-->Unsolicited: Unit=[141] status=[18]/[DIM 2] type=[2] / []] DIM 2 command (instead of SET LEVEL 20..?)
                    2019-06-05 09:43:26 PM [2] [-->UNIT: desc=[] number=[141] name=[Lounge2 Corr]]
                    2019-06-05 09:43:26 PM [2] [---->Unit]
                    2019-06-05 09:43:26 PM [2] [UNSOLICITED: ExtendedStatus]
                    2019-06-05 09:43:25 PM [2] [--> unitType=2 status=94 statustext=LEVEL 94%]
                    2019-06-05 09:43:25 PM [2] [Unit_Dim: unitId=141 dimVal=19]
                    2019-06-05 09:43:25 PM [2] [SetIOMulti: CC.Ref=[133] CC.ControlValue=[19]]
                    2019-06-05 09:43:20 PM [2] [--> Unit 141 changed status. Updating Homeseer...]
                    2019-06-05 09:43:20 PM [2] [-->Unsolicited: Unit=[141] status=[194]/[LEVEL 94%] type=[2] / []] light went to 94% after the DIM 6 command below was sent
                    2019-06-05 09:43:20 PM [2] [-->UNIT: desc=[] number=[141] name=[Lounge2 Corr]]
                    2019-06-05 09:43:20 PM [2] [---->Unit]
                    2019-06-05 09:43:20 PM [2] [UNSOLICITED: ExtendedStatus]
                    2019-06-05 09:43:18 PM [2] [--> Unit 141 changed status. Updating Homeseer...]
                    2019-06-05 09:43:18 PM [2] [-->Unsolicited: Unit=[141] status=[22]/[DIM 6] type=[2] / []] so here a DIM 6 command arrives at OP2 (rather than SET LEVEL 60?)
                    2019-06-05 09:43:18 PM [2] [-->UNIT: desc=[] number=[141] name=[Lounge2 Corr]]
                    2019-06-05 09:43:18 PM [2] [---->Unit]
                    2019-06-05 09:43:18 PM [2] [UNSOLICITED: ExtendedStatus]
                    2019-06-05 09:43:18 PM [2] [--> unitType=2 status=255 statustext=ON]
                    2019-06-05 09:43:18 PM [2] [Unit_Dim: unitId=141 dimVal=55]
                    2019-06-05 09:43:18 PM [2] [SetIOMulti: CC.Ref=[133] CC.ControlValue=[55]]
                    2019-06-05 09:43:13 PM [2] [--> Unit 141 changed status. Updating Homeseer...]
                    2019-06-05 09:43:12 PM [2] [-->Unsolicited: Unit=[141] status=[1]/[ON] type=[2] / []]
                    2019-06-05 09:43:12 PM [2] [-->UNIT: desc=[] number=[141] name=[Lounge2 Corr]]
                    2019-06-05 09:43:12 PM [2] [---->Unit]
                    2019-06-05 09:43:12 PM [2] [UNSOLICITED: ExtendedStatus]
                    2019-06-05 09:43:12 PM [2] [Unit_On: unitId=141 ]




                    Comment

                    Working...
                    X