Windows GUI/Controller for MySensors
-
correct. you build the .hex file in arduino studio or whatever and copy it to the MY gui firmware folder and edit the csv file and then reload.
http://forum.mysensors.org/topic/1066/bootloader/8
This should help
-
I thinking I am build a DEBUG version of the GW code. but I dont think the logging is working in the app with my eth GW. am I mising something?
So. when I build a DEBUG version of the GW code I get this in the serial console hex size=29k so its bigger.
0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:71.6
1;1;1;0;0;71.6
0;0;3;0;9;read: 2-2-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2;1;1;0;16;0the NON DEBUG I get this. hex size = 26k
1;1;1;0;0;69.8
1;0;1;0;1;35.0
1;1;1;0;0;71.6
1;0;1;0;1;36.0
1;1;1;0;0;73.4
1;0;1;0;1;37.0
2;1;1;0;16;0 -
I thinking I am build a DEBUG version of the GW code. but I dont think the logging is working in the app with my eth GW. am I mising something?
So. when I build a DEBUG version of the GW code I get this in the serial console hex size=29k so its bigger.
0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:71.6
1;1;1;0;0;71.6
0;0;3;0;9;read: 2-2-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2;1;1;0;16;0the NON DEBUG I get this. hex size = 26k
1;1;1;0;0;69.8
1;0;1;0;1;35.0
1;1;1;0;0;71.6
1;0;1;0;1;36.0
1;1;1;0;0;73.4
1;0;1;0;1;37.0
2;1;1;0;16;0@p0lar said:
So. when I build a DEBUG version of the GW code I get this in the serial console hex size=29k so its bigger.
0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:71.6
1;1;1;0;0;71.6
0;0;3;0;9;read: 2-2-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2;1;1;0;16;0that looks good :)
-
Still nothing in the MySensors Debug tab... and only the NON debug info in the log files. maybe this is a ethernet GW issue? So I get debug info in the Arduino Serial monitor but no debug via TCP?
[GENERAL]
VERSION=0.1.2.282[COMMUNICATION]
COM=COM1
SPEED=4
IP=10.1.1.200
PORT=5003
TCPACTIVE=1[STATUS]
LOGGING=1
DEBUGGING=1
SENDMSG=1
LOGPARSE=1
AUTOFW=0
AUTOID=1
UTCTIME=0
CLOSECONFIRM=0
FILTERLOG=1
SAVENODES=1
METRICSYSTEM=0 -
@tekka : I tested the ID reassign by hardcoding the functionality in the serial gw sketch. Reboot node 6, wait for FW_CONFIG_REQUEST, answer with FW_CONFIG_RESPONSE.
Works as expected & described in the MYSBootloader code. Please give me some hint why MYSController does not send the FW_CONFIG_RESPONSE packet with the bootloader commands after the reboot.
I trigger the reassign via the node´s context menu in the gui, MYSBootloader Commands --> reassign ID. Anything wrong with that ?
Maybe someone else has an idea what is happening/not happening ? @tekka could you find something in the log file?
Thanks a lot...
-
Has anyone tested successfully reassigning the node-id with MYSBootloader 1.1 and MYSController 1.2.282 ? Would give me some new motivation to hear it's possible and has been done before. At the very moment I m at a dead end.
If it is not working for you, I would also appreciate your feedback. -
@tekka
Is the (dev branch) MQTTClientGateway supported by MYSController?I'm in the process of moving from Vera and Ethernet GW, to Openhab with MQTTClient gateway and would love to have the OTA functionality your bootloader and controller provides. I looked at this a while back, but ran out of time to play!
So yeah.. Can MYSController talk with the MQTTClientGateway ( over Ethernet) ?
Cheers,
Greg -
In answer to my own question... No..it doesnt seem to.. ;-(
I tried with the IP address of my MQTT client gateway board, and port 5003 ( same port that works for my 1.4 Ethernet GW )
It says it connects, but no data flows in....@tekka @hek - Is it unlikely that the MQTTClient Gateway will be usable with MYSController??
If not, would this work?
Have two networks -
1 for MYSController to perform OTA's using a serial gateway on the PC we typically do sketch changes on.2 for normal MySensors operation. When you want to invoke an update, you could send a I_REBOOT command ( MQTT message in my case), which would reboot the node and if i understand correctly, look for an update on the other network channel.
I guess you would loose all the other functionility of MYSController, but at least we could do OTA.
Cheers,
Greg -
Has anyone tested successfully reassigning the node-id with MYSBootloader 1.1 and MYSController 1.2.282 ? Would give me some new motivation to hear it's possible and has been done before. At the very moment I m at a dead end.
If it is not working for you, I would also appreciate your feedback. -
In answer to my own question... No..it doesnt seem to.. ;-(
I tried with the IP address of my MQTT client gateway board, and port 5003 ( same port that works for my 1.4 Ethernet GW )
It says it connects, but no data flows in....@tekka @hek - Is it unlikely that the MQTTClient Gateway will be usable with MYSController??
If not, would this work?
Have two networks -
1 for MYSController to perform OTA's using a serial gateway on the PC we typically do sketch changes on.2 for normal MySensors operation. When you want to invoke an update, you could send a I_REBOOT command ( MQTT message in my case), which would reboot the node and if i understand correctly, look for an update on the other network channel.
I guess you would loose all the other functionility of MYSController, but at least we could do OTA.
Cheers,
Greg -
@gregl MYSController is currently not supporting MQTT, I'll add it to my feature request w/o ETA.
@tekka You might not have to. I've been working on Node-Red as a controller and more.
With my kit, you need Node-Red, node-red-contrib-mysensors , Mosquitto, and some of my flows which I have available ( http://forum.mysensors.org/topic/2802/flow-to-turn-serialgateway-into-mqtt-serialgateway ).
And it makes this:
http://forum.mysensors.org/topic/2815/flow-to-turn-serialgateway-with-mqtt-flow-to-ethernetgatewayThe only flaw is that when you first connect MYSController, you need to send a junk topic so that MYSController can receive data. It's a bug/peculiarity with Node-Red, but honestly not a big deal. I'm also working on how to fix even that.
-
First time i try OTA. Everything went well until fw update (Pro mini). It sends/recieve like 20-30 packages, and then ends. I need to reconnect Myscontroller and it will start to flow again. I can see there is requests from node on gw led, but nothing comes through in Myscontroller (.282). Using 2.0b ethernet gw. Its just like either GW stops sending to Myscontroller or Myscontroller doesnt accept it. Also getting in domoticz that "MySensors: Connection reset!" Do i need to disconnect Domoticz while I do updates?
Any clues?
Edit: Sorry, jepp - needs to disconnect Domoticz and it works... I bet its those new gateway pings from Domoticz killing it.
-
A quick one: How long does the OTA takes for Blink sketch?
I press update FW, it start rolling and the node changes status from "fw updating" to "booting" but then goes back to fw updating... have been going like this for a long time now (1000 packages sent/recieved).
Also - is it possible to upload via fdti with MYSBootloader or you need to use OTA?
Edit: somethings is not right, its rebooting or starting over again:
2016-01-16 21:09:41 RX 14;255;4;0;2;0A0001002F00 2016-01-16 21:09:43 TX 14;255;4;0;3;0A0001002F008083E1EBF0E0808184608083E0EBF0E0 2016-01-16 21:09:43 RX 14;255;4;0;2;0A0001002F00 2016-01-16 21:09:45 DEBUG Undefined firmware/type for node=14 2016-01-16 21:09:45 INFO BL version=257 2016-01-16 21:09:45 INFO Send FW info to node 14: type=A, version=1, blocks=0x0048, CRC=0xD098 2016-01-16 21:09:45 TX 14;0;4;0;1;0A000100480098D0 2016-01-16 21:09:45 RX 14;255;4;0;0;FFFFFFFFFFFFFFFF0101 2016-01-16 21:09:46 DEBUG FW update started, node id = 14 2016-01-16 21:09:46 TX 14;255;4;0;3;0A0001004700E1F30E940000F9CF0895F894FFCFFFFF 2016-01-16 21:09:46 RX 14;255;4;0;2;0A0001004700 2016-01-16 21:09:47 TX 14;255;4;0;3;0A0001004700E1F30E940000F9CF0895F894FFCFFFFF 2016-01-16 21:09:47 RX 14;255;4;0;2;0A0001004700 2016-01-16 21:09:48 TX 14;255;4;0;3;0A00010046002C020E947000C0E0D0E00E948B002097 -
Fortunately a helpful guy gave me your bootloader 1.3 beta, which fixes the problem with nonworking bootloader commands. It seems I was not the first one asking you...
For all others trying the bootloader commands in bootloader 1.1 : this does not work at all, and you are only wasting your time.
I would really appreciate if the code for bl 1.3 was on github also. I do not mind if its beta only...
Below the working debug output for a reassign nodeid 8 --> nodeid 88
16.01.2016 23:06:46 RX 8;255;3;0;9;0108A000B9F7FFFEDA7221F0001E950F09 16.01.2016 23:06:48 RX 0;0;3;0;9;read: 8-8-0 s=255,c=4,t=0,pt=6,l=10,sg=0:1E00010048047AA801 16.01.2016 23:06:48 INFO BL version=259 16.01.2016 23:06:48 INFO Executing bootloader command section 16.01.2016 23:06:48 TX 8;255;4;0;1;0200580000007ADA 16.01.2016 23:06:48 RX 8;255;4;0;0;1E00010048047AA80103 16.01.2016 23:06:48 RX 0;0;3;0;9;send: 0-0-8-8 s=255,c=4,t=1,pt=6,l=8,sg=0,st=ok:02005800000 16.01.2016 23:06:48 RX 0;0;3;0;9;read: 88-88-255 s=255,c=3,t=7,pt=1,l=1,sg=0:0 -
Fortunately a helpful guy gave me your bootloader 1.3 beta, which fixes the problem with nonworking bootloader commands. It seems I was not the first one asking you...
For all others trying the bootloader commands in bootloader 1.1 : this does not work at all, and you are only wasting your time.
I would really appreciate if the code for bl 1.3 was on github also. I do not mind if its beta only...
Below the working debug output for a reassign nodeid 8 --> nodeid 88
16.01.2016 23:06:46 RX 8;255;3;0;9;0108A000B9F7FFFEDA7221F0001E950F09 16.01.2016 23:06:48 RX 0;0;3;0;9;read: 8-8-0 s=255,c=4,t=0,pt=6,l=10,sg=0:1E00010048047AA801 16.01.2016 23:06:48 INFO BL version=259 16.01.2016 23:06:48 INFO Executing bootloader command section 16.01.2016 23:06:48 TX 8;255;4;0;1;0200580000007ADA 16.01.2016 23:06:48 RX 8;255;4;0;0;1E00010048047AA80103 16.01.2016 23:06:48 RX 0;0;3;0;9;send: 0-0-8-8 s=255,c=4,t=1,pt=6,l=8,sg=0,st=ok:02005800000 16.01.2016 23:06:48 RX 0;0;3;0;9;read: 88-88-255 s=255,c=3,t=7,pt=1,l=1,sg=0:0@stebra The 1.3 is a closed beta and is not supposed to be distributed (ping @niccodemi). It is not supported in any terms nor should it be used in a productive environment, the compatibility to any library version is not guaranteed.
Currently, there is ongoing work for MYSBootloader 2.0 and the ETA is tbd, same for the code. -
A quick one: How long does the OTA takes for Blink sketch?
I press update FW, it start rolling and the node changes status from "fw updating" to "booting" but then goes back to fw updating... have been going like this for a long time now (1000 packages sent/recieved).
Also - is it possible to upload via fdti with MYSBootloader or you need to use OTA?
Edit: somethings is not right, its rebooting or starting over again:
2016-01-16 21:09:41 RX 14;255;4;0;2;0A0001002F00 2016-01-16 21:09:43 TX 14;255;4;0;3;0A0001002F008083E1EBF0E0808184608083E0EBF0E0 2016-01-16 21:09:43 RX 14;255;4;0;2;0A0001002F00 2016-01-16 21:09:45 DEBUG Undefined firmware/type for node=14 2016-01-16 21:09:45 INFO BL version=257 2016-01-16 21:09:45 INFO Send FW info to node 14: type=A, version=1, blocks=0x0048, CRC=0xD098 2016-01-16 21:09:45 TX 14;0;4;0;1;0A000100480098D0 2016-01-16 21:09:45 RX 14;255;4;0;0;FFFFFFFFFFFFFFFF0101 2016-01-16 21:09:46 DEBUG FW update started, node id = 14 2016-01-16 21:09:46 TX 14;255;4;0;3;0A0001004700E1F30E940000F9CF0895F894FFCFFFFF 2016-01-16 21:09:46 RX 14;255;4;0;2;0A0001004700 2016-01-16 21:09:47 TX 14;255;4;0;3;0A0001004700E1F30E940000F9CF0895F894FFCFFFFF 2016-01-16 21:09:47 RX 14;255;4;0;2;0A0001004700 2016-01-16 21:09:48 TX 14;255;4;0;3;0A00010046002C020E947000C0E0D0E00E948B002097 -
Hello @tekka,
is the feature 'save nodes' supposed to be working or WIP? With every start of MYSController I get a blank page and have to wait for every sensor to appear. At the moment that's not a big problem for me because of only 3 sensors, but already got a doubled ID once because new sensor requested an ID before the old #1 was recognized.
Thanks a lot for your work with the controller, it's great.
