# \[APP\]\[Pro\] smpl products - Battery powered e-ink display **URL:** \ **Category:** Apps\ **Tags:** app, zigbee, official, tools, homey-pro\ **Created:** [February 23, 2022, 1:01pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932 "2022-02-23T13:01:21Z")\ **Posts on this page:** 20\ **Page:** 12
**Author:** ![Nitramevo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nitramevo/32/17475_2.png) [@Nitramevo](https://community.homey.app/u/Nitramevo)\ **Post date:** [January 10, 2024, 7:16pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/231 "2024-01-10T19:16:59Z")
…anyone else with problems (pairing and/or updating) after updating to latest Homey firmware beta rc5?? ---
**Author:** ![Sebastian\_Sjalin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sebastian_sjalin/32/30000_2.png) [@Sebastian\_Sjalin](https://community.homey.app/u/Sebastian_Sjalin)\ **Post date:** [January 19, 2024, 3:14pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/232 "2024-01-19T15:14:42Z")
I got some problems updating my display. ![Screenshot 2024-01-19 154412](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/1/9122e777f2d6df6d5cda91cbf6b206231ec99f37.png) I got connection to the displays and got a page with 5 points I think. Release button, unplug, wait 5s, button again and then connect. Or something like that and I think the error came when i pressed next. Then I get an error message and the program crashes. Next time the program crashes the on the first “plug in the usb”-screen. Windows information: OS Name Microsoft Windows 11 Business Version 10.0.22621 Build 22621 I tried on a windows 10 computer also and then i got some installation prompt before the program starts but no connection to the device. This is the log with both the first crash/fail and the second where it did not come as far, second crash will be in next post since it was to big with all the logs… ```auto 2024-01-19 15:39:00.5739|Info|Polling task working | 2024-01-19 15:39:00.5963|Info|A device has been found! | 2024-01-19 15:39:00.5963|Info|Polling task canceled | 2024-01-19 15:39:00.5963|Trace|Log message received: STM32CubeProgrammer API v2.15.0 | Windows-64Bits | 2024-01-19 15:39:00.5963|Trace|Log message received: | 2024-01-19 15:39:00.5963|Trace|Log message received: | 2024-01-19 15:39:00.6194|Trace|Log message received: Device Descriptor: | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bLength : 0x12 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDescriptorType : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bcdUSB : 0x0200 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDeviceClass : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDeviceSubClass : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDeviceProtocol : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bMaxPacketSize : 0x40 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_idVendor : 0x0483 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_idProduct : 0xdf11 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bcdDevice : 0x0200 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_iManufacturer : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_iProduct : 0x02 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_iSerialNumber : 0x03 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bNumConfigurations : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: Configuration Descriptor: | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDescriptorType : 0x02 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_wTotalLength : 0x2d | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bNumInterfaces : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bConfigurationValue : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_iConfiguration : 0x02 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bmAttributes : 0xc0 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bMaxPower : 0x32 | 2024-01-19 15:39:00.6194|Trace|Log message received: Interface Descriptor Alternate Settings: 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bAlternateSetting : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_iInterface : 0x06 | 2024-01-19 15:39:00.6194|Trace|Log message received: Interface Descriptor Alternate Settings: 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bAlternateSetting : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_iInterface : 0x07 | 2024-01-19 15:39:00.6194|Trace|Log message received: Interface Descriptor Alternate Settings: 0x02 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bAlternateSetting : 0x02 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_iInterface : 0x08 | 2024-01-19 15:39:00.6194|Trace|Log message received: Functional Descriptor : | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bDescriptorType : 0x21 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bmAttributes : 0x0b | 2024-01-19 15:39:00.6194|Trace|Log message received: |_wDetachTimeOut : 0xff | 2024-01-19 15:39:00.6194|Trace|Log message received: |_wTransferSize : 0x0400 | 2024-01-19 15:39:00.6194|Trace|Log message received: |_bcdDFUVersion : 0x011a | 2024-01-19 15:39:00.6194|Trace|Log message received: USB speed : Full Speed (12MBit/s) | 2024-01-19 15:39:00.6194|Trace|Log message received: Manuf. ID : STMicroelectronics | 2024-01-19 15:39:00.6194|Trace|Log message received: Product ID : DFU in FS Mode | 2024-01-19 15:39:00.6194|Trace|Log message received: SN : 207D32913456 | 2024-01-19 15:39:00.6194|Trace|Log message received: DFU protocol: 1.1 | 2024-01-19 15:39:00.6194|Trace|Log message received: Board : -- | 2024-01-19 15:39:00.6194|Trace|Log message received: Device ID : 0x0495 | 2024-01-19 15:39:00.6194|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:00.6194|Trace|Log message received: DFU state = 9 : dfuUPLOAD-IDLE | 2024-01-19 15:39:00.6194|Trace|Log message received: Status: 0, State: 9 | 2024-01-19 15:39:00.6194|Trace|Log message received: sending an abort request | 2024-01-19 15:39:00.6194|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:00.6219|Trace|Log message received: DFU state = 2 : dfuIDLE | 2024-01-19 15:39:00.6219|Trace|Log message received: setting the address pointer to address: 0x08000000 | 2024-01-19 15:39:00.6219|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:00.6219|Trace|Log message received: DFU state = 4 : dfuDNBUSY | 2024-01-19 15:39:00.6219|Trace|Log message received: DFU status = 11 : errVENDOR | ... 2024-01-19 15:39:01.1446|Trace|Log message received: DFU status = 11 : errVENDOR | 2024-01-19 15:39:01.1446|Trace|Log message received: DFU state = 10 : dfuERROR | 2024-01-19 15:39:01.1446|Trace|Log message received: received memory address is wrong or unsupported | 2024-01-19 15:39:01.1446|Trace|Log message received: Status: errVENDOR, State: dfuERROR | 2024-01-19 15:39:01.1446|Trace|Log message received: Warning: Device is under Read Out Protection | 2024-01-19 15:39:01.1446|Trace|Log message received: Device Read Unprotect requested | 2024-01-19 15:39:01.1446|Trace|Log message received: DFU status = 11 : errVENDOR | 2024-01-19 15:39:01.1446|Trace|Log message received: DFU state = 10 : dfuERROR | 2024-01-19 15:39:01.1446|Trace|Log message received: Status: 11, State: 10 | 2024-01-19 15:39:01.1446|Trace|Log message received: sending a clear status request | 2024-01-19 15:39:01.1446|Trace|Log message received: DFU status = 14 : errUNKNOWN | 2024-01-19 15:39:01.1446|Trace|Log message received: DFU state = 10 : dfuERROR | 2024-01-19 15:39:01.1446|Trace|Log message received: an error occured after sending the clear status request | 2024-01-19 15:39:01.1446|Trace|Log message received: Status: errUNKNOWN, State: dfuERROR | 2024-01-19 15:39:01.1446|Trace|Log message received: sending a clear status request | 2024-01-19 15:39:01.1446|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:01.1446|Trace|Log message received: DFU state = 2 : dfuIDLE | 2024-01-19 15:39:01.1446|Trace|Log message received: sending a read unprotect request | 2024-01-19 15:39:05.1011|Trace|Log message received: libusb get status error [-9] : LIBUSB_ERROR_PIPE | 2024-01-19 15:39:05.1011|Trace|Log message received: libusb get status error [-9] : LIBUSB_ERROR_PIPE | 2024-01-19 15:39:05.1011|Trace|Log message received: Reconnecting... | 2024-01-19 15:39:05.3585|Trace|Log message received: Reconnected | 2024-01-19 15:39:05.3585|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:05.3585|Trace|Log message received: DFU state = 9 : dfuUPLOAD-IDLE | 2024-01-19 15:39:05.3585|Trace|Log message received: Status: 0, State: 9 | 2024-01-19 15:39:05.3585|Trace|Log message received: sending an abort request | 2024-01-19 15:39:05.3585|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:05.3585|Trace|Log message received: DFU state = 2 : dfuIDLE | 2024-01-19 15:39:05.3585|Trace|Log message received: setting the address pointer to address: 0x08000000 | 2024-01-19 15:39:05.3585|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:05.3585|Trace|Log message received: DFU state = 4 : dfuDNBUSY | 2024-01-19 15:39:05.3585|Trace|Log message received: DFU status = 11 : errVENDOR | ... 2024-01-19 15:39:05.8812|Trace|Log message received: DFU status = 11 : errVENDOR | 2024-01-19 15:39:05.8812|Trace|Log message received: DFU state = 10 : dfuERROR | 2024-01-19 15:39:05.8812|Trace|Log message received: received memory address is wrong or unsupported | 2024-01-19 15:39:05.8812|Trace|Log message received: Status: errVENDOR, State: dfuERROR | 2024-01-19 15:39:05.8812|Trace|Log message received: Error: Database cannot be found. DatabasePath = C:\Users\SebastianSj�lin\AppData\Local\Temp\SMPL_Mini_Display_Update_Tool\lib/../Data_Base/STM32_Prog_DB_0x495.xml | 2024-01-19 15:39:05.8812|Info|RDU disabled! | 2024-01-19 15:39:05.8812|Trace|Log message received: Disconnected from device. | 2024-01-19 15:39:39.4523|Info|The device has been found again! | 2024-01-19 15:39:39.4523|Info|Polling task canceled | 2024-01-19 15:39:39.4523|Trace|Log message received: STM32CubeProgrammer API v2.15.0 | Windows-64BitsWindows-64Bits | 2024-01-19 15:39:39.4523|Trace|Log message received: | 2024-01-19 15:39:39.4523|Trace|Log message received: | 2024-01-19 15:39:39.4704|Trace|Log message received: Device Descriptor: | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bLength : 0x12 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDescriptorType : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bcdUSB : 0x0200 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDeviceClass : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDeviceSubClass : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDeviceProtocol : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bMaxPacketSize : 0x40 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_idVendor : 0x0483 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_idProduct : 0xdf11 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bcdDevice : 0x0200 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_iManufacturer : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_iProduct : 0x02 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_iSerialNumber : 0x03 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bNumConfigurations : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: Configuration Descriptor: | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDescriptorType : 0x02 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_wTotalLength : 0x2d | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bNumInterfaces : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bConfigurationValue : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_iConfiguration : 0x02 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bmAttributes : 0xc0 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bMaxPower : 0x32 | 2024-01-19 15:39:39.4704|Trace|Log message received: Interface Descriptor Alternate Settings: 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bAlternateSetting : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_iInterface : 0x06 | 2024-01-19 15:39:39.4704|Trace|Log message received: Interface Descriptor Alternate Settings: 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bAlternateSetting : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_iInterface : 0x07 | 2024-01-19 15:39:39.4704|Trace|Log message received: Interface Descriptor Alternate Settings: 0x02 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bAlternateSetting : 0x02 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_iInterface : 0x08 | 2024-01-19 15:39:39.4704|Trace|Log message received: Functional Descriptor : | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bDescriptorType : 0x21 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bmAttributes : 0x0b | 2024-01-19 15:39:39.4704|Trace|Log message received: |_wDetachTimeOut : 0xff | 2024-01-19 15:39:39.4704|Trace|Log message received: |_wTransferSize : 0x0400 | 2024-01-19 15:39:39.4704|Trace|Log message received: |_bcdDFUVersion : 0x011a | 2024-01-19 15:39:39.4704|Trace|Log message received: USB speed : Full Speed (12MBit/s) | 2024-01-19 15:39:39.4704|Trace|Log message received: Manuf. ID : STMicroelectronics | 2024-01-19 15:39:39.4704|Trace|Log message received: Product ID : DFU in FS Mode | 2024-01-19 15:39:39.4704|Trace|Log message received: SN : 207D32913456 | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU protocol: 1.1 | 2024-01-19 15:39:39.4704|Trace|Log message received: Board : -- | 2024-01-19 15:39:39.4704|Trace|Log message received: Device ID : 0x0495 | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU state = 9 : dfuUPLOAD-IDLE | 2024-01-19 15:39:39.4704|Trace|Log message received: Status: 0, State: 9 | 2024-01-19 15:39:39.4704|Trace|Log message received: sending an abort request | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU state = 2 : dfuIDLE | 2024-01-19 15:39:39.4704|Trace|Log message received: setting the address pointer to address: 0x08000000 | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU state = 4 : dfuDNBUSY | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU state = 5 : dfuDNLOAD-IDLE | 2024-01-19 15:39:39.4704|Trace|Log message received: Error: Database cannot be found. DatabasePath = C:\Users\SebastianSj�lin\AppData\Local\Temp\SMPL_Mini_Display_Update_Tool\lib/../Data_Base/STM32_Prog_DB_0x495.xml | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU state = 9 : dfuUPLOAD-IDLE | 2024-01-19 15:39:39.4704|Trace|Log message received: Status: 0, State: 9 | 2024-01-19 15:39:39.4704|Trace|Log message received: sending an abort request | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU state = 2 : dfuIDLE | 2024-01-19 15:39:39.4704|Trace|Log message received: setting the address pointer to address: 0x08000000 | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU state = 4 : dfuDNBUSY | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:39:39.4704|Trace|Log message received: DFU state = 5 : dfuDNLOAD-IDLE | 2024-01-19 15:39:39.4704|Trace|Log message received: Error: CUBEPROGRAMMER_ERROR_NOT_SUPPORTED | 2024-01-19 15:39:39.4704|Info|Failed to connect co the device | 2024-01-19 15:39:42.1370|Error|MessageBox with error shown: Failed to connect to the device. Please, try again. | 2024-01-19 15:40:05.1150|Info|Polling task working | ... ``` ---
**Author:** ![Sebastian\_Sjalin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sebastian_sjalin/32/30000_2.png) [@Sebastian\_Sjalin](https://community.homey.app/u/Sebastian_Sjalin)\ **Post date:** [January 19, 2024, 3:15pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/233 "2024-01-19T15:15:17Z")
The rest of the log. ```auto ... 2024-01-19 15:40:16.7774|Info|Polling task working | 2024-01-19 15:40:16.7943|Info|A device has been found! | 2024-01-19 15:40:16.7943|Info|Polling task canceled | 2024-01-19 15:40:16.7943|Trace|Log message received: STM32CubeProgrammer API v2.15.0 | Windows-64Bits | 2024-01-19 15:40:16.7943|Trace|Log message received: | 2024-01-19 15:40:16.7943|Trace|Log message received: | 2024-01-19 15:40:16.8157|Trace|Log message received: Device Descriptor: | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bLength : 0x12 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDescriptorType : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bcdUSB : 0x0200 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDeviceClass : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDeviceSubClass : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDeviceProtocol : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bMaxPacketSize : 0x40 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_idVendor : 0x0483 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_idProduct : 0xdf11 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bcdDevice : 0x0200 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_iManufacturer : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_iProduct : 0x02 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_iSerialNumber : 0x03 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bNumConfigurations : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: Configuration Descriptor: | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDescriptorType : 0x02 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_wTotalLength : 0x2d | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bNumInterfaces : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bConfigurationValue : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_iConfiguration : 0x02 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bmAttributes : 0xc0 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bMaxPower : 0x32 | 2024-01-19 15:40:16.8157|Trace|Log message received: Interface Descriptor Alternate Settings: 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bAlternateSetting : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_iInterface : 0x06 | 2024-01-19 15:40:16.8157|Trace|Log message received: Interface Descriptor Alternate Settings: 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bAlternateSetting : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_iInterface : 0x07 | 2024-01-19 15:40:16.8157|Trace|Log message received: Interface Descriptor Alternate Settings: 0x02 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDescriptorType : 0x04 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceNumber : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bAlternateSetting : 0x02 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bNumEndpoints : 0x00 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceClass : 0xfe | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceSubClass : 0x01 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bInterfaceProtocol : 0x02 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_iInterface : 0x08 | 2024-01-19 15:40:16.8157|Trace|Log message received: Functional Descriptor : | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bLength : 0x09 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bDescriptorType : 0x21 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bmAttributes : 0x0b | 2024-01-19 15:40:16.8157|Trace|Log message received: |_wDetachTimeOut : 0xff | 2024-01-19 15:40:16.8157|Trace|Log message received: |_wTransferSize : 0x0400 | 2024-01-19 15:40:16.8157|Trace|Log message received: |_bcdDFUVersion : 0x011a | 2024-01-19 15:40:16.8157|Trace|Log message received: USB speed : Full Speed (12MBit/s) | 2024-01-19 15:40:16.8157|Trace|Log message received: Manuf. ID : STMicroelectronics | 2024-01-19 15:40:16.8157|Trace|Log message received: Product ID : DFU in FS Mode | 2024-01-19 15:40:16.8157|Trace|Log message received: SN : 207D32913456 | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU protocol: 1.1 | 2024-01-19 15:40:16.8157|Trace|Log message received: Board : -- | 2024-01-19 15:40:16.8157|Trace|Log message received: Device ID : 0x0495 | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU state = 9 : dfuUPLOAD-IDLE | 2024-01-19 15:40:16.8157|Trace|Log message received: Status: 0, State: 9 | 2024-01-19 15:40:16.8157|Trace|Log message received: sending an abort request | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU state = 2 : dfuIDLE | 2024-01-19 15:40:16.8157|Trace|Log message received: setting the address pointer to address: 0x08000000 | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU state = 4 : dfuDNBUSY | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU state = 5 : dfuDNLOAD-IDLE | 2024-01-19 15:40:16.8157|Trace|Log message received: Device Read Unprotect requested | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:16.8157|Trace|Log message received: DFU state = 5 : dfuDNLOAD-IDLE | 2024-01-19 15:40:16.8157|Trace|Log message received: Status: 0, State: 5 | 2024-01-19 15:40:16.8157|Trace|Log message received: sending a read unprotect request | 2024-01-19 15:40:16.8427|Trace|Log message received: libusb get status error [-9] : LIBUSB_ERROR_PIPE | 2024-01-19 15:40:16.8427|Trace|Log message received: libusb get status error [-9] : LIBUSB_ERROR_PIPE | 2024-01-19 15:40:16.8427|Trace|Log message received: Reconnecting... | 2024-01-19 15:40:17.1068|Trace|Log message received: Reconnected | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU state = 9 : dfuUPLOAD-IDLE | 2024-01-19 15:40:17.1068|Trace|Log message received: Status: 0, State: 9 | 2024-01-19 15:40:17.1068|Trace|Log message received: sending an abort request | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU state = 2 : dfuIDLE | 2024-01-19 15:40:17.1068|Trace|Log message received: setting the address pointer to address: 0x08000000 | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU state = 4 : dfuDNBUSY | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU state = 5 : dfuDNLOAD-IDLE | 2024-01-19 15:40:17.1068|Trace|Log message received: Error: Database cannot be found. DatabasePath = C:\Users\SebastianSj�lin\AppData\Local\Temp\SMPL_Mini_Display_Update_Tool\lib/../Data_Base/STM32_Prog_DB_0x495.xml | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU state = 9 : dfuUPLOAD-IDLE | 2024-01-19 15:40:17.1068|Trace|Log message received: Status: 0, State: 9 | 2024-01-19 15:40:17.1068|Trace|Log message received: sending an abort request | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU state = 2 : dfuIDLE | 2024-01-19 15:40:17.1068|Trace|Log message received: setting the address pointer to address: 0x08000000 | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU state = 4 : dfuDNBUSY | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU status = 0 : OK | 2024-01-19 15:40:17.1068|Trace|Log message received: DFU state = 5 : dfuDNLOAD-IDLE | 2024-01-19 15:40:17.1068|Trace|Log message received: Error: CUBEPROGRAMMER_ERROR_NOT_SUPPORTED | 2024-01-19 15:40:17.1068|Info|Failed to disable RDU | 2024-01-19 15:40:19.2666|Error|MessageBox with error shown: Failed to configure the device. Please, try again. | 2024-01-19 15:40:20.8666|Info|Polling task working | ``` ---
**Author:** ![Nitramevo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nitramevo/32/17475_2.png) [@Nitramevo](https://community.homey.app/u/Nitramevo)\ **Post date:** [January 20, 2024, 11:44am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/234 "2024-01-20T11:44:55Z")
Hi Sebastian: Please consider: 1. Trying different USB cables 2. Making sure your USB port is configured correctly and not blocked (e.g. by Antivirus, other PC security measures etc.) 3. Trying different PC’s 4. Trying several times ---
**Author:** ![Sebastian\_Sjalin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sebastian_sjalin/32/30000_2.png) [@Sebastian\_Sjalin](https://community.homey.app/u/Sebastian_Sjalin)\ **Post date:** [February 3, 2024, 1:58pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/235 "2024-02-03T13:58:29Z")
Now I have taken me further on a windows 11 laptop but i fail later. I put the log on pastebin [SMPL uppdate fail log - Pastebin.com](https://pastebin.com/HY83c1mP) It seems like it loses connection to the target in the process. I have tried several times and with both my displays and I get the same fail on both at what I can see the same step: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/f/cf63ce770915339127bb89c950ab37d1a5331a99.png) What shall I try next? ---
**Author:** ![Nitramevo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nitramevo/32/17475_2.png) [@Nitramevo](https://community.homey.app/u/Nitramevo)\ **Post date:** [February 3, 2024, 5:31pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/236 "2024-02-03T17:31:27Z")
I am not a PC support expert, so my best advice based on other users experience is still: 1. Trying different USB cables 2. Making sure your USB port is configured correctly and not blocked (e.g. by Antivirus, other PC security measures etc.) 3. Trying different PC’s 4. Trying several times ---
**Author:** ![johan\_W](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_w/32/17556_2.png) [@johan\_W](https://community.homey.app/u/johan_W)\ **Post date:** [February 3, 2024, 9:45pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/237 "2024-02-03T21:45:40Z")
Option to do Start the update programe with run as administrator. (Right mouse then choose run as…) Just a try ---
**Author:** ![KaiF](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaif/32/17746_2.png) [@KaiF](https://community.homey.app/u/KaiF)\ **Post date:** [February 5, 2024, 7:37am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/238 "2024-02-05T07:37:54Z")
Just wanted to thank @Nitramevo for his excellent support. We finally solved the issue after trying to reflash etc. myself. Finally Martin offered me to send back the unit and reflash there. Now everything is working fine. Many thanks! ---
**Author:** ![Daniel\_Lofgren](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_lofgren/32/1075_2.png) [@Daniel\_Lofgren](https://community.homey.app/u/Daniel_Lofgren)\ **Post date:** [February 15, 2024, 5:00am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/239 "2024-02-15T05:00:10Z")
Hi. After Homey update 10.3.0 both my displays have gone dead. Says redy to display info but nothing pop up. Tried to reset one of them but unable to connect the device. Is it only me? ---
**Author:** ![Roger\_K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/roger_k/32/79682_2.png) [@Roger\_K](https://community.homey.app/u/Roger_K)\ **Post date:** [February 15, 2024, 6:57am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/240 "2024-02-15T06:57:09Z")
The same with me. Since the Homey update to version 10.3.0 my smpl display has frozen. After a reset I can no longer pair the display with Homey. ![sshot-4](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/f/1f7aa05da16e710e31b05a79f5cba53fac93fa2b.png) ---
**Author:** ![Koktail](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koktail/32/51498_2.png) [@Koktail](https://community.homey.app/u/Koktail)\ **Post date:** [February 15, 2024, 9:44am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/241 "2024-02-15T09:44:38Z")
I’m running v10.3.0 but I cannot reproduce your issue. My German isn’t that good, can you translate the message from Homey? ---
**Author:** ![Peter\_van\_Meer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_van_meer/32/74898_2.png) [@Peter\_van\_Meer](https://community.homey.app/u/Peter_van_Meer)\ **Post date:** [February 15, 2024, 3:38pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/242 "2024-02-15T15:38:51Z")
> [@Roger\_K](#): > > The same with me. > Since the Homey update to version 10.3.0 my smpl display has frozen. > After a reset I can no longer pair the display with Homey. Same here with 3x SMPL displays, Deleting the App and reinstalling it did not provide any improvement. Also removing the displays and restarting them is no longer possible. Now just wait for an update of the SMPL App and hope that it works again. ---
**Author:** ![Nitramevo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nitramevo/32/17475_2.png) [@Nitramevo](https://community.homey.app/u/Nitramevo)\ **Post date:** [February 15, 2024, 4:51pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/243 "2024-02-15T16:51:35Z")
@Peter_van_Meer @Roger_K @Daniel_Lofgren Please reach out to Athom support about this. I have also made a direct comment to the fw update post in the Slack channel to highlight the issue to Athom developers Niels de Boer and Robin Bolcher. ---
**Author:** ![Roger3](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/roger3/32/79404_2.png) [@Roger3](https://community.homey.app/u/Roger3)\ **Post date:** [February 15, 2024, 5:06pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/244 "2024-02-15T17:06:41Z")
lost my smpl after autoupgrade of homey pro during the night (10.3.0) ---
**Author:** ![Jiri\_Pech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jiri_pech/32/48190_2.png) [@Jiri\_Pech](https://community.homey.app/u/Jiri_Pech)\ **Post date:** [February 15, 2024, 8:18pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/245 "2024-02-15T20:18:37Z")
Same here, ended with this ![IMG_0495](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/9/b95d11b0c0d193b0a5af07b8e767f63325870e23.jpeg) Display is not reacting to battery swap, getting batteries out or any press of button… ---
**Author:** ![Oskarenator](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oskarenator/32/34192_2.png) [@Oskarenator](https://community.homey.app/u/Oskarenator)\ **Post date:** [February 17, 2024, 10:21am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/246 "2024-02-17T10:21:14Z")
Same here… ---
**Author:** ![Nitramevo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nitramevo/32/17475_2.png) [@Nitramevo](https://community.homey.app/u/Nitramevo)\ **Post date:** [February 17, 2024, 10:40am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/247 "2024-02-17T10:40:01Z")
**Cases of HP23 fw update 10.3.0 breaking connectivity for smpl mini display** Athom is currently not able to reproduce the issue with their smpl mini display. The same goes for our own installations. But the ‘only’ similarity between the cases and the timing is the HP23 firmware update. Please also contact Athom support about the issue: [Support | Homey](https://homey.app/en-dk/support/) in order for them to collect more cases. Current feedback is: _the Zigbee Thread has been modified, this is not handled well by smpl. During the Homey beta, there was also a problem with ZCL commands._ ---
**Author:** ![Ranney](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@Ranney](https://community.homey.app/u/Ranney)\ **Post date:** [February 17, 2024, 3:53pm UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/248 "2024-02-17T15:53:15Z")
Ok. Here the same. All my smpl displays are not working anymore. One other zigbee device (Aqara roller shade driver e1) is working less stable (missing commands and stops working after some hours until reboot of homey). All other devices on zigbee running fine as far as I can see. ---
**Author:** ![Astra77](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/astra77/32/1216_2.png) [@Astra77](https://community.homey.app/u/Astra77)\ **Post date:** [February 18, 2024, 9:53am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/249 "2024-02-18T09:53:39Z")
Same issue on both my SMPL devices. I’ve opened a ticket with Homey and send them the diagnostic report ID’s for the app and the Homey. I think there are a lot more things at the moment, in the confirmation email it had the following sentence: "Please note that we are currently experiencing a sharp increase in ticketload. This is why our expected reply time is 2-3 weeks. " ---
**Author:** ![Roger3](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/roger3/32/79404_2.png) [@Roger3](https://community.homey.app/u/Roger3)\ **Post date:** [February 18, 2024, 10:00am UTC](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932/250 "2024-02-18T10:00:36Z")
I lost my smpl display when homey was upgraded to 10.3.0. Not sure what firmware I have on my smpl display now… but I see that it is possible to install this version: FW 1.19 | Zigbee Stack 1.17.2 Does anyone know if that will solve the issues with zigbee on homey 10.3.0 ? [Previous page](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932.md?page=11) [Next page](https://community.homey.app/t/app-pro-smpl-products-battery-powered-e-ink-display/60932.md?page=13)