beepnl / beep-react-native-app

React native app for Android and iOS
1 stars 0 forks source link

Unable to open Temperature "Configure" screen (0.0.16) #2

Closed ezja closed 2 years ago

ezja commented 2 years ago

No value shown at "Current Reading" in the Temperature screen and unable to open the "Configure" screen from there (one DS1820 temperature sensor connected).

adb log when opening the Temperature screen:


08-19 16:39:39.860  4718 12335 D ReactNativeBleManager: Write to: D5:DC:45:32:0F:D4
08-19 16:39:39.860  4718 12335 D ReactNativeBleManager: Message(1): 04
08-19 16:39:40.172  4718  4748 D ReactNativeBleManager: Command queue empty
08-19 16:39:40.172  4718  4748 D ReactNativeBleManager: onCharacteristicChanged: 040109E9 from peripheral: D5:DC:45:32:0F:D4
08-19 16:39:40.173  4718 12333 I ReactNativeJS: Written data: 04
08-19 16:39:44.865  4718 12335 D ReactNativeBleManager: Write to: D5:DC:45:32:0F:D4
08-19 16:39:44.865  4718 12335 D ReactNativeBleManager: Message(2): 84FF
08-19 16:39:45.123  4718  4748 D ReactNativeBleManager: Command queue empty
08-19 16:39:45.124  4718 12333 I ReactNativeJS: Written data: 84FF
08-19 16:39:45.124  4718  4748 D ReactNativeBleManager: onCharacteristicChanged: 008400000000 from peripheral: D5:DC:45:32:0F:D4
08-19 16:39:45.125  4718 12333 I ReactNativeJS: 'BLE response', { '0': 132, '1': 0, '2': 0, '3': 0, '4': 0 }
08-19 16:39:45.126  4718 12333 I ReactNativeJS: 'BLE response', { '0': 132, '1': 0, '2': 0, '3': 0, '4': 0 }

log when attempting to to open the Temperature "Configure" screen:

08-19 16:34:21.837  4718 12335 W unknown:ReactNative: Attempt to set local data for view with unknown tag: 1777
08-19 16:34:21.840  4718 12335 W unknown:ReactNative: Attempt to set local data for view with unknown tag: 1823
08-19 16:34:21.846  4718 12335 I chatty  : uid=10369(it.vandillen.beep) mqt_native_modu identical 1 line
08-19 16:34:21.849  4718 12335 W unknown:ReactNative: Attempt to set local data for view with unknown tag: 1823
08-19 16:34:21.851  4718 12335 W unknown:ReactNative: Tried to update size of non-existent tag: 1889
maartenvandillen commented 2 years ago

Probably caused by inconsistent number of sensor definitions vs actual sensors. I have removed this constraint but we should discuss how this can happen.

ezja commented 2 years ago

In 0.0.17: the Current Value of the sensor is displayed now, but the least recently created sensor definition for t_0 is used ("Sensor 1")

Image

Opening the Configure-page does not work. Error: command code 132, invalid state.