Windows GUI/Controller for MySensors

[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

[rvendrame]

Anyone who owns a Vera controller, and perhaps was able to connect this nice MYSController to the mySensors serial-gateway hooked into Vera USB?

The serial port is exposed in TCP/IP by Vera via ser2net, however I wasn't successful by setting MYSController to <my-vera-ip>:3482 (3482 is the port displayed in Vera -> APPS -> Develop Apps -> Serial port config ) .

(maybe the Vera MYSensor plugin opens the serial connection to GW in 'exclusive' mode or something like that? )

If I remove the GW from Vera USB and plug in my computer, MYSController works fine.

Anyone? Am I wanting too much?

[JoergP]

I'm new to MySensors and playing around with this implementation since some weeks. I implemented an interface from serial to MQTT per python and everything is running fine so far. The last days I spend some time with the bootloader (it is a great feature!!!). I created also a python mqtt client that will take care on that.

I got really crazy the last 2 days with the CRC calculation. I always got a different CRC as as the MYSController. Now I found out, that it seems that the last byte within the HEX file is interpreted as 0xFF instead of the real data. I flashed now one sensor with the MYSController and as I can see in the log-file -> the last byte is read from the HEX as wrong value (0xFF instead of 0x14) -> therefore the HEX file is not flashed correctly (last byte is wrong) -> it seems that this is a bug in MYSController. (I'm using version 0.1.2.278)

Can you check that please?

[tekka]

@JoergP Indeed, bug confirmed. There is an error in the block padding code. I will push the update soon. Thanks for reporting!

[cdr]

Hello,

First of all, thanks Tekka for the great MYScontroller!

I want to get started with the MYSbootloader but I can't get it to work. I've followed each step securely but I never "see" my arduino in MYScontroller after flashing the bootloader. Perhaps I misunderstand the theory behind the bootloader? Maybe the fuses are wrong, I don't know.

Perhaps someone can reply to the following;

• Can I just attach a radio module to an Arduino Nano as instructed on the site, clear the eeprom and then burn the bootloader using usbasp? (as instructed in this thread) Or do I need to upload the gateway sketch before burning the bootloader?
• I have a hard time understanding what the bootloader does, I think it enables low level nrf functionality for OTA and Myscontroller instructions like reboot and clear eeprom etc. But when I upload a sketch does that mean the bootloader inits the nrf first and then the uploaded sketch will just re-init the nrf again?
• Is there a way to debug the bootloader?

Have a good laugh if you will at these noob questions, but any help is appreciated :)

[tekka]

@cdr said:

• Can I just attach a radio module to an Arduino Nano as instructed on the site, clear the eeprom and then burn the bootloader using usbasp? (as instructed in this thread) Or do I need to upload the gateway sketch before burning the bootloader?

Yes, simply attach the radio and burn the bootloader with the correct fuse settings (see the fuses.txt file in the bootloader directory). If you intend to use MYSController, set AutoID to automatically assign IDs to the nodes.

• I have a hard time understanding what the bootloader does, I think it enables low level nrf functionality for OTA and Myscontroller instructions like reboot and clear eeprom etc. But when I upload a sketch does that mean the bootloader inits the nrf first and then the uploaded sketch will just re-init the nrf again?

Yes, that's correct. The bootloader is a small piece of code located at the end of the flash area that is (if the fuses are set accordingly) executed first upon rebooting and allows for low-level OTA updates.

• Is there a way to debug the bootloader?

Yes, there are several ways (e.g. visual with LED, serial output, or AVR DebugWire)...you may want to google these topics for further information..

Have a good laugh if you will at these noob questions, but any help is appreciated :)

no problem :)

[cdr]

Hi tekka,

Thanks for the response and clarification. I think I need more knowledge about fuses and bootloaders, it could be that the arduino clones are giving me sh&t.

Looking forward to my success and MYSloader 2.0 ofcourse!

Thanks again for all your work.