OR / Velbus / VMB1BLS

Designer 2.5
1

Hi

Recently I bought an automatic shutters / blinds. I used a VMB1BLS from Velbus. Within Velbus it works fine.

Too attach it to Openremote should be easy. The simple version is an UP an DOWN command, so:

module adress, as like in Velbus 252

command is UP

Command Value is 1 (channel 1)

Velbus Network ID is 1 (like with any other command in my system)

I also used command Value “1:10”

I started with a slider, but when that did not work I tried this simple UP and DOWN. And this does not work, so I make another mistake.

In the hardware compatiblity list it says:

VMB1BLS
Aug 2015
Not available for testing but assured they perform as single channel version of VMB2BLEhttps://github.com/openremote/Documentation/wiki/Velbus

Any suggestions?

RIchard

2

Hi,

I cannot remember if I included this module within the 2.5 Velbus protocol; there should be a velbus specific log file in the logs dir which will indicate what happened during module initialisation (search by module address), please post output here.

Rich

3

Hi Richard

Thank for your reply. I Somehow missed the reply, Sorry for that.

And I am not sure if I understand your reply.

Do you mean the attached velbus.log or boot.log file?

The velbus.log says:

WARN 2019-08-31 11:14:57,739 (Velbus): Unkown command ‘246’ will be ignored
WARN 2019-08-31 11:16:57,821 (Velbus): Unkown command ‘246’ will be ignored
INFO 2019-08-31 13:41:20,375 (Velbus): Device is not reachable so not adding sensor
INFO 2019-08-31 13:41:20,375 (Velbus): Device is not reachable so not adding sensor
WARN 2019-08-31 13:45:00,036 (Velbus): Unkown command ‘246’ will be ignored
WARN 2019-08-31 13:55:00,040 (Velbus): Unkown command ‘245’ will be ignored
INFO 2019-08-31 14:31:34,092 (Velbus): Device is not reachable so cannot process command
INFO 2019-08-31 14:31:37,138 (Velbus): Device is not reachable so cannot process command
INFO 2019-08-31 14:31:39,007 (Velbus): Device is not reachable so cannot process command
INFO 2019-08-31 14:31:41,329 (Velbus): Device is not reachable so cannot process command
INFO 2019-08-31 14:31:43,055 (Velbus): Device is not reachable so cannot process command
INFO 2019-08-31 14:31:44,465 (Velbus): Device is not reachable so cannot process command
INFO 2019-08-31 14:31:45,667 (Velbus): Device is not reachable so cannot process command

the boot.log is attached. It says about the sensors:

These are 2 sensors it mention when starting openremote

INFO 2019-07-25 21:22:27,620 : Registered sensor : Sensor (Name = ‘253_01_SE_POSITION_STATUS’, ID = ‘873747’, State Mappings: {})
INFO 2019-07-25 21:22:27,620 : Registered sensor : Sensor (Name = ‘252_01_SE_POSITION_STATUS’, ID = ‘873746’, State Mappings: {})

As normal.

Thanks

Richard

190831 bootlog at initilization.txt (33.1 KB)

4

Is that the full velbus.log output?

5

Hi richard,

No that is not. The list is full with this :

WARN 2019-08-31 11:14:57,739 (Velbus): Unkown command ‘246’ will be ignored

But that was normal, as it always have been,

So, in a way , yes that is all.

Richard

6

Hi everyone

Well, this is the list. See attached.

Anyone knows why I can not reach the automatic shutters?

I ll be glad with any help.

RIchard

rules log.txt (87.8 KB)