Mysensors WiFi Gateway

---

I didn’t get one step further. Coffeescript is definitely not for me even though I did quite some stuff in javascript in the past.

I tried to convert the MQTTgateway into an Esp8266MQTTGateway and it compiles fine and flashes fine and is available on the network but that’s all. It’s not functioning as MQTT broker.
Then I tried to create an MQTTclient-gateway on the Esp and suddenly found that that is available in the mysensors development branch, also because the MQTTgateway itself is very limited and a client to a full-fledged mqtt broker is preferred.
But that GatewayESP8266MQTTClient doesn’t do anything at all. Static ip doesn’t work, no serial output, not connection to my mosquitto broker.
I flashed 2 nodemcu’s that work fine with the 1.5 espgateway but they do not function (yet) with the new GatewayESP8266MQTTClient.
But I do think that will be the best option for the future until mysensors-pimatic plugin supports a network gateway.

Just for completeness and for reference, so as not to leave loose ends:
I stopped looking at the ethernet coffee script.
I got the GatewayESP8266MQTTclient working and described it here.

Mhhh I am hoping that there will be an implementation of ESP8266-WiFi-Gateway in mysensors-plugin sometime? Is there somebody on the track? @sweebee or @mwittig ? Thank you!

An update with an idea I had few days ago:
Maybe NodeRed is a good solution. I read about it in the mysensors forum. It can connect to both, serial and tcp on input and output. This way it might be able to create a serial device to communicate with the pimatic plugin on one end and a tcp connection to an esp8266 wifi gateway on the other.
There is a package with mysensor communication nodes for NodeRed made by tbowmo and a description how he used it with a serial device here: https://forum.mysensors.org/topic/1965/nodered-injected-between-domoticz-and-mysensors/2 and a nice thread about connection to a tcp gateway here: https://forum.mysensors.org/topic/3150/use-node-red-to-allow-multiple-connections-to-ethernet-gateway
I will try this and report if it works or not. Only thing is I don’t want to mess up my productive pimatic, so I will set this up on another rpi. As I’m a bit short in spare time this might take a few weeks. But in case someone here has the time and patience you can go ahead.
Maybe we can get the full functionality of the plugin this way (btw how are ACKs etc handled with the mqtt way? @Harry-van-der-Wolf). Another reason of not wanting to use mqtt is that my OTA update controller (MYSController) can not connect to mqtt, so I can not update my nodes with this implementation without touching them.

Good news! We got it working. Thanks to @Oitzu

See: https://github.com/DheerajKhajuria/pimatic-mysensors/tree/ethernet

still some bugs:

• some garbaged data when receiving sketch name / version
• sending does work, but gives an error

Hope to fix it with oitzu tomorrow.

@sweebee @Oitzu great work. Could you please give a short how-to-use? I would realy like to test it and report errors/bugs when I find some.

@Anduril: firstly you would need to clone the git repository, sweebee linked, into your pimatic installation. (Manual Plugin installation)
The rest is configuration.

{
      "plugin": "mysensors",
      "driver": "ethernet",
      "protocols": "1.5.1",
      "startingNodeId": 1,
      "driverOptions": {
        "host": "127.0.0.1"
        "port": 5003
      }
}

ok for the noobs here (including me) with github and manual plugin installation: how does this work? And what happens if the original plugin is updated? Will this update overwrite the ethernet version?

This is the easiest way:

open a terminal

sudo service pimatic stop
cd /home/pi/pimatic-app
sudo npm i DheerajKhajuria/pimatic-mysensors#ethernet

when done edit the config and start pimatic again.

Next update will include the ethernet driver.

Some more fixes:

• driver can now be changed and modified from the gui (with host/port/ etc).
• sending works without an error

todo: error handling on timeout (when gateway is disconnected).

thanks @sweebee
I tried some minutes before to simply download and copy the changed files. After starting I got the following error:

19:56:47.807 [pimatic] Could not initialize the plugin "mysensors": @config.driver in ["serialport", "gpio"]

when installing with your npm command thing seem to go wrong…

~/pimatic-app$ sudo npm i DheerajKhajuria/pimatic-mysensors#ethernet
-
> serialport@2.0.6 install /home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport
> node-pre-gyp install --fallback-to-build

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/4.4.5"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/.node-gyp"
make: Entering directory '/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/build'
make: *** No rule to make target '../.node-gyp/4.4.5/include/node/common.gypi', needed by 'Makefile'.  Stop.
make: Leaving directory '/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.16-4-osmc
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/build/Release/node-v46-linux-arm/serialport.node" "--module_name=serialport" "--module_path=/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/build/Release/node-v46-linux-arm"
gyp ERR! cwd /home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport
gyp ERR! node -v v4.4.5
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/build/Release/node-v46-linux-arm/serialport.node --module_name=serialport --module_path=/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/build/Release/node-v46-linux-arm' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:827:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Linux 4.4.16-4-osmc
node-pre-gyp ERR! command "/usr/local/bin/node" "/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport
node-pre-gyp ERR! node -v v4.4.5
node-pre-gyp ERR! node-pre-gyp -v v0.6.18
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/build/Release/node-v46-linux-arm/serialport.node --module_name=serialport --module_path=/home/osmc/pimatic-app/node_modules/pimatic-mysensors/node_modules/serialport/build/Release/node-v46-linux-arm' (1)
npm ERR! Linux 4.4.16-4-osmc
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "DheerajKhajuria/pimatic-mysensors#ethernet"
npm ERR! node v4.4.5
npm ERR! npm  v2.15.5
npm ERR! code ELIFECYCLE

npm ERR! serialport@2.0.6 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the serialport@2.0.6 install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/osmc/pimatic-app/npm-debug.log

and no working version of the ethernet mysensors plugin is installed.

little sidenote @Oitzu it seems to me that you forgot the , behind your host adress, is that correct?

@Anduril made some more modifications, try to do it manually again.

well copying now worked and got it started, but the mysensors class was not present in pimatic. Maybe that was because i removed the complete folder of this plugin and during start there was a message 20:22:12.757 [pimatic] Could not initialize the plugin "mysensors": Cannot find module 'bluebird'.
I will reinstall the normal mysensors by deleting yours and starting pimatic and then stop pimatic and copy yours in there. I will report back.

ok, here the 2 ways I tried:
copying your files to an existing mysensors plugin folder:
at start of pimatic it says 20:32:18.857 [pimatic] Invalid config of pimatic-mysensors: Property "#/driver" Should have enum serialport, was: ethernet in /driver
and few lines later 20:32:23.494 [pimatic] Could not initialize the plugin "mysensors": @config.driver in ["serialport", "gpio", "ethernet"]
mysensors plugin is not realy loaded and in the config of the plugin there is no ethernet option.

copying your files to an empty folder:
it is compiling some stuff and giving this message:

coffee-cache: compiling coffee-script file "ethernet.coffee"...Done
20:36:36.670 [pimatic] Could not initialize the plugin "mysensors": Cannot find module 'bluebird'

In the plugin config there is the option to chose ethernet.

Hope this helps you to track things down.

can you post the config of the mysensors plugin

{
      "plugin": "mysensors",
      "driver": "ethernet",
      "protocols": "1.5.1",
      "startingNodeId": 30,
      "driverOptions": {
        "host": "192.168.38.19",
        "port": 5003
      }
    },

@Anduril seems fine, it works for me.

@Anduril it do not find the npm module “bluebird” or not the correct version.
do

cd /home/osmc/pimatic-app && npm ls

to see any depency problems.

here the results. some of the first lines are missing, the history of my terminal (putty) is not that long…

â   â âââ string_decoder@0.10.31
â   âââ reinterval@1.1.0
â   ââ⬠split2@2.1.0
â   â ââ⬠through2@2.0.1
â   â   ââ⬠readable-stream@2.0.6
â   â     âââ core-util-is@1.0.2
â   â     âââ isarray@1.0.0
â   â     âââ process-nextick-args@1.0.7
â   â     âââ string_decoder@0.10.31
â   â     âââ util-deprecate@1.0.2
â   ââ⬠websocket-stream@3.2.1
â   â ââ⬠duplexify@3.4.3
â   â â ââ⬠end-of-stream@1.0.0
â   â â â ââ⬠once@1.3.3
â   â â â   âââ wrappy@1.0.2
â   â â ââ⬠readable-stream@2.1.4
â   â â   âââ buffer-shims@1.0.0
â   â â   âââ core-util-is@1.0.2
â   â â   âââ isarray@1.0.0
â   â â   âââ process-nextick-args@1.0.7
â   â â   âââ string_decoder@0.10.31
â   â â   âââ util-deprecate@1.0.2
â   â ââ⬠through2@2.0.1
â   â â ââ⬠readable-stream@2.0.6
â   â â   âââ core-util-is@1.0.2
â   â â   âââ isarray@1.0.0
â   â â   âââ process-nextick-args@1.0.7
â   â â   âââ string_decoder@0.10.31
â   â â   âââ util-deprecate@1.0.2
â   â ââ⬠ws@1.1.1
â   â   âââ options@0.0.6
â   â   âââ ultron@1.0.2
â   âââ xtend@4.0.1
ââ⬠pimatic-mysensors@0.8.34
â âââ UNMET DEPENDENCY bluebird@^2.2.2
â âââ UNMET DEPENDENCY serialport@~2.0.6
ââ⬠pimatic-openweather@0.8.23
â âââ openweathermap@1.0.0 (git+https://github.com/sweetpi/node-openweathermap.git#cc5eb0c82f4bd19966178851b3929f92344d1971)
â ââ⬠promise-retryer@0.0.1
â   âââ promise-object@0.1.7
ââ⬠pimatic-ping@0.9.5
â ââ⬠net-ping@1.2.0
â   ââ⬠raw-socket@1.5.0
â     âââ nan@2.3.5
ââ⬠pimatic-pushbullet@0.9.0
â ââ⬠pushbullet@1.4.2
â   ââ⬠form-data@0.1.4
â   â âââ async@0.9.2
â   â ââ⬠combined-stream@0.0.7
â   â   âââ delayed-stream@0.0.5
â   âââ mime@1.2.11
â   ââ⬠request@2.44.0
â   â âââ aws-sign2@0.5.0
â   â ââ⬠bl@0.9.5
â   â â ââ⬠readable-stream@1.0.34
â   â â   âââ core-util-is@1.0.2
â   â â   âââ inherits@2.0.1
â   â â   âââ isarray@0.0.1
â   â â   âââ string_decoder@0.10.31
â   â âââ caseless@0.6.0
â   â âââ forever-agent@0.5.2
â   â ââ⬠hawk@1.1.1
â   â â âââ boom@0.4.2
â   â â âââ cryptiles@0.2.2
â   â â âââ hoek@0.9.1
â   â â âââ sntp@0.2.4
â   â ââ⬠http-signature@0.10.1
â   â â âââ asn1@0.1.11
â   â â âââ assert-plus@0.1.5
â   â â âââ ctype@0.5.3
â   â âââ json-stringify-safe@5.0.1
â   â âââ mime-types@1.0.2
â   â âââ node-uuid@1.4.7
â   â âââ oauth-sign@0.4.0
â   â âââ qs@1.2.2
â   â âââ stringstream@0.0.5
â   â âââ tough-cookie@2.2.2
â   â âââ tunnel-agent@0.4.3
â   ââ⬠websocket@1.0.23
â     ââ⬠debug@2.2.0
â     â âââ ms@0.7.1
â     âââ nan@2.3.5
â     ââ⬠typedarray-to-buffer@3.1.2
â     â âââ is-typedarray@1.0.0
â     âââ yaeti@0.0.4
ââ⬠pimatic-shell-execute@0.9.7
â âââ pimatic-plugin-commons@0.9.2
ââ⬠pimatic-sunrise@0.8.7
â âââ suncalc@1.4.0
ââ⬠pimatic-sysinfo@0.9.4
â ââ⬠nsutil@0.1.4 (git+https://github.com/sweetpi/nsutil.git#6e9c0ead7ca4f1d3fb2fdebd9f79e43d04cdb3fe)
â   âââ nan@2.3.5
ââ⬠sqlite3@3.1.3
  âââ nan@2.2.1
  ââ⬠node-pre-gyp@0.6.25
    ââ⬠mkdirp@0.5.1
    â âââ minimist@0.0.8
    ââ⬠nopt@3.0.6
    â âââ abbrev@1.0.7
    ââ⬠npmlog@2.0.3
    â âââ ansi@0.3.1
    â ââ⬠are-we-there-yet@1.1.2
    â â âââ delegates@1.0.0
    â â ââ⬠readable-stream@2.0.6
    â â   âââ core-util-is@1.0.2
    â â   âââ inherits@2.0.1
    â â   âââ isarray@1.0.0
    â â   âââ process-nextick-args@1.0.6
    â â   âââ string_decoder@0.10.31
    â â   âââ util-deprecate@1.0.2
    â ââ⬠gauge@1.2.7
    â   âââ has-unicode@2.0.0
    â   ââ⬠lodash.pad@4.1.0
    â   â âââ lodash.repeat@4.0.0
    â   â âââ lodash.tostring@4.1.2
    â   ââ⬠lodash.padend@4.2.0
    â   â âââ lodash.repeat@4.0.0
    â   â âââ lodash.tostring@4.1.2
    â   ââ⬠lodash.padstart@4.2.0
    â     âââ lodash.repeat@4.0.0
    â     âââ lodash.tostring@4.1.2
    ââ⬠rc@1.1.6
    â âââ deep-extend@0.4.1
    â âââ ini@1.3.4
    â âââ minimist@1.2.0
    â âââ strip-json-comments@1.0.4
    ââ⬠request@2.69.0
    â âââ aws-sign2@0.6.0
    â ââ⬠aws4@1.3.2
    â â ââ⬠lru-cache@4.0.1
    â â   âââ pseudomap@1.0.2
    â â   âââ yallist@2.0.0
    â ââ⬠bl@1.0.3
    â â ââ⬠readable-stream@2.0.6
    â â   âââ core-util-is@1.0.2
    â â   âââ inherits@2.0.1
    â â   âââ isarray@1.0.0
    â â   âââ process-nextick-args@1.0.6
    â â   âââ string_decoder@0.10.31
    â â   âââ util-deprecate@1.0.2
    â âââ caseless@0.11.0
    â ââ⬠combined-stream@1.0.5
    â â âââ delayed-stream@1.0.0
    â âââ extend@3.0.0
    â âââ forever-agent@0.6.1
    â ââ⬠form-data@1.0.0-rc4
    â â âââ async@1.5.2
    â ââ⬠har-validator@2.0.6
    â â ââ⬠chalk@1.1.3
    â â â âââ ansi-styles@2.2.1
    â â â âââ escape-string-regexp@1.0.5
    â â â ââ⬠has-ansi@2.0.0
    â â â â âââ ansi-regex@2.0.0
    â â â ââ⬠strip-ansi@3.0.1
    â â â â âââ ansi-regex@2.0.0
    â â â âââ supports-color@2.0.0
    â â ââ⬠commander@2.9.0
    â â â âââ graceful-readlink@1.0.1
    â â ââ⬠is-my-json-valid@2.13.1
    â â â âââ generate-function@2.0.0
    â â â ââ⬠generate-object-property@1.2.0
    â â â â âââ is-property@1.0.2
    â â â âââ jsonpointer@2.0.0
    â â â âââ xtend@4.0.1
    â â ââ⬠pinkie-promise@2.0.0
    â â   âââ pinkie@2.0.4
    â ââ⬠hawk@3.1.3
    â â âââ boom@2.10.1
    â â âââ cryptiles@2.0.5
    â â âââ hoek@2.16.3
    â â âââ sntp@1.0.9
    â ââ⬠http-signature@1.1.1
    â â âââ assert-plus@0.2.0
    â â ââ⬠jsprim@1.2.2
    â â â âââ extsprintf@1.0.2
    â â â âââ json-schema@0.2.2
    â â â âââ verror@1.3.6
    â â ââ⬠sshpk@1.7.4
    â â   âââ asn1@0.2.3
    â â   ââ⬠dashdash@1.13.0
    â â   â âââ assert-plus@1.0.0
    â â   âââ ecc-jsbn@0.1.1
    â â   âââ jodid25519@1.0.2
    â â   âââ jsbn@0.1.0
    â â   âââ tweetnacl@0.14.3
    â âââ is-typedarray@1.0.0
    â âââ isstream@0.1.2
    â âââ json-stringify-safe@5.0.1
    â ââ⬠mime-types@2.1.10
    â â âââ mime-db@1.22.0
    â âââ node-uuid@1.4.7
    â âââ oauth-sign@0.8.1
    â âââ qs@6.0.2
    â âââ stringstream@0.0.5
    â âââ tough-cookie@2.2.2
    â âââ tunnel-agent@0.4.2
    ââ⬠rimraf@2.5.2
    â ââ⬠glob@7.0.3
    â   ââ⬠inflight@1.0.4
    â   â âââ wrappy@1.0.1
    â   âââ inherits@2.0.1
    â   ââ⬠minimatch@3.0.0
    â   â ââ⬠brace-expansion@1.1.3
    â   â   âââ balanced-match@0.3.0
    â   â   âââ concat-map@0.0.1
    â   ââ⬠once@1.3.3
    â   â âââ wrappy@1.0.1
    â   âââ path-is-absolute@1.0.0
    âââ semver@5.1.0
    ââ⬠tar@2.2.1
    â âââ block-stream@0.0.8
    â ââ⬠fstream@1.0.8
    â â âââ graceful-fs@4.1.3
    â âââ inherits@2.0.1
    ââ⬠tar-pack@3.1.3
      ââ⬠debug@2.2.0
      â âââ ms@0.7.1
      ââ⬠fstream@1.0.8
      â âââ graceful-fs@4.1.3
      â âââ inherits@2.0.1
      ââ⬠fstream-ignore@1.0.3
      â âââ inherits@2.0.1
      â ââ⬠minimatch@3.0.0
      â   ââ⬠brace-expansion@1.1.3
      â     âââ balanced-match@0.3.0
      â     âââ concat-map@0.0.1
      ââ⬠once@1.3.3
      â âââ wrappy@1.0.1
      ââ⬠readable-stream@2.0.6
      â âââ core-util-is@1.0.2
      â âââ inherits@2.0.1
      â âââ isarray@1.0.0
      â âââ process-nextick-args@1.0.6
      â âââ string_decoder@0.10.31
      â âââ util-deprecate@1.0.2
      âââ uid-number@0.0.6

npm ERR! missing: bluebird@^2.2.2, required by pimatic-mysensors@0.8.34
npm ERR! missing: serialport@~2.0.6, required by pimatic-mysensors@0.8.34

npm install bluebird
will probably do it in this case. But i need to speak with @sweebee to get the dependencys right.