Device Script Buttons

[NicolaiL]

Hi Peter

Attached the 2 extra copies for the additional COM ports.

As I mentioned in an earlier post I could possibly, sometime in the future, add the code to regularly resend the values. However, this is somewhat down my list of priorities at the moment so I'm not sure when I will get to it.

Regards
Nicolai

[peterpc]

Hi Nicolai,
Any thoughts about initializing the modules at startup of Homeseer to their last settings?
Or resend the last settings at a pre-defined interval?
Like when one of the modules does a powercycle, the leds will default to the settings in the module, not the settings in Homeseer.

When can you update the other 2 versions for the other com ports?

[peterpc]

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.

[NicolaiL]

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

Hopefully all good now?

[NicolaiL]

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

[NicolaiL]

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.

[peterpc]

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.

[peterpc]

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.

[NicolaiL]

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?

[NicolaiL]

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.

[peterpc]

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.

[peterpc]

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.

[NicolaiL]

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.

[NicolaiL]

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 ...

[peterpc]

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.