Mysensors WiFi Gateway
Hello, i also wan’t to try the ESP8266 Gateway.
Does anybody got it to work now?
(And can give me some support what i have to do) 
I have the following hardware:
ESP --> Wemos D1 Mini
Radio --> NRF24L01
I think the wiring example would be like the sample on my sensors.org
https://www.mysensors.org/build/esp8266_gateway
But what are the next steps on/in pimatic?
How do i have to implement the Wemos in Pimatic?
Mit freundlichen Grüßen
Chris
@Anduril and others
Hi, I also started today with the WiFi Gateway. As the mysensors plugin still doesn’t support the wifi gateway I continued with @Anduril socat script and modified it to “daemonize” it. I also renamed it to pimsocat (not! pimsocat.sh).
See here:
#!/bin/bash
### BEGIN INIT INFO
# Provides: socat
# Required-Start:
# Required-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: start socat tunnel for use with MySensors gateway
# Description: Open socat tunnel between /dev/ttyMS-Gateway and my
# ESP8266 wifi gateway for MySensors
### END INIT INFO
# Initial author: user Anduril @ pimatic forum
# Expanded: Harry van der Wolf <hvdwolf@gmail.com>
# Install:
# cp pimsocat /etc/init.d/pimsocat
# chmod +x /etc/init.d/pimsocat
# chown root:root /etc/init.d/pimsocat
# update-rc.d pimsocat defaults
# Specify here the address of your ESP MySensors WiFi Gateway
IPADDRESS="192.168.144.240"
PORT="5003" # default on 5003 but change this if you changed it on your gateway ino
PATH=/bin:/usr/bin:/sbin:/usr/sbin
SOCAT=/usr/bin/socat
PKILL=/usr/bin/pkill
DAEMON=/usr/bin/socat
NAME="socat"
OPTIONS="-d -d pty,link=/dev/ttyMS-Gateway,raw,echo=0,waitslave tcp:${IPADDRESS}:${PORT}"
# Do the binaries exist
test -f $SOCAT || exit 0
test -f $PKILL || exit 0
# Get lsb functions
. /lib/lsb/init-functions
case "$1" in
start)
log_begin_msg "Starting socat as listener for our mysensors gateway"
$SOCAT -d -d pty,link=/dev/ttyMS-Gateway,raw,echo=0,wait-slave tcp:${IPADDRESS}:${PORT} & >/dev/NULL
log_end_msg $?
;;
stop)
log_begin_msg "Stopping socat as listener for our mysensors gateway"
$PKILL $NAME
log_end_msg $?
;;
restart)
$0 stop
sleep 5
$0 start
;;
status)
status_of_proc "$DAEMON" pimsocat
;;
*)
echo "Usage: (sudo) service pimsocat {start|stop|restart|status}" >&2
exit 2
;;
esac
exit 0
As socat is not a real daemon it doesn’t have a stop command. It can only be killed. However, every kill or pkill command immediately terminates a script. Therefore we can’t kill socat from this script and then restart it from the same script immediately. Hence the trick with the internal call.
I also modified the default Esp8266Gateway.ino as I want a fixed ip address.
You will find the following lines in the void setup()
(void)WiFi.begin(ssid, pass);
while (WiFi.status() != WL_CONNECTED)
{
delay(500);
Serial.print(".");
}
I changed that to the following:
(void)WiFi.begin(ssid, pass);
while (WiFi.status() != WL_CONNECTED)
{
delay(500);
Serial.print(".");
}
// Configure a static ip address
IPAddress ip(192,168,144,240);
IPAddress gateway(192,168,144,1);
IPAddress subnet(255,255,255,0);
WiFi.config(ip, gateway, subnet);
Change this to your own network setup!
(This works of course for every esp ino)
And finally: As socat works like a daemon (but is not a daemon) you can also restart it with (sudo) service pimsocat restart
That means you can (re)start the socat “daemon” whenever pimatic (re)starts with a rule like:
"rule": "if pimatic is starting then execute \"service pimsocat restart\"",
or with a button like explained in this howto from @leader21
@Harry-van-der-Wolf I’m not familiar with daemonizing things, but doesn’t your script just start after pimatic start in your rule? Don’t you have the problem of connecting to a not yet existing serial device with MySensors plugin?
It would be great if it works this way, but I don’t think so.
Yes, you are right. When starting from pimatic it is too late. The device needs to exists before pimatic tries to use it.
I will change it to make some kind of combined pimatic/socat script.
maybe one should extend the mysensors plugin to either cope with not existing devices and keep trying or directly support the network serial connection all this is just a workarround
maybe use something like this in the plugin:
https://github.com/sizuhiko/tcpsocket-serialport
I tried to implement it, but no luck so far. This is the way to open a tcp connection in node/javascript:
https://github.com/rakeshpai/mysensors-controller/blob/master/index.js#L32
Should be no problem in theory but I did not yet implement a raw tcp connection.
http://www.hacksparrow.com/tcp-socket-programming-in-node-js.html
I however implemented a raw UDP interface for Orvibo S20 sockets which works fine with nodejs.
I mentioned that I would create a System V combined script for socat and pimatic, but how does the mechanism work when pimatic starts after updating plugins and so on?
Does pimatic restarts itself or is this done via the system V settings in the init.d script with a service pimatic restart?
If it is the first mechanism a combined script has no use.
If it is done via the latter system V mechanism it can be done via a combined init.d script.
I did make a work around. I left the pimatic service in place and I also left my own pimsocat “service” script in place.
When doing a reboot it works anyway as the pimatic startup is a lengthy one and socat is long running before pimatic is at the stage of the mysensors plugin.
I created a second small script which I called restart_pimatic_socat.sh
#!/bin/bash
service pimatic stop
service pimsocat stop
sleep 5
service pimsocat start
service pimatic start
Create a ButtonsDevice like described here by @leader21.
Create the rule for the pimatic restart like
"if button-pimatic-restart is pressed then execute \"sudo /home/<some_user_name>/pimatic/scripts/restart_pimatic_socat.sh\"",
Now when you have updated your plugins, do not simply press the button “restart pimatic” inside the “Updates” screen, but backout of the “Updates” screen and press your “Restart pimatic” button.
This works fine.
Now let’s hope the mysensors plugin will be modified to support the wifi gateway so that this work-around is no longer necessary
I’m hoping for a tcp connection for mysensors plugin too.
@Harry-van-der-Wolf do you have a stable connection? I loose connection from time to time with the result of no messages getting to pimatic. But the serial device is still there. I didn’t had a chance upto now to hunt down the issue, maybe bad tcp connection or bug…
I started last Sunday. I did some experiments with the script and so on so it has never been up more then 10 hours. In these 10 hours it was stable.
At this moment I have no intentions to change it again until the mysensors plugin has been extended
So, I will see how stable it is.
By the way: I copied your command without checking it. But the waitslave is wrong. It should be wait-slave.
Another way to make sure that socat restarts after a broken socket is to loop it like
while true; do
socat -d -d pty,link=/dev/ttyMS-Gateway,raw,echo=0,reuseaddr,forever,wait-slave tcp:192.168.38.19:5003 &>/dev/NULL
done
or better to make sure the OS has enough time to capture the SIGINT signal:
while sleep 1; do
socat -d -d pty,link=/dev/ttyMS-Gateway,raw,echo=0,reuseaddr,forever,wait-slave tcp:192.168.38.19:5003 &>/dev/NULL
done
If you put this in a script at startup of your RPi like in the /etc/init.d it should work constantly.
I did not try this one yet. Maybe in a few days. See what the stability is.
@Anduril
Today I lost connection. So my socat-pimatic connection is not stable either.
Added some files for the ethernet gateway, but can’t get it work 
Not enough knowledge.
https://github.com/sweebee/pimatic-mysensors#development
ethernet.coffee must be modified to get it working, just adopted it from the serialport.coffee and added the net module.
plugin config:
{
"plugin": "mysensors",
"driver": "ethernet",
"driverOptions": {
"host": "192.168.1.99",
"port": 5003
}
}
Maybe someone has time to look in to it with enough knowledge like @mwittig or @michbeck100 😇
File that needs to be fixed: https://github.com/sweebee/pimatic-mysensors/blob/development/ethernet.coffee
Error i got now:
16:41:56.080 [pimatic] Could not initialize the plugin "mysensors": this.connection.connect(...).then is not a function
16:41:56.081 [pimatic] TypeError: this.connection.connect(...).then is not a function
16:41:56.081 [pimatic]> at EthernetDriver.connect (/Users/Wiebe/pimatic-beta/node_modules/pimatic-mysensors/ethernet.coffee:19:34)
16:41:56.081 [pimatic]> at Board.connect (/Users/Wiebe/pimatic-beta/node_modules/pimatic-mysensors/MySensors.coffee:191:40)
16:41:56.081 [pimatic]> at MySensors.init (/Users/Wiebe/pimatic-beta/node_modules/pimatic-mysensors/MySensors.coffee:377:14)
16:41:56.081 [pimatic]> at MySensors.init (/Users/Wiebe/pimatic-beta/node_modules/pimatic-mysensors/MySensors.coffee:1:1)
16:41:56.081 [pimatic]> at PluginManager.initPlugins (/Users/Wiebe/pimatic-beta/node_modules/pimatic/lib/plugins.coffee:506:25)
16:41:56.081 [pimatic]> at /Users/Wiebe/pimatic-beta/node_modules/pimatic/lib/framework.coffee:891:34
16:41:56.081 [pimatic]> at tryCatcher (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
16:41:56.081 [pimatic]> at Promise._settlePromiseFromHandler (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:502:31)
16:41:56.081 [pimatic]> at Promise._settlePromise (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:559:18)
16:41:56.081 [pimatic]> at Promise._settlePromise0 (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:604:10)
16:41:56.081 [pimatic]> at Promise._settlePromises (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:683:18)
16:41:56.081 [pimatic]> at Async._drainQueue (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/async.js:138:16)
16:41:56.081 [pimatic]> at Async._drainQueues (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/async.js:148:10)
16:41:56.081 [pimatic]> at Immediate.Async.drainQueues [as _onImmediate] (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
16:41:56.081 [pimatic]> at processImmediate [as _immediateCallback] (timers.js:383:17)
16:41:56.124 [pimatic] A uncaught exception occured: Error: connect EHOSTDOWN 192.168.1.99:5003 - Local (192.168.1.21:54256)
16:41:56.124 [pimatic]> at Object.exports._errnoException (util.js:870:11)
16:41:56.124 [pimatic]> at exports._exceptionWithHostPort (util.js:893:20)
16:41:56.124 [pimatic]> at connect (net.js:849:16)
16:41:56.124 [pimatic]> at net.js:937:9
16:41:56.124 [pimatic]> at nextTickCallbackWith0Args (node.js:420:9)
16:41:56.124 [pimatic]> at process._tickCallback (node.js:349:13)
16:41:56.124 [pimatic]>From connect
16:41:56.124 [pimatic]> at Socket.connect (/Users/Wiebe/pimatic-beta/node_modules/pimatic/startup.coffee:55:29)
16:41:56.124 [pimatic]> at EthernetDriver.connect (/Users/Wiebe/pimatic-beta/node_modules/pimatic-mysensors/ethernet.coffee:19:23)
16:41:56.124 [pimatic]> at Board.connect (/Users/Wiebe/pimatic-beta/node_modules/pimatic-mysensors/MySensors.coffee:191:40)
16:41:56.124 [pimatic]> at MySensors.init (/Users/Wiebe/pimatic-beta/node_modules/pimatic-mysensors/MySensors.coffee:377:14)
16:41:56.124 [pimatic]> at MySensors.init (/Users/Wiebe/pimatic-beta/node_modules/pimatic-mysensors/MySensors.coffee:1:1)
16:41:56.124 [pimatic]> at PluginManager.initPlugins (/Users/Wiebe/pimatic-beta/node_modules/pimatic/lib/plugins.coffee:506:25)
16:41:56.124 [pimatic]> at /Users/Wiebe/pimatic-beta/node_modules/pimatic/lib/framework.coffee:891:34
16:41:56.124 [pimatic]> at tryCatcher (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
16:41:56.124 [pimatic]> at Promise._settlePromiseFromHandler (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:502:31)
16:41:56.124 [pimatic]> at Promise._settlePromise (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:559:18)
16:41:56.124 [pimatic]> at Promise._settlePromise0 (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:604:10)
16:41:56.124 [pimatic]> at Promise._settlePromises (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:683:18)
16:41:56.124 [pimatic]> at Async._drainQueue (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/async.js:138:16)
16:41:56.124 [pimatic]> at Async._drainQueues (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/async.js:148:10)
16:41:56.124 [pimatic]> at Immediate.Async.drainQueues [as _onImmediate] (/Users/Wiebe/pimatic-beta/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
16:41:56.124 [pimatic]> at processImmediate [as _immediateCallback] (timers.js:383:17)
16:41:56.124 [pimatic]> This is most probably a bug in pimatic or in a module, please report it!
@sweebee said:
Maybe someone has time to look in to it with enough knowledge …
OK, I’ll have a look at this.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
I mentioned in one of the posts above "By the way: I copied your command without checking it. But the waitslave is wrong. It should be wait-slave."
That is not correct:
As the socat solution is not a stable one I now made a rule combined on my “service” script and the small work around script.
The rule is based on the fact that if a “every 10 minute temperature sensor” is not updated after 35 minutes, so no connection for 3 measurements in a row, it sends me a message and stops pimatic/socat and restarts socat/pimatic.
{
"id": "mysensors-tuintemp-niet-veranderd",
"name": "mysensors_tuintemp_niet veranderd",
"rule": "if temperature of MSTemp2 was not updated for 35 minutes then execute \"sudo telegram-cli -W -e \\\"msg <User> The mysensors garden temperature has not been refreshed for more than 35 minutes\\\"\" and execute \"sudo /home/<user_id>/pimatic/scripts/restart_pim_socat.sh\"",
"active": true,
"logging": true
}
It works but actually we need a stable solution 
Hello,
do we have some news about the implementation of the ethernet gateway?
mfg
Chris
@sweebee
I wanted to take a look at your code on your github but you seem to have it removed. Do you still have a copy?
@Harry-van-der-Wolf Oh yes, i cleaned up my github. I probably have a backup. Will have a look.
@sweebee Thanks. Those 3 files were exactly the ones I thought I needed.
My coffeescript skills are extremely basic. Until now I only managed to create an extra sensor for the RF plugin for my own weather station. But I have programmed in about 10-11 languages (with different “dialects”) in the past 30 years (yes, I’m a little older 
), so I simply want to give it a shot.
Edit: I just forked the repo.