Global Sync with 20x4 LCD and BME280s - No info displayed on LCD

[robatbentley]

My problem is that I'm unable to display BME280 x 2 and TSL2561 device on a globally sync'ed 20x4 LCD device. I've had this working previously but since migrating to more recent ESPEasy-2.0 builds I started having problems where (e.g.) only the TSL2561 device couldn't be shared but more recently the problem has spread to all shared devices. The most recent build I've loaded is from 8th Feb 2018 (ESPEasy-2.0-20180206) and have the same problem with this too.

The setup is...
* All 3 sensors (2xBME280 and 1xTSL2561) can "see" each others globally sync'ed sensor values such as temp, humidity, pressure and Lux. However, the 20x4 LCD cannot. i.e. The LCD Device Summary page shows all sensor values as zero. See attached screen-shots.
* All sensors and LCD have configured with UDP 65501, sync'ed and global options selected, power-down and power-up of all devices to sync devices.

I've swapped out the LCD, the LCD support ESPEasy node ESP8266 board but still not help solve the problem.
Any suggestions will be greatly appreciated as I've spent a few days trying to solve this now and need some help.
Thanks...

Update:
* Loaded latest firmware ESP_Easy_v2.0-20180209_normal_ESP8266_4096
* Found that I'd omitted to complete the LCD 8266 units Config/WiFi Settings for the SSID. Entered SSID and repeated all the shutdowns and restarts of all 8266 nodes but still the same problem. One thing I have noticed is that the LCD node was the only one which required an SSID configuring. All the sensors has it setup already from the building of the 8266 node. I just get the feeling that my LCD 8266 node isn't linked to my wifi network router in the same way that the sensors are. Must have omitted something but they all (sensors and LCD 8266 nodes) appear to have the same wifi SSID and passwords.

BME280DeviceSummary20180209.JPG (69.94 KiB) Viewed 23540 times

[Domosapiens]

IIRC,
time is important.
Check NTP on, on both.
Compare the time on both.

[robatbentley]

Thanks for the feedback.
Checked that NTP selected for all, and it was. See attached. ...but the DST wasn't selected for all of the, It is now. As far as I can tell, the NTP and DST options are identical.
...and the node time seems to be consisent across all devices.
Did a power-up and down cycle on all nodes but still same problem.

Anything else I should look for? Cheers...

PS Interesting to see differences in the "Age" compared between LCD and BME280 nodes. See screen-shots of Main summaries. Not sure if relevant.

[Domosapiens]

Ohhh latest version of DST....
No experience with that yet (a TD-er contribution)

Advanced tab:
Global sync enabled?
A shared (=same) UDP port selected?

[robatbentley]

Yes... Advanced/Global sync: enabled for both LCD and BME280 devices. ...and common UDP port of 65501 also set for both. Global sync enabled for BME280 device (Task settings/global sync). ...and numerous power-down and ups for all nodes.

[grovkillen]

And you see data being broadcasted on that port using a sniffer?

[robatbentley]

Re

data being broadcast on that port using a sniffer...

I don't know as I've never used a sniffer before. However, the data does appear to be shared between the 3 sensors (all on different ESPEasy nodes) as per my initial post. i.e. They can all "see" each others sensor data. It's only the LCD that can't "see" this data.

[grovkillen]

Re

data being broadcast on that port using a sniffer...

I don't know as I've never used a sniffer before. However, the data does appear to be shared between the 3 sensors (all on different ESPEasy nodes) as per my initial post. i.e. They can all "see" each others sensor data. It's only the LCD that can't "see" this data.

Sorry, missed that information.

[Domosapiens]

Apple in your house? Apple uses 65501 for SAN.

In my Inter-ESPEasy set-up (GIT version: v2.0.0-dev12), the "slaved" Tasks on the display node are NOT-Enabled (=red cross)

[robatbentley]

Re Apple using UDP 65501... I've reset all sensors and the LCD to using 65500. ...followed by a power-up and down.
Re slaved devices not enabled... I agree, and can confirm that all slaved devices are not enabled, as per screen-shot below.
However, still no sensor data appearing in LCD node.

[TD-er]

Ohhh latest version of DST....
No experience with that yet (a TD-er contribution)

Advanced tab:
Global sync enabled?
A shared (=same) UDP port selected?

When in doubt, disable DST and then it's for sure the 'old' behavior


You're using quite long strings for the sensor values.
Perhaps for a test, try shorter ones?

[Domosapiens]

Space in the name of your node? ... Robs LCD in your last pic

RobsLCD as Node name and as Task name?

[robatbentley]

Re "Space in the name of your node? ... Robs LCD in your last pic". Removed space in unit name. Now called RobsLCD.
Re "RobsLCD as Node name and as Task name?" Renamed LCD device to LCD_THP.

Powered-down/up sequence for all nodes but no change.

Re "When in doubt, disable DST and then it's for sure the 'old' behavior". Deselected Advanced/DST for all nodes.

Powered-down/up sequence for all nodes but no change.

Re "You're using quite long strings for the sensor values. Perhaps for a test, try shorter ones?". Renamed sensor variables to BoxedT, BoxedH, BoxedP, IDT, IDH, IDP. ...and deleted all slave devices in each nodes device list.

Powered-down/up sequence for all nodes but still no slave devices appearing in the RobsLCD node. However, I did notice that the sensor variables have changed between the master node (e.g. BoxedTHP node) in that the master has variables BoxedT, BoxedH, BoxedP, but the slaved BoxedTHP node in the other nodes has variables called Temperature, Humidity and Pressure. ...but, the same story for the InDoorTHPSensor node is different in that the same variable names appear for both master and all slaves. I've attached screen-shots below. ...but don't know whether this is relevant.
PS Similar story for the luminosity sensor in that the master variable is called LSLux but the slaves reverted back to Lux

[robatbentley]

Updated all sync'd nodes to ESP_Easy_v2.0-20180212_normal_ESP8266_4096.
...but still not fixed the problem.

I've also noticed that there is no Global Sync tick-box in the LCD_THP task settings, as per attached screen-shot. Not sure if there used to be but there are for all the other sensor nodes global sync'd (or attempted) to the LCD node. Was there a global sync tick-box in a previous build?

[Shardan]

So let's start at a very basic point to find out what's going on.

You have GlobalSync enabled and set a common port to both devices, right?

Then let both devices run for a while and then check the "Main" page of the devices.
You will see the usual section with NTP activated, time is..., Free memory is .... and so on.
Beneath you should see a list of the ESPEasy devices in your net.

This list is there and correct (IP Asdresses)?

PS: No, the LCD has no "GlobalSync" box, that is correct.
GlobalSync needs a sensor giving values, the values are "pushed" to other devices.
A LCD does not give values at all.....

Regards
Shardan

[robatbentley]

Re "You have GlobalSync enabled and set a common port to both devices, right?" ...Yes, tick box selected in Tools/Advanced and all nodes using common UDP of 65500.
Re "This list is there and correct (IP Asdresses)?" ...Yes, I can see all 4 IP adresses of all 4 nodes. ...and same list visible on all of the 4 nodes.

I'd like to emphasise the difference in behaviour when configuring global sync'ing a few months ago vs what's currently happening. The biggest difference is that after the power-down and then up sequence across all sync'd nodes, the slave device node sensor values do not appear in the RobsLCD node device list. They used to and wonder if their absence indicates a potential cause of the problem in the global syncing mechanism.

[Shardan]

Hm... if all devices show up in the list the items are communicationg wich eachother.

I have another suspicion, honestly it's just a bit of prophecy, i might be wrong.
GlobalSync pushes the Value of for example Item 1 / Task 3 to another device, lets say Item 2 / Task 3.

So if i configure a BME280 on Task 3, this task should be left empty on the receiving device.
Remember: Every globalsync enabled device is a receiver!

If i see your config you have a lot of devices with globalsync enabled.
Some tasks are occupied but disabled - but they are not empty.
I'm not sure but this might cause some problems.

I'd suggest a simple test:
Set one single sensor device to another UDP port, for example 61234.
Set your display to the same port.
This divides these two devices away from all other UDP communication.
Configure the display on task 1 on the display device and leave all other tasks empty!
Configure the sensor(s) on the sensing device to task 2, task 3 and so on.
Enable sensor and tick globalsync only for these sensor(s), nothing else.

The sensor values should show up in the diplays device's task 2,3..... after a while - be patient, it takes some minutes.

If this config runs you may move the other sensors one by one to the new UDP port and configure accordingly.
Always remember that the task you set a sensor to must be empty on the receiving device (display).
It might get tricky as the tasks of the sensors must be different on all sensor devices.
So if your first BME runs on device 1 / task 2, the next BME on device 2 should not occupy task 2.
As ESPEasy has a max of 12 tasks you will run into some config limits soon: The values are pushed to
all (!) global sync enabled devices.

Regards
Shardan

[robatbentley]

Right...! Think I've followed your instructions.
I've now configured the nodes RobsLCD (aka the display) and BoxedTHP (aka the sensor) to UDP 61234. I've left the other two sensors as they were (Optical Sensor and IndoorTHPSensor) with UDP 65500.
The resulting Main/Node List reflects the two groups of UDP nodes. See attached screen-shot

Re "Configure the display on task 1 on the display device and leave all other tasks empty!". Done! See attached image below.

Re "Configure the sensor(s) on the sensing device to task 2, task 3 and so on.". Done (I think...) ...as per attached image below.

Re "Enable sensor and tick globalsync only for these sensor(s), nothing else.". Turned off global sync (Tools/Advanced) on both Optical Sensor and InDoorTHPSensor nodes

Re "The sensor values should show up in the diplays device's task 2,3..... after a while - be patient, it takes some minutes." No, still can't see any (BoxedTHP) sensor values in the RobsLCD nodes Device task list after about 5 mins. See attached image.

Have a look at the images and see if you think I've followed your instructions correctly. The interesting aspect seems to be the lack of sensor task info in the display nodes device task list. Pretty sure they used to appear here in older builds of a few weeks ago. I'll have a play and see if I can go back to older builds to see where the changes appeared.

[Shardan]

That is strange.
I'll get my hands on a test circuit as soon as possible and check.
Hopefully next weekend as I'm on the road this week.

Regards
Shardan

[robatbentley]

I've experimented with a number ESP8266 nodes for the LCD nodes, flashing them from scratch. i.e. Flashing them with zeros and then with the ESPeasy build.

Summary of analysis: Having done the testing outlined below, I suspect the following...
* Firmware at or around v2.0.0-dev12 then global sync does work (i.e. slave sensor device appears in the LCD device list) and valid sensor values do appear on the LCD screen. However, I did have to submit null values of the sensor device on the sensor node to get this GS working.
* Firmware ESP_Easy_v2.0-20180212_normal_ESP8266_4096 does appear to GS (as per above) but I can't get the valid sensor values to appear on the LCD screen (see screenshot of LCD device list attached).
* The nodes I've tested had different responses to the zero-flash/firmware-flash in that some (via my smart phone) provided the IP address either after a 20 sec countdown or went straight to a "Welcome to ESP Easy Mega AP"showing the IP. Those in the latter group were more difficult to get global syncing working, if at all. Not sure whether this is down to me using cheap ESP8266 clones or what.

All the following tests were done with varying firmwares on the LCD node, but staying with ESP_Easy_v2.0-20180212_normal_ESP8266_4096 on the Sensor node.

LCD Node v1: (This is the node used in most of the above posts).
* All attempts at flashing v2.0.0-dev12 couldn't get 20s count-down, and global sync not work. Learning from nodes below, I submitted (no changes) the BoxedTHP device and the GS started working straight away.
* Reflashed to ESP_Easy_v2.0-20180212_normal_ESP8266_4096, deleted BoxTHP slaved device from the LCD_THP1 device list and submitted blank changes to the master BoxedTHPSensor device. This time, the slaved BoxedTHP slave device appeared in the LCD_THP1 list of devices with valid sensor values, but sensor readings did not appear in the LCD itself.
* Reflashed zeros and then ESP_Easy_v2.0-20180212_normal_ESP8266_4096 but no 20s countdown, just displayed IP same as last time. Reconfigured the LCD node and then submitted null changes to the BoxedTHPSensor resulting in the slave sensor device appearing in the LCD device list, but valid sensor values did not appear in the LCD itself.

LCD Node v2:
* Flashed to v2.0.0-dev12 firmware and got 20s countdown. Global sync worked. Upgraded firmware to ESP_Easy_v2.0-20180212_normal_ESP8266_4096 and global sync stopped working. Reloaded older firmware to v2.0.0-dev12 and GS started working again.

LCD Node v3:
* Flashed and couldn't get 20s countdown and GS not work. Changed UDP up and down but no apparent benefit. Then set LCD device Delay from 60 to 10 seconds, as per Boxed THP delay, and then GS started working!!!

LCD Node v4:
* Inital flash created IP address immediately (no 20s count-down), and couldnt get global sync to work. Reflashed and got 20s count-down but still not get global sync to work. Cycled through different UDPs (as per v5 below) but GS still not work. Then set UDPs to 61238 with no obvious effect. Then submitted BoxedTHP device with no changes and then GS started working

LCD Node v5:
* Initial flash provided the 20s countdown. GS not work immediately so change UDP from 61234 to 61235. still not work, then back to 61234 and GS started working.

[TD-er]

If you exchange settings, are always the same physical devices causing problems?

Can you make a list of MAC addresses and IP-addresses of all nodes?
Just to make sure no 2 devices have the same.

[robatbentley]

Re "If you exchange settings, are always the same physical devices causing problems?" - The same physical devices change behaviour when settings are modified. However, any initialised device that doesn't go through the 20 sec countdown seems to have more problems re global sync.

...and details requested...

BME280 Sensor...
AP MAC: A2-20-A6-1C-0C-08
IP: 192.168.1.8

...and the LCD nodes...

LCD1:
AP MAC: A2-20-A6-1C-46-08
IP: 192.168.1.10

LCD2:
AP MAC: A2-20-A6-1B-2A-01
IP: 192.168.1.20

LCD3:
AP MAC: 62-01-94-1F-85-08
IP: 192.168.1.11

LCD4:
AP MAC: A2-20-A6-15-F5-08
IP: 192.168.1.4

LCD5:
AP MAC: 62-01-94-1F-7A-08
IP: 192.168.1.21

[Shardan]

I've made a simple test breadboard with two nodeMCU's and a BMP180 sensor from my shelf.

I've had the same problem as the thread opener - until I configured the sensor node to connect to my FHEM home controller and send data.
Then i get readings on the second node.

So it seems GlobalSync only works if the data transfer to a home controller is activated.

At dev's: Is this a bug or is that a feature?

Regards
Shardan

[TD-er]

[...]
So it seems GlobalSync only works if the data transfer to a home controller is activated.

At dev's: Is this a bug or is that a feature?
[...]

Sounds like a (serious) bug.
Will look into it.
I might be the one who introduced it.

[Shardan]

^+1
Thanks

[robatbentley]

...and a thanks from me too!
Can you let me know when there's something to try out?

[TD-er]

Ofcourse.
I was looking for this thread to link it into a new Github issue for fixing this.
Let's hope I get to it this evening.

[TD-er]

I've been looking through all the code for hours now and I find this part a bit strange:

Almost every call to a plugin with "PLUGIN_READ" will return 'success = true'. Well at least when a value is read.
Except P012_LCD.
That one returns "success = false"
Perhaps with the idea no value is being read.


In ESPEasy.ino in

Code: Select all

void SensorSendTask(byte TaskIndex)

There is a check which does a call with PLUGIN_READ:

Code: Select all

    if(Settings.TaskDeviceDataFeed[TaskIndex] == 0)  // only read local connected sensorsfeeds
      success = PluginCall(PLUGIN_READ, &TempEvent, dummyString);
    else
      success = true;

    if (success)
    {
      for (byte varNr = 0; varNr < VARS_PER_TASK; varNr++)
      {
        if (ExtraTaskSettings.TaskDeviceFormula[varNr][0] != 0)
        {
           [...]
        }
      }
      sendData(&TempEvent);
    }

This sendData does also do other things and eventually do a checkUDP().
It is being called from other controllers also, which may explain why it would work when some controller is enabled.

As a test, I will move the call to sendData outside the scope of the if(success) check, since the TempEvent is not changed within that if-scope.

See pull request https://github.com/letscontrolit/ESPEasy/pull/896

If someone could test it, that would be great

[TD-er]

I was just thinking about it. There are better ways to fix it, given it is the problem.

So if anyone could test it is a "fix", then I will write a better fix for it.
This will result in more updates than desired.

[TD-er]

Hopefully the last version of my pull request will result in less frequent unneeded updates.
Could someone test it?
https://github.com/letscontrolit/ESPEasy/pull/896

Eventually I want to change the way global sync is handled.
It is essentially just a controller and thus it should be treated as one, not as a special use case. Those will always lead to strange and hard to debug issues.
I don't like exceptions, especially in software design

[robatbentley]

Sorry TD-er, didn't see your update. I'll give it a test tonight.

Update: I rebuilt 2 x 8266 nodes (loaded with zeros and then the latest build of ESP_Easy_v2.0-20180221_normal_ESP8266_4096), one for the LCD (192.168.1.10) and the other for the BME280 (192.168.1.8) sensor.
I managed to get the global synch working as far as valid sensor values appearing in the LCD nodes device list. ...but still no sensor values appearing on the LCD itself. I tried my usual trick of submitting changes to the BME280 sensor but to no effect.

I noticed that the LCD device had a new option called "LCD command Mode:" but left this as the default of "Continue to next line (as in v1.4)"

I've attached a few LCD screen-shots (apologies for the repetition of some of them - can't get rid of them!) but if further details are needed then just ask. ...and if there's there're any changes you'd like me to test then get back to me again.

[robatbentley]

I've uploaded the latest firmware version ESP_Easy_v2.0-20180228_normal_ESP8266_4096 on both my LCD and sensor nodes but still the same problem.
Can anyone else duplicate this issue? ...as, so far, it seems to be just me with the problem.

[Martinus]

Can you try with the latest version and check the logging on both sender and receiver. Use debug level DEBUG_MORE.
You should see stuff like this:

Sending unit
150500 : C013 : Send UDP message to 1
150511 : C013 : Send UDP message to 3
150521 : C013 : Send UDP message to 4
150532 : C013 : Send UDP message to 5
150543 : C013 : Send UDP message to 6
150553 : C013 : Send UDP message to 7
150624 : C013 : Send UDP message to 14
150634 : C013 : Send UDP message to 15
150665 : C013 : Send UDP message to 18
150786 : C013 : Send UDP message to 30

Receiving unit:
11678439 : UDP : 60:01:94:0F:A2:3F,192.168.0.102,2
11688458 : C013 : msg 5 2 18 10 10
11689498 : UDP : 5C:CF:7F:0F:50:BC,192.168.0.106,6
11690156 : C013 : msg 5 2 18 11 11

Check if the sending units actually sends a UDP message to the receiving unit.
And check if the receiving unit gets it. It should say C013: msg 5 x x x x

[giobbe]

Hi,
But does it work or not at today?
Thanks
Giobbe

[blb4lci]

Can you try with the latest version and check the logging on both sender and receiver. Use debug level DEBUG_MORE.
You should see stuff like this:
.......
Receiving unit:
11678439 : UDP : 60:01:94:0F:A2:3F,192.168.0.102,2
11688458 : C013 : msg 5 2 18 10 10
11689498 : UDP : 5C:CF:7F:0F:50:BC,192.168.0.106,6
11690156 : C013 : msg 5 2 18 11 11

Check if the sending units actually sends a UDP message to the receiving unit.
And check if the receiving unit gets it. It should say C013: msg 5 x x x x

Hi Martinus, I do see these messages on sending and receiving unit, but I don't get the task visible on the receiving unit. What Do I have to do to get this fixed?

[Martinus]

Can you try with the latest version and check the logging on both sender and receiver. Use debug level DEBUG_MORE.
You should see stuff like this:
.......
Receiving unit:
11678439 : UDP : 60:01:94:0F:A2:3F,192.168.0.102,2
11688458 : C013 : msg 5 2 18 10 10
11689498 : UDP : 5C:CF:7F:0F:50:BC,192.168.0.106,6
11690156 : C013 : msg 5 2 18 11 11

Check if the sending units actually sends a UDP message to the receiving unit.
And check if the receiving unit gets it. It should say C013: msg 5 x x x x

Hi Martinus, I do see these messages on sending and receiving unit, but I don't get the task visible on the receiving unit. What Do I have to do to get this fixed?

When UDP communication is ok, you should open and submit the sending device task. This should send a message with the sensor config data and receiving units should create a task automatically (but only if that task is unused!)

[blb4lci]

Thanks Martinus, now it's working again! The task was already active on the sending unit before, now with the change of global sync to a controller it's nessesary to submit again, good to know.