Windows GUI/Controller for MySensors

[DomoJimbo]

@tekka

Hi tekka,

I have tested MYSController, and it was a massive success ! thanks a lot for your work.

I have just one question, in the csv file there is a type.
According to my reading this is to tag a node type, but where are the already known types ?
Type 1 => only temperature
Type 2 => only humidity
Type 3 => temp & hum
etc
Is there another config file where to specify user types ?

Type,Name,Version,File,Comments
10,Blink,1,Blink.hex,blinking example
20,TimeReporter,1,TimeReporter.hex,TimeReporter
100,Sensebender Micro,1,SensebenderMicro.cpp.hex,Sensebender Micro
110,Sensebender Blink,1,SensebenderBlink.cpp.hex,Sensebender Blink

[pdey]

@hek - would it be possible to get a subforum for MYSController stood up in the Controllers forum? This thread is getting pretty long and off topic (also, the RSS feed stops at the 27th post)

[hek]

I'll have a talk with @tekka about it. But you always have the optaion to start a new thread.

[tekka]

@DomoJimbo No, you are free to choose the node types. This information is used for OTA FW updates.

[ThomasDr]

Hello,

for Linux, it works with wine, with TCP and serial.

regards
Thomas

[MarkV]

@tekka

I'Ve done the steps witch you describe but it doesn't show up in the ArduinoIDE.
Step 1, added the lines to boards.txt
Step 2, made a directory \MySensors under
D:\Program Files\Arduino\hardware\arduino\avr\bootloaders
Step 3, copied the .hex file into D:\Program Files\Arduino\hardware\arduino\avr\bootloaders\MySensors

What did i do wrong???

[cdr]

@MarkV you might want to check your "AppData" folder, I noticed the same behaviour and had to change boards.txt in this location.

C:\Users{{user}}\AppData\Local\Arduino15\packages\arduino\hardware\avr\1.6.10

GL

[Mark Swift]

Guys,

I'm trying to get this working with my nano clone but am having no luck.

When I flash the boot loader the nano doesn't send the request (the light on the nano comes on red and stays on).

I'm presuming it's because I haven't updated the fuse settings etc for the nano? Would someone be so kind as to offer some help with regards what I need to change?

Edit: I'm up and running!

[Mark Swift]

Did anyone figure out how to get MySensors debug messages to show? My sketch has debug uncommented and I can see them via serial, but not in the app?

[tekka]

@Mark-Swift The MySensors debug tab only shows gateway debug messages (not sensor debug).

[Mark Swift]

@tekka Yeah, I get that, that's what I'm struggling with. I have the debug line uncommented on my ESP8266 gateway, but see nothing in the mysensors debug tab? I'm using the latest beta build as I run 2.0.0.

Also, I've asked a couple of times, is the default firmware pre release 1.3 bootloader (16mhz) suitable in its default state for both my Uno's and Nano's?

Thanks in advance,

Mark

[tekka]

@Mark-Swift the ESP8266 GW is not sending debug msgs over TCP/IP - only over the serial console.
And yes, MYSBootloader 1.3pre/16Mhz is suitable for Uno and Nano V3 (both share the same atmega328p mcu)

[Mark Swift]

@tekka That explains it then :) Thank you very much for the confirmations!

[pdey]

@Mark-Swift : If you're happy to modify the MySensors library in an unsupported way, I've added a logMessage function to transmit text/debug messages from remote nodes:
https://github.com/peterdey/MySensors-Arduino/commit/f5f339b71620ec3cd896304a2ca6aba40ad40218

Found it useful, particularly in conjunction with MYSController OTA firmware updates.

[Mark Swift]

@pdey Let me get this straight, this allows me to see the serial debug messages from my nodes running the modified boot loader? That would be a dream come true, I really miss debug messages...

Thank you!

[pdey]

@Mark-Swift: You'll need to replace Serial.Print with node.logMessage - but yes, I use it for transmitting debug messages, wirelessly, to the controller.

No gateway modifications required (the gateway will just pass the message over to the controller). Old versions of MYSController (e.g. 0.1.2.276) would actually show the debug messages as a LOG_MESSAGE in the "Messages" tab; later versions hide it away in the "Debug" tab.

[Mark Swift]

@pdey That's fantastic, the only thing I was missing with the modified boot loader was debug...

@hek @tekka Any reason why we can't implement this into development, it seems a great feature.

Now if I can only figure out how to apply @pdey 's fix to the current dev branch....

[gonzalonal]

Hi @tekka ,
Just starting testing beta version and it looks really nice. Thanks for sharing this great tool.
I usually use it to debug mysensors network.

I think I have found a little bug regarding message subtype.
For example, when I choose to send a message using as subtype V_VAR1, it sends out as V_VAR4.
To actually send it as V_VAR1 I have to choose as Subtype V_HVAC_FLOW_STATE.

Can someone try this in their MYSController Beta 1.0.0beta so as to verify if it is only happening to me, or is a funny bug in the beta.

Once againg, thank you very much.
Regards.
Gonzalo

[Dirk_H]

@gonzalonal @tekka
Yes I can confirm the exact same behaviour gonzalonal describes. Please say if you need any more details tekka (with the @ function).

[tekka]

@Dirk_H @gonzalonal This has been fixed in the most recent build (3314). Thanks for reporting.
=> update pushed.