What to do ?

[pjgueno]

Hi, I am PJ from Sensor.Community. I accepted the invitation. Can you explain me the current statut: Is it working ? Does it receive the data ? What should I do ?

Please use my SC mail for important communication because a lot of messages are lost between all the communication channels...

[RikDrabs]

I'm relatively new on GitHub, while an active hardware/software designer since 1977. You already know me, sending you the SDS011's from Belgium, remember ? I'm supporting sensor.community PM sensors in Belgium through LUCHTPIJP since September 2018. And in 2019 I've designed a display for sensor.communty PM sensors, to be rolled out in Brussels. The display consists of 16 blocks 8*8 LED dot matrix MAX7219, grouped in 4 modules of 4 blocks, cascaded, and controlled by an ESP8266 WiFi controller, the same as in the PM sensor. I use several libraries, one of which is the Parola library. COVID stopped the roll out of the display. The intention from the beginning was to publish the design and software of the display on GitHub. Things accelerated in mid-2023 when I became co-organizer of Civic Lab Brussels, under the umbrella of Open Knowledge Belgium. I then wanted to relaunch the InfluencAir project, with the new material that was available in the meantime, including my display. And we are now also going to roll out the DNMS here in Belgium for the first time. The display project is in working order, although a web interface is in the making for configuring it. Configuration now is through recompiling. It gets its data through the API-ID, receiving JSON messages containing the data for the wanted sensor or sensors to show on display. It shows measured values, and text messages describing the air quality. I think it is a useful addition to sensor.community make the general public aware of the problem of PM in polluted air. Since i'm new here, and didn't read all the docs yet, but understood that at least two persons are needed to review code, i thought of you as that second man. We will be organizing building sessions for the display, and other things. See: https://www.meetup.com/nl-NL/civic-lab-brussels/

[pjgueno]

Have you my own system? It is SC Clock in my account.

Can you explain me exactly what it does ?

Call API and show colors ?

[RikDrabs]

Van: Rik Drabs @.> Date: ma 5 feb 2024 om 18:54 Subject: Re: [Luchtpijp/displayPM] What to do ? (Issue #4) To: Luchtpijp/displayPM < @.>

Hi PJ,

Apparently we did some things in parallel. My development of DisplayPM started independently in 2019, not being aware of your intentions... The rollout of the display was halted by COVID, and so was the development. Only recently (mid-2023), while becoming (co-)organiser of Civic Lab Brussels, I wanted to restart the development, and the rollout, together with the rollout of new sensors (SPS30 / BME280 instead of SDS011 / DHT22) and the (first) rollout in Belgium of DNMS. It was the intention of making the display development public on Github from the beginning.

BTW, your SC Clock is nice & adaptable. Some work doesn't need to be duplicated.

The hardware of DisplayPM is simple. 4 blocks 488 dot matrix leds MAX7219. Right now only monocolor LEDs are supported, but a 2.5 times bigger RGB version WS2812B is in the making. Connected to a ESP8266 controller on a small PCB, which i will publish on GitHub too. Right now the prototype is already useable with compiled parameters, but i'm working on a web interface for the parameters. The WiFi SSID & password are parameters which need recompilation too for now.

I will update from time to time, first to implement the web interface, and then more... I can send you one of the prototypes, so you can see for yourself what it does, and how interesting it is to show PM data and corresponding messages to the general public. Also how setup parameters change what is shown, according to the needs of the user. Five user languages are supported: Dutch, French, German, English & Italian. Spanish is in the making.

You can connect it over the WiFi and internet to any PM sensor via the API interface, using JSON messages, and identifying the PM sensor by its API-ID. It can show the result of one sensor, or of two sensors or of a whole bunch of sensors. While showing two sensors, two configurations are supported: two sensors outside, and one sensor outside, and one inside. In both cases sensors can be compared, and the result shown as clear text. While showing a whole bunch, mean values are calculated and shown, and then sensors identified by name are shown exceeding a preset limit, or not working, so a whole region can be monitored with a minimum of messages.

Publishing on GitHub is meant to distribute the knowledge behind the display to other groups needing a similar display in their actions against PM pollution. It certainly is not a finished product right now.

When performing a demo on ByteNight (the FOSDEM conference afterparty) this past saturday with 12 displays showing PM values and corresponding messages from sensors all over the world, I had a problem. https://fosdem.org/2024/ https://foss.events/2024/02-03-bytenight.html

Everything worked well in the preparation phase, but then, after approx. three hours, the messages said "no new data" on all the displays simultaneously. Debugging showed the http server connection showed an error 500, instead of producing the wanted JSON message containing the data.

The API-id's for which the data was requested are: 78346, 42694, 5937, 3491, 819, 21665, 43901, 56321, 61875, 34060, 50367, 9413. On all of them, the failure was reported. And nothing, even restarting the displays or restarting the local router, could solve it. All this while another display, showing the results of a sensor at the location of ByteNight, worked perfectly, over the same router. That display was started several hours later, and also stopped working correctly after +/- 5 hours. When i put one display in test at my home on sunday evening it worked correctly, and continued working correctly till now (monday evening 19h). Do you have server access? To look in the log files, to see which incident at server side produced this problem? So I can adjust the way i'm interacting with the server...

Thanks for the info, thanks for sharing SC Clock...

mvg,

Rik Drabs Assestraat 55, 1700 St-Ulriks-Kapelle Tel: +32(0)475/70.72.60

Op di 23 jan 2024 om 12:48 schreef Pierre-Jean Guéno < @.***>:

Have you my own system? It is SC Clock in my account.

Can you explain me exactly what it does ?

Call API and show colors ?

— Reply to this email directly, view it on GitHub https://github.com/Luchtpijp/displayPM/issues/4#issuecomment-1905872888, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJLIM7FXALCEWGDDGF3RE3DYP6PRNAVCNFSM6AAAAABCD3SIQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBVHA3TEOBYHA . You are receiving this because you were assigned.Message ID: @.***>