In parking meter view, if attendant picks to choose area map loading and spanning is not responsive and doesn't stop loading making it unresponsive for a long period of time.

Making new parking event for a register number that already is registered for parking will override previous event regardless of expiration time. E.g. if first event would expire in an hour, and second in 5 minutes, the latter will override previous. This should be: latter event will override previous event only if it would expire later.

Both in driver app(paid parking view) and attendant app(disc and smart meter view) scan buttons are spammable for unlimited time. This makes application scan for bluetooth devices unlimited amount of times at the same time and displaying the results for each by refreshing view after each scan ends.
If there is no device detected this results in user getting spammed back with dialog box "Nothing detected .." while making application unusable.

The attendant map is not reloaded after the following steps:

1. Start attendant app
2. Select "Parking meter" > "Choose area" > "Back" > "Home" > "Parking meter" > "Choose area"

See Google Cloud Log with insertid "282mbvg1cwj0je".

At the moment, it is not checked if the incoming parking type + parking area id combination matches to the actual parking area data. Should be validated instead.

If smart meter send error message on failed price request (e.g. no internet connection), Driver app displays 'NaN/hour' as the price.

Scanning BLE beacons in attendant gear shows items like 'ABC123_00318' in beacon list after scanning. This should be changed to 'ABC123'. Filter '_' and everything after it.

1. open app
2. go to map
   3 go to situations and then to check the parking meter parking events and click Change area.
   ->the map is stuck to loading

If there is a paid parking beacons nearby and if you scan and detect those beacons in parking disc view they always show up as invalid(expired) parking regardless if they are invalid or not in paid parking areas. Also there aren't any distinctions between disc and paid parking in disc view making it possible them to mix up in close areas.

Driver app, paid parking view, after connecting to smart meter and pressing pay button makes pay button disabled for 1-2 seconds but it enables again even though this time is mostly not enough for process to complete.
This leaves like 3-4 seconds where there is no visual feedback for user on screen to understand that there is payment confirmation going on and pay button is still clickable during this time, clicking results in undesired behaviour.