Jochen Scheib

MQTT as central information model for home automation

Jochen Scheib — Sat, 06 Jan 2018 16:35:45 GMT

MQTT as information model

Mqtt is my central communication platform at my smart home, every digital bit and byte should be reflected in the mqtt topic tree and all devices should communicate over mqtt. Data sources which don't support mqtt will be tranformed and forwarded to mqtt by Node-RED. This also applies to mqtt topics that can not be configured to fit the model described below.

MQTT schemas

The mqtt topic tree is the semantic description of the values. Generally it contains a description of the source of a specific mqtt message. There are two approaches commonly used:

location-based: Home/Bathroom/light/isOn:true
device-based: zigbee/00212effff0058a2/isOn:true

Both topics describe the same data source, the location-based approach is perfectly readable by human, but you need a mapping to actually address the device at the backend. The device-based approach contains the address of the light bulb and can be directly addressed without additional mapping.

A very good approach is described by Martin @harizanov.com. He is grouping the values into three groups: places, cloud and people. The places tree is mostly a location-based approach mixed with devices and the actual values as leaves.
This schema is perfectly readable by human but not by a machine. You will have to hard code the topic or you have to create complex regular expressions to get the context of the data integrated into the MQTT tree.

The people and cloud branch are even harder.

The new schema

There are many blog post regarding how to structure your mqtt topics, but I was not able to find one of them, which is really machine readable without domain or application specific knowledge and also perfectly readable by human. Together with some colleges we tried to define a mqtt tree structure which addresses this topic. We defined a convention to address the issue and to easily transform the topic into a tag oriented model.
To automatically parse the topic and assign a description to the data in the mqtt topic, we decided to add the type to the topic structure surrounded by brackets.

[places]/springfield/[rooms]/kitchen/[sockets]/coffeeMachine/isOn
[places]/springfield/[rooms]/bedroom/temperature

What is the benefit of it?

You can easily transform this schema into a semantic description of a leaf by transforming it into a json obect, e.g.:

{
  isOn: true,
  place: home,
  room: kitchen,
  socket: coffeeMachine
}

This makes it much more easy to process the value in your application and works well with e.g. Time Series Databases like influxdb.

Another benefit of this structure is, you can easily utilise the + character to subscribe to special classes, e.g.
[places]/+/[rooms]/+/temperature
This will help you to get all inside room temperatures. You will not get temperatures from outside or something else, without creating complex pattern.

Still it has some drawbacks, e.g. if you have different hierarchical levels: Think of one place has floors, the other does not. This is still not resolved.

In the picture below you can find a screenshot of my current mqtt tree.

Climate Control

Jochen Scheib — Thu, 23 Nov 2017 18:54:10 GMT

InfluxDB to store your sensor data

Jochen Scheib — Sun, 13 Nov 2016 15:17:00 GMT

To store sensor data from my mqtt message broker I use influxdb. Influxdb is a time series database to make historical analysis, predictive analysis and anomaly detection. The nice thing about it, its open source (MIT) and easy to install, though not so easy to configure or manage.

In this post I will describe how I use influxdb to archive my data, I will describe how the data goes into influxdb and how I use the retention policies and continuous queries to reduce the amount of data points over time.

Influxdb - A brief summary

Influxdb uses a totally different approach as relational database (e.g. mysql), it is a so called NoSQL (Not only SQL) database.
In influxdb everything revolves around time. Time is the central concept in influxdb hence all data in the database are associated with a corresponding timestamp.
Further the data points have at least one field set. Field sets are used to store data in key-value pairs, with the field key as a string describing the value. Each data point can have multiple of such field sets.
Beside that all data points can optionally have multiple tags as another key-value pair. They are used to store further meta data to semantically describe the data point. and can help you to create easy queries.
All the data points are aggregated in a measurement which acts as container for data points and are conceptional similar to tables. They are identified by a name.

Here is a short example from my influxdb database, at the moment I only use one field for each measurement, but this may change in the future:

> select * from temperature LIMIT 10
name: temperature
-----------------
time				heatings	places		rooms		value
2016-11-12T17:15:29.233Z			Moensheim			1.7
2016-11-12T17:15:30.945Z			Moensheim	Schlafzimmer	17.1
2016-11-12T17:15:30.951Z	Essbereich	Moensheim	Wohnzimmer	22
2016-11-12T17:15:30.97Z		Heizung		Moensheim	Schlafzimmer	17.1
2016-11-12T17:15:31.086Z			Moensheim	Wohnzimmer	22
2016-11-12T17:16:29.886Z	Heizung		Moensheim	Bad		15.5
2016-11-12T17:16:29.892Z			Moensheim	Bad		15.5
2016-11-12T17:16:33.482Z			Moensheim			0.7
2016-11-12T17:17:36.856Z	Heizung		Moensheim	Schlafzimmer	17.1
2016-11-12T17:17:36.859Z			Moensheim	Schlafzimmer	17.1

Each measurement belongs to a specific retention policy. The policy defines how long data points are stored and when they should be discarded to free up space. They also define how many copies of the data should be saved if you have a cluster.

Every data point with the same retention policy, measurement and tag set belongs to the same series.

Retention policies and continuous queries

Each database can have multiple retention policies, one of them has to be set as default where all new points are stored. I use three retention policies to store my measurements:

default: Retention: 1 week;
a_year: Retention: 1 year; Data point interval: 1h;
infinite: Retention: infinite; Data point interval: 1d;

All new data points are saved in the default retention policy and are deleted after 1 week. To move points between retention policies you can use continuous queries or use the INTO clause in a normal query. Both require a function, an INTO clause and a GROUP BY time() clause.

Continuous queries are executed in the time interval defined in the GROUP BY time() clause. Here are the continuous queries I use to move data from the default retention policy to the a_year and the infinite retention policy:

name: metrics
-------------
name	query
cq_1d	CREATE CONTINUOUS QUERY cq_1d ON metrics BEGIN SELECT mean(*) INTO metrics.infinite.:MEASUREMENT FROM metrics."default"./.*/ GROUP BY time(1d), * END
cq_1h	CREATE CONTINUOUS QUERY cq_1h ON metrics BEGIN SELECT mean(*) INTO metrics.a_year.:MEASUREMENT FROM metrics."default"./.*/ GROUP BY time(1h), * END

The goal of the continuous query is to reduce the amount of data stored. There for the mean function together with the GROUP BY time() clause is used. This means for the provided example in the Listing above, that every hour the mean value over the last hour will be calculated for every series in the default retention policy. The calculated value will then be moved to the a_year retention policy and saved for one year. The second contininuous query will calculate the same but for the last day.
The raw data in the default retention policy will be deleted after one weak, at this moment only the aggregated data will be available.

How the data get into influxdb

As priviously described the central data hub in my system is a MQTT broker. The data flow is managed by node-RED, hence the data points are added with a specific flow in node-RED, that can be seen in the screenshot.

Input node is a mqtt node to subscribe to everything in [Places]/# followed by a function to transform the mqtt topic into tags:

var regexTags = /(?:\[([\w]*)\]\/([^\/]*)?)/g;
var regexMeasurement = /^(?:\[[\w]+\]\/[\w]+\/)*([\w]+)$/g;

if (measurement = regexMeasurement.exec(msg.topic)) {
    msg.measurement = measurement[1];
    
    msg.tags = {};
    while(match = regexTags.exec(msg.topic))
    {
        msg.tags[match[1].toLowerCase()] = match[2];
    }
    return msg;
}

In the following function the message is formated into the database format:

node.send(
    {
        topic: msg.topic,
        payload: [
            JSON.parse(msg.payload),
            msg.tags
        ],
        measurement: msg.measurement
    }
);

After filtering out some unwanted measurements the data is written into the influxdb database.

Edimax Smart Plug - Firmware Image

Jochen Scheib — Tue, 19 Jul 2016 15:57:26 GMT

binwalk

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             CSYS header, little endian, size: 458752
20            0x14            uImage header, header size: 64 bytes, header CRC: 0xBFFB8484, created: 2015-03-25 02:14:33, image size: 2871212 bytes, Data Address: 0x80000000, Entry Point: 0x80213000, data CRC: 0x80762D51, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "Linux Kernel Image"
84            0x54            LZMA compressed data, properties: 0x5D, dictionary size: 8388608 bytes, uncompressed size: 2282468 bytes
786432        0xC0000         Squashfs filesystem, little endian, non-standard signature, version 3.0, size: 2082392 bytes, 293 inodes, blocksize: 65536 bytes, created: 2015-03-25 02:14:33

CSYS Header Format (20 bytes):

00000000  43 53 59 53 CSYS
00000004  00 00 10 01 ....
00000008  00 00 07 00 ....
0000000C  52 4e 37 31 RN71  = Model Id
00000010  ee cf 2b 00 ..+.  = image length without csys header

Last 4 bytes: Checksum:

Edimax Smart Plug - Enable Telnet Access

Jochen Scheib — Tue, 19 Jul 2016 15:57:10 GMT

The Edimax Smart Plug SP-2101W is a wifi-based smart plug to switch electric devices on and off. It also measures the power and energy consumption of the plugged in device.

Some smart developers have reversed engineered the REST protocol a while ago and we now have apis for a various of programming languages and of course for node-RED. I noticed that after some time the smart plug is no longer reachable and you have to reset it (plug out and in again). My first assumption was, that the wifi connection is not stable and the plug is not reconnecting, but this assumption was not confirmed.

So I did some more research an found out that it is related to the frequence and number of http requests to the smart plug. Maybe the web server logs?

I recently found out, that you can access the plug by telnet and I was able to confirm, that there is a log file /var/access.log which logs every request.

To enable telnet you have to do the following steps:

Reset your smart plug to factory settings
Connect your PC with the EdiPlug.Setup wifi
Call the http://192.168.20.3:10000/tnb2, it should confirm with "OK"
Now connect with a telnet client on 192.168.20.3 port 1355
To enable telnet after the initial setup, call nvc set Device.Test.HiddenPage.Enable ON
Now you can configure the device via the EdiPlug App
After this call http://192.168.20.3:10000/tnb2 and connect over telnet 192.168.20.3 port 1355 and have some fun.

Interesting tools:

Usage: nvc [command] [NAME] [VALUE]
command:
        set        Set VALUE to NAME
        get               Get value by NAME
        unset             Unset value by NAME
        ms    ...      Set column
        mg                Get row
        mu                Unset table
        all                     Show all values
        default [default file]  Restore default values

Usage: elecc [command] [NAME] [VALUE]
command:
        get_now
        notify
        read_budget
        get_history   
        read_budget  
                get  history energy from  to 
                where:  can be HOUR/DAY/MONTH

usage: ledctl LED   [args]
  where:  can be POWER|2G|RESET
          can be ON|OFF|BLINK
         [args] MUST BE specified for BLINK
         ex. ledctl POWER BLINK  
       ledctl GPIO   
       ledctl SWITCH

Volumes

dev:    size   erasesize  name
mtd0: 00030000 00010000 "Bootloader"
mtd1: 00010000 00010000 "Config"
mtd2: 00010000 00010000 "Factory"
mtd3: 000c0000 00010000 "Kernel"
mtd4: 00220000 00010000 "RootFS"
mtd5: 00050000 00010000 "elecdata0"
mtd6: 00050000 00010000 "elecdata1"
mtd7: 00020000 00010000 "nvram"
mtd8: 00010000 00010000 "hwconfig"
mtd9: 002e0000 00010000 "Uimage"

A list of values:

# nvc all
Device.LAN.2G.Repeater.Band=BGN
Device.System.RemoteManagement.Enable=ON
Run.WAN.Interface=apcli0
Run.Device.System.Power.NowPower=0
Run.FW.Version=1.03
Device.WAN.Mode=DHCP
Device.LAN.2G.CTS=Auto
Device.System.Power.OverCurrent.UpperLimit=16
Device.WAN.Static.MTU=1454
Run.Device.System.Power.Schedule.Support=1
Device.System.RemoteManagement.IPAddress=
Run.Device.System.Power.NowEnergy.Week=0.000
Device.System.Power.Budget.Week.Notify=OFF
Device.System.TimeZone.Zone=23
Device.System.FwUpgrade.Enable=ON
Device.Firewall.Enable=OFF
Device.System.Power.Budget.Month.UpperLimit=0
Device.WAN.IPV6.Enable=ON
Device.System.TimeZone.Daylight.Enable=ON
Device.LAN.2G.NFixRate=Auto
Device.System.Password.Name=admin
Run.LAN.MAC.Address=801F02FA5FF2
Device.WAN.DHCPClient.MTU=1454
Device.LAN.2G.NChannelWidth=20
Device.System.FwUpgrade.Notification.Enable=ON
Device.LAN.NetMask=255.255.255.0
Device.LAN.2G.0.Security.WPAPSK.Key=11111111
Run.WAN.MAC.Address=000A8A20bd01
Run.Device.System.FwUpgrade.Support=1
HW.CountryCode=EU
Device.WAN.Static.DNS1=
Device.Configuration.HW.ModelName=SP2101W
Device.WAN.Static.DNS2=
Device.LAN.2G.0.MACAC.Num=0
Device.LAN.2G.Repeater.Security.WPAPSK.Key=wpakey
Device.System.Power.OverCurrent.MaxUpperLimit=16
Device.System.Power.Budget.Day.UpperLimit=0
Run.meth0=eth2
Device.LAN.2G.APMode=LiteRepeater
Device.System.Power.OverPower.UpperLimit=3680
Device.NAT.UPNP.Enable=ON
Device.LAN.2G.Repeater.Channel=11
Run.WAN.Gateway=192.168.80.1
Device.System.TimeZone.Server.Address.0=pool.ntp.org
Device.LAN.2G.WPS.ConfigType=Configured
Run.Device.System.Power.LastToggleTime=20160718094006
Device.System.TimeZone.Server.Address.1=europe.pool.ntp.org
Device.System.TimeZone.Server.Address.2=oceania.pool.ntp.org
Device.System.TimeZone.Server.Address.3=north-america.pool.ntp.org
Device.System.TimeZone.Server.Address.4=south-america.pool.ntp.org
Device.System.Power.Report.Energy.Month.Notify=OFF
Device.System.Internet.Check.Port=80
Device.LAN.2G.Repeater.MAC.Address=3431C4D8C8CC
Device.LAN.DHCPServer.Start=192.168.20.100
Run.Model=SP2101W
Device.LAN.2G.FragThreshold=2346
Device.NAT.VirtualServer.Enable=OFF
Run.WAN.DNS=192.168.80.1
Device.LAN.DHCPServer.End=192.168.20.200
Device.System.RemoteManagement.Port=
Device.LAN.2G.0.Security.WPAPSK.PSKFormat=Passphrase
Device.System.Power.Budget.Month.Enable=OFF
Device.System.Power.Report.Energy.Day.Notify=OFF
Device.System.Power.OverPower.MaxUpperLimit=3680
Device.System.HiddenPage.Enable=OFF
Device.LAN.2G.Repeater.Security.WPAPSK.PSKFormat=Passphrase
Run.br0=br0
Device.System.Power.Toggle.Notify=OFF
Device.System.FwUpgrade.Time=Auto
Device.System.Internet.Check.Address=www.google.com
Device.LAN.2G.0.Security.WPAPSK.CipherSuite=WPA2AES
Device.System.Power.Budget.Mode=ENERGY
Device.LAN.2G.Enable=ON
Device.LAN.DHCPClient.Enable=OFF
Device.LAN.2G.Repeater.Security.WPAPSK.CipherSuite=WPA2AES
Device.NAT.PortForward.Enable=OFF
Device.Configuration.SW.APRTSwitch=AP
Device.LAN.2G.Coexist.Enable=ON
Device.System.Power.Budget.UnitPrice=0
Device.System.Power.Budget.Day.Enable=OFF
Device.WAN.Static.IPAddress=172.1.1.1
Device.Test.HiddenPage.Enable=ON
HW.RegionDomain=1
Device.LAN.DHCPServer.Enable=ON
Run.Cus=Edimax
Device.WAN.DHCPClient.DNS.Enable=Auto
Device.WAN.Ping.Enable=OFF
Device.LAN.2G.0.Security.Mode=Disable
Device.LAN.Client.Mode=DHCP
Run.Device.System.Power.NowEnergy.Month=0.000
Device.LAN.2G.Repeater.Security.Mode=WPAPSK
Run.BackUp.MAC=000A8A796c00
Device.System.Power.Budget.Month.Notify=OFF
HW.LAN.MAC.Address=801F02FA5FF2
Device.LAN.2G.WPS.Enable=OFF
HW.LAN.2G.0.MAC.Address=801F02FA5FF3
Device.WAN.DynIP.HostName=
Run.w2c0=apcli0
Run.w2d0=wds0
Device.LAN.2G.Band=BGN
Run.w2d1=wds1
Run.w2d2=wds2
Run.w5c0=apclii0
Run.w5d0=wdsi0
Run.w2d3=wds3
Run.w2g0=ra0
HW.WAN.MAC.Address=000A8A20bd01
Run.w5d1=wdsi1
Run.w2g1=ra1
Run.w5d2=wdsi2
Run.w2g2=ra2
Run.w5d3=wdsi3
Run.w5g0=rai0
Run.w2g3=ra3
Device.LAN.2G.0.HideSSID.Enable=OFF
HW.LAN.2G.MSSID.Mode=PREVIOUS
Device.System.Power.Budget.Week.UpperLimit=0
Run.Device.System.Power.NowEnergy.Day=0.000
Device.LAN.Client.ConnTest.Enable=OFF
Device.System.Name=Pumpe
Device.System.Power.Budget.Day.Notify=OFF
Device.QoS.Download.Bandwidth=
Device.LAN.2G.BeaconInterval=100
Device.LAN.2G.0.MACAC.Enabled=OFF
Device.System.Cloud.Server.Address=www.myedimax.com
Run.LAN.Client.MAC.Address=801F02FA5FF3
Run.Device.System.Power.Budget.ControlMask=0
Device.LAN.2G.DTIMPeriod=3
Device.LAN.DHCPServer.LeaseTime=31536000
Device.LAN.2G.0.SSID=EdiPlug.Setup
Device.LAN.2G.Repeater.SSID=gallien
Run.Device.System.Power.NextToggle=-1
Run.LAN.IPAddress=192.168.20.3
Run.Device.System.Power.State=OFF
Run.Device.System.Power.Manual.Flag=ON
Run.lan0=eth2.1
Device.LAN.2G.RTSThreshold=2347
Device.LAN.2G.0.Enable=ON
Device.LAN.2G.1.Enable=OFF
Device.LAN.5G.0.Enable=OFF
Run.WAN.IPAddress=192.168.80.26
Device.System.Power.Report.Energy.Week.Notify=OFF
Device.NAT.Enable=OFF
Device.WAN.Static.NetMask=255.255.255.0
Run.wan0=eth2.2
Run.wan1=eth2.2
Run.Device.System.Power.NowCurrent=0
Device.LAN.2G.FixRate=Auto
Device.QoS.Upload.Bandwidth=
Device.LAN.IPAddress=192.168.20.3
Device.QOS.Enable=OFF
Device.LAN.2G.TXPower=100
Device.LAN.2G.Channel=Auto
Run.APMode.Enable=OFF
Device.System.Power.Budget.Week.Enable=OFF
Device.LAN.2G.0.WMM.Enable=ON
Device.LAN.2G.PreambleType=Short
Device.WAN.Static.Gateway=172.1.1.254
Device.Configuration.KernelMessage.Enabled=ON
Device.LAN.DHCPServer.NetMask=255.255.255.0
Run.Device.System.SMTP.Support=1
Device.System.Password.Password=password
Run.WAN.Mask=255.255.255.0

Understanding the FrSky Smartport Protocol

Jochen Scheib — Mon, 26 Oct 2015 09:21:14 GMT

Data Stream

Byte: Start Sensor Frame (0x7e)
Byte: Sensor Id
Byte: Start Data Frame (0x10)
Byte: Sensor Data Type[0]
Byte: Sensor Data Type[1]
Byte: Data[0]
Byte: Data[1]
Byte: Data[2]
Byte: Data[3]
Byte: CRC

Available Sensor Ids:

#define ID1 0x00
#define ID2 0xA1
#define ID3 0x22
#define ID4 0x83
#define ID5 0xE4
#define ID6 0x45
#define ID7 0xC6
#define ID8 0x67
#define ID9 0x48
#define ID10 0xE9
#define ID11 0x6A
#define ID12 0xCB
#define ID13 0xAC
#define ID14 0x0D
#define ID15 0x8E
#define ID16 0x2F
#define ID17 0xD0
#define ID18 0x71
#define ID19 0xF2
#define ID20 0x53
#define ID21 0x34
#define ID22 0x95
#define ID23 0x16
#define ID24 0xB7
#define ID25 0x98
#define ID26 0x39
#define ID27 0xBA
#define ID28 0x1b

Sensor Data Types:

#define AccX_DATA_ID 0x0700
#define AccY_DATA_ID 0x0710
#define AccZ_DATA_ID 0x0720
#define ASS_SPEED_DATA_ID 0x0A00
#define FAS_CURR_DATA_ID 0x0200
#define FAS_VOLT_DATA_ID 0x0210
#define FLVSS_CELL_DATA_ID 0x0300
#define FUEL_DATA_ID 0x0600
#define GPS_LAT_LON_DATA_ID   0x0800
#define GPS_ALT_DATA_ID       0x0820
#define GPS_SPEED_DATA_ID     0x0830
#define GPS_COG_DATA_ID       0x0840
#define GPS_HDOP_DATA_ID      0xF103
#define RPM_T1_DATA_ID 0x0400
#define RPM_T2_DATA_ID 0x0410
#define RPM_ROT_DATA_ID 0x0500
#define SP2UARTB_ADC3_DATA_ID 0x0900
#define SP2UARTB_ADC4_DATA_ID 0x0910
#define VARIO_ALT_DATA_ID 0x0100
#define VARIO_VSI_DATA_ID 0x0110

Integration of the Edimax Smartplug into your node-RED flow

Jochen Scheib — Wed, 26 Aug 2015 19:51:28 GMT

I decided to replace the current flow to control the edimax smartplug over node-RED with two smartplug specific nodes. The node makes use of the existing node.js module edimax-smartplug by mwittig. The node.js package node-red-contrib-smartplug adds two new nodes to your node-RED palette, one input node and one output node.

The input node polls the status of your edimax smartplug in a given interval and inserts the value as json object into your flow:

In the node configuration you can select which information the node should read from the smartplug. The output is a json object, e.g.:

{ "deviceinfo": { "vendor": "Edimax", "model": "SP2101W", "fwVersion": "1.03", "mac": "801F02FA5FF3" }, "schedule": { "0": "i0iu0", "1": "i0iu0", "2": "i0iu0", "3": "i0iu0", "4": "i0iu0", "5": "i0iu0", "6": "i0iu0" }, "status": { "state": false, "nowPower": 0, "nowCurrent": 0, "day": 0, "week": 0, "month": 0.089, "lastToggleTime": "2015-08-25T15:14:07.000Z" } }

The with the output node you can change the state of the plug and switch it on or off. It will only accept a boolean as input payload. Sending true will switch the smartplug on, sending false will switch it off. You can configure the node to send the new state after toggle as output:

Feedback an suggestions are welcome. Try it out by install the package over npm:

npm install -g node-red-contrib-smartplug

SAMBA4 AD ON SYNOLOGY DS211J

Jochen Scheib — Sun, 26 Aug 2012 21:04:00 GMT

Install debian-chroot spk from SynoCommunity

Mount partitions with user_xattr therefore add this to /etc/rc.local

mount -o remount,user_xattr /  
mount -o remount,user_xattr /volume1

Chroot:

chroot /volume1/@appstore/debian-chroot/var/chroottarget/ /bin/bash

Install git and dependencies (see here):

apt-get install build-essential libacl1-dev libattr1-dev  
   libblkid-dev libgnutls-dev libreadline-dev python-dev 
   python-dnspython gdb pkg-config libpopt-dev libldap2-dev 
   dnsutils libbsd-dev attr krb5-user git

Install Samba (takes some time) (more):

cd  
git clone git://git.samba.org/samba.git samba-master  
cd samba-master  
./configure
make  
make install

Konfigure bind9

Provision Samba4

/usr/local/samba/bin/samba-tool domain provision --host-name=majestix --realm=gallien.jochen-scheib.de --domain=GALLIEN --adminpass='testtest1234!' --server-role=dc --use-ntvfs --host-ip=192.168.80.201 --dns-backend=BIND9_FLATFILE

Edit the /usr/local/samba/etc/smb.conf

# Global parameters

[global]
    workgroup = GALLIEN
    realm = gallien.jochen-scheib.de
    netbios name = MAJESTIX
    server role = active directory domain controller
    interfaces = 192.168.80.201
    bind interfaces only = yes
    server services = rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc, dnsupdate, smb
    dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver, winreg, srvsvc
    posix:eadb = /usr/local/samba/private/eadb.tdb



[netlogon]
    path = /usr/local/samba/var/locks/sysvol/gallien.jochen-scheib.de/scripts
    read only = No

[sysvol]
    path = /usr/local/samba/var/locks/sysvol
    read only = No

Copy Kerberos config to /etc

cp /usr/local/samba/private/krb5.conf /etc/

Make sure to configure DNS on Router:

hostname gallien.jochen-scheib.de 192.168.80.200
dns forwarding /gallien.jochen-scheib.de/192.168.80.200

TODO:

Roaming
Check which services are really needed
Add samba4 AD to synology directory client| working more or less