Hey,

I have a question related to this tool. is it possible to search for appointments for a specific service I am looking for? I am looking to book an appointment to change my passport info on the blue card. Thanks in advance

https://service.berlin.de/dienstleistung/326798/en/

As a young software developer new in Berlin I had to accept a job offer but the next appointment for anmeldung was in 8 weeks, thanks to your tool I got one the same day. For you it must be insignificant and you will have received thousands of similar messages but for me it means the world. Thanks ❤️

When a client joins the server, only that client needs the last_message and a broadcast to all is not really needed.

This avoid processing in the server side + makes the response frequency/events more expectable if that makes sense.

Description

Sometimes in the Output results, there are duplicate dates in the appointmentDates array. I suppose from the web requests its happening and needs to be handled accordingly.

Actual Result

The following values are repeated {'time':` '2022-02-01T14:01:50Z', 'status': 200, 'message': None, 'appointmentDates': ['2022-02-01T00:00:00Z', '2022-03-01T00:00:00Z', '2022-03-01T00:00:00Z', '2022-03-09T00:00:00Z', '2022-03-09T00:00:00Z', '2022-03-28T00:00:00Z', '2022-03-28T00:00:00Z', '2022-03-29T00:00:00Z', '2022-03-29T00:00:00Z', '2022-03-31T00:00:00Z', '2022-03-31T00:00:00Z'], 'connectedClients': `0}

Expected Result

Duplicate Values should be removed.

Recommendation

For Example:

# using naive method
# to remove duplicated 
# from list 
res = []
for i in test_list:
    if i not in res:
        res.append(i)

Raising an exception when the required environment variables are not present will prevent the server from running either way and sending None as the email and tool id.

Additonally, when the server starts running, an info message is emited for better debugging.

The function that fetches appointments was blocking the main thread, mainly because it was using the requests library that does not support async/await.

That meant that during the get_appointment duration (which was ~ the latency of 2 requests + 1 second of sleep) the websocket server was not able to attend new connections and clients would need to wait until the thread was freed to establish connection.

Moving to the aiohttp library constantly frees the main thread so it is able to attend new incoming connections, thus making the experience more responsive for clients

Description

The telegram notification functionality is added to the existing application. Therefore, one can setup his telegram bot and receive the message every 30 seconds regarding the status. If the appointment dates are available, then the person will receive the message along with the available dates and appointment URL.

Screenshot

Output

The next appointment for flat registration is available on the following dates 29-Mar-2022 Please use this URL to book the appointment faster: (https://service.berlin.de/terminvereinbarung/termin/tag.php?termin=1&anliegen[]=120686&dienstleisterlist=122210,122217,327316,122219,327312,122227,327314,122231,122243,327348,122252,329742,122260,329745,122262,329748,122254,329751,122271,327278,122273,327274,122277,327276,330436,122280,327294,122282,327290,122284,327292,327539,122291,327270,122285,327266,122286,327264,122296,327268,150230,329760,122301,327282,122297,327286,122294,327284,122312,329763,122314,329775,122304,327330,122311,327334,122309,327332,122281,327352,122279,329772,122276,327324,122274,327326,122267,329766,122246,327318,122251,327320,122257,327322,122208,327298,122226,327300&herkunft=http%3A%2F%2Fservice.berlin.de%2Fdienstleistung%2F120686%2F)