tony-fav / tasmota-blerry Goto Github PK

View Code? Open in Web Editor NEW

91.0 91.0 29.0 7.24 MB

License: GNU General Public License v3.0

C 4.52% Berry 95.48%

tasmota-blerry's People

Contributors

Stargazers

Watchers

tasmota-blerry's Issues

Legacy Support Switchbot Plus (was: BRY: Exception> 'key_error')

Hi;
I tried to read the new Switchbot Plus
with the WOSensorTH driver.
(I'm still on legacy, as I started with it, ran well until now and my tries to get the new blerry SW lead to unresponsive devices)
I get the following errors:

BRY: Exception> 'key_error' - C4C21F0FF871/1
stack traceback:
: in native function
: in function DetailsBLE_callback
: in function try_rule
: in function exec_rules
: in function event

How can I support to get this device running? I don't expect much changes to the current driver.

Not getting anything but RSSI for Siwtchbot TH

I got a new switchbot temperature meter and its on Firmware v2.8.
I'm using the WoSensorTH with no luck. All it shows is RSSI and no Temperature / Humidity or battery.

What info can I provide to help troubleshoot?

Switchbot W1901400 - BlerryGetConfig returns Command Unknown

Hi.

Trying to get blerry configured on W1901400. Like in #57 , I'm using tasmota32c3-bluetooth.bin built in past 24 hours.

When following the doc. to set blerry, it seems to do would it should. I ran it multiple time so the reason it's finding a existing files.

Found an existing blerry_config.json
Removing blerry.bec
Found Blerry Load as Part of Rule 1
Blerry Setup Complete

But then on the console, running BlerryGetConfig returns:

04:32:24.893 MQT: stat/Washer/RESULT = {"Command":"Unknown"}

I do not see any driver when looking at the filesystem. I uploaded the WoHand one hoping that would fix it but didn't. I admit I am brand new to tasmota, any help is appreciated.

Thank you!

Shelly Blu Door/Window Sensor

Hi,
do you see a Chance to Support the new Shelly Blu D/W sensor?
https://shellyparts.de/products/shelly-blu-door-window

Issue loading Blerry

I have flashed Tasmota 10.0.0.1 with BLE enabled on Linkind dimmer switch with ESP32. I `m following the manual install because the automatic script was giving me an error.

After applying the RULE1 I get this error.

I``m using latest BLERRY version 0.2

`00:41:56.959 RUL: SYSTEM#BOOT performs "br load('blerry.be')"

00:41:57.039 BRY: Error be_top is non zero=1

00:41:57.053 MQT: stat/Garage_hall/RESULT = {"Br":"[syntax_error] blerry.be:37: class static error"}

00:41:57.066 QPC: Reset`

this is the Automatic script error

SwitchBot TH crashing esp32 c3 - switchbot_plugmini_W1901400

ref #47
I am using the blerry dev branch and the development branch of Tasmota on these: https://templates.blakadder.com/switchbot_plugmini_W1901400.html

ATCpvvx alone seems to work fine on one plug and not cause issues but on another with just one WoSensorTH it will last up to an hour before freezing and becoming completely unresponsive. The button on the side to toggle the plug relay is dead and no http or anything. Pulling the plug out of the outlet and replugging it is the only way to bring it back... It then runs for a random time not more than an hour and repeat.

I am starting to suspect exclusively WoSensorTH as I've had others with ATCpvvx and WP6003 with no issue.

What else can I provide to help troubleshoot? turn on berry debug? send to syslog?

ESP32 stops working

For whatever reason, My ESP32 seems to stop working randomly. Sometimes once a day, sometimes multiple time, sometimes it'll go a few days. I have to power cycle it to get it running again.

Is this a Blerry issue? A Tasmota issue? A user issue!?

I'm using a NodeMCU-type ESP32 Devkit board. Haven't had any similar problems with other uses of it with just Tasmota. A buddy that also started using Blerry has had similar issues.

I'm running 7 InkBird TH2 sensors right now (problem started when I only had one a couple of weeks ago).
Thanks,
Brummy

MQTT attributes publish attributes -> publish_attributes

Minor bug in documentation, the correct JSON attribute for enabling individual MQTT attributes is publish_attributes with underscore.

Code not compiling

I watched Travis's video and used the latest blerry files with the edit for my Mac address. I added rule 1, restarted but the files did not compile. I am running it on an esp32 ble device withe the latest tasmota firmware. Any idea on what I am doing wrong?

Slight change to the readme

I missed the rule1 1 and I see others have as well. I think if you had:

Create the following rule: Rule1 ON System#Boot DO br load('blerry.be') ENDON
Enable (Rule1 1)
Restart Tasmota (Some of the commands used in blerry.be are not initialized by the time autoexec.be is run. So, you must load blerry.be as part of a rule.)
I missed the rule1 1 and I see that others have as well. Otherwise the directions and code work very well! Another excellent video from
Travis.

BRY: failed to load '/blerry_newBLE.be' (syntax_error - /blerry_newBLE.be:40: 'BLE' undeclared (first use in this function))

Hi,

I'm just doing my first steps with Berry and Blerry so please forgive me if I ask silly questions.

I managed to flash Tasmota 13.0.0 (Web flasher) to my Esp32Cam module, uploaded Blerry files first by executing the setup script and again manually (because blerry.be was empty).
Files are now present: blerry.be ~31.5k, blerry_newBLE.bs ~3,6k, blerry_config.json with 1 module configured, blerry_driver_Xiaomi.be automatically got downloaded during my tests, rule1 is configured and working).

But I get the error message during load of blerry_newBLE.be stating that BLE() is not defined.

I tried to find a definition of BLE() in the files but did not succeed.
I renamed BLE() to Blerry() as I assumed that this could be a typo in the code. But seemed to be a silly idea. System got extremely slow and got another error stating that Blerry has not atribute named adv_cb. But this attribute is also found nowhere in Blerry code base...

Any idea what is going wrong? Is BLE() a system object provided by Tasmota/Berry or is there a bug somewhere in Blerry?

Thanks a lot for your help
Eva

add force_update option for discovery

if possible to add force_update as optional config to be added to the discovery topic.

bindkey

I add MCCGQ02HL (Xiaomi Mijia Window Door Sensor 2) but is showing a NO KEY message.
I have the bindkey of the device, how can I add it in the settings?

Xiaomi Hhcc Flora Monitor

Hello,

Is this MI Flower monitor sensor supported by blerry_model_ATCmi.be

Regards,
Dirk

Flashing tasmota32solo1-linkind-ble-berry.bin from DEV branch causes bootloops

tasmota32solo1-linkind-ble-berry.bin from DEV branch under tested firmware
https://github.com/tony-fav/tasmota-blerry/raw/dev/tasmota32_firmware/tasmota32solo1-linkind-ble-berry.bin

Causes boot-loop when flashed to Linkind Solo1 Switch

Steps to duplicate (two methods tried)

1a) Serial flash Solo1 special from Tasmota Web Installer to 2022.01.3 Solo1 Bluetooth

2a) Connect to Wifi
3a) OTA File update using above linked file.

Serial Log


rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0030,len:184
load:0x40078000,len:12356
load:0x40080400,len:2720
entry 0x40080594

00:00:00.003 HDW: ESP32-U4WDH 
00:00:00.018 UFS: FlashFS mounted with 308 kB free
00:00:00.058 CFG: Loaded from File, Count 7
00:00:00.068 QPC: Count 1
00:00:00.166 BRY: Berry initialized, RAM used=3930 bytes
00:00:00.190 Project tasmota - TESTBENCH Version 2022.01.3(tasmota)-2_0_2_1(2022-01-23T16:07:46)
00:00:00.192 iBeacon register for advert callbacks
00:00:00.203 M32: init: request callbacks
00:00:00.975 WIF: Connecting to AP1 ElksInNC-IOT in mode 11n as TESTBENCH...
00:00:04.568 WIF: Connected
00:00:04.779 HTP: Web server active on TESTBENCH with IP address 10.10.10.174
19:39:44.136 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"2022.01.3(tasmota)","FallbackTopic":"cmnd/DVES_701F60_fb/","GroupTopic":"cmnd/tasmotas/"}}
19:39:44.151 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"TESTBENCH","IPAddress":"10.10.10.174"}}
19:39:44.154 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU"}}
19:39:44.939 QPC: Reset
19:39:49.871 RSL: STATE = {"Time":"2022-01-23T19:39:49","Uptime":"0T00:00:12","UptimeSec":12,"Heap":128,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":225,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":38},"Wifi":{"AP":1,"SSId":"ElksInNC-IOT","BSSId":"E6:63:DA:77:82:09","Channel":6,"Mode":"11n","RSSI":86,"Signal":-57,"LinkCount":1,"Downtime":"0T00:00:05"}}
19:39:49.902 RSL: SENSOR = {"Time":"2022-01-23T19:39:49","ESP32":{"Temperature":148.0},"TempUnit":"F"}
19:39:49.910 RSL: BLE = {"Time":"2022-01-23T19:39:49","BLEDevices":{"total":0}}
19:39:49.914 RSL: BLE = {"Time":"2022-01-23T19:39:49","BLE":{"scans":0,"adverts":0,"devices":0,"resets":0}}
19:41:01.310 RSL: RESULT = {"OtaUrl":"https://github.com/tony-fav/tasmota-blerry/raw/dev/tasmota32_firmware/tasmota32solo1-linkind-ble-berry.bin"}
19:41:01.507 RSL: RESULT = {"Upgrade":"Version 2022.01.3 from https://github.com/tony-fav/tasmota-blerry/raw/dev/tasmota32_firmware/tasmota32solo1-linkind-ble-berry.bin"}
19:41:03.404 BLE: Stopping if active
19:41:03.407 HTP: Web server stopped
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0030,len:184
load:0x40078000,len:12356
load:0x40080400,len:2720
entry 0x40080594

abort() was called at PC 0x40084450 on core 0


Backtrace:0x40084e85:0x3ffe3ba00x40097b95:0x3ffe3bc0 0x4009cb15:0x3ffe3be0 0x40084450:0x3ffe3c60 0x4007912e:0x3ffe3c90  |<-CORRUPTED




ELF file SHA256: 0000000000000000

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0030,len:184
load:0x40078000,len:12356
load:0x40080400,len:2720
entry 0x40080594

abort() was called at PC 0x40084450 on core 0


Backtrace:0x40084e85:0x3ffe3ba00x40097b95:0x3ffe3bc0 0x4009cb15:0x3ffe3be0 0x40084450:0x3ffe3c60 0x4007912e:0x3ffe3c90  |<-CORRUPTED

Alternative is to flash device after above incident with ESP Flasher because partitions are correct. Flashing back to previous custom compile and the OTA File flashing to current custom compile.

1b) ESP Flasher - flash pre-TLS special from:
https://github.com/tony-fav/tasmota-blerry/raw/main/tested_firmware/tasmota32solo1-linkind-ble-berry.bin

Using '/dev/cu.usbserial-0001' as serial port.
Connecting.....
Detecting chip type... ESP32
Connecting...

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-U4WDH (revision 3)
 - Number of Cores: 1
 - Max CPU Frequency: 80MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: YES
 - Has Factory-Calibrated ADC: YES
 - MAC Address: B8:F0:09:70:1F:60
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
 - Flash Size: 4MB
 - Flash Mode: dout
 - Flash Frequency: 40MHz
Erasing flash (this may take a while)...
Chip erase completed successfully in 19.0s
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x0017afff...
Compressed 17104 bytes to 11191...
Writing at 0x00001000... (100 %)
Wrote 17104 bytes (11191 compressed) at 0x00001000 in 0.6 seconds (effective 226.5 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 129...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.1 seconds (effective 367.4 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 521.2 kbit/s)...
Hash of data verified.
Compressed 1485840 bytes to 1000863...
Writing at 0x00010000... (1 %)
Writing at 0x00018fab... (3 %)
Writing at 0x00020233... (4 %)
Writing at 0x00029a21... (6 %)
Writing at 0x00034a5e... (8 %)
Writing at 0x0003cccd... (9 %)
Writing at 0x000452ac... (11 %)
Writing at 0x0004a683... (12 %)
Writing at 0x0004f74b... (14 %)
Writing at 0x000546ac... (16 %)
Writing at 0x00059bbc... (17 %)
Writing at 0x0005f26a... (19 %)
Writing at 0x000643bc... (20 %)
Writing at 0x0006a16a... (22 %)
Writing at 0x0006f11d... (24 %)
Writing at 0x00074107... (25 %)
Writing at 0x00078c49... (27 %)
Writing at 0x0007de90... (29 %)
Writing at 0x00083c82... (30 %)
Writing at 0x0008978f... (32 %)
Writing at 0x0008ef73... (33 %)
Writing at 0x00094978... (35 %)
Writing at 0x0009a6ec... (37 %)
Writing at 0x0009fdd5... (38 %)
Writing at 0x000a5604... (40 %)
Writing at 0x000aad91... (41 %)
Writing at 0x000b0116... (43 %)
Writing at 0x000b5c7b... (45 %)
Writing at 0x000bb74d... (46 %)
Writing at 0x000c118e... (48 %)
Writing at 0x000c6beb... (50 %)
Writing at 0x000cbf63... (51 %)
Writing at 0x000d14ec... (53 %)
Writing at 0x000d682d... (54 %)
Writing at 0x000dbc25... (56 %)
Writing at 0x000e102c... (58 %)
Writing at 0x000e6100... (59 %)
Writing at 0x000ebed3... (61 %)
Writing at 0x000f1f3b... (62 %)
Writing at 0x000f81aa... (64 %)
Writing at 0x000fd4a8... (66 %)
Writing at 0x0010279f... (67 %)
Writing at 0x0010887c... (69 %)
Writing at 0x0010de33... (70 %)
Writing at 0x00112fd8... (72 %)
Writing at 0x00118348... (74 %)
Writing at 0x0011d78b... (75 %)
Writing at 0x00122cd6... (77 %)
Writing at 0x00128581... (79 %)
Writing at 0x0012e35f... (80 %)
Writing at 0x00133bad... (82 %)
Writing at 0x00139497... (83 %)
Writing at 0x0013fe11... (85 %)
Writing at 0x001484ad... (87 %)
Writing at 0x00150d3d... (88 %)
Writing at 0x0015608f... (90 %)
Writing at 0x0015e594... (91 %)
Writing at 0x00163e3c... (93 %)
Writing at 0x001693d8... (95 %)
Writing at 0x0016f2d3... (96 %)
Writing at 0x001746cb... (98 %)
Writing at 0x0017a334... (100 %)
Wrote 1485840 bytes (1000863 compressed) at 0x00010000 in 26.2 seconds (effective 454.0 kbit/s)...
Hash of data verified.

Leaving...
Hard Resetting...
Hard resetting via RTS pin...
Done! Flashing is complete!

Showing logs:

2b) Set up wifi
3b) OTA File update via web interface file downloaded from:
https://github.com/tony-fav/tasmota-blerry/blob/dev/tasmota32_firmware/tasmota32solo1-linkind-ble-berry.bin

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8

00:00:00.003 HDW: ESP32-U4WDH 
00:00:00.015 UFS: FlashFS mounted with 304 kB free
00:00:00.041 CFG: Loaded from File, Count 11
00:00:00.050 QPC: Count 1
00:00:00.080 BRY: Berry initialized, RAM used=3504
00:00:00.092 BRY: no 'preinit.be'
00:00:00.098 Project tasmota - TESTBENCH Version 10.1.0.1(linkind-ble-berry)-2_0_1_1(2022-01-06T22:47:00)
00:00:00.100 iBeacon register for advert callbacks
00:00:00.159 BRY: no 'autoexec.be'
00:00:00.778 WIF: Connecting to AP1 ElksInNC-IOT Channel 6 BSSId E6:63:DA:77:82:09 in mode 11n as TESTBENCH...
00:00:04.709 WIF: Connected
00:00:04.966 HTP: Web server active on TESTBENCH with IP address 10.10.10.174
19:21:14.869 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"10.1.0.1(linkind-ble-berry)","FallbackTopic":"cmnd/DVES_701F60_fb/","GroupTopic":"cmnd/tasmotas/"}}
19:21:14.883 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"TESTBENCH","IPAddress":"10.10.10.174"}}
19:21:15.003 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU"}}
19:21:16.942 QPC: Reset
19:21:18.955 RSL: STATE = {"Time":"2022-01-23T19:21:18","Uptime":"0T00:00:09","UptimeSec":9,"Heap":138,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":48},"Wifi":{"AP":1,"SSId":"ElksInNC-IOT","BSSId":"E6:63:DA:77:82:09","Channel":6,"Mode":"11n","RSSI":90,"Signal":-55,"LinkCount":1,"Downtime":"0T00:00:04"}}
19:21:18.984 RSL: SENSOR = {"Time":"2022-01-23T19:21:18","ESP32":{"Temperature":146.0},"TempUnit":"F"}
19:21:18.991 RSL: BLE = {"Time":"2022-01-23T19:21:18","BLEDevices":{"total":0}}
19:21:18.995 RSL: BLE = {"Time":"2022-01-23T19:21:18","BLE":{"scans":0,"adverts":0,"devices":0,"resets":0}}
19:22:50.553 BLE: Stopping if active
19:22:50.770 UPL: File tasmota32solo1-linkind-ble-berry (9).bin
19:23:34.954 UPP: Multicast (re)joined
19:23:36.833 UPL: Successful 1484576 bytes
19:23:38.045 APP: Restarting

ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8

abort() was called at PC 0x40084450 on core 0


Backtrace:0x40084e85:0x3ffe3b500x40097b95:0x3ffe3b70 0x4009cb15:0x3ffe3b90 0x40084450:0x3ffe3c10 0x40079247:0x3ffe3c40  |<-CORRUPTED




ELF file SHA256: 0000000000000000

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8

abort() was called at PC 0x40084450 on core 0


Backtrace:0x40084e85:0x3ffe3b500x40097b95:0x3ffe3b70 0x4009cb15:0x3ffe3b90 0x40084450:0x3ffe3c10 0x40079247:0x3ffe3c40  |<-CORRUPTED


Additionally - attempted to build myself from:
https://github.com/tony-fav/Tasmota.git

Successful local compile with same results as above.  Also attempted to ESP Flash factory via serial.  Same boot loop.

Linkind Switch ESP32Solo WS240010008, Rule1 breaks MQT BLE.

Im Using a Linkind Switch ESP32Solo WS240010008 (thermostat+BLE) with Blerry 0.1.3 and all was fine until I setup multi-press options to the switch and a Rule1. I applied the following and restarted the device after each command. So73 1, So1 1, So32 2, rule1 on button1#state=10 do power1 toggle endon, Rule1 1, Restarted and all BLE MQT activity stopped. Tried several times and same result.

var user_config = {'494208006617': {'alias': 'inkbird', 'model': 'IBSTH2', 'discovery': true},
'A4C1381AF1BC': {'alias': 'govee', 'model': 'GVH5075', 'discovery': true}}

"Looking around" with dev device shows no devices

Hi,
I just found your blerry implementation and really like it, I would like to get a feeling for this and try to discover some devices using the dev driver, but neither the console, nor the berry console, nor the main menu show any devices. Am I missing something?

Here is some information about my setup that might help.

Program Version	12.0.1(bluetooth)
Build Date & Time	2022-06-17T14:38:58
Core/SDK Version	2_0_3/v4.4.1
Uptime	0T00:07:47
Flash write Count	23
Boot Count	12
Restart Reason	Software reset CPU
 
AP1 SSId (RSSI)	MySSID (100%, -22 dBm) 11n
Hostname	tasmota-977178-4472
MAC Address	12:34:56:78:90:AB
IP Address (wifi)	123.123.123.123
Gateway	123.123.123.123
Subnet Mask	255.255.255.0
DNS Server1	123.123.123.123
DNS Server2	0.0.0.0
 
HTTP API	Enabled
 
MQTT Host	
MQTT Port	1883
MQTT TLS	Disabled
MQTT User	DVES_USER
MQTT Client	DVES_977178
MQTT Topic	tasmota_%06X
MQTT Group Topic 1	cmnd/tasmotas/
MQTT Full Topic	cmnd/tasmota_977178/
MQTT Fallback Topic	cmnd/DVES_977178_fb/
MQTT No Retain	Disabled
 
Emulation	None
 
ESP Chip Id	9924984 (ESP32-D0WDQ6 rev.1)
Flash Chip Id	0x1640EF
Flash Size	4096 KB
Program Flash Size	4096 KB
Program Size	1524 KB
Free Program Space	1355 KB
Free Memory	84.6 KB (frag. 18%)
 
Partition safeboot	832 KB (used 90%)
Partition app0*	2880 KB (used 52%)
Partition fs	320 KB

This is what the console output looks like:

00:00:00.003 HDW: ESP32-D0WDQ6 
00:00:00.101 UFS: FlashFS mounted with 288 kB free
00:00:00.164 CFG: Loaded from File, Count 22
00:00:00.181 QPC: Count 1
00:00:00.511 BRY: Berry initialized, RAM used=3731 bytes
00:00:00.539 Project tasmota - Tasmota Version 12.0.1(bluetooth)-2_0_3(2022-06-17T14:38:58)
00:00:00.540 iBeacon register for advert callbacks
00:00:00.541 MI32Option0: 1
00:00:00.552 MI32Option1: 0
00:00:00.552 MI32Option2: 0
00:00:00.553 MI32Option4: 1
00:00:00.554 MI32Option5: 0
00:00:00.554 MI32Option6: 0
00:00:00.565 M32: init: request callbacks
00:00:01.403 WIF: Connecting to AP1 mySSID Channel 6 BSSId 12:34:56:78:90:AB in mode 11n as tasmota-977178-4472...
00:00:03.463 WIF: Connected
00:00:03.675 HTP: Web server active on tasmota-977178-4472 with IP address 123.123.123.123
12:23:21.004 BLE: MasterEnable->1
12:23:21.018 BLE: BLETask:Starting NimBLE
12:23:22.290 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"12.0.1(bluetooth)","FallbackTopic":"cmnd/DVES_977178_fb/","GroupTopic":"cmnd/tasmotas/"}}
12:23:22.307 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-977178-4472","IPAddress":"123.123.123.123"}}
12:23:22.313 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":12}}
12:23:22.359 RUL: SYSTEM#BOOT performs "br load('blerry.be')"
12:23:23.045 RSL: RESULT = {"Br":"true"}
12:23:24.828 QPC: Reset
12:23:26.824 RSL: STATE = {"Time":"2022-06-19T12:23:26","Uptime":"0T00:00:10","UptimeSec":10,"Heap":84,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":4,"Objects":52},"Wifi":{"AP":1,"SSId":"mySSID","BSSId":"12:34:56:78:90:AB","Channel":6,"Mode":"11n","RSSI":100,"Signal":-29,"LinkCount":1,"Downtime":"0T00:00:04"}}
12:23:26.856 RSL: SENSOR = {"Time":"2022-06-19T12:23:26","ESP32":{"Temperature":33.9},"TempUnit":"C"}
12:23:26.864 RSL: BLE = {"Time":"2022-06-19T12:23:26","BLEDevices":{"total":2,"2CAB33012C89":{"i":0,"r":-86},"7C0A3F53C69D":{"i":1,"r":-76}}}
12:23:26.881 RSL: BLE = {"Time":"2022-06-19T12:23:26","BLE":{"scans":0,"adverts":66,"devices":2,"resets":0}}
12:28:26.826 RSL: STATE = {"Time":"2022-06-19T12:28:26","Uptime":"0T00:05:10","UptimeSec":310,"Heap":86,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":4,"Objects":52},"Wifi":{"AP":1,"SSId":"mySSID","BSSId":"12:34:56:78:90:AB","Channel":6,"Mode":"11n","RSSI":100,"Signal":-23,"LinkCount":1,"Downtime":"0T00:00:04"}}
12:28:26.857 RSL: SENSOR = {"Time":"2022-06-19T12:28:26","ESP32":{"Temperature":34.4},"TempUnit":"C"}
12:28:26.866 RSL: BLE = {"Time":"2022-06-19T12:28:26","BLEDevices":{"total":2,"2CAB33012C89":{"i":0,"r":-93},"7C0A3F53C69D":{"i":1,"r":-80}}}
12:28:26.883 RSL: BLE = {"Time":"2022-06-19T12:28:26","BLE":{"scans":15,"adverts":5272,"devices":2,"resets":0}}
12:33:26.827 RSL: STATE = {"Time":"2022-06-19T12:33:26","Uptime":"0T00:10:10","UptimeSec":610,"Heap":78,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":20,"MqttCount":0,"Berry":{"HeapUsed":4,"Objects":52},"Wifi":{"AP":1,"SSId":"mySSID","BSSId":"12:34:56:78:90:AB","Channel":6,"Mode":"11n","RSSI":100,"Signal":-23,"LinkCount":1,"Downtime":"0T00:00:04"}}
12:33:26.859 RSL: SENSOR = {"Time":"2022-06-19T12:33:26","ESP32":{"Temperature":33.9},"TempUnit":"C"}
12:33:26.868 RSL: BLE = {"Time":"2022-06-19T12:33:26","BLEDevices":{"total":2,"2CAB33012C89":{"i":0,"r":-90},"7C0A3F53C69D":{"i":1,"r":-78}}}
12:33:26.886 RSL: BLE = {"Time":"2022-06-19T12:33:26","BLE":{"scans":30,"adverts":10953,"devices":2,"resets":0}}

And my blerry_config.json looks like this:

{
  "devices": {
    "7C0A3F53C69D": {
      "alias": "7C0A3F53C69D",
      "model": "dev"
    },
    "2CAB33012C89": {
      "alias": "2CAB33012C89",
      "model": "dev"
    },
    "90F157245840": {
      "alias": "90F157245840",
      "model": "dev"
    }
  }
}

The driver file blerry_driver_dev.be is uploaded and right next to blerry.be and I have restarted the device.
I am curious why I can see the 2CAB33... device in the console output but cannot find it with the dev information?
Would appreciate any help.

kind regards,
Johannes

Crash during setup on Tasmota 12.5.0

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:184
load:0x40078000,len:12680
load:0x40080400,len:2908
entry 0x400805c4

00:00:00.002 HDW: ESP32-D0WD-V3 
00:00:00.055 UFS: FlashFS mounted with 296 kB free
00:00:00.086 CFG: Loaded from File, Count 14
00:00:00.096 QPC: Count 1
00:00:00.253 BRY: Berry initialized, RAM used=4041 bytes
00:00:00.271 TFS: File '.drvset003' not found
00:00:00.271 CFG: Energy use defaults as file system not ready or file not found
00:00:00.276 Project tasmota - Tasmota Version 12.5.0(bluetooth)-2_0_7(2023-04-17T08:07:04)
00:00:00.288 iBeacon register for advert callbacks
00:00:00.288 MI32Option0: 1
00:00:00.288 MI32Option1: 0
00:00:00.289 MI32Option2: 0
00:00:00.299 MI32Option4: 1
00:00:00.300 MI32Option5: 0
00:00:00.300 MI32Option6: 0
00:00:00.300 M32: init: request callbacks
00:00:00.955 WIF: Connecting to AP1 REMOVED Channel 6 BSSId 58:CB:52:AB:40:76 in mode 11n as tasmota-6393B0-5040...
00:00:01.097 WIF: Connected
00:00:01.357 HTP: Web server active on tasmota-6393B0-5040 with IP address 10.0.0.138
03:36:05.003 BLE: MasterEnable->1
03:36:05.011 BLE: BLETask:Starting NimBLE
03:36:05.766 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"12.5.0(bluetooth)","FallbackTopic":"cmnd/DVES_6393B0_fb/","GroupTopic":"cmnd/tasmotas/"}}
03:36:05.781 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6393B0-5040","IPAddress":"10.0.0.138","IP6Global":"REMOVED","IP6Local":"REMOVED"}}
03:36:05.802 RSL: INFO3 = {"Info3":{"RestartReason":{"Exception":29,"Reason":"StoreProhibited","EPC":"40084c54","EXCVADDR":"00000000","CallChain":["40084c51","40098a55","4009e33d","401ed352","401ec5af","401ec516","401ec5c1","4011175a","401117ce","40109131","4012c968","400f0479","400f05a3","400f1709","400f28da","400f7f66","4012f970","4011824d","401107ae","40110ee5","40112151","4014cd89","4011b209","401577d6","40161481","400e698b"]},"BootCount":7}}
03:36:08.911 QPC: Reset
03:36:08.918 RSL: STATE = {"Time":"2023-06-12T03:36:08","Uptime":"0T00:00:06","UptimeSec":6,"Heap":89,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":45},"Wifi":{"AP":1,"SSId":"REMOVED","BSSId":"REMOVED","Channel":6,"Mode":"11n","RSSI":100,"Signal":-39,"LinkCount":1,"Downtime":"0T00:00:02"}}
03:36:08.949 RSL: BLE = {"Time":"2023-06-12T03:36:08","BLEDevices":REMOVED}
03:36:08.962 RSL: BLE = {"Time":"2023-06-12T03:36:08","BLE":{"scans":0,"adverts":30,"devices":1,"resets":0}}
03:37:14.145 CMD: br load('blerry_setup.be')

abort() was called at PC 0x401ed352 on core 1


Backtrace: 0x40084c51:0x3ffd33c0 0x40098a55:0x3ffd33e0 0x4009e33d:0x3ffd3400 0x401ed352:0x3ffd3480 0x401ec5af:0x3ffd34a0 0x401ec516:0x3ffd34c0 0x401ec5c1:0x3ffd34e0 0x4011175a:0x3ffd3500 0x401117ce:0x3ffd3540 0x40109131:0x3ffd3560 0x4012c968:0x3ffd3620 0x400f0479:0x3ffd3640 0x400f05a3:0x3ffd3700 0x400f1709:0x3ffd3720 0x400f28da:0x3ffd3740 0x400f7f66:0x3ffd37c0 0x4012b9bd:0x3ffd3800 0x4015cb6e:0x3ffd3880 0x4012ed74:0x3ffd38c0 0x4011b209:0x3ffd38e0 0x40161331:0x3ffd3900 0x40161455:0x3ffd39f0 0x401626dd:0x3ffd3a60 0x400e698b:0x3ffd3ad0




ELF file SHA256: 0000000000000000

Rebooting...

CGG1 e-ink display

I have a couple of the CGG1 Cleargrass (Qingping): hygro thermometer, round body, e-ink displays. I know I can get them working using ESP home, but you need a bindkey. Is this something that can be supported in tasmota-blerry? What would you need from me to try and get this functioning?

Here is an Amazon link to the device I am talking about: https://www.amazon.com/Qingping-Bluetooth-Thermometer-Hygrometer-Temperature/dp/B08N64HC6B?ref_=ast_sto_dp&th=1&psc=1

This is an awesome project. Thanks so much.

Moved Blerry to different device now sensors unavailable in HA.

I had Blerry installed on a Linkind switch with bluetooth but noticed excessive RSSI activity from a Inkbird sensor. I think the activity was too much for the esp32 to handle. I was getting missed and delayed switch presses as I watched the console. I am no longer using the Linkind switch for BLE. I am now using a esp32 with esp32-bluetooth installed. BLE and MQT messages look good but sensor entities show unavailable in HA. What could cause this after switching devices? I am getting the tele from the esp32 temp etc...

Curious about Moes Bluetooth Smart Switch Relay

https://www.moeshouse.com/products/bluetooth-smart-switch-relay-module-single-point-control-and-pairing-without-wifi-network-bluetooth-sigmesh-functional-wireless-remote-control-with-bluetooth-gateway

Already Bluetooth Mesh Sig, haven't a clue whats inside or really much tasmota knowledge just noticed more devices seem to be coming online and my curiosity thought what the hell so I got x2.
They are cheap 2x from aliexpress cost me £10 and awaiting for them to arrive and haven't the foggiest how to control them from a Pi but just looking around on a fact finding mission hence why here.

Mqtt entity name stats with device name, new mqtt requirements

The new nqtts requirements that a entity not to use the device name, it looks like blerry names the device and entities with duplicate name thatxwill stop working soon.
Below is warning I got

Some MQTT entities have an entity name that starts with the device name. This is not expected. To avoid a duplicate name the device name prefix is stripped off the entity name as a work-a-round. Please inform the maintainer of the software application that supplies the affected entities to fix this issue

Sensors to not appear as statistics in HA

Thanks for this project!

I have been able to configure a govee device, however in HA it does not appear as a statistic (so that I can chart it).

I think this is because the discovery topic lacks a state_class: measurement field.

I am new to HA so may be mistaken and would be grateful if there is a work-around. I have also asked the workaround question on the HA forums here.

BRY: Exception> 'value_error' - unsupported protocol when running auto setup script

Running the auto setup script from the dev README throws the following error:

BRY: Exception> 'value_error' - unsupported protocol
stack traceback:
	<native>: in native function
	input:5: in function `start_blerry_setup`
	input:18: in function `main`

Firmware: https://github.com/tony-fav/tasmota-blerry/blob/main/tested_firmware/tasmota32solo1-linkind-ble-berry.bin
Device: Linkind 2 button switch, non-dimmer

Gigaset G-Tag

Hi, would like to have support for the Gigaset G-Tag. Is it possible to add this device to get the battery state? It is just a single command in unix: gatttool -b macid --char-read --handle=0x001b - and it returns e.g. 2f as the value:

gatttool -b xx:xx:xx:xx:xx:xx --char-read --handle=0x001b Characteristic value/descriptor: 2f
Would be great to get this with tasmota/blerry.

Support a Friendly Name

Allow the name in Home Assistant for the device to contain spaces and be separate from the bluetooth alias and mqtt topic.
In Tasmota this is known as the friendly_name and it is separate and can be set independently. As far as I can tell there is currently no way to have a space in the name presented to Home Assistant other than to edit it in home assistant after the fact.

Some ideas:
use string_replace on alias and replace spaces. Then use the replacement for mqtt topic and bluetooth alias while using original alias as Name for discovery etc.

Add a new attribute called friendly_name to allow the setting of the home assistant name independently of the topic and bluetooth alias.