Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
VMB7IN && Comfort
#1
Hello
i have pretty ince velbus setup with an VMB7IN module witch is used to interface presence detectors. 
While evrything is working fine velbus is lacking of inteligence when it comes to do complex scenarios. 

This why i want to use compfort logic engine to get messages form velbus and act as \"Brain\" to create scenarios. 
My question is : 
- will VMB7IN work with comfort (as its not listed in the doc
Regards
Reply
#2
We do not support this at the moment
I believe it is a new product
Can you use the other Velbus input modules for the same function?
Reply
#3
sadly no as all other modules are discontinued now.

could you take a look to the protocol :

http://www.velleman.eu/downloads/0/velbu...vmb7in.pdf

Maybe you could include it in a next release ?
As all velbus customers will face the same problem.

Regards
Reply
#4
certainly we will look at it but I know there are many many new modules in process in R&D, new versions of Cbus, KNX and PHC included so it may be some time
Reply
#5
Might sound like I am simplifying things but is this not almost the same as the vmbp6in and would it mean very little changes required to add this module?

Comfort works very well with velbus, the logic engine almost sounds ideally suited for what the op wants.
Reply
#6
Do you know what other new modules there are which are not supported?
Reply
#7
All the new glass pannels

http://www.velleman.eu/downloads/0/velbu...mbgptc.pdf

more generaly all the dirty work was already done by this guy :

https://github.com/Cereal2nd/domogik-plu.../velbus.py

so its rather trivial to reimplement it in your code by adding new module types and frame.

Comfort looks like an ideal brain for velbus its a pity its not update.

Because now all the news modules and pannels are not supported.

Regards
Reply
#8
Any hope to have a timeline for these ?

It would be great so i can already order the parts and wait for the new FW...
Reply
#9
The github code does not help much as it is a plug in for a certain software, which is not compatible to our embedded firmware

For systems like C-bus and KNX, all modules conform to a protocol so they can add or remove or change modules without affecting the interface to Comfort
For velbus every module has a slightly different protocol, so it is a problem if they remove or add modules. The UCM/Velbus firmware must be constantly updated which makes it difficult

So we cannot give you any timeline but we will try to look at the changes in protocol


Reply
#10
Hello

github do help as its a working example of new protocol implementation and it just give you the new codes and return values for new modules. So you dont have to read the documentation that is sometimes unaccurate .

The protocol does not realy change they do add new modules codes but this is not big changes the logic is the same.

regards
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)