@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.

@Marcel Thank you for your patience! 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) When I have a new node, this will publish an auto node ID. Then I cannot upload new firmware because if I do this the default firmware will be loaded? I am not sure if that is even possible with manually assigned numberings of nodes. Assigning node ID is a different process than OTA. So do not get confuse with node ID assignment. So the next step is that I press edit on the new node and assign the firmware to it (that I added to utilities\firmware tab) and save this and the press the above button upload firmware? This seems to work but I am not sure if this is the correct process as I find this not very logical. Yes, this is the correct way to upload firmware and it is by design. You can keep any number of version of the firmware and assign a version to a particular node. When I would like to update a node, I add the software again to the utilities\firmware tab, edit the specific node and assign this new software and do the upload firmware again? Correct? Yes, correct The part where it did goes wrong is that I put the default switch on for firmware as I saw errors in the logging about this. Then this will upload software (which is already on another node) to the new node and you get duplicated node numbers. Default firmware should not contain node id statically. It is mainly used when we use MYSBootloader. With this boot loader, we may not have any firmware. So we can keep default firmware for the first time. and later we can switch to new firmware by assigning manually. That is up to our convenience. We can go without default firmware also. You can disable it as follows, So preferable, I would like to see. Add also the possibility that you have a split menu. Upload Assigned/default firmware or upload firmware where you get a popup and select the one you would like to upload to your node. Yes, nice feedback/enhancement request. Could you please create a ticket in GitHub? Secondly, I had a problem with my boot software. The first time it advertises itself and after the upload of the new firmware, I could never upload new firmware again. I have downloaded the MySensors Bootloader and recompiled it for my hardware (slim node atMega328p 8MHz) and this bootloader seems to work okay Great! I hope you have mentioned MYSBootloader ^^

@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");

@Tag See update here.... https://forum.mycontroller.org/topic/224/booting-rpi3-mycontroller-from-usb-only

@jkandasa said: var temperatureSen = mcApi.uidTag().getByUid("my-sensor-1").getResource(); Also faced this issue when i imported my database on a different node. had to change the scripts to use the new variable.... Gauges work now after changing the variables.. For the rest no issues found, all work like a charm!!!! Thank you for the great support!!!

Thanks, it is working for me now!

Here is some good news !!! First after getting update from github , here is some screen shot from GUI We can see that MyController is in the list ! Also, Esp send correctly data to mosquitto (which i use by default) Now , i have to test and learn to send data , like temperature or lighmeter . Thank you for your time and your support.

8 Days and looking good - no errors, no crashes. Just a couple of nodes that misbehave sometimes...... On that note, today I noticed one node had not sent data for many hours and when I got to it, the led connected to pin 13 was rapidly flashing. This is not normally the case, but I can't spare the laptop to monitor the serial port for a week+ just in case it happens again - any ideas? This was using the standard MYS prog for bmp180 pressure sensor. Running on mains powered 5v pro mini.

@jkandasa Cool!, Thx! will give it a try on the snapshot version.

@tag Thank you for the feedback. the CPU temp is shown as 0.049c instead of 49c I have filed an issue with pi4j. Seems it's fixed. Let me check with recent version and update. https://github.com/Pi4J/pi4j/issues/356 Which image do you use (in my opinion armbian jesse is still the best..) Yes, I too use armbian. Which is super cool image for Orange PI and what is "hot" can you keep your finger on the cpu for a minute? Sure, Will update you jkandasa created this issue in Pi4J/pi4j closed SystemInfoProvider CPU temperature should be standard across platforms #356

Hi Jeeva! I would like to test Alpha2! Thanks Tibi

Yes it does. Thanks

@jkandasa I've just added the JSON settings for the amp, it was missing in the first post....Opps! Thank you for making it all possible!

@jkandasa Thanks much.

@jkandasa Sorry... I thought I'd edited or deleted that reply saying it didn't work. It now works... I'd taken the sensor ID from the summary page and not the edit page as you pointed me to in your last reply. So its working now... my mistake, thanks for your patience.

@Daniele Thanks for sharing your knowledge. I still use the bootloader that is installed in China, so not the issue for me. I also specify node ID in the sketch to avoid issues with getting it assigned from the GW. I have had a much better experience lately with new quality power supply, but still had a weird crash this week. I woke to find the pi running, activity light flashing as it normally does, but no web page served, no ssh access and no activity light on the SSD. Within a few days I will re-build removing as many dupont connectors as I can and soldering wires instead. It's really the last thing I can think of, but I am seeing things improve which is a good thing!

Hmmmmm....something is not right, see log below..... Argh, can't post the log in code tags or plain text, will email it to you.... It seems to be the strange characters in the log that prevent it from being copied and pasted, so sent you a screenshot instead.

I can confirm that with 23 hours the scheduler works perfectly now! Thanks a lot!

@daniele no worries. I am happy that you find the root cause of the issue