CubeCell Configurator

[Gipsyblues]

Had a potential professional group test the cubececell capsule today using the configurator designed by @rsmedia

1. Geographical region: US
2. This is the output of the debug screen:

Downloadind Firmware …
Downloadind Firmware done
Flashing Firmware …
Flashing Firmware done
CleanUp Starting
CleanUp done
AT+DevEui=0053BCEFDE322854
AT+AppEui=70B3D57ED0027527
AT+AppKey=9997374D3E037024033967622987D154
AT+DutyCycle=900000

AT+RESET=1

Please note the following when reading @rsmedia configuration guide
Under the CubeCell Configurator for configuration, section Use CubeCell Configurator for configuration please read as follows

a. Go to TTN, and create an application if you haven’t already

b Under your application create a device for the CubeCell device you are setting up

c. copy the keys: Device EUI, Application EUI and App Key

Please note that you should copy and paste only one key at a time. On TTN you will notice that there is a Copy icon at the end of each key field. Then back in the Configurator screen just paste each value you copied from the TTN device screen

d. Once those three values are entered, click on write

e. The keys will be saved in the CubeCell device and the device will reboot
If you click on the Debug type you should see the above log entry - last line should read
AT+RESET=1

The guide does not say what is supposed to happen or what you should do next

Any pointers: the 915 MHz capsule is connected to a USB board connected to Com15 of an HP PC
TIA

[sronan]

As per my message here:

CubeCell Configurator

Sure! But now, after I reflash the firmware and then connect and enter the user data (DevEUI, etc.) and duty cycle and try to write it, it just gets this far: AT+DevEui=003981B550BD22EA AT+AppEui=70B3D57ED00269A4 AT+AppKey=B423D01003D3F1A1B932C2A7CD027990 AT+DutyCycle=900000 AT+RESET=1 And then stops. And if I then disconnect and connect again, the DevEUI, etc. are blank.

just yesterday (December 13) I had results similar to what you describe and subsequently a new version of the firmware was developed.

Could you try again now?

I’d add to your excellent, clear outline of procedures just a reminder to select the right frequency (e.g., US915) in the Configurator.

[rsmedia]

thank you @[Gipsyblues
just updated the guide to make the needed steps a little clearer.

Please note that the version of the configurator ist not the version of the firmware.
The configurator downloads allways the newest firmware.

[Gipsyblues]

Thank you guys for your prompt responses - @rsmedia and @sronan in particular.
@sronan, the configurator software I downloaded was only yesterday night, so I will assume that it is the latest .

Also you should know that I did test the Configurator software using a CubeCell dev board and the software worked perfectly! So the issue has to be with the CubeCell capsule I am using for the test

One thing I noticed, BTW I am using a Windows PC, when I used the dev board, the DOS window shows a complete count down/up of 10, 20, 30, etc. However with the capsule the DOS windows closes before the count down/up.

I intend to try the capsule setup again and hopefully report the results.

Once again @rsmedia, thanks you for your fantastic work. Just another comment: could you please fix a typo in the debug messages. the word downloading is spelt as “downloadind” it should be corrected to downloading - ending with a “g” and not a “d” . Please pardon my comment, too many years of spending time in the air force and teaching at a college make me do that:smile:

[rsmedia]

Will fix the typo later today. Thank for reporting @Gipsyblues
Will take a look why the firmware write for the capsule does not work as intended. I am right now in berlin and took only a dev board with me. All capsule are left at home.

Please keep in mind that the version of the configurator has nothing to do with the firmware version.
The newest firmware is allways downloaded before flashing.

[sronan]

Did you have a chance to see how the CubeCell capsule shows up in the Windows device manager?

This may perhaps be relevant

Warning regarding cubecell capsule

As you suggested, I tried another USB cable and instead of a “not recognized” USB in device manager I then saw CP2102 USB to UART Bridge Controller There was a triangle with exclamation mark and the explanation “The drivers for this device are not installed.” “There are no compatible drivers for this device.” Update driver didn’t find an appropriate driver… but I installed a driver from here https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers And the …

[Gipsyblues]

Yes, I did. The strange thing is that I have successfully tested and proven system working using 2 different dev boards. But no matter what I do I just cannot get the dos prompt screen entries to go beyond" initialising bootloader". However the Configurator debug screen claims that the capsule is flashed but definitely no uploading of any sort being done.

The next thing will be me replacing the USB cable to see if the capsule just doe not like what I am using now - which by the way works properly with the dev boards!

@rsmedia , @Sivaelid does the capsule need to have a battery installed inside in addition to the USB power for it to be debugged properly??

[rsmedia]

no battery needed inside the capsule.
The power from the USB board is ok.
Will be back at home on tuesday evening and will test it with my capsules.

the configurator does not check the output of the dos windows for flashing and will allways report flashing done.
this is on my agenda to check the output and report the result in the configurator.

there will be a update of the configurator next week.
in this update there will be many fixes and error messages if somethings goes wrong.

[Gipsyblues]

Thanks for the answer

As selfish as i could be at times, I would say @rsmedia, please take some, while away from all of us, to rest - at least while away from home! You have more than earned it!

[rsmedia]

the new configurator is online. it now handel some common failures.

i have found a failure in my compiling script. some firmware files were compiled with AT commands disabled.
this is now fixed and all firmware files updated.

now i will go out to have a beer or two.

good night to all of you.

[sronan]

So do you have “Silicon Labs CP210x USB to UART Bridge” showing in your device manager for the capsule? That’s what I have after installing their driver.

[rsmedia]

the driver should be installed via windows update.
if not you can find it here:

https://www.silabs.com/documents/public/software/CP210x_Universal_Windows_Driver.zip

[Gipsyblues]

@sronan, the Silicon Labs CP210x driver once correctly or successfully installed would appear in the Device Manager dialog box (window) as “Silicon Labs CP210x USB to UART Bridge” under Ports (COM & LPT) - if you connect any device using any of the CP210x chips. When you remove the device, that entry for the driver vanishes from below the Port(COM & LPT) listing. So as you are reporting, you have successfully installed the driver

Using the version 2.6 of the Configurator by @rsmedia, I am getting an error about format and operation hanging at joining and never connecting to TTN please see the debug output that follows

For the capsule board I had to reflash more than 9 times before success and at times just could not repeat the results!
@rsmedia, could you please confirm what the error means in the debug screen, and why one needs to flash that many times on a capsule. TIA GB.

Downloadind Firmware …
Downloading Firmware done
Flashing Firmware …
Initialising bootloader.
Silicon ID 0x256a11b5, revision 0.
Verifying rows.
Array 0: first row 34, last row 511.
Starting upload.
Uploading ( 10 / 100 )
Uploading ( 20 / 100 )
Uploading ( 30 / 100 )
Uploading ( 40 / 100 )
Uploading ( 50 / 100 )
Uploading ( 60 / 100 )
Uploading ( 70 / 100 )
Uploading ( 80 / 100 )
Uploading ( 90 / 100 )
Uploading ( 100 / 100 )
Checksum verifies OK.
Rebooting.
Total upload time 23.13s
Flashing Firmware done
CleanUp Starting
CleanUp done
Copyright @ 2019 Heltec Automation.All rights reserved.
+ERROR: error input format
+OK
+DutyCycle=900000
Scanning…
I2C device found at address 0x01 !
I2C device found at address 0x02 !
I2C device found at address 0x03 !
I2C device found at address 0x04 !
I2C device found at address 0x05 !
I2C device found at address 0x06 !
I2C device found at address 0x07 !
I2C device found at address 0x08 !
I2C device found at address 0x09 !
I2C device found at address 0x0A !
I2C device found at address 0x0B !
I2C device found at address 0x0C !
I2C device found at address 0x0D !
I2C device found at address 0x0E !
I2C device found at address 0x0F !
I2C device found at address 0x10 !
I2C device found at address 0x11 !
I2C device found at address 0x12 !
I2C device found at address 0x13 !
I2C device found at address 0x14 !
I2C device found at address 0x15 !
I2C device found at address 0x16 !
I2C device found at address 0x17 !
I2C device found at address 0x18 !
I2C device found at address 0x19 !
I2C device found at address 0x1A !
I2C device found at address 0x1B !
I2C device found at address 0x1C !
I2C device found at address 0x1D !
I2C device found at address 0x1E !
I2C device found at address 0x1F !
I2C device found at address 0x20 !
I2C device found at address 0x21 !
I2C device found at address 0x22 !
I2C device found at address 0x23 !
found BH1750
I2C device found at address 0x24 !
I2C device found at address 0x25 !
I2C device found at address 0x26 !
I2C device found at address 0x27 !
I2C device found at address 0x28 !
I2C device found at address 0x29 !
I2C device found at address 0x2A !
I2C device found at address 0x2B !
I2C device found at address 0x2C !
I2C device found at address 0x2D !
I2C device found at address 0x2E !
I2C device found at address 0x2F !
I2C device found at address 0x30 !
I2C device found at address 0x31 !
I2C device found at address 0x32 !
I2C device found at address 0x33 !
I2C device found at address 0x34 !
I2C device found at address 0x35 !
I2C device found at address 0x36 !
I2C device found at address 0x37 !
I2C device found at address 0x38 !
I2C device found at address 0x39 !
I2C device found at address 0x3A !
I2C device found at address 0x3B !
I2C device found at address 0x3C !
I2C device found at address 0x3D !
I2C device found at address 0x3E !
I2C device found at address 0x3F !
I2C device found at address 0x40 !
Found HDC1080
I2C device found at address 0x41 !
I2C device found at address 0x42 !
I2C device found at address 0x43 !
I2C device found at address 0x44 !
I2C device found at address 0x45 !
I2C device found at address 0x46 !
I2C device found at address 0x47 !
I2C device found at address 0x48 !
I2C device found at address 0x49 !
I2C device found at address 0x4A !
I2C device found at address 0x4B !
I2C device found at address 0x4C !
I2C device found at address 0x4D !
I2C device found at address 0x4E !
I2C device found at address 0x4F !
I2C device found at address 0x50 !
I2C device found at address 0x51 !
I2C device found at address 0x52 !
I2C device found at address 0x53 !
I2C device found at address 0x54 !
I2C device found at address 0x55 !

AT Rev 0.5

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=0000000000000000(For OTAA Mode)
+AppEui=0000000000000000(For OTAA Mode)
+AppKey=00000000000000000000000000000000(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)

LoRaWan Class A start!
joining…
AT+DevEui=00A5151A240545EA
AT+AppEui=70B3D57ED0027527
AT+AppKey=99D22FAAD556D60FC3D552C74E5AA886
AT+DutyCycle=900000

AT+RESET=1
+ERROR: error input format
+OK
+DevEui=00A5151A240545EA(For OTAA Mode)
+OK
+AppEui=70B3D57ED0027527(For OTAA Mode)
+OK
+AppKey=99D22FAAD556D60FC3D552C74E5AA886(For OTAA Mode)
+OK
+DutyCycle=900000
+OK
Copyright @ 2019 Heltec Automation.All rights reserved.
Scanning…
I2C device found at address 0x01 !
I2C device found at address 0x02 !
I2C device found at address 0x03 !
I2C device found at address 0x04 !
I2C device found at address 0x05 !
I2C device found at address 0x06 !
I2C device found at address 0x07 !
I2C device found at address 0x08 !
I2C device found at address 0x09 !
I2C device found at address 0x0A !
I2C device found at address 0x0B !
I2C device found at address 0x0C !
I2C device found at address 0x0D !
I2C device found at address 0x0E !
I2C device found at address 0x0F !
I2C device found at address 0x10 !
I2C device found at address 0x11 !
I2C device found at address 0x12 !
I2C device found at address 0x13 !
I2C device found at address 0x14 !
I2C device found at address 0x15 !
I2C device found at address 0x16 !
I2C device found at address 0x17 !
I2C device found at address 0x18 !
I2C device found at address 0x19 !
I2C device found at address 0x1A !
I2C device found at address 0x1B !
I2C device found at address 0x1C !
I2C device found at address 0x1D !
I2C device found at address 0x1E !
I2C device found at address 0x1F !
I2C device found at address 0x20 !
I2C device found at address 0x21 !
I2C device found at address 0x22 !
I2C device found at address 0x23 !
found BH1750
I2C device found at address 0x24 !
I2C device found at address 0x25 !
I2C device found at address 0x26 !
I2C device found at address 0x27 !
I2C device found at address 0x28 !
I2C device found at address 0x29 !
I2C device found at address 0x2A !
I2C device found at address 0x2B !
I2C device found at address 0x2C !
I2C device found at address 0x2D !
I2C device found at address 0x2E !
I2C device found at address 0x2F !
I2C device found at address 0x30 !
I2C device found at address 0x31 !
I2C device found at address 0x32 !
I2C device found at address 0x33 !
I2C device found at address 0x34 !
I2C device found at address 0x35 !
I2C device found at address 0x36 !
I2C device found at address 0x37 !
I2C device found at address 0x38 !
I2C device found at address 0x39 !
I2C device found at address 0x3A !
I2C device found at address 0x3B !
I2C device found at address 0x3C !
I2C device found at address 0x3D !
I2C device found at address 0x3E !
I2C device found at address 0x3F !
I2C device found at address 0x40 !
Found HDC1080
I2C device found at address 0x41 !
I2C device found at address 0x42 !

AT Rev 0.5

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=00A5151A240545EA(For OTAA Mode)
+AppEui=70B3D57ED0027527(For OTAA Mode)
+AppKey=99D22FAAD556D60FC3D552C74E5AA886(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)

LoRaWan Class A start!
joining…

[Gipsyblues]

@rsmedia, I just noticed an updated Configurator software. I will go back and test using the latest version and report back

[Gipsyblues]

@rsmedia, I just installed the v2.7 Configurator. There appears to be errors but the device at least successfully connected to TTN. @rsmedia, could you please check the debug output and confirm what these errors are? TIA

Downloadind Firmware …
Downloading Firmware done
Flashing Firmware …
Initialising bootloader.
Silicon ID 0x256a11b5, revision 0.
Verifying rows.
Array 0: first row 34, last row 511.
Starting upload.
Uploading ( 10 / 100 )
Uploading ( 20 / 100 )
Uploading ( 30 / 100 )
Uploading ( 40 / 100 )
Uploading ( 50 / 100 )
Uploading ( 60 / 100 )
Uploading ( 70 / 100 )
Uploading ( 80 / 100 )
Uploading ( 90 / 100 )
Uploading ( 100 / 100 )
Checksum verifies OK.
Rebooting.
Total upload time 23.05s
Flashing Firmware done
CleanUp Starting
CleanUp done
Copyright @ 2019 Heltec Automation.All rights reserved.
+ERROR: error input format
+OK
+DutyCycle=900000
Scanning…
I2C device found at address 0x01 !
I2C device found at address 0x02 !
I2C device found at address 0x03 !
I2C device found at address 0x04 !
I2C device found at address 0x05 !
I2C device found at address 0x06 !
I2C device found at address 0x07 !
I2C device found at address 0x08 !
I2C device found at address 0x09 !
I2C device found at address 0x0A !
I2C device found at address 0x0B !
I2C device found at address 0x0C !
I2C device found at address 0x0D !
I2C device found at address 0x0E !
I2C device found at address 0x0F !
I2C device found at address 0x10 !
I2C device found at address 0x11 !
I2C device found at address 0x12 !
I2C device found at address 0x13 !
I2C device found at address 0x14 !
I2C device found at address 0x15 !
I2C device found at address 0x16 !
I2C device found at address 0x17 !
I2C device found at address 0x18 !
I2C device found at address 0x19 !
I2C device found at address 0x1A !
I2C device found at address 0x1B !
I2C device found at address 0x1C !
I2C device found at address 0x1D !
I2C device found at address 0x1E !
I2C device found at address 0x1F !
I2C device found at address 0x20 !
I2C device found at address 0x21 !
I2C device found at address 0x22 !
I2C device found at address 0x23 !
found BH1750
I2C device found at address 0x24 !
I2C device found at address 0x25 !
I2C device found at address 0x26 !
I2C device found at address 0x27 !
I2C device found at address 0x28 !
I2C device found at address 0x29 !
I2C device found at address 0x2A !
I2C device found at address 0x2B !
I2C device found at address 0x2C !
I2C device found at address 0x2D !
I2C device found at address 0x2E !
I2C device found at address 0x2F !
I2C device found at address 0x30 !
I2C device found at address 0x31 !
I2C device found at address 0x32 !
I2C device found at address 0x33 !
I2C device found at address 0x34 !
I2C device found at address 0x35 !
I2C device found at address 0x36 !
I2C device found at address 0x37 !
I2C device found at address 0x38 !
I2C device found at address 0x39 !
I2C device found at address 0x3A !
I2C device found at address 0x3B !
I2C device found at address 0x3C !
I2C device found at address 0x3D !
I2C device found at address 0x3E !
I2C device found at address 0x3F !
I2C device found at address 0x40 !
Found HDC1080
I2C device found at address 0x41 !
I2C device found at address 0x42 !
I2C device found at address 0x43 !
I2C device found at address 0x44 !
I2C device found at address 0x45 !
I2C device found at address 0x46 !
I2C device found at address 0x47 !
I2C device found at address 0x48 !
I2C device found at address 0x49 !
I2C device found at address 0x4A !
I2C device found at address 0x4B !
I2C device found at address 0x4C !
I2C device found at address 0x4D !
I2C device found at address 0x4E !
I2C device found at address 0x4F !

AT Rev 0.5

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=0000000000000000(For OTAA Mode)
+AppEui=0000000000000000(For OTAA Mode)
+AppKey=00000000000000000000000000000000(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)

LoRaWan Class A start!
+ERROR: error input format
joining…
+OK
+DevEui=0000000000000000(For OTAA Mode)
+OK
+AppEui=0000000000000000(For OTAA Mode)
+OK
+AppKey=00000000000000000000000000000000(For OTAA Mode)
+OK
+DutyCycle=900000
AT+DevEui=00A5151A240545EA
AT+AppEui=70B3D57ED0027527
AT+AppKey=99D22FAAD556D60FC3D552C74E5AA886
AT+DutyCycle=900000

AT+RESET=1
+ERROR: error input format
+OK
+DevEui=00A5151A240545EA(For OTAA Mode)
+OK
+AppEui=70B3D57ED0027527(For OTAA Mode)
+OK
+AppKey=99D22FAAD556D60FC3D552C74E5AA886(For OTAA Mode)
+OK
+DutyCycle=900000
+OK
Copyright @ 2019 Heltec Automation.All rights reserved.
Scanning…
I2C device found at address 0x01 !
I2C device found at address 0x02 !
I2C device found at address 0x03 !
I2C device found at address 0x04 !
I2C device found at address 0x05 !
I2C device found at address 0x06 !
I2C device found at address 0x07 !
I2C device found at address 0x08 !
I2C device found at address 0x09 !
I2C device found at address 0x0A !
I2C device found at address 0x0B !
I2C device found at address 0x0C !
I2C device found at address 0x0D !
I2C device found at address 0x0E !
I2C device found at address 0x0F !
I2C device found at address 0x10 !
I2C device found at address 0x11 !
I2C device found at address 0x12 !
I2C device found at address 0x13 !
I2C device found at address 0x14 !
I2C device found at address 0x15 !
I2C device found at address 0x16 !
I2C device found at address 0x17 !
I2C device found at address 0x18 !
I2C device found at address 0x19 !
I2C device found at address 0x1A !
I2C device found at address 0x1B !
I2C device found at address 0x1C !
I2C device found at address 0x1D !
I2C device found at address 0x1E !
I2C device found at address 0x1F !
I2C device found at address 0x20 !
I2C device found at address 0x21 !
I2C device found at address 0x22 !
I2C device found at address 0x23 !
found BH1750
I2C device found at address 0x24 !
I2C device found at address 0x25 !
I2C device found at address 0x26 !
I2C device found at address 0x27 !
I2C device found at address 0x28 !
I2C device found at address 0x29 !
I2C device found at address 0x2A !
I2C device found at address 0x2B !
I2C device found at address 0x2C !
I2C device found at address 0x2D !
I2C device found at address 0x2E !
I2C device found at address 0x2F !
I2C device found at address 0x30 !
I2C device found at address 0x31 !
I2C device found at address 0x32 !
I2C device found at address 0x33 !
I2C device found at address 0x34 !
I2C device found at address 0x35 !
I2C device found at address 0x36 !
I2C device found at address 0x37 !
I2C device found at address 0x38 !
I2C device found at address 0x39 !
I2C device found at address 0x3A !
I2C device found at address 0x3B !
I2C device found at address 0x3C !
I2C device found at address 0x3D !

AT Rev 0.5

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=00A5151A240545EA(For OTAA Mode)
+AppEui=70B3D57ED0027527(For OTAA Mode)
+AppKey=99D22FAAD556D60FC3D552C74E5AA886(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)

LoRaWan Class A start!
joining…
joined
[BH1750] ERROR: received NACK on transmit of data
[BH1750] Device is not configured!
[BH1750] Device is not configured!
BH1750: Light = -2.00lx
BatteryVoltage: 4148, AppDataSize: 5
6 FF EC 10 34
confirmed uplink sending …
receive data: rssi = -64, snr = 12, datarate = 13

[sronan]

When you are seeing
LoRaWan Class A start!
joining…

have you been able to check TTN application data and gateway traffic data?

On several recent attempts, while seeing “joining” in the Configurator and (occasionally “join failed”), I’ve at the same time seen at TTN a 15 minutes long series of periodic join accepts that seem not truly successful with the dev. address changing on each occasion. Then after 15 minutes I’ve seen payload starting to be successfully delivered… And at that point the Configurator starts to show additional activity.
Coincidentally or not (I suspect not), I have a 15 minute duty cycle set via the Configurator

[Gipsyblues]

@sronan, re your question about the data shown on TTN when the debug screen still says “joining”, I have the same observation like you. Yes it appears despite the joining status as per the debug screen, the device during that interval is trying to send data to TTN.

As you rightly observed, the payload once an “interval”, the 15 minute duty cycle selected during configuration, gets through to TTN.

We need to confirm this behaviour and let @rsmedia know, so that we could amend the guide to advise that the user checks the data tab of the device on TTN

[Gipsyblues]

@rsmedia, I got a question for you.
Please see the debug screen log below.
Is it possible to add time stamps to the activities indicated?
The reason I am asking is I notice that data is being uploaded to the TTN device - the capsule in this case. However on checking the device data on TNN, the data does not seem to be getting there.
(BTW the gateway is just located in the room only less than 20 feet from where the sensor is

join failed
join failed
joined
BH1750: Light = 3.33lx
BatteryVoltage: 4080, AppDataSize: 5
6 0 21 F F0
confirmed uplink sending …
BH1750: Light = 4.58lx
BatteryVoltage: 4102, AppDataSize: 5
6 0 2D 10 6
confirmed uplink sending …
BH1750: Light = 3.75lx
BatteryVoltage: 4106, AppDataSize: 5
6 0 25 10 A
confirmed uplink sending …
BH1750: Light = 4.17lx
BatteryVoltage: 4100, AppDataSize: 5
6 0 29 10 4
confirmed uplink sending …
BH1750: Light = 4.17lx
BatteryVoltage: 4122, AppDataSize: 5
6 0 29 10 1A
confirmed uplink sending …
BH1750: Light = 2.92lx
BatteryVoltage: 4102, AppDataSize: 5
6 0 1D 10 6
confirmed uplink sending …
BH1750: Light = 3.33lx
BatteryVoltage: 4100, AppDataSize: 5
6 0 21 10 4
confirmed uplink sending …
BH1750: Light = 3.33lx
BatteryVoltage: 4100, AppDataSize: 5
6 0 21 10 4
confirmed uplink sending …
BH1750: Light = 1.25lx
BatteryVoltage: 4108, AppDataSize: 5
6 0 C 10 C
confirmed uplink sending …

[rsmedia]

This log entry:

+ERROR: error input format

Means an error in the communication between cubecell and configurator. Sometimes the configurator sends two commands to fast after each other. This is on my agenda.

The log entries:

I2C device found at address …

Counting up indicates a faulty i2c bus.
There should only be such a message with the addresses of the i2c devices connected.
Sometimes a shortage one line or a i2c device holding a i2c line on low level.

[rsmedia]

Adding timestamps in the configurator is a good idea.
Will implement it today