Windows GUI/Controller for MySensors

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

[tekka]

@pdey Filtering I_LOG_MESSAGE from the main message tab can be (de)activated in the settings.

[Mark Swift]

@tekka I've tried to apply @pdey 's change to the current dev branch; but due to the recent refactoring, wasn't successful - I'll keep trying.

Would you happen to have any other suggestions how we can get debug messages back to the controller from remote nodes? Some of my nodes are running some fairly complex code and without debug it becomes a tedious task.

Many thanks in advance,

Mark

[vikasjee]

Was @pdey 's change applied to the dev branch?

Any suggestions for debug messages to the controller from remote nodes?

@Mark-Swift said:

@tekka I've tried to apply @pdey 's change to the current dev branch; but due to the recent refactoring, wasn't successful - I'll keep trying.

Would you happen to have any other suggestions how we can get debug messages back to the controller from remote nodes? Some of my nodes are running some fairly complex code and without debug it becomes a tedious task.

Many thanks in advance,

Mark

[Harrdy]

My current running setup is a Arduino via USB-Serial attached to a Arduino with my Controller Software. But i want to use this Windows Controller at the same time. Anyone a idea how i can do this (local serial and serial2net at the same time on the same serial device)? if i start the serial2net my raspberry controller is broken and can't connect to the arduino usb serial but the serial2net work.

[tekka]

@Harrdy you can use the "GW mode" in the latest release and have your controller pointing to your PC's IP.

[Harrdy]

Thanks @ @tekka I saw the button "gw mode" but pimatic unfortunately only supports serial gateways. so if i use the "gw mode" i need a package like net2ser (instead of ser2net). But i think something like that does not exist

edit:
okay, it works with socat

sudo socat -d -d pty,link=/dev/ttyPimaticGW,raw,echo=0,waitslave tcp:192.168.170.32:5003;

[tekka]

@Harrdy cool, thanks for reporting 👍

[Anduril]

@Harrdy I made the experience that a socat tcp tunnel is not stable all the time. I was trying to establish a connection between my ESP8266 gateway and a serial port (to be used with pimatic), but that tended to disconnect after few hours/days. This was also reported by other users in the pimatic forum. But maybe this is only a problem in relation with a ESP gateway.
I would just recommend to check your connection regularly.
If it is also unstable for you, I am testing node-red for that purpose at the moment and it looks promising. I will report when testing is finished.

[techRH]

Maybe this helps any one else:
I run openHAB on a RPI3 and i have made a Mysensors serial GW on a arduino nano.
I want to use openHAB for the interface and MySController for the managment. So i need to forward my serial communication to a TCP socket.

ser2net is a nice tool works fast but it block the Serial connection for openHAB.
socat works better for me by executing the following command:
$ sudo socat tcp-l:5003,reuseaddr,fork file:/dev/mySensorsCOM,nonblock,waitlock=/var/run/mySensorsCOM.lock

next step will be to put it in a script and sends the process to the background and restarts it if there went something go's wrong.