We need a structured list of all messages and commands

Stef_Coene · April 22, 2020, 11:51am

I know the protocol files are saying 33 = temperature sensor name.
But if you open Velbuslink, it uses channel 34 for the temperature. There is nu channel 33 in Velbuslink.
So I also use channel 34 in my scripts to be consistent with Velbuslink.

Stef

GertSt · April 25, 2020, 9:10am

I’m refactoring my Velbus-Node-Red connector to get Velbus module names by using @Stef_Coene’s JSON file.
All is working fine so far!
I will try to get more module commands out of this JSON data over time.

Stef_Coene · April 25, 2020, 11:26am

I created a web frontend for the json file:
https://qos.docum.org/velserver/
This is work in progress, but maybe it can be useful for someone else.
I’m also going to include extra comments to explain the json.

By reading my own json file, I realized I have to figure out what I did for the Edlge lid panels.
I don’t own one myself. I did some coding for it on a remote setup and I don’t remember the logic behind my own code

Stef

Stef_Coene · April 27, 2020, 12:44pm

I don’t know who is interested, but I updated the json file (some information was missing).

Link to the json file:

github.com

StefCoene/moduleprotocol/blob/master/out/protocol.json

{
   "ChannelTypes" : {
      "Blind" : {
         "Get" : {
            "Message" : "EC"
         },
         "Module" : {
            "03" : {
               "Action" : {
                  "Get" : "yes",
                  "Set" : "yes"
               }
            },
            "09" : {
               "Action" : {
                  "Get" : "yes",
                  "Set" : "yes"
               }
            },
            "1D" : {

This file has been truncated. show original

Documentation regarding the json file:

github.com

StefCoene/velserver/blob/master/README-Internal.md

# General
All the information is stored in `%global`.

- `$global{Cons}` contains all the fixed data
  - this is defined in the `Velbus_data_*.pm` files and will never change
- `$global{Vars}` contains all variable data
  - this is all the information extracted from the messages

# Parsing messages
When a message is parsed, the data about the that message is stored in %message:

- `$message{address}`: the address of this message.
- `$message{MessageType}`: the hex code of the message

We also check for correct STX, ETX, Prio and checksum.

Messages are parsed with subfunction process_message in file `lib/Velbus.pm`.

## Scan message
A Scan message has a RTR of 40.

This file has been truncated. show original

Link to a php website based on the json file:
https://qos.docum.org/velserver/

I also updated https://github.com/StefCoene/velserver so it uses the json file as data source.

Stef

GertSt · April 27, 2020, 1:21pm

Very handy, tx!

Are you aware that there’s no SSL certificate, so going to https://qos.docum.org/velserver/ gives an “unsecure site” warning. Let’s Encrypt might help.

Stef_Coene · April 27, 2020, 1:42pm

Yeah, I know, that’s a website that’s normally only used by me.
I’m just too lazy to fix the ssl error
And when my home router gets a new ip, I have to fix the dns entry manually.

Stef