MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

[tekka]

@karlheinz2000 Try with the latest build (MYSController 1.0.0beta build 3316) - MYSController will inform you about an available update.

[manutremo]

@tekka Where can that be downloaded? All the links I find lead to a 404...

[tekka]

@manutremo see above, you will get notified when running MYSController

[manutremo]

Done, nice job, I see the new message types have been added, probably other enhancements under the hood? thanks!

[Mark Swift]

@tekka it's been some time since I flashed the bootloader, I notice I currently have a lot of different hex files (which I believe I compiled myself), do I no longer need different files for different speeds, i.e 16 / 8 /1Mhz?

[Mark Swift]

I'd also love to use the signal report features, I thought it was enabled by default in MS, seems not to work here when I request an item from MYS?

[karlheinz2000]

The new build runs since several hours with no problems :+1:
The old one stoped within 10min.

[manutremo]

I'm sorry to say that in my case FOTA updates seem to be worse than with the previous version, they stop before the 5th line of sent code... but it may be my fault, I'll continue investigating.

[manutremo]

@manutremo As expected, it was my fault. FOTA updates work correctly with this version.

[Chris83]

Hi,

I 'm new to MySensors and MySController. I have everything working and I thanks all the good developers here :-)

I have 1 question to better understand how everything works: when I start MYSController I can see in the message tab those 2 messages (heartbeat) repeating every 10 seconds. Can someone tell me what they are? Where does the GW send the heartbeat to? Is it going through RF24?

Thanks in advance for the reply.

[raptorjr]

@chris83 Which version do you use? I only have the RX line?

I thought it was for the MYSController, since it is connected to the gateway. Guess the gateway sends it to all connected clients.

[Chris83]

@raptorjr Thanks for the quick reply... I'm running MYSController version: 1.0.0beta:
b3316.

[raptorjr]

@chris83 Thank you. I use the same version.

[Chris83]

@raptorjr So if I got it right, MYSController is sending a ping to my GW every 10 seconds?

[raptorjr]

@chris83 Yes, as I understand it. But I could be wrong. But it feels logical.

[itbeyond]

How is the upcoming bootloader release (1.3S) going?

I may be wrong but think I need this to push signed firmware to a node. I have a node with soft signing required. The node works but I cannot update it OTA is this 1.3S to support this?

[diogoc]

There are already support for rfm69?

[mbedarff]

tekka, first of all, thank you very much for your efforts and shared results on MYSController and MYSBootloader! :)

I am trying to upload new firmware to battery operated nodes via MYSController 1.0.0beta. But it seems that MYSController does not send an ST_FIRMWARE_CONFIG_RESPONSE message after the node has sent an I_PRE_SLEEP_NOTFICATION before its next smart sleeping. Thus no firmware packages are requested from the node using ST_FIRMWARE_REQUEST messages.

Uploading firmware to nodes that are not sleeping and powered by a power supply basically works. One limitation seems to be that the node has to be restarted while MYSController is connected to the gateway. My guess is that the ST_FIRMWARE_CONFIG_REQUEST message from the node must be received first by MYSController before the assign firmware selection inits a ST_FIRMWARE_CONFIG_RESPONSE message. If the nodes are not sleeping, this can easily be done using the request reboot function of MYSController. In the case of the battery-operated node, this reboot request is not transmitted on the next wake-up respectively pre sleep notification.

I also noticed another bug: After receiving the reboot messages from a node, it is always set as a Sensebender board.

My setup:
MySensors version: 2.3.2
Gateway: ESP8266 with RFM69HW
Nodes: Canique MK2 boards (Moteino clone) with Atmega328P, RFM69HW, 4mbit Winbond W25X40CLSNIG flash chip and DualOptiboot bootloader.

@tekka: I would like to have a look at the code of MYSController to understand the firmware OTA start problem and the wrong detection of the board and to fix it if necessary. Would you be interested in making your code available on GitHub, for example, so that MYSController is developed further together? Please don't bother with code cleaning in advance.

[luizrrocha]

I also have problems with my battery-powered sleeping-most-of-the-time nodes. I actually have to disassemble them and force reset several times until the OTA FW update function starts to work, which pretty much negates its usage.

@Tekka, I echo mbedarff´s words, your job is fantastic but can we all try to add on our efforts and try to make it even better than it already is ?

Cheers from Portugal.

Luiz

[tekka]

@luizrrocha Can you post your sketch and (if available) debug log here?