I believe that the entire member list was being sent in 2 cases: 1. when any member's location name had changed or when no members' location had changed... Although I think there's more to it and I suspect it has to do with different circles and places and there being only 1 "updated_locations" array...

The same location can have a life360 place with a different name in a different circle. E.g. circles made by different users that invite one another. The way it was written, overlapping places cause spurious location events.

Files checked in: nodes/*

… that is planned.

Files checked in: index.js nodes/location.* nodes/server.js

I have only tested the any circle, any event case.
Also, this currently does not support multiple location nodes.

Files checked in: nodes/location.js nodes/server.js

Changed the changed value callback to an array to support multiple location nodes.
Fixed a problem with the calculation of a location's previous occupancy.
Added some debug statements.

Files checked in: nodes/location.js nodes/server.js

…-life into first_arrive_leave_trigger

…t72/node-red-contrib-life into first_arrive_leave_trigger

Files checked in: nodes/location.html nodes/location.js nodes/server.js

Files checked in: index.js nodes/location.html nodes/location.js nodes/server.js

Files checked in: nodes/server.js

…ing last to leave.

Files checked in: nodes/server.js

…eave events on startup.

Files checked in: nodes/location.html nodes/location.js nodes/server.js

Files checked in: package.json