I've been testing more... It seems that in order for the new firmware to be loaded to the node and then show as running in MyController the node needs a hard reset (pull power and restore). Issuing reboots from the controller does not seem to work.

I've yet to figure out what combination of things is actually triggering the update though. I just keep trying different things and eventually it works. But consistently the new firmware version will not be shown in MyController until a hard reset on the node is completed.

I'm using 5v 16Mhz Pro Mini.

I've also noticed that once the firmware version has been put on a node I can't re-send the same version, I need to increment the versions everywhere. Is this correct or should I be able to re-flash with the same firmware version by issuing the command?

Not sure what is up, I rebooted flashed the bootloader again on the node and deleted re-added the node and now it works. Also not getting the error either.

@jkandasa I will work on the English documentation if you wish.

@jkandasa ,

I loaded your latest snapshot, I am not getting the following error, OTA firmware update no longer seems to work either.

ERROR [Thread-5] [org.mycontroller.standalone.message.MessageMonitorThread:123] Throws exception while processing!, [RawMessage(gatewayId=1, data=1;255;4;0;2;010001007E04, subData=null, isTxMessage=false, networkType=MY_SENSORS, timestamp=1478706446658)]
java.lang.IndexOutOfBoundsException: Index: 18400, Size: 1024
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at org.mycontroller.standalone.message.McMessageEngine.procressFirmwareRequestMySensors(McMessageEngine.java:552)
at org.mycontroller.standalone.message.McMessageEngine.streamSubMessageTypeSelector(McMessageEngine.java:489)
at org.mycontroller.standalone.message.McMessageEngine.execute(McMessageEngine.java:136)
at org.mycontroller.standalone.message.McMessageEngine.run(McMessageEngine.java:1148)
at org.mycontroller.standalone.message.McMessageUtils.sendToMcMessageEngine(McMessageUtils.java:616)
at org.mycontroller.standalone.provider.mysensors.MySensorsProviderBridge.executeRawMessage(MySensorsProviderBridge.java:58)
at org.mycontroller.standalone.message.McMessageUtils.sendToProviderBridge(McMessageUtils.java:562)
at org.mycontroller.standalone.message.MessageMonitorThread.processRawMessage(MessageMonitorThread.java:112)
at org.mycontroller.standalone.message.MessageMonitorThread.run(MessageMonitorThread.java:191)
at java.lang.Thread.run(Thread.java:745)
2016-11-09 10:47:30,960 ERROR [Thread-5] [org.mycontroller.standalone.message.MessageMonitorThread:123] Throws exception while processing!, [RawMessage(gatewayId=1, data=1;255;4;0;2;010001007E04, subData=null, isTxMessage=false, networkType=MY_SENSORS, timestamp=1478706450936)]
java.lang.IndexOutOfBoundsException: Index: 18400, Size: 1024
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at org.mycontroller.standalone.message.McMessageEngine.procressFirmwareRequestMySensors(McMessageEngine.java:552)
at org.mycontroller.standalone.message.McMessageEngine.streamSubMessageTypeSelector(McMessageEngine.java:489)
at org.mycontroller.standalone.message.McMessageEngine.execute(McMessageEngine.java:136)
at org.mycontroller.standalone.message.McMessageEngine.run(McMessageEngine.java:1148)
at org.mycontroller.standalone.message.McMessageUtils.sendToMcMessageEngine(McMessageUtils.java:616)
at org.mycontroller.standalone.provider.mysensors.MySensorsProviderBridge.executeRawMessage(MySensorsProviderBridge.java:58)
at org.mycontroller.standalone.message.McMessageUtils.sendToProviderBridge(McMessageUtils.java:562)
at org.mycontroller.standalone.message.MessageMonitorThread.processRawMessage(MessageMonitorThread.java:112)
at org.mycontroller.standalone.message.MessageMonitorThread.run(MessageMonitorThread.java:191)
at java.lang.Thread.run(Thread.java:745)

Great, thanks again @jkandasa!

I tried this and got it to work, however, some clarification is still needed as my results are inconsistent.

First thing I noticed is, when the .hex file is generated by the Arduino IDE two .hex files are created:

• SketchName.ino.hex

• SketchName.ino.with_bootloader.hex

Which one should be uploaded to the MyController Firmware section? Does it matter?

Next, a little more clarification on the update process...

Once a new version of the firmware is uploaded into MyController, how do we push that out to the node?

I know there is an option to select the node and then from the Actions Menu choose "Upload firmware". Does that initiate the upload immediately and refresh refresh the node or must a "Reboot" be selected after pushing "Upload firmware"?

If a reboot is needed, can it be done immediately after choosing "Upload firmware"? If not how long should we wait before clicking "Reboot"?

I'm able to get the updates out eventually but that is just because I keep clicking reboot and upload, and even resetting the node manually. That seems like a poor way to achieve what I am doing. There must be a certain order to doing this with consistent results. I would like to know what part of what I am doing is actually necessary and what is not.

Can you please provide a step by step guide.

Also, is there any way we could monitor the Firmware Upload progress in MyController? That would be very helpful. Should I add that feature request to GitHub?

@yd / @jkandasa ,

I would be more than happy to do the writing, I am quite new to the platform however so I'm still discovering the system myself as you can see...

With your help I can write the documentation once I understand what exactly it is I'm documenting. I see @jkandasa has already an outline created on GIT hub, we just need to add moer specifics to that. Hotlinking to support right in the application will also be a huge help to users.

Thank you so much. I feel dumb for not figuring out the adding of the Types and Versions.. I guess when I saw those buttons there I thought they were for sorting rather than managing sub-lists. Maybe some UI improvements needed here, or maybe I'm just tired. Eiter way, thanks for clarifying on that.

I think I have a better idea what to do now. We should get a WIKI going as I can't seem to come up with much in terms of documentation other than the forum? +1?

@yd I'm not sure where you create the new "type" and "version" you are referring to? Can you please be more specific?

Also, I understand that the firmwares will need to be loaded to the nodes via MyController once the node is running the MYSBootloader. My question is, how does the node with just a bootloader installed know where to find its firmware? What tells a newly loaded node with only the bootloader on it where and what firmware it should be running?

Let's say I get a brand new Pro Mini, I flash it with the bootloader. Then what? Is there some type of configuration I need to do on the bootloader before loading it so it has a unique ID or something? How does it find home when it doesn't know where home is?

@imedia said:

206 ERROR [Quartz_Scheduler_Worker-7] [org.mycontroller.standalone.operation.model.OperationSendPushbulletNote:128] Timer will not support for this operation

Issue #301 Created: https://github.com/mycontroller-org/mycontroller/issues/301

Thanks for the info @yd, going to give this a try shortly..

Just to confirm, I export the sketch (firmware) using Sketch > Export compiled binary in the Arduino IDE correct? I then import that file into MySensors on the Firmware page. However, on that page it says "Nothing Selected" for both the Type and Version. There is also nothing appearing in the drop downs to select something and you cannot save and upload the firmware without selecting both these drope downs. Maybe @jkandasa can advise on that?

So Let's assume I can get the firmware loaded into MyController. How does the node know to connect this specific Gateway / MyController and download it's specific firmware? There needs to be a relationship between the two created correct? If so how is that created and ensure the correct node is getting the correct firmware from the correct controller?

Thanks,

Ok @jkandasa,

I see you point, however, I believe a case for the ability to send e-mail and or push notifications from a timer is valid.

Here is a usage case:

If you have a sensor that senses whether a door is open when the door opens the timer is started to make sure the door is closed within a set amount of time. If it is not the timer expires and sends a notification. If the door closes before the timer expires a separate rule disables the timer before the notification is sent.

Am I thinking right on this or is there a better way for me to achieve what I'm doing. I'm unclear on the dampening option under rules. Maybe an option to trigger an Operation after a set amount of time that a Sensor Variable remains in a set state? Could we add that functionality maybe?

Thanks,

Should also mention this also does not work for E-Mail Notify:

550 ERROR [Quartz_Scheduler_Worker-5] [org.mycontroller.standalone.operation.model.OperationSendEmail:145] Timer will not support for this operation

@jkandasa I've created a timer in 0.0.3-FINAL Alpha 2 and they seem to be failing.

I have a timer setup to do a simple PushBullet notify timer runs and then stops but no push is sent and the following is seen in the log:

206 ERROR [Quartz_Scheduler_Worker-7] [org.mycontroller.standalone.operation.model.OperationSendPushbulletNote:128] Timer will not support for this operation

@yd, Would you be willing to share how you got the bootloader loaded to your nodes and got OTA firmware updates working with MyController?

I've been trying for days now and every guide, or forum post I've found is way over my head. I'm confused with all the fuse settings etc that people are discussing and just want to load MYSBootloader to my nodes so I can push the updates from the Controller. All the other jargon is bogging me down.

I'm running MySensors 2.0 on a Serial Gateway and the nodes, and My Controller v0.0.3-FINAL2

Thanks,

Been working on this a bit more... The documentation / guides in the links you provided are a bit over my head. I'm not familiar with the purpose of fuse settings and other bootloader characteristics, perhaps this is a little too low-level for me...

Is there not a guide that is a bit more step by step to get a working system using the MYSBootloader? I seem to just be going in circles with the forum posts and technical details I cannot make sense of, and the dialogue is way over my head. I'm not technically inept, or at least I don't think I am, but do know I'm not a low-level programmer.

Perhaps a quick guide on how to get a system working would help many leaving out all the jargon? Am I alone?

I think I figured it out...

I thought the variables were passed as part of the myImports object, but they need to be imported using mcApi.variable().get("delaySeconds"); instead.

@jkandasa,

Is it possible to pass variables to a script? I have written a script and I would like to pass a delay time variable depending on what triggers it. Is this possible? I think it is be means of bindings but doesn't seem to work.

I put { delaySeconds: 10 } as the script bindings on a Operation that executes the script, on the other end I do myImports.delaySeconds but the variable seems to be null.

Can you provide an example of doing this if it is possible?

Thanks,

Thanks again @jkandasa

Ok thanks for the info @jkandasa ,

Do you know of any documentation that properly explains the use and installation of the MySensorsBootloaderRF24 process?

I would really like to also get the remote firmware update as part of MyController working as well and I understand the bootloader is required. If that also resolves this issue perfect!

Documentation seems scarce on all of this so any help is much appreciated!