Posts made by akbooer

Oh yes, my bad! Thanks.

@homer

Sorry I missed seeing your post. It should be just the IP address, same as running on Vera.

Did you get this to work?

AK

Thanks so much for that, I did wonder. My nodes include a old SenseBender node and I don't have an easy means to update this, so looks like I'll go for the older version.

I'm trying to build the above, following instructions here:
https://www.mysensors.org/build/raspberry

But I'm confused by the fact that the RPi branch here:
https://github.com/mysensors/Raspberry
says "DEPRECATED"

Is it the case that the RPi code is now part of the master branch?

I am trying to run a controller (openLuup) on the same board as the gateway. It appears to receive messages from the MySensors network, but inclusion fails (does nothing.) I'm somewhat at a loss as to how to proceed.

It all used to work so well 18 months ago with earlier versions and an Arduino Gateway. Is it a problem that I am using the latest gateway version, but my sensors are running an old (1.4?) firmware version?

Thanks for any guidance on this. It's quite a while since I did any Arduino development, so it's taking some time to get back up to speed. Lots seems to have changed (for the good!) in the meantime.

AK

It's been a while since I posted here, but openLuup has continued development and is now a really very capable controller with extensive plug-in compatibility with Vera. Latest version always available from GitHub here https://github.com/akbooer/openLuup

The latest version (Release 7) of openLuup is now available on GitHub here https://github.com/akbooer/openLuup

It supports a number of new features including

• no dependencies on system HTTP port 80 server (easier setup)
• remote access possible through weaved.com
• Lua modules as CGIs for easy functionality extensions
• sundry bug fixes and internal improvements

That's a really good price! A whole lot better than a Yún. I've not tried a Dragino but they seem to offer similar functionalities. I'm not sure about the details of the serial link handling for the bridge - if the bridge library has the same calls, it should work OK.

Just to put a footnote to the above (copied from another post - apologies, but it does belong here) ...

GitHub fork with the Yun Gateway

https://github.com/akbooer/Arduino/tree/development/libraries/MySensors/examples/GatewayYun

@zurli, Ive updated my GitHub fork with the Yun Gateway

https://github.com/akbooer/Arduino/tree/development/libraries/MySensors/examples/GatewayYun

I'm not near my development system for the next few days, but will post the Yún gateway on GitHub when I'm back.

@pdey So what controller are you running on the OpenWRT processor, or are you just using this as a serial gateway?

The latest version (Release 6) of openLuup is now available on GitHub here https://github.com/akbooer/openLuup

There's also now a section for this in the MySensors Controllers list http://www.mysensors.org/controller/openluup pointing to documentation as well as the code.

An active discussion board is here http://forum.micasaverde.com/index.php/board,79.0.html, with help from people who have installed this on different systems (Mac, Windows, Arduino, BeagleBone, RPi, Ubuntu, OpenWRT, Synology, ...) but also any questions welcomed right here too.

I've been using it as the main controller for my MySensors network for at least three months.

It's a force-directed graph, see https://en.m.wikipedia.org/wiki/Force-directed_graph_drawing

Actually built into the UI that I'm using (AltUI by @amg0) as part of my controller ( openLuup, see Controllers page) and it also runs on a Vera controller.

It's implemented in JavaScript in a browser.

@hek, No, not at all. Easy to set the status of a Vera device to failed, which gives a visual indication (albeit a somewhat misleading text message) on all versions of the UI (viz. UI5, UI7, and the impeccable ALTUI)

UI5:

UI7:

ALTUI:

This should certainly be possible to flag with some code changes to the Vera MySensors plugin. I'm taking a look at trying to merge the main branch and the UI7 versions, so will give it some consideration. Of course, someone else could always beat me to it!

Would a single value for all sensors be acceptable? I suspect not. In which case you'd need a neat way of specifying this on a per device basis.

The latest version (Release 5) of openLuup(cross-platform Vera emulator) is now available from the Vera BB here: http://forum.micasaverde.com/index.php/topic,32315.msg252150.html#msg252150

It runs the MySensors plugin (ethernet connection to gateway only) and I'm using it as my main HA controller for MySensors devices (and bridged to Vera for Zwave access.)

@BartE said:

So the problem is NOT controlling the device, but having the RGBController to startup correctly as child.

OK, here's my confusion: you can't have the Arduino plugin AND the RGBW Controller plugin both controlling the RGBW device. By definition, it is a child of the Arduino plugin and all functionality for that child device has to be provided by the parent. Are there, perhaps, some actions defined in the services or implementation file which are not, in fact, implemented by your additional code in the Arduino plugin?

@BartE OK, so the device D_RGBController1.xml is actually a child of the Arduino plugin, which handles (with your changes) the action call you showed. The problem, then is that @vosmont's plugin does not recognise this device as one it can control? Or is it that you are expecting, somehow, the colour wheel to work directly with the MYSensor plugin?

Sorry to be so dim about this, but I'd hate to be chasing up the wrong tree.

Just to start again from the beginning, you are trying to get the RGBW Controller plugin to work with MySensors RGBW devices. What I don't know is how MySensors presents an RGBW device - I am assuming you get a node with 4 child dimmers, but perhaps not? This is what a native Vera multi-colour dimmer typically does (eg. Fibaro.)

One problem I foresee is that the MySensors plugin is parent to all the MySensors devices, be they actual nodes or individual sensors, so you don't get the same logical grouping with one Vera RGBW device controlling its separate R G B W children (which is what, I think, @vosmont's controller requires.)

Happy to help. I've played a bit with @vosmont's RGB plugin when getting it to run under openLuup. It would be best if he could add a new device as part of the standard plugin - it does have some very specific code for different manufacturers. I guess I need to take a closer look at the workflow in the OP and try and understand what is needed and what is not working.

You mention an Arduino Yún. I don't know if this thread Ethernet Gateway on Arduino Yún is of any interest or help. It ports the gateway code to the Arduino bit enabling a controller to run under Linux on the same board.

Just tried out my first Sensebender...
soldered pins and battery power...
turn on...
led flashes once...
start inclusion...
3 devices...
Vera restarts (actually, it's openLuup running on an Arduino Yún)...
there they are...
and updating every minute!

Thanks so much to all who made this level of sophistication so easy!! (Z-wave was never this simple!)

Whilst I need a couple of temp/humidity sensors, I also need to reflash one as a 4-switch sensor. Can I do this with an Arduino Uno configured with the ArduinoISP sketch as described here ?
https://www.arduino.cc/en/Tutorial/ArduinoISP

Any advice or useful pointers? Thanks.

Oh no! Lousy timing, I just bought some...
... in fact, they arrived today.

Speaking of which, whilst I got them to run the default sketch, do I actually need a programmer to do anything different, or can this be done OTA (from a Mac) ?

@cyberthom said:

I want to run multiple Arduino sensors ( temperature )and send their data directly to the Raspberry over NRF24. So I have a NRF24L01+ connected to my Raspberry B . I have the NRF24 Libary downloaded from GitHub and I proceeded according to the following howto :
http://forum.mysensors.org/topic/1151/tutorial-raspberry-pi-nrf24l01-direct-connection

However, when I call PiGatewaySerial , it always stops at "check wires"

have checked the cables several times . The CPU load is at 100 % .
I had already seen this one thread , but found no solution . I have both PINs for CE connected, hardware PIN 22 and PIN hardware PIN 25.

Just to close the loop on the question in the original post...

@humblehacker said:

I wonder how difficult it would be to integrate the MySensors library with the bridge Library? In theory, doing so would eliminate the need for a separate controller altogether.

It turns out that it was not too difficult to add support for the Yún's Bridge library, details here: Ethernet Gateway on Arduino Yún

@humblehacker also said:

Support for Linino/Yun/OpenWRT would not only free up MiniPC hardware for use elsewhere but it would also allow you to merge together the gateway and the controller functions into a single board.

This also works, details of the controller I'm using in openLuup - a Vera emulator for all platforms

And to address this concern...
@daulagari said:

I think [...] Linino/Yun/OpenWRT would be too thin.

...it turns out that, in this case, it's not.

I am currently moving my 'production' HA system to a Yún where the Linux processor itself is running a configuration managing the MySensors network (yet to be fully populated), two WiFi connected Netatmo systems, the DataYours plugin suite logging key events to a Whisper (RRD) database on a CIFS-mounted remote NAS, the ALTUI interface, and a remotely bridged Vera with around 70 devices.

Even with the relative low-power processor the Linux cpu is only running at about 5% average loading and the whole system fits in around 10 Mbytes. Also, unlike Vera, it runs continuously and does not spontaneously reset.

Just by way of demonstration, here's an ALTUI-produced map of the current device network handled by the Yún (the purple spot in the middle.)

Success! I now have a functioning Ethernet Gateway running on a Yún using the Bridge library which connects the Arduino Yún to the on-board Linux processor.

The software changes are broadly those outlined here in an earlier post. I am more than happy to put this up on GitHub if someone can advise the best way / place for this (ie. should it be a a new file, say YunEthernet, or a conditional compilation of the main gateway, or what?)

It works with hardware SPI and again the wiring is as described previously (with earlier doubts now dispelled.)

There's two possible configurations:

• as a 'normal' gateway, addressable from the LAN (with the IP handing all done on the Linux processor)
• as a 'private' gateway, only addressable from the local host processor (as a controller)

The latter of the above options is the way I am currently running this, otherwise there's little point in using a Yún at all, with my own 'openLuup' Vera emulator running on the Linux processor using the standard Arduino plugin to link to the gateway.

I don't know about the speed of the Arduino/Linux bridge (it is reported elsewhere as being notoriously slow) but it seems very adequate for the job I am currently using it for (perhaps not a very heavy network load.)

Wondering, now, how to wire up the NRF module to the Yún. I'm following the Ethernet Gateway guide at http://www.mysensors.org/build/ethernet_gateway, but, of course, the pin configuration is different from that shown.

Am I right in assuming that I use the pins on the ICSP for SCK, MISO, and MOSI, then digital pins 5 and 6 for CE and CSN?

Also supposing that there's no need for software SPI in this case?

Advice most welcome! Thanks in advance.

Actually, I think there are thousands of approaches to this problem... it's certainly been well addressed in other HA fora.

I was rather intrigued by this scientific paper...

Through-the-Wall Sensing of Personnel Using Passive Bistatic WiFi Radar at Standoff Distances
http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6020778

...which claimed to detect presence using Doppler analysis of ambient WiFi signals at 2.4 or 5 GHz.

Not that there's a MySensors node for that yet, but I'd quite like to prototype one... or anyone else? (I was wondering if the NRF radio could be called into service as the RF front-end?)

Ah, well, thank you for that anyway.

Maybe it was the wrong question, but I hope to have solved the problem by discovering another server method 'print', which takes the right argument type. (A little knowledge is a dangerous thing.)

I'm trying to port the Ethernet Gateway sketch to an Arduino Yún using the Bridge library which connects the Yún to the on-board Linux processor (which will be running my controller.)

I've prototyped a stand-alone server which works well, so I know how to use the gateway. The port seems as though it should be straight-forward:

• no need to provide IP or MAC address, since this is handled on the Linux side
• EthernetServer --> YunServer
• EthernetClient --> YunClient
• Ethernet.begin() --> Bridge.begin()
• server.available() --> server.accept()

However...

I get a type conversion error at compile time on this line:

void output(const char *fmt, ... ) {
   va_list args;
   va_start (args, fmt );
   vsnprintf_P(serialBuffer, MAX_SEND_LENGTH, fmt, args);
   va_end (args);
   Serial.print(serialBuffer);
   server.write(serialBuffer);  // <-- ERROR HERE
}

with this diagnostic

Arduino: 1.7.6 (Mac OS X), Board: "Arduino Yún"

YunMSGateway.ino: In function 'void output(const char*, ...)':
YunMSGateway.ino:143:29: error: invalid conversion from 'char*' to 'uint8_t {aka unsigned char}' [-fpermissive]
In file included from YunMSGateway.ino:83:0:
/Users/akbooer/Documents/Arduino/Arduino 1.7.6.app/Contents/Java/libraries/Bridge/src/YunServer.h:35:20: error:   initializing argument 1 of 'virtual size_t YunServer::write(uint8_t)' [-fpermissive]
     virtual size_t write(uint8_t c);
                    ^
Error compiling.

So I guess the question is, simply, how do I coerce from char* to uint8_t ?

I know next to nothing about C or C++, but I have tried the simple (uint8_t) prefix with similar errors. I'm sure this is trivial and (hopefully) the only thing standing between me and a fully functioning Ethernet Gateway on the Yún.

Any help much appreciated.

This site has rather a good review of techniques http://dreamgreenhouse.com/projects/2013/presence/index.php

From a processing point of view, my favourite is the "Wasp in a Box" algorithm.

Does this thread shed any light on your issue?

http://forum.arduino.cc/index.php?topic=329990.0

It should have red bars above the icon.

I didn't think the gateway node supported attached sensors?

Yes, the Ethernet gateway library.

If you're not using a radio, how are you connecting to any sensor nodes?

I have a Uno and the same shield as you, although I connect to a Vera Edge. I'm using the V1.5 library on the Uno and a Nano for a sensor node.

Aside from the changing parameter for soft SPI, I compiled for both gateway and node with no trouble. On Vera I used the plugin from the UI7 branch of GitHub (are you using UI7 ?)

This is a very common setup, so should work OK... you HAVE configured your gateway IP address in the Vera plugin attributes?

Have you tried restarting Vera once the gateway is up and running, and then doing an include?

The usual Vera log /var/log/cmh/LuaUPnP.log should contain key messages from the nodes and plugin.

I use DataYours on Vera with CIFS-mounted NAS for data logging and display (but I am biased. I wrote it.)

To me, this is exactly the sort of low-level thing that should be done in a node. That way you don't load the controller or the network... and you can change controller in future and it will still work.

Shouldn't need a bunch of switches, just one 'mode' variable.

@rvendrame

Yes, I made a mod to the Arduino plugin. The changes are on GitHub:

https://github.com/akbooer/Vera/blob/features-for-altui/L_Arduino.lua

I'm hoping to get this merged with the master branch in due course, but I've not finished.

The point is that no one actually has a solution right now.

I see two ways forward, described here

http://forum.micasaverde.com/index.php/topic,27712.msg246892.html#msg246892

And here

http://forum.micasaverde.com/index.php/topic,28943.msg207265.html#msg207265

The second one requires us to do nothing but wait for a month (so they say) at which time the Vera firmware will be changed to reinstate the missing command.

The first approach is a pragmatic workaround which could be relatively easily coded in the modules I mentioned previously.

@blacey
You are, of course, right. The problem is that the plugin does not implement the TemperatureSetpoint1 service. Requires a small change to the I_Arduino1.xml file and possibly the Lua file too.

@leeoz said:

Sorry, I'm new to Lua and vera stuff so I don't understand what I need to do in order to fix it, or to find the error? I know c++ and c# so I familiar with programming but this is something I never done before.
my vera version: 1.7.1320
is this UI7?

Yes, it is.

The issue under discussion here is something which definitely needs fixing once and for all by a plugin developer familiar with Lua, and Vera, and UI5, and UI7, and thermostats. I fail on the last point (but can learn) and am taking a look at the issue now, although that certainly doesn't stop anyone else from giving it a go.

I notice that code has "NewCurrentSetpoint" and wonder whether it should not, instead, be "newCurrentSetpoint" ?

The latest version (Release 4) of the openLuup environment is now available from the Vera BB here: http://forum.micasaverde.com/index.php/topic,32315.msg246814.html#msg246814

It runs the ethernet gateway plugin and has been tested with both real sensors and emulated ones (Mock My Sensors) on Mac, BeagleBone Black, and Arduino Yun platforms.

I am now truly up and running with MySensors and, no doubt, drifting away from the Zwave world into a whole new and exciting one of homebrew devices. Thanks to all for the help along the way so far.

Well, thank you. But I have to say that the L&F is all down to the amazing ALTUI plugin produced by @amg0 on the Vera BB. I just do the behind-the-scenes bits which make it work on platforms other than Vera.

Ah, that's what I had read about the shield. So, just to confirm, with no changes at all, the ethernet gateway sketch can serve up to 4 different controllers simultaneously - the only interaction being through any state change of the MySensors nodes? That sounds like magic.

I've had to make some changes to openLuup to fully support the MySensors ethernet gateway, but now have it smoothly running cross-platform (Mac, BeagleBone, Arduino Yun.) At the moment, the gateway sketch does not run on the same board as the openLuup controller on the Yun, but the aim is to do that. I need to crack the Unix/Arduino bridge that comes with that device in order to achieve the goal of an integrated controller / gateway on the same board.

I new here, so likely to ask stupid questions... I'm led to believe that the gateway is stateless (sounds like a good plan) and I'm wondering if it's possible for an ethernet gateway to serve multiple controllers. It would presumably need to service multiple ports to do that, but I think that the shield I am using (5100) can do that.

I'm presuming that there would need to be minimal changes to the gateway sketch... but really asking if (a) this has been / could be done, and (b) if this is a really silly thing to be asking.

I'm most grateful for your work on this sketch - I've used it to exercise my gateway as I developed and debugged my Vera emulation environment called 'openLuup'. I now have a controller for MySensors running on Vera, BeagleBone Black, and an Arduino Yun, all running the ALTUI interface, so it looks like the attached.

Many thanks for the code and the initial explanations.

Serial: It probably works just fine, but I've always had a little trouble with serial devices on a Vera.

UI7 Latest release: Yes, a disaster, but the previous version is good.

ALTUI: Yes, it's excellent. Only difference UI5 vs. UI7 is the aforesaid house modes and the icons are a little different.

MySensors plugin: I've modified it to be ALTUI friendly: currently it displays the IP address of the gateway, but I will add number of nodes and sensors - this seemed like the most useful information?

The biggest change was really a new interface and the addition of house modes: home, away, night, vacation. Whether everything works depends on what devices you have. If it's mostly MySensors you're after, then all should be well, although are you using serial or Ethernet interface?

The UI7 interface is rubbish. Just use the fabulous ALTUI plugin instead.

@Drcashman reports (on the Vera forum) that openLuup works with the MySensors gateway, so that seems like good news.

I've just posted Release 3 of 'openLuup', which is a pure-Lua open-source emulation of the Vera Luup environment, on the Vera forum here: http://forum.micasaverde.com/index.php/topic,32315.msg244893.html#msg244893

I'm taking the liberty of mentioning this here partly because this release is the first which should run the Arduino gateway plugin - I'd love some help in testing because I've not yet got any Arduino sensors.

If you like Vera, but hate how it crashes often and would like it to run faster and more reliably on a different hardware platform, then this is the environment for you!

Release 3 is a quite extensive (but not complete) implementation of Luup, and includes a set of features which are generally sufficient to run a number of standard plugins.

What openLuup Release 3 does:

• runs on any Unix machine - I often run it within my development environment on a Mac (makes debugging easy.)
• also runs under Windows. However, plugins which spawn commands using the Lua os.execute() function may not operate correctly.
• runs the ALTUI plugin to give a great UI experience
• runs the Arduino plugin (ethernet connection to gateway only) which is really the main goal - to have a Vera-like machine built entirely from third-party (open source)
• includes a bridge app to link to remote Veras (which can be running UI5 or UI7 and require no additional software.)
• runs many plugins unmodified – particularly those which just create virtual devices (eg. Netatmo, ...)
• uses a tiny amount of memory and boots up very quickly (a few seconds)
• creates all devices on startup (this means they are numbered consecutively for those that worry about these things.)
• supports scenes with timers (but not triggers)
• has its own port 3480 server which supports multiple asynchronous client requests
• has a fairly complete implementation of the luup API and the HTTP requests
• has a simple to understand log structure - written to LuaUPnP.log in the current directory - most events generate just one entry each in the log.
• writes variables to a separate log file for ALTUI to display variable and scene changes.

What it doesn't do:

• Has no persistence – except for rooms and scenes. Persistence arises from either the remote Veras to which you bridge, or any database applications you may have (eg. DataYours). Your local device (plugin) structure is created by the startup code using standard luup calls.
• Doesn't have scene triggers (or notifications) – scene actions and timers ARE supported but triggers may be done differently. That functionality can be replaced with luup.variable_watch callbacks triggering scenes.
• Doesn't support the <incoming> or <timeout> action tags, but does support the device-level <incoming> tag.
• Won't run encrypted, or licensed, plugins.
• Doesn't use lots of memory.
• Doesn't do UPnP (and never will.)

I have tested it extensively under Debian (on BeagleBone Black), OpenWRT (on Arduino Yun), and Mac OS.

Any feedback from willing testers welcome! (I'm more than aware of the plethora of controllers out there, but this one is aimed at Vera lovers who want to branch out to other hardware.)

Thanks so much.

OK and thanks for the quick response!
I knew I knew nothing.

So, just to be sure, I run this on an Arduino with a radio, but not sensors. This is going to talk to my Arduino gateway, with radio, and either serial or ethernet connection to the controller, whichever I choose.

@barduino

Please excuse newness and ignorance (which go hand-in-hand.) Do I understand correctly that this sketch replaces a serial gateway? If so, what changes might be required to make this work for an ethernet gateway? Or, perhaps, do I have this all completely wrong?

I'm wanting to check out an ethernet connection between a Vera controller (or equivalent) and a Uno, on which I plan to run an internet gateway when I have built some sensors. Not yet having connected a radio, can I use this to mock up some sensors sending data to the Vera gateway plugin, just from an ethernet connected Uno?

Any help appreciated.

@hek said:

Did you create a Vera emulator??

Yes, details (some posts with images of ALTUI running on it) here: http://forum.micasaverde.com/index.php/topic,32315.msg235161.html#msg235161

Resurrecting a slightly old thread here, but I was wondering if there was any progress on the gateway running on a Yun?

A particular reason for asking is that I now have a fairly complete emulation of the Vera platform's Luup environment running on any generic Unix machine. I've recently put it on a Yun and it works a treat. Most Vera plugins work without modification, and I'm keen to integrate this with the MySensors gateway running on the Arduino processor on the same board.

As an aside, the 400 MHz cpu running OpenWRT is more than fast enough to make this an excellent controller. The web interface is provided by the excellent ALTUI plugin written by @amg0 on the Vera forum.