Velbus Domogik module

thanks, did you try a dimmer?

in the log i only see on/off messages

The dimmer neither the shutters work.
When the dimmer button is pushed a rinor error message window is displayed… **RINOR : ‘No data or timeout on getting command response’ (/rinor/api/command/velbus/08/)
**

Output velbus.log tail…
2012-02-06 14:02:32,646 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘251’)])
2012-02-06 14:02:32,658 domogik-velbus DEBUG normal send
2012-02-06 14:02:32,678 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=251
}

2012-02-06 14:02:40,831 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘33’)])
2012-02-06 14:02:40,831 domogik-velbus DEBUG normal send
2012-02-06 14:02:40,851 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=33
}

2012-02-06 14:02:42,224 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘None’)])
2012-02-06 14:02:42,224 domogik-velbus DEBUG normal send
2012-02-06 14:02:42,244 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=None
}

2012-02-06 14:03:09,875 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘None’)])
2012-02-06 14:03:09,875 domogik-velbus DEBUG normal send
2012-02-06 14:03:09,903 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=None
}

2012-02-06 14:04:20,747 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘255’), (‘device’, ‘07-1’)])
2012-02-06 14:04:20,767 domogik-velbus DEBUG normal send
2012-02-06 14:04:20,775 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=255
device=07-1
}

2012-02-06 14:04:20,791 domogik-velbus DEBUG set relay on
2012-02-06 14:04:20,807 domogik-velbus INFO write packet
2012-02-06 14:04:20,811 domogik-velbus INFO START SENDING PACKET 0x7
2012-02-06 14:04:20,811 domogik-velbus DEBUG 8
2012-02-06 14:04:21,587 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘0’), (‘device’, ‘07-1’)])
2012-02-06 14:04:21,599 domogik-velbus DEBUG normal send
2012-02-06 14:04:21,607 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=0
device=07-1
}

2012-02-06 14:04:21,607 domogik-velbus DEBUG set relay off
2012-02-06 14:04:21,607 domogik-velbus INFO write packet
2012-02-06 14:04:21,631 domogik-velbus INFO START SENDING PACKET 0x7
2012-02-06 14:04:21,631 domogik-velbus DEBUG 8
2012-02-06 14:04:26,554 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘255’), (‘device’, ‘04-3’)])
2012-02-06 14:04:26,562 domogik-velbus DEBUG normal send
2012-02-06 14:04:26,590 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=255
device=04-3
}

2012-02-06 14:04:26,590 domogik-velbus DEBUG set relay on
2012-02-06 14:04:26,638 domogik-velbus INFO write packet
2012-02-06 14:04:26,638 domogik-velbus INFO START SENDING PACKET 0x4
2012-02-06 14:04:26,654 domogik-velbus DEBUG 8
2012-02-06 14:04:29,180 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘0’), (‘device’, ‘04-3’)])
2012-02-06 14:04:29,192 domogik-velbus DEBUG normal send
2012-02-06 14:04:29,192 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=0
device=04-3
}

2012-02-06 14:04:29,224 domogik-velbus DEBUG set relay off
2012-02-06 14:04:29,224 domogik-velbus INFO write packet
2012-02-06 14:04:29,236 domogik-velbus INFO START SENDING PACKET 0x4
2012-02-06 14:04:29,236 domogik-velbus DEBUG 8
2012-02-06 14:05:10,863 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:10,875 domogik-velbus DEBUG normal send
2012-02-06 14:05:10,899 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:12,480 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘down’), (‘device’, ‘06’)])
2012-02-06 14:05:12,492 domogik-velbus DEBUG normal send
2012-02-06 14:05:12,508 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=down
device=06
}

2012-02-06 14:05:13,921 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:13,933 domogik-velbus DEBUG normal send
2012-02-06 14:05:13,957 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:14,949 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘down’), (‘device’, ‘06’)])
2012-02-06 14:05:14,953 domogik-velbus DEBUG normal send
2012-02-06 14:05:14,957 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=down
device=06
}

2012-02-06 14:05:15,858 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:15,858 domogik-velbus DEBUG normal send
2012-02-06 14:05:15,866 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:17,047 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:17,059 domogik-velbus DEBUG normal send
2012-02-06 14:05:17,067 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:18,271 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:18,283 domogik-velbus DEBUG normal send
2012-02-06 14:05:18,303 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:19,792 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘down’), (‘device’, ‘06’)])
2012-02-06 14:05:19,800 domogik-velbus DEBUG normal send
2012-02-06 14:05:19,832 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=down
device=06
}

2012-02-06 14:05:23,542 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:23,550 domogik-velbus DEBUG normal send
2012-02-06 14:05:23,570 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:24,567 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:24,575 domogik-velbus DEBUG normal send
2012-02-06 14:05:24,619 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:25,227 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:25,239 domogik-velbus DEBUG normal send
2012-02-06 14:05:25,263 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:27,104 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘down’), (‘device’, ‘06’)])
2012-02-06 14:05:27,108 domogik-velbus DEBUG normal send
2012-02-06 14:05:27,112 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=down
device=06
}

2012-02-06 14:05:27,953 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:27,953 domogik-velbus DEBUG normal send
2012-02-06 14:05:27,981 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:33,832 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:33,832 domogik-velbus DEBUG normal send
2012-02-06 14:05:33,856 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:35,005 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘down’), (‘device’, ‘06’)])
2012-02-06 14:05:35,005 domogik-velbus DEBUG normal send
2012-02-06 14:05:35,017 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=down
device=06
}

2012-02-06 14:06:10,913 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:06:10,925 domogik-velbus DEBUG normal send
2012-02-06 14:06:10,937 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

the shutter is expected, but the dimmer should work …
this will be a lot harder to debug remotely …

can, you give me the output of velbus.log when a dimmer is used with normal pushbuttons?
because then i can see what messages are transmitted

The dawndusk plugin is nice too. Can it be used together with the velbus plugin to turn on a light in the kitchen when the dusk value is triggered and to turn off the light when the dawn value is triggered?

If possible, how to configure the parameters :

schema : the schema to use to send the command (ie x10.basic)
addname : the name of the adress field (ie device)
add : the adresse of the device (ie A1)
command : the name of the command field (ie command)
dawn : Value of command when dawn event occurs (ie on)
dusk : Value of command when dusk event occurs (ie off)

What should I add to the schema parameter, what to the addname parameter and what to the add parameter?

Dimmer test as requested…

Errors on web page like… RINOR : ‘No data or timeout on getting command response’ (/rinor/api/command/velbus/08/)

Velbus.log tail…
2012-02-06 14:23:09,798 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘255’)])
2012-02-06 14:23:09,798 domogik-velbus DEBUG normal send
2012-02-06 14:23:09,814 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=255
}

2012-02-06 14:23:38,394 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘None’)])
2012-02-06 14:23:38,418 domogik-velbus DEBUG normal send
2012-02-06 14:23:38,422 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=None
}

ah, but i need the output if you dim with the velbus pushbuttons, so don’t use domogic for controlling, just start it and have the tail running, so i see what messages are transmitted on the bus :slight_smile:

after some code reading i think i found a bug :slight_smile:
just committed a fix for it

hg pull
hg update
hg merge

and restart and try again

This does not look good anymore… and velbus plugin is not working anymore

adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
(run ‘hg update’ to get a working copy)
root@domogik:/home/domogik/domogik# hg update
*** failed to import extension alias: No module named alias
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
root@domogik:/home/domogik/domogik# hg merge
*** failed to import extension alias: No module named alias
abort: branch ‘default’ has one head - please merge with an explicit rev
(run ‘hg heads’ to see all heads)
root@domogik:/home/domogik/domogik# /etc/init.d/domogik restart

  • Stopping Plugins… Done.
  • Stopping XPL… Done.
  • Stopping Manager… Done.
  • Starting XPL… Done.
  • Starting Manager (with -d -r -p -E)…
    [INFO] Check if dbmgr is running.
    [INFO] Check if rest is running.
    [INFO] Start dbmgr on domogik
    [OK] Component dbmgr started with pid 928
    [INFO] Start rest on domogik
    [INFO] Check non-system plugins to start at manager startup.
    [INFO] Start yweather on domogik
    [INFO] Start dawndusk on domogik
    [INFO] Start foscam on domogik
    [INFO] Start velbus on domogik
    [OK] Component rest started with pid 943
    ** [ERROR] Component yweather failed to start. Please look in this component log files
    [ERROR] Component foscam failed to start. Please look in this component log files
    [ERROR] Component velbus failed to start. Please look in this component log files**
    ^C
    root@domogik:/home/domogik/domogik# tail -f -n 300 /var/log/domogik/velbus.log 2012-02-06 14:05:27,112 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
    {
    hop=1
    source=domogik-velbus.domogik
    target=*
    }
    shutter.device
    {
    command=down
    device=06
    }

2012-02-06 14:05:27,953 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:27,953 domogik-velbus DEBUG normal send
2012-02-06 14:05:27,981 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:33,832 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:05:33,832 domogik-velbus DEBUG normal send
2012-02-06 14:05:33,856 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:05:35,005 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘down’), (‘device’, ‘06’)])
2012-02-06 14:05:35,005 domogik-velbus DEBUG normal send
2012-02-06 14:05:35,017 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=down
device=06
}

2012-02-06 14:06:10,913 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:06:10,925 domogik-velbus DEBUG normal send
2012-02-06 14:06:10,937 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:10:10,656 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘0’), (‘device’, ‘07-2’)])
2012-02-06 14:10:10,660 domogik-velbus DEBUG normal send
2012-02-06 14:10:10,664 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=0
device=07-2
}

2012-02-06 14:10:10,684 domogik-velbus DEBUG set relay off
2012-02-06 14:10:10,684 domogik-velbus INFO write packet
2012-02-06 14:10:10,724 domogik-velbus INFO START SENDING PACKET 0x7
2012-02-06 14:10:10,724 domogik-velbus DEBUG 8
2012-02-06 14:10:16,015 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘255’), (‘device’, ‘07-2’)])
2012-02-06 14:10:16,027 domogik-velbus DEBUG normal send
2012-02-06 14:10:16,055 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=255
device=07-2
}

2012-02-06 14:10:16,087 domogik-velbus DEBUG set relay on
2012-02-06 14:10:16,087 domogik-velbus INFO write packet
2012-02-06 14:10:16,111 domogik-velbus INFO START SENDING PACKET 0x7
2012-02-06 14:10:16,111 domogik-velbus DEBUG 8
2012-02-06 14:10:18,532 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘0’), (‘device’, ‘07-2’)])
2012-02-06 14:10:18,540 domogik-velbus DEBUG normal send
2012-02-06 14:10:18,552 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=0
device=07-2
}

2012-02-06 14:10:18,552 domogik-velbus DEBUG set relay off
2012-02-06 14:10:18,572 domogik-velbus INFO write packet
2012-02-06 14:10:18,572 domogik-velbus INFO START SENDING PACKET 0x7
2012-02-06 14:10:18,572 domogik-velbus DEBUG 8
2012-02-06 14:10:23,363 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:10:23,367 domogik-velbus DEBUG normal send
2012-02-06 14:10:23,371 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:10:27,989 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘down’), (‘device’, ‘06’)])
2012-02-06 14:10:27,989 domogik-velbus DEBUG normal send
2012-02-06 14:10:28,017 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=down
device=06
}

2012-02-06 14:10:29,826 domogik-velbus INFO schema:shutter.device, data:OrderedDict((‘command’, ‘up’), (‘device’, ‘06’)])
2012-02-06 14:10:29,838 domogik-velbus DEBUG normal send
2012-02-06 14:10:29,874 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
shutter.device
{
command=up
device=06
}

2012-02-06 14:23:09,798 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘255’)])
2012-02-06 14:23:09,798 domogik-velbus DEBUG normal send
2012-02-06 14:23:09,814 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=255
}

2012-02-06 14:23:38,394 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘None’)])
2012-02-06 14:23:38,418 domogik-velbus DEBUG normal send
2012-02-06 14:23:38,422 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=None
}

2012-02-06 14:41:35,527 domogik-velbus INFO Someone asked to stop velbus, doing.
2012-02-06 14:41:35,543 domogik-velbus DEBUG normal send
2012-02-06 14:41:35,647 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
domogik.system
{
host=domogik
command=stop
plugin=velbus
}

2012-02-06 14:41:35,647 domogik-velbus DEBUG force_leave called
2012-02-06 14:41:35,647 domogik-velbus DEBUG Try to stop timer <domogik.xpl.common.xplconnector.XplTimer instance at 0xa21eeac>
2012-02-06 14:41:35,647 domogik-velbus DEBUG Timer : stop, try to join() internal thread
2012-02-06 14:41:35,651 domogik-velbus INFO self._should_stop set, leave.
2012-02-06 14:41:35,699 domogik-velbus DEBUG Timer : stop, internal thread joined, unregister it
2012-02-06 14:41:35,699 domogik-velbus DEBUG ASk for timer unregister : <__InternalTimer(internal-timer, stopped -1249768592)>
2012-02-06 14:41:35,699 domogik-velbus DEBUG Timer stopped <domogik.xpl.common.xplconnector.XplTimer instance at 0xa21eeac>
2012-02-06 14:41:35,699 domogik-velbus DEBUG Calling stop additionnal method : leave
2012-02-06 14:41:35,739 domogik-velbus DEBUG xPL thread stopped
2012-02-06 14:41:35,739 domogik-velbus DEBUG Try to stop thread <Thread(thread-monitor, stopped -1224590480)>
2012-02-06 14:41:35,739 domogik-velbus DEBUG Thread stopped <Thread(thread-monitor, stopped -1224590480)>
2012-02-06 14:41:35,739 domogik-velbus DEBUG Try to stop thread <Thread(velbus-process-reader, stopped -1241375888)>
2012-02-06 14:41:35,755 domogik-velbus DEBUG Thread stopped <Thread(velbus-process-reader, stopped -1241375888)>
2012-02-06 14:41:35,755 domogik-velbus DEBUG Try to stop thread <__InternalTimer(internal-timer, stopped -1249768592)>
2012-02-06 14:41:35,755 domogik-velbus DEBUG Thread stopped <__InternalTimer(internal-timer, stopped -1249768592)>
2012-02-06 14:41:35,755 domogik-velbus DEBUG Try to stop thread <Thread(Manager-new-message-cb, started -1258161296)>
2012-02-06 14:41:35,779 domogik-velbus DEBUG Thread stopped <Thread(Manager-new-message-cb, started -1258161296)>
2012-02-06 14:41:35,779 domogik-velbus INFO The thread write_packets_process was not registered, killing it
2012-02-06 14:42:42,133 domogik-velbus INFO Daemonize plugin velbus
2012-02-06 14:42:42,185 domogik-velbus DEBUG watcher fork
2012-02-06 14:42:42,189 domogik-velbus INFO ----------------------------------
2012-02-06 14:42:42,233 domogik-velbus INFO Starting plugin ‘velbus’ (new manager instance)
2012-02-06 14:42:42,297 domogik-velbus DEBUG Write pid file for pid ‘1046’ in file ‘/var/run/domogik/velbus.pid’
2012-02-06 14:42:42,305 domogik-velbus DEBUG xPL plugin velbus socket bound to 192.168.1.80, port 46323
2012-02-06 14:42:42,329 domogik-velbus DEBUG xPL thread started for velbus
2012-02-06 14:42:42,329 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-cmnd’, ‘schema’: ‘domogik.system’}
2012-02-06 14:42:42,369 domogik-velbus DEBUG end single xpl plugin
2012-02-06 14:42:42,369 domogik-velbus DEBUG Init config query instance
2012-02-06 14:42:42,397 domogik-velbus DEBUG QC : ask > h=domogik, t=velbus, k=use-socket
2012-02-06 14:42:42,409 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-stat’, ‘technology’: ‘velbus’, ‘hostname’: ‘domogik’, ‘schema’: ‘domogik.config’}
2012-02-06 14:42:42,409 domogik-velbus DEBUG normal send
2012-02-06 14:42:42,429 domogik-velbus DEBUG xPL Message sent by thread MainThread : xpl-cmnd
{
hop=1
source=domogik-velbus.domogik
target=*
}
domogik.config
{
technology=velbus
hostname=domogik
key=use-socket
}

2012-02-06 14:42:42,565 domogik-velbus DEBUG QC : res > h=domogik, t=velbus, k=use-socket, v=False
2012-02-06 14:42:42,573 domogik-velbus DEBUG Config value received : use-socket : False
2012-02-06 14:42:42,617 domogik-velbus DEBUG QC : ask > h=domogik, t=velbus, k=use-socket
2012-02-06 14:42:42,617 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-stat’, ‘technology’: ‘velbus’, ‘hostname’: ‘domogik’, ‘schema’: ‘domogik.config’}
2012-02-06 14:42:42,617 domogik-velbus DEBUG normal send
2012-02-06 14:42:42,629 domogik-velbus DEBUG xPL Message sent by thread MainThread : xpl-cmnd
{
hop=1
source=domogik-velbus.domogik
target=*
}
domogik.config
{
technology=velbus
hostname=domogik
key=use-socket
}

2012-02-06 14:42:42,765 domogik-velbus DEBUG QC : res > h=domogik, t=velbus, k=use-socket, v=None
2012-02-06 14:42:42,765 domogik-velbus DEBUG Config value received : use-socket : None
2012-02-06 14:42:42,785 domogik-velbus DEBUG QC : ask > h=domogik, t=velbus, k=device
2012-02-06 14:42:42,785 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-stat’, ‘technology’: ‘velbus’, ‘hostname’: ‘domogik’, ‘schema’: ‘domogik.config’}
2012-02-06 14:42:42,785 domogik-velbus DEBUG normal send
2012-02-06 14:42:42,801 domogik-velbus DEBUG xPL Message sent by thread MainThread : xpl-cmnd
{
hop=1
source=domogik-velbus.domogik
target=*
}
domogik.config
{
technology=velbus
hostname=domogik
key=device
}

2012-02-06 14:42:42,929 domogik-velbus DEBUG QC : res > h=domogik, t=velbus, k=device, v=/dev/ttyACM0
2012-02-06 14:42:42,929 domogik-velbus DEBUG Config value received : device : /dev/ttyACM0
2012-02-06 14:42:42,953 domogik-velbus ERROR A socket device is in the form of :, exitting
2012-02-06 14:42:42,953 domogik-velbus DEBUG force_leave called
2012-02-06 14:42:42,953 domogik-velbus DEBUG Calling stop additionnal method : leave
2012-02-06 14:42:42,961 domogik-velbus DEBUG xPL thread stopped
2012-02-06 14:42:42,961 domogik-velbus DEBUG Try to stop thread <Thread(thread-monitor, started -1224209552)>
2012-02-06 14:42:44,934 domogik-velbus INFO self._should_stop set, leave.
2012-02-06 14:42:44,934 domogik-velbus DEBUG Thread stopped <Thread(thread-monitor, stopped -1224209552)>
2012-02-06 14:42:44,934 domogik-velbus DEBUG Try to stop thread <Thread(Manager-new-message-cb, stopped -1232602256)>
2012-02-06 14:42:44,938 domogik-velbus DEBUG Thread stopped <Thread(Manager-new-message-cb, stopped -1232602256)>
2012-02-06 14:42:45,034 domogik-velbus DEBUG del Single xpl plugin
2012-02-06 14:42:45,034 domogik-velbus DEBUG force_leave called

Solved it…

  1. /etc/init.d/domogik stop
  2. /etc/init.d/domogik start

Dimmer test need more time, does not work…

Velbus.log tail output…
2012-02-06 14:54:43,646 domogik-velbus INFO Daemonize plugin velbus
2012-02-06 14:54:43,674 domogik-velbus DEBUG watcher fork
2012-02-06 14:54:43,670 domogik-velbus INFO ----------------------------------
2012-02-06 14:54:43,694 domogik-velbus INFO Starting plugin ‘velbus’ (new manager instance)
2012-02-06 14:54:43,710 domogik-velbus DEBUG Write pid file for pid ‘1902’ in file ‘/var/run/domogik/velbus.pid’
2012-02-06 14:54:43,718 domogik-velbus DEBUG xPL plugin velbus socket bound to 192.168.1.80, port 56619
2012-02-06 14:54:43,738 domogik-velbus DEBUG xPL thread started for velbus
2012-02-06 14:54:43,738 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-cmnd’, ‘schema’: ‘domogik.system’}
2012-02-06 14:54:43,746 domogik-velbus DEBUG end single xpl plugin
2012-02-06 14:54:43,750 domogik-velbus DEBUG Init config query instance
2012-02-06 14:54:43,790 domogik-velbus DEBUG QC : ask > h=domogik, t=velbus, k=use-socket
2012-02-06 14:54:43,806 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-stat’, ‘technology’: ‘velbus’, ‘hostname’: ‘domogik’, ‘schema’: ‘domogik.config’}
2012-02-06 14:54:43,814 domogik-velbus DEBUG normal send
2012-02-06 14:54:43,818 domogik-velbus DEBUG xPL Message sent by thread MainThread : xpl-cmnd
{
hop=1
source=domogik-velbus.domogik
target=*
}
domogik.config
{
technology=velbus
hostname=domogik
key=use-socket
}

2012-02-06 14:54:43,923 domogik-velbus DEBUG QC : res > h=domogik, t=velbus, k=use-socket, v=False
2012-02-06 14:54:43,927 domogik-velbus DEBUG Config value received : use-socket : False
2012-02-06 14:54:43,931 domogik-velbus DEBUG QC : res > h=domogik, t=velbus, k=use-socket, v=False
2012-02-06 14:54:43,939 domogik-velbus DEBUG Config value received : use-socket : False
2012-02-06 14:54:43,967 domogik-velbus DEBUG QC : ask > h=domogik, t=velbus, k=use-socket
2012-02-06 14:54:43,967 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-stat’, ‘technology’: ‘velbus’, ‘hostname’: ‘domogik’, ‘schema’: ‘domogik.config’}
2012-02-06 14:54:43,967 domogik-velbus DEBUG normal send
2012-02-06 14:54:43,979 domogik-velbus DEBUG xPL Message sent by thread MainThread : xpl-cmnd
{
hop=1
source=domogik-velbus.domogik
target=*
}
domogik.config
{
technology=velbus
hostname=domogik
key=use-socket
}

2012-02-06 14:54:44,083 domogik-velbus DEBUG QC : res > h=domogik, t=velbus, k=use-socket, v=False
2012-02-06 14:54:44,087 domogik-velbus DEBUG Config value received : use-socket : False
2012-02-06 14:54:44,131 domogik-velbus DEBUG QC : ask > h=domogik, t=velbus, k=device
2012-02-06 14:54:44,131 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-stat’, ‘technology’: ‘velbus’, ‘hostname’: ‘domogik’, ‘schema’: ‘domogik.config’}
2012-02-06 14:54:44,131 domogik-velbus DEBUG normal send
2012-02-06 14:54:44,151 domogik-velbus DEBUG xPL Message sent by thread MainThread : xpl-cmnd
{
hop=1
source=domogik-velbus.domogik
target=*
}
domogik.config
{
technology=velbus
hostname=domogik
key=device
}

2012-02-06 14:54:44,219 domogik-velbus DEBUG QC : res > h=domogik, t=velbus, k=device, v=/dev/ttyACM0
2012-02-06 14:54:44,219 domogik-velbus DEBUG Config value received : device : /dev/ttyACM0
2012-02-06 14:54:44,295 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-cmnd’, ‘schema’: ‘lighting.basic’}
2012-02-06 14:54:44,295 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-cmnd’, ‘schema’: ‘shutter.basic’}
2012-02-06 14:54:44,295 domogik-velbus INFO Try to open VELBUS: /dev/ttyACM0
2012-02-06 14:54:44,303 domogik-velbus INFO write deamon
2012-02-06 14:54:44,303 domogik-velbus INFO VELBUS opened
2012-02-06 14:54:44,311 domogik-velbus INFO Start listening VELBUS
2012-02-06 14:54:44,311 domogik-velbus DEBUG Try to enable Heartbeat
2012-02-06 14:54:44,391 domogik-velbus DEBUG New timer registered : <domogik.xpl.common.xplconnector.XplTimer instance at 0xa34676c>
2012-02-06 14:54:44,391 domogik-velbus DEBUG New timer created : <domogik.xpl.common.xplconnector.XplTimer instance at 0xa34676c>
2012-02-06 14:54:44,407 domogik-velbus DEBUG New listener, filter : {‘xpltype’: ‘xpl-cmnd’, ‘schema’: ‘hbeat.request’}
2012-02-06 14:54:44,407 domogik-velbus DEBUG Heartbeat enabled
2012-02-06 14:55:34,299 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘255’)])
2012-02-06 14:55:34,299 domogik-velbus DEBUG normal send
2012-02-06 14:55:34,319 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=255
}

2012-02-06 14:55:42,595 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08’), (‘level’, ‘None’)])
2012-02-06 14:55:42,611 domogik-velbus DEBUG normal send
2012-02-06 14:55:42,628 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08
level=None
}

2012-02-06 14:55:43,964 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘255’), (‘device’, ‘04-2’)])
2012-02-06 14:55:43,992 domogik-velbus DEBUG normal send
2012-02-06 14:55:43,996 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=255
device=04-2
}

2012-02-06 14:55:44,000 domogik-velbus DEBUG set relay on
2012-02-06 14:55:44,000 domogik-velbus INFO write packet
2012-02-06 14:55:44,044 domogik-velbus INFO START SENDING PACKET 0x4
2012-02-06 14:55:44,044 domogik-velbus DEBUG 8
2012-02-06 14:55:50,180 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘level’, ‘0’), (‘device’, ‘04-2’)])
2012-02-06 14:55:50,180 domogik-velbus DEBUG normal send
2012-02-06 14:55:50,216 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
level=0
device=04-2
}

2012-02-06 14:55:50,216 domogik-velbus DEBUG set relay off
2012-02-06 14:55:50,216 domogik-velbus INFO write packet
2012-02-06 14:55:50,220 domogik-velbus INFO START SENDING PACKET 0x4
2012-02-06 14:55:50,220 domogik-velbus DEBUG 8

device=08 level=None

ok, make sure to add a channel number to the device config, if there is only one channel always add -1 otherwise the packet building will fail.

and level=None is weird …

Updated device parameter but still error…

2012-02-06 15:06:07,823 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘255’)])
2012-02-06 15:06:07,823 domogik-velbus DEBUG normal send
2012-02-06 15:06:07,843 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=255
}

2012-02-06 15:06:07,863 domogik-velbus DEBUG set relay on
2012-02-06 15:06:07,863 domogik-velbus INFO write packet
2012-02-06 15:06:07,887 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 15:06:07,887 domogik-velbus DEBUG 8
2012-02-06 15:06:14,307 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘None’)])
2012-02-06 15:06:14,335 domogik-velbus DEBUG normal send
2012-02-06 15:06:14,335 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=None
}

2012-02-06 15:06:14,335 domogik-velbus DEBUG set dimmer value

no idea where the none is coming from …
are you really modifying the dimmer? or are you just clicking it?

Edit:
after checking, somone broke something in the main repository, so i’ll have to wait until they fix it :slight_smile:

Hi,

The dimmer function now works but none of the 3 dimmer widgets do allow to turn off (to value 0) the light completely. The minimum value is always 5.
Only the shiny knob control widget is useful. The Large actuator range or Basic widget are not handy.
Note the constant error message that popsup no matter what you select as dimmer value… RINOR : ‘No data or timeout on getting command response’ (/rinor/api/command/velbus/08-1/)

Velbus.log tail…
2012-02-06 16:00:10,274 domogik-velbus DEBUG 11
2012-02-06 16:00:37,005 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘5’)])
2012-02-06 16:00:37,009 domogik-velbus DEBUG normal send
2012-02-06 16:00:37,053 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=5
}

2012-02-06 16:00:37,053 domogik-velbus DEBUG set dimmer value
2012-02-06 16:00:37,069 domogik-velbus INFO write packet
2012-02-06 16:00:37,081 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:00:37,081 domogik-velbus DEBUG 11
2012-02-06 16:00:58,269 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘None’)])
2012-02-06 16:00:58,269 domogik-velbus DEBUG normal send
2012-02-06 16:00:58,305 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=None
}

2012-02-06 16:00:58,317 domogik-velbus DEBUG set dimmer value
2012-02-06 16:01:17,620 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘None’)])
2012-02-06 16:01:17,628 domogik-velbus DEBUG normal send
2012-02-06 16:01:17,644 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=None
}

2012-02-06 16:01:17,644 domogik-velbus DEBUG set dimmer value
2012-02-06 16:01:31,107 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘67’)])
2012-02-06 16:01:31,123 domogik-velbus DEBUG normal send
2012-02-06 16:01:31,147 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=67
}

2012-02-06 16:01:31,151 domogik-velbus DEBUG set dimmer value
2012-02-06 16:01:31,183 domogik-velbus INFO write packet
2012-02-06 16:01:31,199 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:01:31,199 domogik-velbus DEBUG 11
2012-02-06 16:01:35,650 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘None’)])
2012-02-06 16:01:35,662 domogik-velbus DEBUG normal send
2012-02-06 16:01:35,662 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=None
}

2012-02-06 16:01:35,698 domogik-velbus DEBUG set dimmer value
2012-02-06 16:01:46,284 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘7’)])
2012-02-06 16:01:46,288 domogik-velbus DEBUG normal send
2012-02-06 16:01:46,292 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=7
}

2012-02-06 16:01:46,332 domogik-velbus DEBUG set dimmer value
2012-02-06 16:01:46,364 domogik-velbus INFO write packet
2012-02-06 16:01:46,368 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:01:46,368 domogik-velbus DEBUG 11
2012-02-06 16:01:53,944 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘118’)])
2012-02-06 16:01:53,960 domogik-velbus DEBUG normal send
2012-02-06 16:01:53,996 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=118
}

2012-02-06 16:01:53,996 domogik-velbus DEBUG set dimmer value
2012-02-06 16:01:54,000 domogik-velbus INFO write packet
2012-02-06 16:01:54,004 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:01:54,004 domogik-velbus DEBUG 11
2012-02-06 16:01:57,578 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘230’)])
2012-02-06 16:01:57,594 domogik-velbus DEBUG normal send
2012-02-06 16:01:57,622 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=230
}

2012-02-06 16:01:57,622 domogik-velbus DEBUG set dimmer value
2012-02-06 16:01:57,622 domogik-velbus INFO write packet
2012-02-06 16:01:57,658 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:01:57,658 domogik-velbus DEBUG 11
2012-02-06 16:02:00,468 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘254’)])
2012-02-06 16:02:00,488 domogik-velbus DEBUG normal send
2012-02-06 16:02:00,500 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=254
}

2012-02-06 16:02:00,520 domogik-velbus DEBUG set dimmer value
2012-02-06 16:02:00,540 domogik-velbus INFO write packet
2012-02-06 16:02:00,544 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:02:00,544 domogik-velbus DEBUG 11
2012-02-06 16:02:06,299 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘65’)])
2012-02-06 16:02:06,311 domogik-velbus DEBUG normal send
2012-02-06 16:02:06,351 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=65
}

2012-02-06 16:02:06,351 domogik-velbus DEBUG set dimmer value
2012-02-06 16:02:06,351 domogik-velbus INFO write packet
2012-02-06 16:02:06,363 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:02:06,363 domogik-velbus DEBUG 11
2012-02-06 16:02:14,179 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘20’)])
2012-02-06 16:02:14,208 domogik-velbus DEBUG normal send
2012-02-06 16:02:14,208 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=20
}

2012-02-06 16:02:14,224 domogik-velbus DEBUG set dimmer value
2012-02-06 16:02:14,244 domogik-velbus INFO write packet
2012-02-06 16:02:14,244 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:02:14,260 domogik-velbus DEBUG 11
2012-02-06 16:02:45,817 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘8’)])
2012-02-06 16:02:45,833 domogik-velbus DEBUG normal send
2012-02-06 16:02:45,849 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=8
}

2012-02-06 16:02:45,849 domogik-velbus DEBUG set dimmer value
2012-02-06 16:02:45,885 domogik-velbus INFO write packet
2012-02-06 16:02:45,885 domogik-velbus INFO START SENDING PACKET 0x8
2012-02-06 16:02:45,901 domogik-velbus DEBUG 11
2012-02-06 16:02:49,499 domogik-velbus INFO schema:lighting.device, data:OrderedDict((‘device’, ‘08-1’), (‘level’, ‘None’)])
2012-02-06 16:02:49,499 domogik-velbus DEBUG normal send
2012-02-06 16:02:49,519 domogik-velbus DEBUG xPL Message sent by thread Manager-new-message-cb : xpl-trig
{
hop=1
source=domogik-velbus.domogik
target=*
}
lighting.device
{
device=08-1
level=None
}

2012-02-06 16:02:49,519 domogik-velbus DEBUG set dimmer value

hmm, could it be that None is send every time you try to set the value to 0?

Note that the velbus dimmer module has a lot of function including the memory function. I’m using this function.
How does it work:
scenario 1: I push a button and the dimmer turns on the light to a pre-memorised value. I push the same button again and the dimmer shuts off the light.
scenario 2: I push once the push button and the light goes on (to the last used value). I push again and the light goes out.
When I keep holding the push button the lights dim more or less.

Your setup does not allow to trun of the light once I have clicked on the widget.
I then have to walk to the wall button and push once to turn of the light.

ok, we can fix this :slight_smile:

but first you can adjust the light level via the widget? if that works we can extend it a bit :slight_smile:

Yes, I can adjust the light level with the widget but not turn off the dimmer (minimum value = 5)

The dawndusk plugin is nice too. Can it be used together with the velbus plugin to turn on a light in the kitchen when the dusk value is triggered and to turn off the light when the dawn value is triggered?

If possible, how to configure the parameters :

schema : the schema to use to send the command (ie x10.basic)
addname : the name of the adress field (ie device)
add : the adresse of the device (ie A1)
command : the name of the command field (ie command)
dawn : Value of command when dawn event occurs (ie on)
dusk : Value of command when dusk event occurs (ie off)

What should I add to the schema parameter, what to the addname parameter and what to the add parameter?

the preset stuff can be added later, but its difficult if you can not test it before you commit …
To bad velleman was not willing to loan me some modules so i could fully integrate them …

Anyway i’ll start adding some other options for relays and dimmers (like forced on/off, presets, …) and when the domoweb dev creates multiple action widgets it can be worked out that all these tings can be acomplished with one widget

Do you think you have some time to work on the blinds integration? I would appreciate testing it.

Here is some information.
Protocol documentation for shutter/blinds (VMB1BL controls one shutter, VMB2BL controls 2 shutters)
velleman.be/downloads/0/velb … vmb1bl.pdf
velleman.be/downloads/0/velb … vmb2bl.pdf

This is the xml for the shutter module VMB1BL:

<?xml version="1.0" encoding="ISO-8859-1" ?> Blind 1 Up 00 28 Immediately Up 1C 28 Down 38 28 Immediately Down 54 28 Name 70 16

**
This is the xml for the shutter module VMB2BL:**

<?xml version="1.0" encoding="ISO-8859-1" ?> Blind 1 Up 00 28 Immediately Up 1C 28 Down 38 28 Immediately Down 54 28 Name 70 16 Blind 2 Up 80 28 Immediately Up 9C 28 Down B8 28 Immediately Down D4 28 Name F0 16

yeah i will have time when i’m back in the country, tonight :slight_smile:

the only problem i see is that the blind modules need a time parameter, so i need to find a way to add that time parameter. or i should use always 0, and then the time parameter should be configured at the module itself.

not sure what to choose here …

Edit: just committed the changes, it should be able to fully turn of the dimmer now

Hi,

Don’t worry about the time parameter on the blind control modules. The time setup is done on the modules. On each blind control module there is dip switch with 4 selections which are 15s, 30s, 1min or 2min.
I have set mine to 30 sec which is enough to completely bring up or bring down a blind.
If you have any other questions do not hesitate and ask me. That is why we velbus customers are here. If Velleman does not support a team of developers, who try to have an alternate autmatisation product available, the community will work together in order to achieve this.