SmartServer (Proxy TCP sockets to the cloud, Smappee MQTT, Duotecno IP Nodes, Homekit interface)
npm install homebridge-smartsystem
updown =>
if name contains $ => "garagedoor"
if name contains * => "door"
else => "window-covering"
mood =>
if name contains $ => "unlocker", locks again after 1.2 sec
if name contains * => permanent locked=on/unlocked=off
else => "mood" (turns of 1.2 seconds after being turned on)
switch =>
if name contains $ => "lock"
if name contains * => "switch" (also still works with "stk", "STK" and "Stk")
else => "lightbulb"
$3
- sending -1 to moods not 0/1 (we don't do long on/off in homebridge)$3
- store displaynames and types in the config
- startup from config
- no platform if not all masters logged in
- (b2) read db info on startup
- (b2) have 10 QR codes on the server
- (b3) go from services directly to edit node.$3
- return audio room config
- (b2) try fix for mood pushes
- (b3) new app build
- (b4) read lowercase files for backup & audio + new app
- (b5) new app version
- (b6) Fixed error in homebridge config (no soc- and smart-app at the same time)$3
- also respond to /tabs/control etc... from the ionic 5 app$3
- added run9998/9999.ts files for server runs
- added stored nodenames in master config
- better support for status/value in ejs files$3
- experimental up/down for Somfy$3
- added http up/down
- don't crash if the unit is not found
- added a "pm2 flush" in the update script$3
- added smappee info (channels, plugs, switches, config)$3
- better smappee plug support
- added stop to somfy controls$3
- added wait/busy in somfy gpio access
- moved a number of helper functions to types.ts
- removed: logicalReqNodeAddress (never used)
- removed test configs from repo$3
- trying to fix connection loss$3
- add heartbeat to master to prevent connection loss$3
- fix PIR and other stuff like values for virtual units / macro's$3
- added logging for files
- R2: added new version of the app v2.3.4 B2
- R3: keep heartbeat if socket closes unexpectedly
- R4: added not ready message
- R5: support for short url's /node/unit/value$3
- smappee channel rules now accept 3+2+7 format for a channel$3
- smappee now has "sun" rules: low == (production < consumption>)$3
- Added API calls /masters/list & services /units/set & get$3
- added extended type selection in master->node->unit->detail page (not yet tested !!) $3
- added stubs for openHAB switch/dimmer/updown$3
- added active / used unit flag, allowing more units in the gateway, only those "actice" are sent to Homebridge$3
- openHAB support for up/downs, dimmers en switches. copied from smartapp.js file of Pieter Becu $3
- added git user.name/email to update.sh$3
- better upgrade to new config layout (used - active units)$3
- waiting for active config units (not total units)$3
- Extended saved type was not used on restart$3
- Added $T (0-511) for bindings (Hue)
- trying to fix up/down - windowcovering
- trying to fix ready state (nr units in systems versus in config)
$3
- changed mood-press(true) to (-1)
$3
- send "stop" to openHAB for status = 0
$3
- app upgrade to 2.3.7
$3
- delete spaces from backup names
- updated files on the server: for f in \ .json ; do mv "$f" ${f//\ /}; done$3
- fixed bug in sun/power selection of rule
- changed power rule functionality (now: compare channels with "sun-consumption")
$3
- change name of master does not generate new master anymore
$3
- turn of debug -> production
$3
- Fixed Long standing rule editing bug: kEmptyRule included an array
$3
- don't do request status of clicking an up/down in the web interface
- added extra logging for heartbeats
$3
- tryout for "no-macro" on a switch
- fixes no-macro "save" bug
- added send-no-stop for up/downs$3
- added reconnect in the master conf file
- cleaned up a lot of logging
- auto read config file in constructor
$3
- use heartbeat to reconnect after network connection lost. Needs last version op ip master soft, in previous versions the heartbeat was broken.
$3
- fixed problem when checking smappee switch (only used nr, not type)
$3
- added reboot command -> in the homebridge page or as an url: /reboot$3
- added "power" bindings -> set 1/10th of value of unit to power of channels. Visualisation is done in the Pro and Lite app.
$3
- Display nr devices on HomeBridge$3
- network settings + reboot
$3
- listen on gpio pinv6.0.x - 01-07-2022
Homebridge UI version
- .1: first working version
- .9: read version from package.json
- .10: removed "homekit" nav tab,
added "restart plugin" to settings,
set lock target state to "locked"$3
- global debug, log, err functions in types.ts
- split smappee.ts in PowerBase + smappee/p1/shelly$3
- 0: implemented P1 power meter telegram
- 1: bugfixes, timeout mgt, etc...
- 2: try fixing logfunction errors
- 3: reverting to console.log
- 4: errors when starting power mgrs from platform.ts
- 5: v6.1.3 changes were gone... restored them.
- 6: added login with pw in config + http.get with on-error
- 6: allow + and - in power rules expressions
- 7: allow NaN in bindings compare for update$3
- receive config through Platform on startup,
- moved all config to global variable, keep in sync through API of HB-UI
- implemented login page, use HB-UI api -> bearer jwt token
- added upgrade method from 6.1.x to v6.2.x (adding files from /home/homebridge/duotecno/config..json to global config.)
- homebridge config is saved by UI in: /var/lib/homebridge/config.json (as well as the logfile: homebridge.log)
- smartapp calls Homebridge UI API to save changes$3
- 1 : always write config to file too (next to sending through the HB-UI API)
- 2: added headers to http calls from switches, dimmers and up/down's (including OH stuff)
- 3: fixed bug in Sanitizer of UnitConfig preventing from publishing units to homebridge
- 4: fixed empty name bug in unit-def / new accessory()
- 5: fixed bad displayNames in published units
- 6: power: 5% instead of 10% for power rules$3
- 1: first test Shelly PM - allow address or addresses, example: "192.168.0.95,102.168.0.96"
- 2: logging now more according to debug true/false in the config file
- 3: power bindings now when: 5% change < 1000W, 2% change > 1000W
- 4: added if in set-plug if smappee not (yet) connected.$3
- 0: writing to registers
- 1: ask/show protocol version -> publish
- 2 & 3: test on protocol version, not firmware for using registers, due to bug in master firmware pre v101.x $3
- 0: published$3
- 0: Extra "Switch" type openHAB, uses username/password to ask for a token$3
- 0: implemented "links" between HB accessories and Duotecno units.
- 1: updated the readme file
- 2: use HB Accessory characteristics in set/get, ignore status for the moment
- 2: remember/show username in login screen + set focus to password
- 3: do dimmers/up-downs
- 4: better up-down values to and from HB
$3
- 0: first version including the proxy
- 1: max/min values for hbValues
- 2: HB up/down -> don't respond to motor unit's, only macro
- 3: remember request before the login kicked in (and redirect to that one, once the login was succesful)
- 4: now using only TCP sockets to the server
- 5: making it more robust / inline with repo-service version
- 6: 26 aug / removed double error handlers on cloudSocket
- 7: 28 aug / restart if no free connections
- 8: 28 aug / less logging (through logConfig) for device set/get functions
- 9: corrected reading the local config file + dump it in the logs
- 10: wrong default port for cloud server
- 11: use new DNS entries + exponential backoff for new connections, give up after 16 seconds.
- 12, 13: small changes for missing value for Target... $3
- 0: added mDNS/Bonjour + always port 80 + don't preload EJS files if system.debug == true
- 4: fixed a bug when shelly has empty list of ip addresses
- 5: better error handling in the proxy.ts + show connection in the /proxy page$3
- 0: master + config ports in the proxy
- 1: fix for reading the proxy config
- 2: missing port number in unique id for master portHardware
A Raspberry Pi that connects to a Duotecno IP Node
and (if configured) to a Smappee Infinity (power and plugs)
and to http switches (bi-directional)
and to openHAB http (from v5.1)
and linked to HB accessories (from v6.7)
Desired functions
* Use a web app on a Raspberry PI to
* setup the IP address of the Duotecno IP Node
* select desired nodes / units to use with
* setup the IP address of the Smappee
* configure rules for the Smappee (high, low values + Duotecno message — see example below)
* control remote Smappee plugs, remote Shelly switches* Raspberry runs a homebridge server
* allowing homekit to connect
* homekit app on the iPhone, Mac, iPad works
* siri will understand the commands
* Raspberry connects to (if available) the Smappee and:
* monitors the MQTT datastream from the Smappee
* if high/low + messages are defined, executes them
* send plug on/off to Smappee
* Raspberry implements
* switches that are triggered on status changes of Duotecno units and emit a http request
* scenes (a collection of units + a state) that are triggers by a status change (moods, inputs, ...)
* backup / restore
* Jullix:
* I would now like to have a websocket server (on the same ports as the SmartApp) that uses JSON as format.
* The client that connects can send 2 things: see below, but we should always answer with a number of "switchable items" (relays) together with the power/energy usaged, either measured of estimated (measured: false).
* An example we could send:
[
{ "id": 1, "name": "Airco", "power": 1.0, "energy": 10.0, "voltage": 230.0, "current": 1.0, "relay": true, "measured": true},
{ "id": 2, "name": "Zwembad pomp", "power": 1.0, "energy": 10.0, "voltage": 230.0, "current": 1.0, "relay": true, "measured": false}
]
* What we send / what is in this array needs to be configured though a new section in the web interface.
The id's of the relays should be node-numbers * 256 + unit-numbers of Duotecno units (of the first master) and the web/config-page should allow the user to add a "Device" and fill in the details (no id given) + edit a device already in the list. (pass id) (similar as in link-list.ejs and link-details.ejs)
* Messages we could receive:
[] (empty array) keep of keep alice / poll for status
[
{ "id": 513 "relay": true },
{ "id": 258, "relay": false }
]
which would mean: turn unit 1 in node 2 (from 513=2256+1) "on" and turn unit 2 of node 1 "off" (from 258=1256+2)How to set up
1. Configure IP address of the Raspberry on the SDCard on a PC or Mac (put it in, edit cmdline.txt and you’re done), perhaps DHCP? WiFi?
2. Put it into the Raspberry and boot it up
3. Connect with a web browser to it’s address on port 5002 (ex: http://192.168.1.71:5002 ) to start configuring.
4. Configure the IP addresses of the Duotecno’s IP Nodes that you want to use as main database node, incl port and password.
5. Configure the nodes you want to use and for each node the units you want to export to homekit, new nodes are highlighted.
6. (optional from here) Configure the IP address of a Smappee infinity
7. Add rules to the Smappee config to execute commands (mood, light, …) when exceeding a defined high or low of a specific channel.
8. Add switches, see below for status callback's
Setting units
http://[ip of Raspberry]:[port of Raspberry]/units/set?master=[ip of duotecno node]:[port of duotecno node]&unit=[node logical address]:[unit logical address]&value=[Y/N/0/1... other value]
Example: http://192.168.0.99:5002/units/set?master=192.168.0.98:5001&unit=0x3;0x1c&value=1
The url for http switches
the url field contains 3 parts
fixed url part | zero part | one part
if the status of the unit = 0 we send "fixed"+"zero part",
if = 1 "fixed"+"one part"
Example: http://192.168.0.101/relay/0?turn=|off|on
The url for http dimmers
the url field can contains a $
this $ is replaced by the value of the attached unit
Example: http://192.168.0.101/relay/0?turn=on&brightness=$
How to set up a Raspberry Pi - from V6.0 on
1. Setup Debian in Pi on 192.168.0.9- download “Raspberry Pi Imager” from https://www.raspberrypi.com/software/
- install “Raspberry PI OS Lite 32bit” in settings: user, password, name, enable ssh, etc… in settings
- add “ip=192.168.0.9” to /boot/cmdline.txt (or whatever free address)
- put the card into a Pi and power on
- try to connect with ssh pi@192.168.0.9
2. Install Homebridge
(see instructions on https://github.com/homebridge/homebridge/wiki/Install-Homebridge-on-Raspbian)
Execute on the Pi via ssh:
if forgotten:
1. for better security enable public key
mkdir ~/.ssh
chmod 700 ~/.ssh
cat "Mac/PC .ssh/id_rsa.pub" >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys
rm ~/id_rsa.pub2. use pi-config
sudo raspi-config
-> enable ssh
-> boot to cmdlineAdd Homebridge to repo’s
curl -sSfL https://repo.homebridge.io/KEY.gpg | sudo gpg --dearmor | sudo tee /usr/share/keyrings/homebridge.gpg > /dev/null
echo "deb [signed-by=/usr/share/keyrings/homebridge.gpg] https://repo.homebridge.io stable main" | sudo tee /etc/apt/sources.list.d/homebridge.list > /dev/nullDeinstall old version running through pm2
pm2 stop homebridge
pm2 delete homebridge
pm2 saveInstall Homebridge
sudo apt-get update
sudo apt-get --yes install homebridge
sudo ln -s /opt/homebridge/bin/node /usr/bin/node
sudo ln -s /opt/homebridge/bin/npm /usr/bin/npminstall smappee and mqtt
sudo npm install -g --force mqtt
sudo ln -s /opt/homebridge/bin/mqtt /usr/bin/mqttconnect to homebridge UI with a browser
http://192.168.0.9:8581
add user, for example: pi / pw…add duotecno plugin to Homebridge config
go to "Plugins"
search for "smartsystem"
click "install"or in advance:
cd /var/lib/homebridge
sudo npm install --save homebridge-smartsystem
set config to:
{
"manufacturer": "Duotecno-Coppieters",
"name": "Duotecno",
"platform": "DuotecnoPlatform",
"smappee": true, "shelly": false, "p1": false,
"smartapp": true,
"system": true,
"socapp": false
}restart Homebridge in webbrowser (right top icon)
connect to Duotecno gateway
http://192.168.0.9:5002
add master and off you go… see "setup" a little bit higher
3. Various optional
Updates
sudo apt-get update
sudo apt-get install homebridge
sudo hb-service update-node
Uninstall
sudo apt-get remove homebridge
sudo rm -rf /etc/apt/sources.list.d/homebridge.list
sudo apt-get purge homebridge
4. Smappee
#find uuid
mqtt sub -t 'servicelocation/#' -h '192.168.0.186’ -v
-> 57e3e0d8-bb05-4b04-8662-1a9871998f3f
#add uuid
mqtt sub -t 'servicelocation/57e3e0d8-bb05-4b04-8662-1a9871998f3f/#' -h '192.168.0.186' -v
http://pro.smappee.net
duotecno/duotecno1234
192.168.0.2
How to set up a Raspberry Pi - V1
$3
dump ->
diskutil list # -> find device
sudo dd if=/dev/disk2 of=~/Desktop/raspberrypi.dmg
restore ->
diskutil unmountDisk /dev/disk2
sudo newfs_msdos -F 16 /dev/disk2
sudo dd if=~/Desktop/raspberrypi.dmg of=/dev/disk2
Install on ARM7/8/9
$3
download rasbian-stretch-lite.img from https://www.raspberrypi.org/downloads/raspbian/
go to diskutils
- find disk nr
- unmount (not eject) the volume
go to terminal
diskutil unmount /Volumes/NONAME
sudo dd bs=1m if=/Users/johan/Projects/Duotecno/ of=/dev/rdisk2 conv=sync
(ctrl-T let's you see progress = siginfo)$3
edit cmdline.txt on the boot partition of the sd card, add "ip=..." at the end of the line.
if desired don't expand the root file system -> remove the init=...
vi /Volumes/boot/cmdline.txt
example:
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=025ce4e3-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet init=/usr/lib/raspi-config/init_resize.sh splash plymouth.ignore-serial-consoles ip=192.168.99.97
$3
add a file called "ssh" to the boot partition of the sd card
touch /Volumes/boot/ssh
sudo vi /var/lib/homebridge/node_modules/homebridge-shelly/util/custom-characteristics.js
perms: ["ev","pr"], //Perms.READ, Perms.NOTIFY],
sudo vi /var/lib/homebridge/node_modules/homebridge-shelly/accessories/lightbulbs.js
return 5; //Accessory.Categories.LIGHTBULB
sudo vi /var/lib/homebridge/node_modules/homebridge-shelly/accessories/switches.js
return 8; //Accessory.Categories.SWITCH
switches.js: return 8; //Accessory.Categories.SWITCH -> 8
lightbulbs.js: return 5; //Accessory.Categories.LIGHTBULB -> 5 (4x)
base.js: return Accessory.Categories.OTHER -> 1
doors.js: return Accessory.Categories.DOOR -> 12
garage-door-openers.js: return Accessory.Categories.GARAGE_DOOR_OPENER -> 4
outlets.js: return Accessory.Categories.OUTLET -> 7
sensors.js: return Accessory.Categories.SENSOR -> 10 (4x)
valves.js: return Accessory.Categories.FAUCET -> 29
window-coverings.js: return Accessory.Categories.WINDOW_COVERING -> 14
windows.js: return Accessory.Categories.WINDOW -> 13
add:
Accessory.Categories = {
OTHER: 1,
BRIDGE: 2,
FAN: 3,
GARAGE_DOOR_OPENER: 4,
LIGHTBULB: 5,
DOOR_LOCK: 6,
OUTLET: 7,
SWITCH: 8,
THERMOSTAT: 9,
SENSOR: 10,
SECURITY_SYSTEM: 11,
DOOR: 12,
WINDOW: 13,
WINDOW_COVERING: 14,
PROGRAMMABLE_SWITCH: 15,
RANGE_EXTENDER: 16,
IP_CAMERA: 17,
VIDEO_DOORBELL: 18,
AIR_PURIFIER: 19,
HEATER: 20,
AIR_CONDITIONER: 21,
HUMIDIFIER: 22,
DEHUMIDIFIER: 23,
SPRINKLER: 28,
FAUCET: 29,
SHOWER_HEAD: 30,
TELEVISION: 31,
TARGET_CONTROLLER: 32
};
Small example of config.
{
"manufacturer": "Duotecno-Coppieters",
"platform": "DuotecnoPlatform",
"debug": false,
"smappee": {
"rules": [],
"address": "",
"uid": "57e3e0d8-bb05-4b04-8662-1a9871998f3f",
"debug": false,
"bindings": []
},
"smartapp": {
"port": 5002,
"switches": [],
"debug": true,
"links": [],
"apiHost": "localhost",
"apiPort": 8581,
"username": "duotecno",
"password": "#Duotecno@1",
"devices": []
},
"system": {
"language": "EN",
"stores": false,
"multiple": false,
"socketserver": "gateway.duotecno.com",
"socketport": 9999,
"mood": "sfeer",
"cmasters": [],
"cunits": [],
"debug": false
},
"socapp": false,
"p1": {
"debug": false,
"rules": [],
"bindings": [],
"address": ""
},
"shelly": {
"debug": false,
"address": "",
"addresses": "",
"rules": [],
"bindings": []
},
"proxy": false
}