Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to decode packets for [192] Govee Water Leak Detector H5054 #2189

Closed
otanim opened this issue Sep 27, 2022 · 16 comments
Closed

Unable to decode packets for [192] Govee Water Leak Detector H5054 #2189

otanim opened this issue Sep 27, 2022 · 16 comments

Comments

@otanim
Copy link

otanim commented Sep 27, 2022 •
edited
Loading

Using the old version 20.02 (the latest apt package for Ubuntu 20.04) which doesn't support the device Govee Water Leak Detector H5054 yet, detects it as Smoke-GS558:

[REDACTED]@[REDACTED]:~/rtl_433/build$ ./src/rtl_433 
rtl_433 version 20.02 branch  at 202002171252 inputs file rtl_tcp RTL-SDR SoapySDR
Use -h for usage help and see https://triq.org/ for documentation.
Trying conf file at "rtl_433.conf"...
Trying conf file at "/home/[REDACTED]/.config/rtl_433/rtl_433.conf"...
Trying conf file at "/usr/local/etc/rtl_433/rtl_433.conf"...
Trying conf file at "/etc/rtl_433/rtl_433.conf"...
Registered 122 out of 149 device decoding protocols [ 1-4 8 11-12 15-17 19-21 23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 ]
Detached kernel driver
Found Rafael Micro R820T tuner
Exact sample rate is: 250000.000414 Hz
[R82XX] PLL not locked!
Sample rate set to 250000 S/s.
Tuner gain set to Auto.
Tuned to 433.920MHz.
Allocating 15 zero-copy buffers
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
time      : 2022-09-27 22:27:06
model     : Smoke-GS558  id        : [REDACTED]
unit      : 31           learn     : 0             Raw Code  : [REDACTED]

However, the latest versions (master branch) don't seem like being able to detect anything for [ 192 ] device, no output, but here is the verbose message for it (used -vv argument, only trigger-receive output):

oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
preamble 2  348 202
norgo_decode: wrong size of bit per row 22
norgo_decode: wrong size of bit per row 48
norgo_decode: wrong size of bit per row 73
norgo_decode: wrong size of bit per row 99
norgo_decode: wrong size of bit per row 122
norgo_decode: wrong size of bit per row 149
norgo_decode: wrong size of bit per row 175
norgo_decode: wrong size of bit per row 195
norgo_decode: wrong size of bit per row 222
norgo_decode: wrong size of bit per row 250
norgo_decode: wrong size of bit per row 282
norgo_decode: wrong size of bit per row 310
norgo_decode: wrong size of bit per row 330
norgo_decode: wrong size of bit per row 354
norgo_decode: wrong size of bit per row 380
norgo_decode: wrong size of bit per row 405
norgo_decode: wrong size of bit per row 429
norgo_decode: wrong size of bit per row 453
norgo_decode: wrong size of bit per row 477
norgo_decode: wrong size of bit per row 501
norgo_decode: wrong size of bit per row 527
norgo_decode: wrong size of bit per row 550
norgo_decode: wrong size of bit per row 575
norgo_decode: wrong size of bit per row 599
ert_idm_decode: rows=1, row0 len=2400
ert_idm_decode: sync_index=2400
ert_netidm_decode: rows=1, row0 len=2400
ert_netidm_decode: sync_index=2400
markisol_decode: bits_per_row[0] = 2
markisol_decode: bits_per_row[0] = 1
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 21
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {29} 27 b2 6d b0 : 00100111 10110010 01101101 10110
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {29} 27 b2 6d b0 : 00100111 10110010 01101101 10110
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {50} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 10
oregon_scientific_v2_1_decode: Badly formatted OS v2.1 message: {49} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 1
oregon_scientific_v3_decode: Unrecognized Msg in OS v3: {49} 7f ff 99 3d 93 6d 80 : 01111111 11111111 10011001 00111101 10010011 01101101 1
norgo_decode: wrong size of bit per row 11
norgo_decode: wrong size of bit per row 35
norgo_decode: wrong size of bit per row 60
norgo_decode: wrong size of bit per row 82
norgo_decode: wrong size of bit per row 106
norgo_decode: wrong size of bit per row 132
markisol_decode: bits_per_row[0] = 28
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 49
markisol_decode: bits_per_row[0] = 48

Any thoughts on what could've caused this, or do I need to provide any additional data for the debugging?
@franki29
Copy link

franki29 commented Oct 4, 2022

Hi , the sensor is already supported see #1518 (comment)
In this thread you will see a cu8 file that works fine with rtl_433, just try it in your installation it should give you:

time : @0.090488s
model : Govee-Water id : 26902
event : Water Leak Raw Code : 96e904040740 Integrity : PARITY

time : @1.670216s
model : Govee-Water id : 26902
event : Water Leak Raw Code : 96e904040740 Integrity : PARITY

If not please generate a cu8 file and post it, than we can have a look

@otanim
Copy link
Author

otanim commented Oct 5, 2022 •
edited
Loading

Hi @franki29, I did test the cu8 file from here, and it worked for me quite fine, I got the above outputs.

Here is the cu8 file from me, for the same above-mentioned device:
DATE-2022-10-05_FCC-2AQA5-H5054.zip

@otanim
Copy link
Author

otanim commented Oct 5, 2022

Btw, it seems like this is a new version, made/manufactured on 2021-08-10, and it has a different PCB:
image

@zuckschwerdt
Copy link
Collaborator

The timing seems a little shorter, but works. Problem is the ID is invalid FFFF (raw dat all zeros) and the checksum/parity doesn't work. It's mostly the same timing and the packet structure looks like we expect though. Strange, someone needs to take a closer look to find out what's going on.

The Bitbuffer here is

{48} 00 00 cf ab 6a cb : 00000000 00000000 11001111 10101011 01101010 11001011

inverted this is

{48} ff ff 30 54 95 34 : 11111111 11111111 00110000 01010100 10010101 00110100

@franki29
Copy link

franki29 commented Oct 6, 2022

Hi @otanim , can you send us a file that include a alarm ?

@otanim
Copy link
Author

otanim commented Oct 6, 2022

Hi @franki29, here it is:
DATE-2022-10-06_FCC-2AQA5-H5054_MODE-alarm.zip

@franki29
Copy link

franki29 commented Oct 7, 2022

Hi @otanim , I am to new to understand what is happening with your sensor.
The only common with your data is ff ff 3 but with only two different data files it is hard to say.
Hope that someone with more knowledge can help, sorry

@otanim
Copy link
Author

otanim commented Oct 7, 2022

@franki29, would this info help to decode the data?
it is working on 20.02 version, it's just detecting the device as Smoke-GS558.

@franki29
Copy link

franki29 commented Oct 7, 2022

Hi @otanim unfortunately not, there is also a thread regarding wrong detection.
Do you have also the gateway for the detector? If so , does it show a ID in your mobile app?
But It may help if you send us some more examples of press the button and alarm cu8 files to compare the data

@zuckschwerdt
Copy link
Collaborator

For the alarm the Bitbuffer here is

{48} 00 00 cd f9 76 1e : 00000000 00000000 11001101 11111001 01110110 00011110

inverted this is

{48} ff ff 32 06 89 e1 : 11111111 11111111 00110010 00000110 10001001 11100001

As @franki29 correctly analyzed, all bits change and the ID of just FFFF is not plausible.
We need more codes, and you should try to reset the device (remove batteries) and check if you get a proper ID somewhere.

We don't need more .cu8 files, get just the codes (only new unique codes) with

rtl_433 -R 0 -X 'n=name,m=OOK_PWM,s=440,l=940,g=900,r=9000,bits>=48,invert'

@otanim
Copy link
Author

otanim commented Oct 7, 2022 •
edited
Loading

@franki29 / @zuckschwerdt, here are some samples:

{27}401d24e, {1}0, {48}ffff3200e927, {1}0, {48}ffff3200e927, {1}0, {48}ffff3200e927, {1}0, {48}ffff3200e927, {1}0, {48}ffff3200e927
{27}403f20c, {1}0, {48}ffff3201f906, {1}0, {48}ffff3201f906, {1}0, {48}ffff3201f906, {1}0, {48}ffff3201f906, {1}0, {48}ffff3201f906
{27}40592ca, {1}0, {48}ffff3202c965, {1}0, {48}ffff3202c965, {1}0, {48}ffff3202c965, {1}0, {48}ffff3202c965, {1}0, {48}ffff3202c965
{27}407b288, {1}0, {48}ffff3203d944, {1}0, {48}ffff3203d944, {1}0, {48}ffff3203d944, {1}0, {48}ffff3203d944, {1}0, {48}ffff3203d944
{27}4095346, {1}0, {48}ffff3204a9a3, {1}0, {48}ffff3204a9a3, {1}0, {48}ffff3204a9a3, {1}0, {48}ffff3204a9a3, {1}0, {48}ffff3204a9a3
{27}40b7304, {1}0, {48}ffff3205b982, {1}0, {48}ffff3205b982, {1}0, {48}ffff3205b982, {1}0, {48}ffff3205b982, {1}0, {48}ffff3205b982
{27}40d13c2, {1}0, {48}ffff320689e1, {1}0, {48}ffff320689e1, {1}0, {48}ffff320689e1, {1}0, {48}ffff320689e1, {1}0, {48}ffff320689e1
{27}40f3380, {1}0, {48}ffff320799c0, {1}0, {48}ffff320799c0, {1}0, {48}ffff320799c0, {1}0, {48}ffff320799c0, {1}0, {48}ffff320799c0
{27}410d05e, {1}0, {48}ffff3208682f, {1}0, {48}ffff3208682f, {1}0, {48}ffff3208682f, {1}0, {48}ffff3208682f, {1}0, {48}ffff3208682f
{27}412f01c, {1}0, {48}ffff3209780e, {1}0, {48}ffff3209780e, {1}0, {48}ffff3209780e, {1}0, {48}ffff3209780e, {1}0, {48}ffff3209780e
{27}41490da, {1}0, {48}ffff320a486d, {1}0, {48}ffff320a486d, {1}0, {48}ffff320a486d, {1}0, {48}ffff320a486d, {1}0, {48}ffff320a486d
{27}416b098, {1}0, {48}ffff320b584c, {1}0, {48}ffff320b584c, {1}0, {48}ffff320b584c, {1}0, {48}ffff320b584c, {1}0, {48}ffff320b584c
{27}4185156, {1}0, {48}ffff320c28ab, {1}0, {48}ffff320c28ab, {1}0, {48}ffff320c28ab, {1}0, {48}ffff320c28ab, {1}0, {48}ffff320c28ab
{27}41a7114, {1}0, {48}ffff320d388a, {1}0, {48}ffff320d388a, {1}0, {48}ffff320d388a, {1}0, {48}ffff320d388a, {1}0, {48}ffff320d388a
{27}41c11d2, {1}0, {48}ffff320e08e9, {1}0, {48}ffff320e08e9, {1}0, {48}ffff320e08e9, {1}0, {48}ffff320e08e9, {1}0, {48}ffff320e08e9
{27}41e3190, {1}0, {48}ffff320f18c8, {1}0, {48}ffff320f18c8, {1}0, {48}ffff320f18c8, {1}0, {48}ffff320f18c8, {1}0, {48}ffff320f18c8
{27}421f62c, {1}0, {48}ffff3210fb16, {1}0, {48}ffff3210fb16, {1}0, {48}ffff3210fb16, {1}0, {48}ffff3210fb16, {1}0, {48}ffff3210fb16
  • it seems like if I remove the battery and put it back and try to trigger the alarm it will generate the exact same sequences of the codes in the same order.
  • if I trigger the alarm within 1-5 seconds, it keeps generating the same lines of codes, but the order won't be broken for the next sequences.

@franki29
Copy link

franki29 commented Oct 7, 2022

Does N2 an N3 shows correct output ? If you just start rtl_433 -R 192 ?

@franki29
Copy link

franki29 commented Oct 7, 2022

So I think that the N1 is just maybe broken or not correctly programmed in the factory.

@otanim
Copy link
Author

otanim commented Oct 7, 2022 •
edited
Loading

@franki29, I'm second-guessing that theory, but I can test the rest of the 4 devices as well, to see if there are any patterns. I'll keep updated here.

@otanim
Copy link
Author

otanim commented Oct 7, 2022 •
edited
Loading

@franki29, you were right, can confirm, the rest 4 devices worked for me without any issues as well...
I've opened the 2nd device, it had the same PCB and date of creation/manufacturing as the device n1.

It is quite interesting that I've been using the defective device out of 7 devices for my project.

@zuckschwerdt / @franki29, thanks again for the support and for your time, I appreciate it. I'm closing the issue.

@otanim otanim closed this as completed Oct 7, 2022
@zuckschwerdt
Copy link
Collaborator

That was unexpected, but really seems the best explanation. Glad to hear we worked out what was wrong.

@franki29 franki29 mentioned this issue Dec 4, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@zuckschwerdt @otanim @franki29