MyController.org

@andmaster I have mycontroller starting via crontab and this always works for me, you could try that and see how it works for you. Here on pi3 it is working no problem and every reboot mycontroller comes right back up. If you can I would recommend replacing the SD card with a SSD HDD. They are quite cheap now (less than £20 in UK) and seem much faster and more stable. I have mine connected to pi via usb adaptor and it is working well. Another thing to keep in mind is that a good quality power supply and good thick cable from power supply to raspberry pi are strongly advised. Pi seems to be affected by power quality easily. I have been around the block a few times with this!

@jgrieco You may try log raw data from the gateway. https://github.com/mycontroller-org/mycontroller/issues/473 This changes available in SNAPSHOT version

@jkandasa Brilliant - thank you!!!

Mine usually tops out at about 30%. What is the output of the following?? $ java -version $ javac -version

@jkandasa actually, MYSBootloader does not implement ACK handling (due to space constraints), but online FOTA does.

Just to end and close the topic, @tekka great work on the Bootloader and @jkandasa great work on MyController... Thank you

I don't know why but now OTA works better; I still get quite some NACKs on the gateway but at least most of the times the OTA is successful even with signing enabled. With ACK enabled the transfer speed is at least 4/5 times slower

There is, I have loaded 5 but none work, besides the first time that actually did started the ota transfer

You need to post your code of the node and the debug from node and gateway, otherwise we can't help

Thank you for your replay. My main doubt was the client-id, I didn't understand if it was a unic name or the GW client-id. You answered my question. Thank You for your help

I have 2 controllers connected to 2 ethernet gateways running all on the same rpi. I don't know really what happens to the mqtt broker if it gets clogged with a queue of undeliverable messages, you have to debug it and see if the mqtt grows too much

@zachflem Can you see a node 0? Select your gateway and run Discover

@jkandasa Great! Thanks for pointing me out. I'll take a look. Regards

If you want to use esp8266 as nodes, there are also some alternative firmwares like espurna, espeasy or tasmota (pretty much the same as espurna), while you can show data on the node-red dashboard connecting with mqtt

@talhatec However, when a sensor calls back to the controller, both HomeAssistant and myController send out replies, and due to this, i think the messages clash, and the controllers endup sending it multiple times. I do not know your preference about, which controller wants to response for your sensors request. Suppose you want MyController only on listen mode, you have to change MQTT Topic publish to some dummy topic on MyController gateway settings. [image: 1502333687367-upload-c572e22b-04f1-423a-a9a2-35e7e42eb3e4-resized.png]

it works now i disabled https, and it works fine thanks folks for help :)