Windows GUI/Controller for MySensors

[tekka]

@Dirk_H , @dzairo: yup, will include this option in the next update. Thanks for reporting.

[therik]

Thank you for this excellent work. I look forward to using it in my network. I just have a couple questions regarding setting up the GUI. I've read through this thread several times, but still have a couple of gaps in my understanding.

1. Is the gateway that interfaces with the GUI an additional gateway which listens to, and sends node messages and updates? That is, additional to one that is interfaced with the controller (in my case a serial gateway connected to a Vera controller)?

2. If my the answer to my first question is, yes, it is an additional gateway, is the code defining the operation different such that is does not interfere with the 'true' gateway? Or is the code the same (standard serial gateway sketch) but simply does not interfere?

3. Do the nodes require the MYSBootloader in order to show up in the 'messages' tab, or will 'messages' tab show all node traffic regardless of bootloader? Of course for over the air (OTA) sketch updates it needs the MYSBootloader.

4. Are these the correct steps to setup operation:

a) download and extract the files.

'b) place the bootloader folder into /arduino/hardware path such that the MYSBootloader and the associated boards show up in the 'tools->boards' menu.

c) connect an Arduino with the gateway sketch to a computer using a USB cable (for the serial connection).

d) run MYSController.exe (on windows) and select the COM port of the serial gateway in the configuration.

e) hit connect and node traffic will show up in the 'messages' tab.

If this is correct (and now that I write it down) it seems pretty straightforward, but I didn't see it explicitly described elsewhere. Sorry to be such a beginner, and thanks for straightening me out if I'm incorrect in any step.

[tekka]

@therik said:

Is the gateway that interfaces with the GUI an additional gateway which listens to, and sends node messages and updates? That is, additional to one that is interfaced with the controller (in my case a serial gateway connected to a Vera controller)?

No, but certainly a good idea to look into.

Do the nodes require the MYSBootloader in order to show up in the 'messages' tab, or will 'messages' tab show all node traffic regardless of bootloader? Of course for over the air (OTA) sketch updates it needs the MYSBootloader.

No, the MYSBootloader is required for OTA updates with MYSController or compatible controllers.

Are these the correct steps to setup operation:

a) download and extract the files.

'b) place the bootloader folder into /arduino/hardware path such that the MYSBootloader and the associated boards show up in the 'tools->boards' menu.

c) connect an Arduino with the gateway sketch to a computer using a USB cable (for the serial connection).

d) run MYSController.exe (on windows) and select the COM port of the serial gateway in the configuration.

e) hit connect and node traffic will show up in the 'messages' tab.

Yes, that's pretty much it. Copying the bootloader directory is only needed for updating to MYSBootloader via ISP.

[tekka]

@Dirk_H , @dzairo BAUD option included in the latest release. Update via software or here.

[pit007]

@tekka Hello, I check your great software and do my first steps with mySensors.

It looks very amazing!

Here are my first comments:

1. I must program the MYSBootloader with the H-fuse setting H:0xD8 (2048 word), the value H:0xDE (in your fuses.txt) or H:0xDA (in your boards.txt) didn't work for me.
2. The blink.hex seems to be the normal blink sketch, it didn't have nrf24 functionality. Needs a local hardreset to flash other firmware.
3. The Arduino IDE (with the enhanced boards.txt) isn't able to program a firmware with the MYSBootloader - think this results in the higher baud rate (115200 vs. 57600) and my case to have the Arduino running in a VM !?
4. The update function in MYSController isn't working because it needs a proxy configuration (not imported).
5. I got a warning sign on the nodes-tree, don't know what it mean, but node is working (no info in the context menu).
6. The interrupt line of the ner24L01 isn't needed.
7. A right click in the open context menu ( e.g. on clear firmware) forces a software error.
   8 ) After connecting the Serial GW the MYSController doesn't responce for a while (searching for nodes?) Maybe a background task or an indicater would be a idea ?!
   9)On XP (or XP style) a selected row in the mesages or nodes tab is not readable - the selection is in dark blue, the text in black.

It should be possible to use the MYSBootloder (.hex) without changes also for 8Mhz nodes (internal RC L:0xE2), OTA only.
The SPI is independent from the clock, Uart is not used, delays are 2 times longer but this should be no problem.

Is there a scenario to keep your MYSController connected and have the mash working at the same time?
For example, with a gateway connected at Raspberry PI and a TCP connection from MYSController to the RPI? Or with two gateways ?

Looking forward for the next features :-),
regards Pit

[tekka]

@pit007 Thanks for your feedback.

1. I must program the MYSBootloader with the H-fuse setting H:0xD8 (2048 word), the value H:0xDE (in your fuses.txt) or H:0xDA (in your boards.txt) didn't work for me.

Ups, this is a mistake in the fuses.txt file, I will update that. The settings in the boards.txt are correct.
The MYSBootloader 1.0 is 1834 bytes in size, therefore 0xDA works (1024W), but 0xD8 (2048W) is also ok (assuming you are programming the atmega328p). All calls are relative, and the MCU skips invalid commands (0xFF) until it starts parsing at 0x7800.

2. The blink.hex seems to be the normal blink sketch, it didn't have nrf24 functionality. Needs a local hardreset to flash other firmware.

yep, correct :)

3. The Arduino IDE (with the enhanced boards.txt) isn't able to program a firmware with the MYSBootloader - think this results in the higher baud rate (115200 vs. 57600) and my case to have the Arduino running in a VM !?

With MYSBootloader 1.0 you can only program a firmware with MYSController or similar tools. I'm currently working on a dual bootloader that includes OTA and Arduino IDE/AVRDude programming.

4. The update function in MYSController isn't working because it needs a proxy configuration (not imported).

Hmm, I assume you are referring to the check for updates function (automatically triggered after startup)? I will look into that.

5. I got a warning sign on the nodes-tree, don't know what it mean, but node is working (no info in the context menu).

The warning sign means no version/type information received. This information is sent during MYSBootloader startup, but not with conventional (e.g. optiboot) bootloaders.

6. The interrupt line of the ner24L01 isn't needed.

The communication is entirely controlled by the gateway - and yes, the interrupt pin is not used in the current gateway setup.

7. A right click in the open context menu ( e.g. on clear firmware) forces a software error.

Please send a screenshot to myscontroller@gmail.com

8 ) After connecting the Serial GW the MYSController doesn't responce for a while (searching for nodes?) Maybe a background task or an indicater would be a idea ?!

Please check the debug tab: any truncated messages or error flags after startup?

9. On XP (or XP style) a selected row in the messages or nodes tab is not readable - the selection is in dark blue, the text in black.

ok, will look into that.

It should be possible to use the MYSBootloder (.hex) without changes also for 8Mhz nodes (internal RC L:0xE2), OTA only.
The SPI is independent from the clock, Uart is not used, delays are 2 times longer but this should be no problem.

Yes, 8Mhz should work, but ideally you recompile the bootloader with F_CPU set to 8 Mhz for correct delay timings.

Is there a scenario to keep your MYSController connected and have the mash working at the same time?
For example, with a gateway connected at Raspberry PI and a TCP connection from MYSController to the RPI? Or with two gateways ?

Not yet, but I have some ideas...

Have fun

[slarti]

Hi and thanks for a cool piece of software!

I finally got around to soldering an ethernet gateway and decided to give this a spin. It worked like a charm for a while but now I get this error everytime any message goes through the gateway to Vera:

OS is 32-bit Windows 7

I can only get rid of this behaviour if I delete the configuration settings file and start over. It seems it only happens if I have logging enabled and exit the program and restart it.

I'll have to start playing with the bootloader soon to get the OTA capabilities.

[dzairo]

Hi.
Just one idea .. your tools is very good .. why not add more better function ..
1.If not received data from sensor more than predefined time then send email or tweet .. etc. for example using https://www.pushingbox.com/
2. Make server version .. for web interface ..
I thinks .. is possible order in TESCO cheap windows 8.1 tablet in price 90Euros ..
one or two year later then will be possible buy in price around 50 euros .. why not use this platform?
I use ASUS with USB serial port and work good .. if make easy uart to wifi (esp8266) converter then can work directly with wifi..

[tekka]

@slarti I've seen this error if the log file is exclusively opened somewhere else. Try deleting or renaming the current logfile and restart the MYSController. I will change the log file handling in a upcoming release.

[tekka]

@dzairo certainly an interesting idea! Please have a look at one of the discussed home automation solutions - there you can even define more complex scenarios.

[dzairo]

yes.. I just that user use RPi etc hardware solution .. but in fact
is possible buy tablet .. complete solution : standard windows 8.1 , LCD , battery .. wifi , bluetooth .. CE .. why not use this platform ..
give link for - home automation solution..

regards..

PS: you can see , I my self make similar software for windows ..but more easy .. and why not use windows core for server , database .. etc ..

[Justin Lim]

@tekka This GUI is great help especially for beginners like me who don't understand what the serial messages mean! You extract all the information so well and so beautifully.
Hope its not too much to ask, but may I take a look at the source code? Because I need to know the method you used to extract the messages, as well as tying the data to the proper fields. I somehow need to push all of these data to the proper fields in my database and I'm stuck at deciphering the messages being received. Thanks in advance and cheers!

[Anticimex]

This is a nice tool. Good work! Is there any possibility to get support for all the message types on the development branch as well?

[tekka]

@Anticimex Thanks :) Yes, I in the upcoming release.

[dzairo]

Hi.
One idea .. FIFO buffer for outgoing message..
low power relay node .. if use bi stable relay then is possible to power only from battery .. but radio must go to sleep.. then wake up every 5 or 10 second .. and ask gateway for new command ..
node just if wake up then waiting for example 0,5 sec for incoming message .. if not received then go sleep ..
gateway wait for node .. and if got command in FIFO for this node then send message ..
just idea..

[tekka]

@dzairo excellent idea, this will be implemented in the .276 release. Thanks

[dzairo]

Hi.
...ehm , in Windows is possible use database and install web server .. you have idea use this?
database is good way , pls try thinking about my idea using cheap windows tablet as controller , by serial port (usb) or lan (wifi ..etc) . .. problem is that tablet memory is not good for many write cycle .. but this is possible solve ..
best regards

[blackdog65]

Hi Tekka,
Great tool and SO useful for debugging.
I have MYSController running under Wine on Linux Mint with no problems.

I do have one small issue though. I have a serial gateway that reports to Domoticz on my Mint PC. This works fine and MSController connects fine. When I tried to move my gateway to a remote installation of Domoticz on a Raspberry Pi (same network) MSController cannot see it if I try to connect by TCP. I hope it's just something silly like port no. or something, but any ideas?

Many thanks

[tekka]

@blackdog65 You will have to pipe the serial gateway via tcp:port with e.g. ser2net.

[blackdog65]

@tekka WOW! I thought that was going to be SO difficult... but it took 10mins total! Thank you very much... I'm good to go ;)