If this is your first visit, be sure to check out the FAQ. You must register before you can post. Your first post will be checked for appropriate content
(SPAM) - please allow a bit of time for that. After that, you'll be able to post at will!

Comment

Enable detailed trace and log to file in the plugins configuration page

Perform the action you are doing - push the dim button only once (make sure?)

Then disable the detailed trace option and log to file

You will find the log file (JowiHue.log) in the logs subdirectory of your Homeseer installation directory. Send this file to jowihue dot ziggo dot nl
Also, please send me wich values can be send from this zwave dimmer? I need to know if they will match what the plugin is expecting. Alse let me know which JowiHue device (reference number of name) you have been testing?

Comment

Comment

I tried with a virtual device (manually created device), to see if i could replicate the issue.

But such a device doesn't write anything to the log-files. W.Vuyk investigated the logs, and found that HS3 sends commands twice to the plugin, which results in the extra command being sent. This might be a bug with the linked device setting in the current HS version.

I have attached a screenshot of the virtual device.

Comment

You could try to hold and press the same zwave button for on..... for several seconds. Does the virtual device update its time? If it does, holding the button a bit can trigger a linked device multiple times as well.

Also you could create an event to force the log line
Just create an event like

IF Virtual device had its value SET to on
THEN
Run (scriptcomand) execute the command &hs.writelog("test virtual", "On command received")

Comment

Then the conclusion would be that the linked structure is doubling the set action, as the plugin receives a command from HS3 and executes it, internally it is not a double logging (what I was expecting first). And the routine running this logging is only directly called by HS3....
Not really an issue as the command is executed and the end result stays the same?

Comment

It would seem that the problem was in the JowiHue plugin - since native devices doesn't send commands twice, when using linked devices.

BUT!!

I testet at bit further - when linking the Virtual device, to a jowihue device; no double commands are sent.

The conclusion? I don't know.....
When linking z-wave devices to virtual devices: Working
When linking virtual devices to Jowihue: Working
When linking z-wave devices to Jowihue: Working - BUT sends the commands twice.