Windows GUI/Controller for MySensors

[tekka]

@diamantmatch The link to the log file is broken (currently, the forum experiences some issues with uploading files / pictures. Can you share it on e.g. dropbox and post the link?).
I've come across similar issues with debug mode activated on the GW sketch - try reflashing the GW with debug mode disabled and give it another shot.

[hek]

@tekka said:

the forum experiences some issues with uploading files

@diamantmatch
I have cherry-picked a couple of patches that should fix file-uploads now. Please try to re-upload your log file. Downloading your logfile works again.

[diamantmatch]

@tekka
Awesome! everything now works like a charm! many thanks for your help!

[5546dug]

@tekka I am still a bit confused after rereading this thread.

I have a humidity sensor plugged by usb and using config and debug see this sensor.
Question is for the full gui do I need to unplug serial usb from gw and plug it into computer and start your program?

If this is correct, then it will be temporarily disconnected from vera3 controller while I study and learn to understand what is being presented to me, when I again config and debug.

After reviewing then reconfigure gw back to vera?

[Francois]

@tekka I update my bootloader to MYSbootloader and the fuses as per the doc but now when I try to program the Arduino mini pro I get this error can you help?

[tekka]

@5546dug MYSController connects directly to the gw to interact with the nodes.

[tekka]

@Francois said:

@tekka I update my bootloader to MYSbootloader and the fuses as per the doc but now when I try to program the Arduino mini pro I get this error can you help?

That's correct: with the MYSBootloader you can upload the firmware OTA only - use MYSController to upload new fw

[5546dug]

thank you @tekka , will try it.

[pit007]

@tekka A further small bug or misunerstanding by us - the unix time:

API:
I_TIME 1 Sensors can request the current time from the Controller using this message. The time will be reported as the seconds since 1970 = unix time ?

The MYSController send the local time, but not the unix time (the unix time is the same all over te world)

[5546dug]

@tekka what does the dc =1 mean in this example?
I understand the s c t pt and l but not d c

is the humidity sensor ok?
pro mini
serial gw nano to win 8.1 via usb interface
ver 1.4
lib 1.4
humidity sketch mysensors

readings seem accurate

also have temp read 30 sec and hum read when changes only

is all well or issues?

thanks

[tekka]

@5546dug dc=1 indicates that the message is truncated (i.e. you lack the first part of the telegram, see below). Please make sure, that you are running the most recent version of the library, i.e. 1.4.1.

Your messages lack the bytes in bold:

3/25/2015 23:24:29 RECV: **5;0;1;0;1;**send: 5-5-0-0...etc

[JeJ]

You seem to have a sensor connected to your MYSController and not a gateway.
Maybe wrong serialport?

/J

[tekka]

"
@JeJ indeed, you are right. thanks!

[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...