Windows GUI/Controller for MySensors

[Mouridsen]

Hi guys! I'm still a newbie but i'm very interested in this tool and I'm quite confused how to install it. I'm only interested in see the communication to start with.

Is there an installation instruction somewhere?

I have tried to install it but I can't see any serial ports in the config window. Here is what I have done:

1. Downloaded the package and run the program (I'm using Wine on a Mac)
2. Uploaded a the standard SerialGateway sketch from Mysensor to a Nano board and have it connected to the computer. I can see from the serial monitor in the Arduino IDE that it sees the communication fine from the various sensors.
   I haven't done anything to the Gateway that's connected to the Vera. Is it that one I should use and connect to the computer???

Sorry for the newbie questions..

[Mouridsen]

Well I found an old Windows laptop and it worked on that, so I guess it's the Mac computer :disappointed_relieved:
Yesterday I tried to make a Repeater with the standard sketch as instructed. Now I can see that it says: Undefined firmware/type. What is the reason for that???

30-03-2015 15:03:38 NODE: New node discovered, node id=34
30-03-2015 15:03:38 CHILD: New child discovered, node id=34, child id=internal
30-03-2015 15:03:38 DEBUG: Update child id=255, type=ARDUINO_RELAY
30-03-2015 15:03:38 RECV: 0;0;3;0;9;read: 34-34-0 s=255,c=3,t=6,pt=1,l=1:0
30-03-2015 15:03:38 RECV: 34;255;3;0;6;0
30-03-2015 15:03:38 SEND: 34;255;3;0;6;M
30-03-2015 15:03:38 RECV: 0;0;3;0;9;send: 0-0-34-34 s=255,c=3,t=6,pt=0,l=1,st=ok:M
30-03-2015 15:03:40 RECV: 0;0;3;0;9;read: 34-34-0 s=255,c=3,t=11,pt=0,l=13:Repeater Node
30-03-2015 15:03:40 RECV: 34;255;3;0;11;Repeater Node
30-03-2015 15:03:40 DEBUG: Undefined firmware/type for node=34
30-03-2015 15:03:40 RECV: 0;0;3;0;9;read: 34-34-0 s=255,c=3,t=12,pt=0,l=3:1.0
30-03-2015 15:03:40 RECV: 34;255;3;0;12;1.0
30-03-2015 15:03:40 DEBUG: Undefined firmware/type for node=34

I think it works because when I disconnect it stops sending messages to MYSController so all communication to this is done via the repeater.
Is it something to worry about???

[tekka]

@Mouridsen MYSController should work using Wine on Mac - for the serial communication, just type e.g. /dev/ttyUSB0 or whatever your GW is assigned to in the serial edit field. The "undefined firmware/type" message appears, if you use the standard arduino bootloader (e.g. optiboot). For OTA functionality, you can use MYSBootloader which will also transmit the firmware type/version to MYSController.

[Mouridsen]

@tekka Thanks, it works perfect. That was a quite easy fix :)

[tekka]

MYSController Version 0.1.2.278 released

New features:

• Support MYSBootloader 2.0 / SHA (signing bootloader) ==> will be released in the nearest future
• Support 1.5 framework (dev branch)
• Parse MySensors log/debug messages
• Div. options

Changelog:

• Moved send message dialog to main window
• Handler adjustments
• Bugfix FW upload in GW debug mode
• Bugfix message logging

Update via update button in MYSController or download here.

[derry]

Brilliant work! Ran perfectly under Wine on Fedora linux by using /dev/ttyUSB0 for serial port [after first checking my gateway was connected to that port]. Solved a problem I was having with a sensor getting assigned a weird node ID. Saved me loads of time tracking down the problem, many thanks for sharing this tool, much appreciated!

[rickmontana83]

This is awesome!

Any plans to provide source or a back-end API that could be used to connect this up to an HA controller? That way you could control everything downstream in the MySensors cloud from this app, and everything upstream (the HA controller and the cloud) could interface with a much richer (and presumably more robust) infrastructure rather than yet again figuring out how to parse the bits coming off of the serial port...

[ch3b7]

@rickmontana83 parse the data from the serial port is easy, im put in other post in this forum with a part of my code in vb.net

[tekka]

@rickmontana83 Serial API is described here.

[Francois]

@tekka once you flash the Arduino with the MYSBootloader is the only why that now you can programme the Arduino is though the MYSController software?

[tekka]

@Francois AFAIK, MYSController and NodeJsController (see framework, link here) are the only controllers that provide OTA updates via bootloader. Both controllers use the OTA protocol described here. However, MYSBootloader 2.0 will support updates OTA and via IDE.

[Francois]

@tekka the reason I asked I has a problem where I had 2 node with the same node ID and a could not do a OTA via MYSController. As i keep the same ID. I clear the EEPROM and still l it did not work. So the only why I could get the node working was to reflash the boot loader.

[tekka]

@Francois in general, if two nodes have the same ID, you have to disconnect one node and reassign ID/clear eeprom of the other node:

• MYSBootloader 1.1: use the bootloader commands in MYSController (right mouse click on the node, then reassign ID or clear EEPROM)
• MYSBootloader 1.0: upload the clear eeprom sketch and have the controller reassigning the ID

[Francois]

@tekka I doing this and still the node ID is not changing. I change this node to 4 and it still come up as Node 3. The reboot command also don't reboot the device. I have to do a manual reset on the device is this normal?

[tekka]

@Francois ok, I see - can you post or send the log (with debug mode on) to myscontroller at gmail dot com.
If the reboot command is not functioning properly you may have a corrupt routing table: Try clearing the routing table of the node & all routing nodes in between (right mouse click on the node in the routing panel|clear routing table) then try again to reboot.

[Francois]

@tekka will it be a problem if I don't have all my node on the MYSbootloader? Currently I only have 2 of my nodes with MYSBootloader. I am still testing before I change all the nodes

[tekka]

@Francois should be fine

[Francois]

@tekka log file send

[Francois]

@tekka See below it reboot the first time when I try it the seconde time it did
not it just say reboot

Here is my routing Tabel:

[tekka]

@Francois the node has AUTO ID or fix assigned ID (i.e. 91?) - if so, this may be an issue in the dev branch