#1 App lags after changing brew temperature

Open
opened 5 years ago by alexDrinkwater · 1 comments

When pressing the temperature up button on the home screen there are a few seconds before the temperature increases. The user does not know if the button press has been successfully registered. If the user presses the button again before the temperature display updates the app can hang and crash. MVP fix would be to disable the buttons while the temperature update is processing.

This was on a LG G6.

When pressing the temperature up button on the home screen there are a few seconds before the temperature increases. The user does not know if the button press has been successfully registered. If the user presses the button again before the temperature display updates the app can hang and crash. MVP fix would be to disable the buttons while the temperature update is processing. This was on a LG G6.
meCoffee commented 5 years ago
Owner

The suggested MVP fix will not cut it. The problem originates from the fact that the Bluetooth connection is assumed to be unreliable : you can be out of range, and BLE just drops those messages. So you might end up with the buttons disabled forever.

So currently it is basically send-and-pray and the user interface will only update when the change in setpoint is fed back from your meCoffee in the regular recurring status messages.

However, things can be improved : meCoffee echoes a change of setting by emitting 'cmd set xyz_s OK' ( notice the '_s' ) when a change to xyz has been registered. As this is echoed back directly, this message should be listened to. If the message is not received within a certain threshold, the user interface should be unlocked again. Or a transmission retry.

So certainly a valid issue but we must thread carefully.

The suggested MVP fix will not cut it. The problem originates from the fact that the Bluetooth connection is assumed to be unreliable : you can be out of range, and BLE just drops those messages. So you might end up with the buttons disabled forever. So currently it is basically send-and-pray and the user interface will only update when the change in setpoint is fed back from your meCoffee in the regular recurring status messages. However, things can be improved : meCoffee echoes a change of setting by emitting 'cmd set xyz_s OK' ( notice the '_s' ) when a change to xyz has been registered. As this is echoed back directly, this message should be listened to. If the message is not received within a certain threshold, the user interface should be unlocked again. Or a transmission retry. So certainly a valid issue but we must thread carefully.
Sign in to join this conversation.
No Label
No Milestone
No assignee
2 Participants
Loading...
Cancel
Save
There is no content yet.