Announcement

Collapse
No announcement yet.

Device Script Buttons

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

    #16
    I never used these commands myself so I must say I am not very familiar with them. I have just checked the API and as far as I can tell I have implemented them correctly.

    When I look at your screen shots I wonder if the way you are using the two effects negate each other? In the first you have a slow Colour Increment, but a high Transition Speed. in the second the reverse?

    Would it be worth trying to control only one of the two (transition or increment) to see if this makes a difference?

    This is quite difficult because I get not reply from the Chromoflex itself so I never know whether it is happy with the commands I send.
    Nicolai L

    Comment


      #17
      When I use my script to change the speed, I use this for high speed:
      CA 00 00 00 00 03 7E 11 01 01 66 99
      And this for low speed:
      CA 00 00 00 00 03 7E 11 FF 01 6D D9
      and leave the color increment as it is. (It will change the speed for all units.)
      03 are the amount of cmd bytes, 7E is the command for TRACK, FF is slowest and 01 is the status byte (always 01). 66 and 99 are the error checksum bytes.

      When I remove the color increments from the events, the On and OFF time is still the same.
      Peter

      http://ohh.pcgsm.nl

      Comment


        #18
        Do you think you can get transition speed to work?
        When your plugin is active, I can't use my script to change it because I get the error:
        Access to the port 'COMX' is denied.
        Peter

        http://ohh.pcgsm.nl

        Comment


          #19
          Yeah, should be possible. The line you gave me above will help. Just need to find sometime to get to work on this. Hopefully yhis weekend ...
          Nicolai L

          Comment


            #20
            Hi Peter

            Try the latest version in the updater. The script call for SetTransitionSpeed now generates the same string as what you have shown above so I am hoping this should now work.

            The format for SetTransitionSpeed is:

            &nhs.PluginFunction("izChromoflex", "", "SetColourIncrement", {"<GroupID>, <Speed>"})

            e.g. &nhs.PluginFunction("izChromoflex", "", "SetColourIncrement", {"0, 1"})

            <Speed> can be 1 to 255

            I have applied the same logic to SetColourIncrement so please test to see if this works as well.
            Nicolai L

            Comment


              #21
              Hi Nicolai,

              Transitionspeed is working ok now!

              For the colorincrement you have to set it for each color.
              It are the steps it will make at every increment.
              When set to 1, it takes 255 steps to go from 0 to 255
              when set to 10, it will step from 0 to 10, 20, 30 ....250, 255

              This is the code to set all colors to 1 increment per step
              ca 00 00 03 00 05 7E 08 01 01 01 01 18 45

              ca 00 00 03 set for module 3
              05, 5 bytes of code
              7E, write to registers
              08, start at register 8
              01 01 01 01 steps for RGBX ( X is not used)
              18 45 checksum bytes.
              Peter

              http://ohh.pcgsm.nl

              Comment


                #22
                Hi Nicolai,

                I know that the Chromoflex communication is one way, so you can't retrieve the status of a Chromoflex.
                But is it possible to save all the changes HS makes in an ini file?
                That way you can restore the Chromoflex values let say for every 15 minutes so Chromoflex status is the same as the devices in Homeseer.
                I did this with my script in HS2, so when I changes the Chromoflex with CF_edit, it allways restored the values from Homeseer within 15 minutes.
                Peter

                http://ohh.pcgsm.nl

                Comment


                  #23
                  Originally posted by peterpc View Post
                  Hi Nicolai,

                  Transitionspeed is working ok now!

                  For the colorincrement you have to set it for each color.
                  It are the steps it will make at every increment.
                  When set to 1, it takes 255 steps to go from 0 to 255
                  when set to 10, it will step from 0 to 10, 20, 30 ....250, 255

                  This is the code to set all colors to 1 increment per step
                  ca 00 00 03 00 05 7E 08 01 01 01 01 18 45

                  ca 00 00 03 set for module 3
                  05, 5 bytes of code
                  7E, write to registers
                  08, start at register 8
                  01 01 01 01 steps for RGBX ( X is not used)
                  18 45 checksum bytes.
                  Try 3.0.3.2 in the updater. Format is the same as before, e.g.

                  &nhs.PluginFunction("izChromoflex", "", "SetColourIncrement", {"3, 1"})

                  But output should now match your output above.
                  Nicolai L

                  Comment


                    #24
                    Originally posted by peterpc View Post
                    Hi Nicolai,

                    I know that the Chromoflex communication is one way, so you can't retrieve the status of a Chromoflex.
                    But is it possible to save all the changes HS makes in an ini file?
                    That way you can restore the Chromoflex values let say for every 15 minutes so Chromoflex status is the same as the devices in Homeseer.
                    I did this with my script in HS2, so when I changes the Chromoflex with CF_edit, it allways restored the values from Homeseer within 15 minutes.
                    I'm not sure I understand what you are after? How would the Chromoflex get out of sync with the values in HS if HS is the only device changing the settings?
                    Nicolai L

                    Comment


                      #25
                      HS is not the only device.
                      You also have local control.
                      Or for me at the moment, switch between HS2 and HS3.
                      Then the LED lights are not the same as the device levels in HS.
                      And when the plugin gets active, it does not send the HS device levels to the units.
                      Peter

                      http://ohh.pcgsm.nl

                      Comment


                        #26
                        Originally posted by NicolaiL View Post
                        Try 3.0.3.2 in the updater. Format is the same as before, e.g.

                        &nhs.PluginFunction("izChromoflex", "", "SetColourIncrement", {"3, 1"})

                        But output should now match your output above.
                        Setcolorincrement is working ok now.
                        But Transitionspeed is writing to register 7 now, and it must be 11.
                        Peter

                        http://ohh.pcgsm.nl

                        Comment


                          #27
                          Originally posted by peterpc View Post
                          Setcolorincrement is working ok now.
                          But Transitionspeed is writing to register 7 now, and it must be 11.
                          Will fix on Friday. Now travelling for the next couple of days.
                          Nicolai L

                          Comment


                            #28
                            Originally posted by peterpc View Post
                            HS is not the only device.
                            You also have local control.
                            Or for me at the moment, switch between HS2 and HS3.
                            Then the LED lights are not the same as the device levels in HS.
                            And when the plugin gets active, it does not send the HS device levels to the units.
                            I still don't quite see the point. If you use local control would you want HS3 to override that local control every 15 minutes? Doesn't that defeat the purpose of having local control?

                            However, I can see the point of having HS sends the last remembered values when you start the plugin. I don't know when I will have time to code this, but I'll add it to the list
                            Nicolai L

                            Comment


                              #29
                              Version 3.0.3.3 should be in the updater now which should fix the transition speed issue.

                              Hopefully all good now?
                              Nicolai L

                              Comment


                                #30
                                Originally posted by NicolaiL View Post
                                Version 3.0.3.3 should be in the updater now which should fix the transition speed issue.

                                Hopefully all good now?
                                Hi Nicolai,

                                It is working perfect now!
                                Thanks for all your work.
                                Peter

                                http://ohh.pcgsm.nl

                                Comment

                                Working...
                                X