@Emenike I do not find a variable Status in your variable repository screenshot, But you are trying to access it,

var LoopThroughValves = mcApi.variable().get("Status");

You too, keep up the support and good work everybody! 🙂

OK, thanks. Will try this.

@Emenike It is free. There are no api keys needed. You go to the main Metcheck page, select your location for the weather location you want to use, then towards the bottom of the page is a button labeled 'JSON'. Click that button and it gives you a url to use (just modify the script above for the url it gives you) Sripts are under Utiliries menu in my controller main page. After that manually running the script fetches data fine, but from there on you will need jkandasas help as this is as far as I have got.

@jkandasa Yup - You appear to have fixed it! 🙂

@Emenike https://forum.mycontroller.org/topic/371/json-parser/10

This is all I know about it so far.

Thank you.

@guille Unfortunately we do not have defined control on topology page. every time, you have to disable it.

@benhub This issue fixed on SNAPSHOT version, for details, have a look here: https://github.com/mycontroller-org/mycontroller/issues/464

I opened up a new thread for my issues...
https://forum.mycontroller.org/topic/370/node-name-gets-reset-everytime-i-restart-the-node

Ok, downgraded the java version by using the

JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java"

line in /etc/environment - AND NOW IT WORKS FINE!

Thanks again! 🙂

@cslauritsen Yes, it should work.

MySenosrs serial Gateway <--> serial2mqtt <--> MyController(MQTT gateway)

@lukash535 Thank you! I have accepted your request.

@manutremo OTA works in the following way,

send available firmware details(version, checksum, etc.,) to the node If node thinks, it is a different sketch, it will request block by block. MyController sends firmware block data(requested block)

@skywatch We are running out of document for more than years. I guess, it is time to update our document.

MyController uses ack as follows when you enabled it,

0_1541212062106_0f2d8218-baa2-41b1-a52a-23ae70c78eb5-image.png

Here I have enabled Ack, retry count is 3, ack wait time 1800 ms and stream ack is disabled.

Sends data to Gateway and wait for 1800 ms, if MyController receives an ack from gateway assumes this data delivered to the end node. Otherwise send the data once again to the gateway and wait for ack. This loop continues until it reaches the maximum retry count.

Stream ack also works in the same way. OTA firmware update comes under stream data type. When we enable ack for firmware update data, it leads to super high delay on the firmware update, So I have introduced new option to disable ack only for stream data(firmware data). So firmware update will be running without ack enabled.

I hope this clears ack concept in MyController?

@skywatch This could be a nice idea. But I never experienced this kind of setup.

Can you assign node id for NRF24l01+ which is attached with RPI? AFAIK, it should be a gateway node right? If yes, we should not have more than one gateway node in a network.

My other easy solution, Keep RPI with a private wifi router, hide ssid and do not connect to the internet. In this case, you can have a controller in one place and from another place you can access the controller via your private router.

@skywatch

See here for reason and solution.....

https://forum.mycontroller.org/topic/328/serial-problem/57

@avamander Thank you for your suggestions.

Your advice is good and I have already done a lot of what you suggested. I didn't put a scope on it, I may make another portable system and try that then as I do not see any pullups on the pro mini nor on the pi3 schematics. That could well be the centre of my problems.

I also stumbled upon this page ...... https://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/

This also seems to pinpoint issues with serial on the Raspberry Pi 3B, and why they happen. Seems the foundation made changes that have had a detrimental effect on serial comms stability. It would explain why this happened after 'upgrading' from Pi 2B to Pi 3B. It seems conclusive to me that the issue is with the RPi 3B serial port not working correctly.....Live and learn I guess 😉

Still, for the last 4 days I have been running with a serial to usb adapter and no ghost nodes and no data spikes on the graphs. I wonder if there are pullups on the board? It's difficult to see clearly with the plastic wrapper on it!
Things are looking very hopeful right now though...

The only issue I still face is random loss of data from some nodes. The outages can be just one value report missing (Most nodes send data once every 5 minutes), right up to over 6 hours of data loss. Then suddenly it all starts working again. I might have more time now to look into that a bit morenow the system is stable again, but it is so random.

I did also find quite a few 'less than good' dupont cables (from China) - So I have soldered directly a lot of connections now or modified/re-crimped the cables that were 'iffy'.

Thanks again to you and Jkandasa for the support and help. I am nearly there with this now and can build some more nodes with confidence. 🙂