Create the Arduino mock

[jomaves]

• Delivers random Data for at least three different read outs (atmospheric pressure, temperature and humidity)
• Defines an interface to the consumer
• Tackles the problem of asynchronicity

[19201080]

Hey @jomaves, i'm working on the interface between the arduino mock and influxdb, and i think it can make sense to have a look at how the data could be formatted to be sent there.

In the branch feature/influxdb_connector (see here), i have an interface that can send data to influxdb. As a parameter to the function writing to influxdb, i use data formatted that way: {'time': '20201125T19:30:20.123456', 'temp': 123, 'atmo': 456, 'humi': 789} time is an optional key, i also provide it in the interface if it's missing. And only one of the temp, atmo, or humi needs to be provided (you can also include two, or all three at once). So these two dicts are also valid parameters: {time': '20201125T19:30:20.123456', 'humi': 789} {'temp': 123, 'atmo': 456}

i do it in this way because maybe not all values are available or accessed at the same time (multiple sensors?). I see in your code for generating values that you have data formatted as [[time], [temp], [atmo], [humi]]. What do you think would be the way to go? Maybe the dictionary could be more robust

[jomaves]

Hey Etienne, perfect, I will create an Dict as you suggested! With time, temp, atmo and humi. One more question, how would we do the actual hand over? Would you request for the dict or would I send it to you in a regular interval? We probably discussed this on Thursday I just can't remember.

[19201080]

Hey, i tell you if you review my pr first 😛 So i think there's many ways to do it. The way i would approach that is:

• a class that creates (and takes care of) a connection to an arduino and can poll it (or alternatively the feature you're creating for faking the arduino data)
• a function that asks the "ArduinoConnector"/"DataGenerator" to get data from the (real or fake) arduino, and sends this data to influxdb through the DatabaseConnector.write function
• some kind of orchestrator to run this function every x minutes (maybe you want 1 measurement per hour or something)

A way to solve this periodic thing could be to use asyncio, and do: poll data → send it → asyncio.sleep → repeat (while loop).

[oxullo]

I'd go for a class approach, starting from the mock random data generator and then create a common ancestor shared between mock and real arduino connector. The class should have a start/stop method that starts a tasks that polls for data, as @19201080 describes. The real deal is how to send the data, for this I'll provide no hint :)

[jomaves]

Thank you Étienne, thank you Marco. I will give my best!