Sonoff-Tasmota
Sonoff-Tasmota copied to clipboard
gemu2015
Keyfob not working
GUIDE
This troubleshooting issue template is meant to help Tasmota users with difficult problems. It is aimed to be opened if using the wiki and the support chat could not solve the issue. The Github Issue tracker is NOT a general discussion forum!
Please DO NOT OPEN AN ISSUE:
- If you have general questions or you need help on Tasmota usage, go to the Tasmota Support Chat
- If your Tasmota version is not the latest from the development branch, please update your device before submitting your issue. Your problem might already be solved. The latest precompiled binaries of Tasmota can be downloaded from http://thehackbox.org/tasmota/
- If your issue is about a new device, please use the Tasmota Template feature.
- If your issue is a flashing issue, please address it to the Tasmota Support Chat
- If your issue is compilation problem, please address it to the Tasmota Support Chat
- If your issue has been addressed before (i.e., duplicated issue), please ask in the original issue
- If your issue is a Wi-Fi problem or MQTT problem, please try the steps provided in the FAQ and troubleshooting wiki articles
Please take a few minutes to complete the requested information below. Our ability to provide assistance is greatly hampered without it. The details requested potentially affect which options to pursue. The small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you.
ISSUE DESCRIPTION - TROUBLESHOOTING
A clear description of what the issue is and be as extensive as possible i have the HM-17 module and the cheap keyfob that can beep. (this: https://www.amazon.de/gp/product/B01DIWX04E/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 ) the hm-17 work with the tasmota, i can see the scan. but when i power on one of the keyfob i see in the debug info only >>00000000:0000 and no data on mqtt or so. on the site it says this keyfob works, i have buy this, ok another color.
so i tried in the driver file change from DISI to DISC, so i can see the mac of the keyfob.
what can i do to get this work?
thanks
REQUESTED INFORMATION
Make sure these boxes are checked before submitting your issue. Thank you
FAILURE TO COMPLETE THE REQUESTED INFORMATION WILL RESULT IN YOUR ISSUE BEING CLOSED
- [x ] Read the Contributing Guide and Policy and the Code of Conduct
- [x ] Searched the problem in issues (https://github.com/arendst/Tasmota/issues)
- [x ] Searched the problem in the wiki (https://github.com/arendst/Tasmota/wiki/Troubleshooting)
- [x ] Searched the problem in the forum (https://groups.google.com/d/forum/sonoffusers)
- [x ] Searched the problem in the chat (https://discord.gg/Ks2Kzd4)
- [ x] Device used (e.g., Sonoff Basic): wemos d1 mini & HM-17
- [ x] Tasmota binary firmware version number used: 8.1
- [ ] Pre-compiled
- [ x] Self-compiled
- [ x] IDE / Compiler used: Arduino IDE
- [ ] Flashing tools used: _____
- [x ] Provide the output of this command:
Backlog Template; Module; GPIO:Configuration output here:
18:23:05 MQT: stat/sonoff/RESULT = {"NAME":"Generic","GPIO":[255,255,255,255,255,255,255,255,255,255,255,255,255],"FLAG":15,"BASE":18} 18:23:06 MQT: stat/sonoff/RESULT = {"Module":{"0":"Generic"}} 18:23:06 MQT: stat/sonoff/RESULT = {"GPIO0":{"9":"Switch1"},"GPIO1":{"168":"iBeacon TX"},"GPIO2":{"157":"LedLink"},"GPIO3":{"169":"iBeacon RX"},"GPIO4":{"1":"DHT11"},"GPIO5":{"106":"RFrecv"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"42":"Counter1"},"GPIO14":{"0":"None"},"GPIO15":{"9":"Switch1"},"GPIO16":{"0":"None"}} 18:23:06 DIS0 OK
- [ ] If using rules, provide the output of this command: ``Backlog Rule1; Rule2; Rule3``:
Rules output here:
- [x ] Provide the output of this command: ``Status 0``:
STATUS 0 output here: 18:22:24 CMD: STATUS 0 18:22:24 MQT: stat/sonoff/STATUS = {"Status":{"Module":0,"FriendlyName":["Tasmota"],"Topic":"sonoff","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}} 18:22:24 MQT: stat/sonoff/STATUS1 = {"StatusPRM":{"Baudrate":9600,"GroupTopic":"tasmotas","OtaUrl":"http://thehackbox.org/tasmota/release/tasmota.bin","RestartReason":"Software/System restart","Uptime":"0T00:11:29","StartupUTC":"2019-12-26T17:10:55","Sleep":50,"CfgHolder":4617,"BootCount":34,"SaveCount":103,"SaveAddress":"3F4000"}} 18:22:24 MQT: stat/sonoff/STATUS2 = {"StatusFWR":{"Version":"8.1.0.1(tasmota)","BuildDateTime":"2019.12.26 12:27:26","Boot":31,"Core":"2_6_1","SDK":"2.2.2-dev(5ab15d1)","Hardware":"ESP8266EX","CR":"333/699"}} 18:22:24 MQT: stat/sonoff/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["0011001000110011",""],"TelePeriod":60,"Resolution":"558180C0","SetOption":["00008009","2805C8000100060000005A00000000000000","00000000","00000000"]}} 18:22:24 MQT: stat/sonoff/STATUS4 = {"StatusMEM":{"ProgramSize":522,"Free":1524,"Heap":23,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"1640EF","FlashMode":2,"Features":["00000407","8F802197","000100A0","020004C5","000000C0","00000904"],"Drivers":"1,2,3,4,8,9,10,17,27,29","Sensors":"1,2,3,5,6,9,22,52"}} 18:22:24 MQT: stat/sonoff/STATUS5 = {"StatusNET":{"Hostname":"sonoff-2261","IPAddress":"192.168.178.23","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.178.1","Mac":"BC:DD:C2:B6:68:D5","Webserver":2,"WifiConfig":4}} 18:22:24 MQT: stat/sonoff/STATUS6 = {"StatusMQT":{"MqttHost":"iobroker.local","MqttPort":1883,"MqttClientMask":"Sicherungskasten","MqttClient":"Sicherungskasten","MqttUser":"mqttuser","MqttCount":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":30}} 18:22:24 MQT: stat/sonoff/STATUS7 = {"StatusTIM":{"UTC":"Thu Dec 26 17:22:24 2019","Local":"Thu Dec 26 18:22:24 2019","StartDST":"Sun Mar 31 02:00:00 2019","EndDST":"Sun Oct 27 03:00:00 2019","Timezone":"+01:00","Sunrise":"08:16","Sunset":"16:11"}} 18:22:24 MQT: stat/sonoff/STATUS10 = {"StatusSNS":{"Time":"2019-12-26T18:22:24","Switch1":"OFF","COUNTER":{"C1":86},"DHT11":{"Temperature":23.7,"Humidity":38.0},"TempUnit":"C"}} 18:22:24 MQT: stat/sonoff/STATUS11 = {"StatusSTS":{"Time":"2019-12-26T18:22:24","Uptime":"0T00:11:29","UptimeSec":689,"Heap":23,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":84,"Signal":-58,"LinkCount":1,"Downtime":"0T00:00:06"}}} 18:22:25 hm17cmd 6
- [ ] Provide the output of the Console log output when you experience your issue; if applicable:
_(Please use_ ``weblog 4`` _for more debug information)_
Console output here:
**(Please, remember to close the issue when the problem has been addressed)**
did you initialize the hm17 ?
you must execute these commands only once (reconfigure the hm17 to master mode) sensor52 1 sensor52 2
then switch debug mode on
#define IBEACON_DEBUG in compiler
and then
sensor 52 d1
yes, i have do this. in the console with debug i can see the scan result. when i turn on the smart-tag it comes >>00000000:0000
when i log the serial communication betwen the tasmota and the hm-17 it display this OK+DIS0:00000000:00000000000000000000000000000000:0000000000:FFFF1A843296:-04 the fff... is the smarttag
you should NOT use DISC but DISI
below is my debug log for 2 ibeacons and one keyfob there are many other bluetooth devices listet that are not compatible compatible devices have the first field set OR MAC starts with "FFFF" (keyfob)
09:43:34 hm17cmd 3 09:43:35 DISCS OK 09:43:35 DISC: OK 09:43:35 >>00000000:00000000000000000000000000000000:0000000000:989E633D04A9:-062 09:43:35 DISC: OK 09:43:35 >>00000000:00000000000000000000000000000000:0000000000:5AEEDA4CA928:-062 09:43:35 DISC: OK 09:43:35 >>4C000C0E:00B381FFCE3E6DFD455B9D5329BD1005:4B1C4EF4C1:59F59CC93F4A:-078 09:43:35 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-27T09:43:35","IBEACON_59F59CC93F4A":{"RSSI":-78}} 09:43:35 DISC: OK 09:43:35 >>00000000:00000000000000000000000000000000:0000000000:604057C2E87F:-068 09:43:35 DISC: OK 09:43:35 >>00000000:00000000000000000000000000000000:0000000000:779D778DE593:-063 09:43:35 DISC: OK 09:43:35 >>00000000:00000000000000000000000000000000:0000000000:FFFF000F893F:-064 09:43:35 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-27T09:43:35","IBEACON_FFFF000F893F":{"RSSI":-64}} 09:43:35 DISC: OK 09:43:35 >>00000000:00000000000000000000000000000000:0000000000:48921D1EB1D8:-064 09:43:35 DISC: OK 09:43:35 >>00000000:00000000000000000000000000000000:0000000000:0024E4204295:-078 09:43:39 DISC: OK 09:43:39 >>4C000215:FDA50693A4E24FB1AFCFC6EB07647825:0005000622:E788BEC6FBF0:-075 09:43:39 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-27T09:43:39","IBEACON_E788BEC6FBF0":{"RSSI":-75}} 09:43:39 DISC: OK 09:43:39 >>00000000:00000000000000000000000000000000:0000000000:989E633D04A9:-066 09:43:40 DISC: OK 09:43:40 >>00000000:00000000000000000000000000000000:0000000000:5AEEDA4CA928:-065 09:43:40 DISCE OK
web menu shows the 3 devices
This is my console output with debug enabled after a new stock flash: 11:27:42 CMD: sensor52 d1 11:27:42 MQT: stat/sonoff/RESULT = {"Sensor52":debug:1} 11:27:47 hm17cmd 3 11:27:47 DISCS OK 11:27:50 DIS0 OK 11:27:50 >>00000000:000 11:27:57 hm17cmd 3 11:27:57 DISCS OK 11:27:59 DIS0 OK 11:27:59 >>00000000:000 11:28:07 hm17cmd 3 11:28:07 DISCS OK 11:28:08 DIS0 OK 11:28:08 >>00000000:000 11:28:17 hm17cmd 3 11:28:17 DISCS OK 11:28:19 DIS0 OK 11:28:19 >>00000000:000 11:28:27 hm17cmd 3 11:28:27 DISCS OK 11:28:29 MQT: tele/sonoff/STATE = {"Time":"2019-12-27T11:28:29","Uptime":"0T00:01:12","UptimeSec":72,"Heap":25,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":92,"Signal":-54,"LinkCount":1,"Downtime":"0T00:00:06"}} 11:28:29 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-27T11:28:29","Switch1":"OFF","COUNTER":{"C1":86},"DHT11":{"Temperature":19.8,"Humidity":40.0},"TempUnit":"C"}
but i found, at the moment when i send the renew command, it shows the right data: 11:43:10 hm17cmd 3 11:43:10 DISCS OK 11:43:12 DIS0 OK 11:43:12 >>00000000:000 11:43:14 CMD: sensor52 s AT+RENEW 11:43:14 MQT: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+RENEW} 11:43:14 296:-052OK+RENEW0000000000000:0000000000:FFFF365C3396:-057OK+DIS0:00000000:00000000000000000000000000000000:0000000000:FFFF1A843
another test with the commands confuesd me complete:
12:07:42 hm17cmd 3 12:07:42 DISCS OK 12:07:43 DIS0 OK 12:07:43 >>00000000:000 12:07:48 CMD: sensor52 s AT+DISC? 12:07:48 MQT: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+DISC?} 12:07:48 00000000000000000000000000000:0000000000:FFFF365C3396:-048OK+DISCEOK+DISCS 12:07:49 OK+DIS0:FFFF1A843296:-056:iTA 12:07:49 G
12:07:49 OK+DIS0:FFFF365C3396:-049:iT 12:07:50 AG
12:07:51 OK+DISCE 12:08:14 CMD: sensor52 3 12:08:14 hm17cmd 3 12:08:14 MQT: stat/sonoff/RESULT = {"Sensor52":hm17cmd:3} 12:08:14 DISCS OK 12:08:16 DIS0 OK 12:08:16 >>00000000:000 12:08:22 hm17cmd 3 12:08:22 DISCS OK 12:08:25 DIS0 OK 12:08:25 >>00000000:000 12:08:27 CMD: sensor52 s AT+DISI? 12:08:27 MQT: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+DISI?} 12:08:27 396:-048OK+DISCEOK+DISCS00000:0000000000:FFFF1A843296:-067OK+DIS0:00000000:00000000000000000000000000000000:0000000000:FFFF365C3 12:08:29 000000000000000000000000000000:0000000000:FFFF365C3396:-050 12:08:31 OK+DIS0:00000000:000000000000000000 12:08:31 00000000000000:0000000000:FFFF1A843296:-062OK+DISCE
may be there is a different firmware in the module please check firmware version with
sensor52 s AT+VERR?
my module was sold with remark "newest firmware version" however it reports V120 which is in conflict with version numbers of the documents
after resetting the module to factory defaults it should only work in role 0 (peripheral role) but it MUST be in role 1 (central role) also it must be in IMME 1 mode
12:24:19 CMD: sensor52 s AT+VERR? 12:24:19 MQT: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+VERR?} 12:24:19 296:-057OK+DISCEOK+Get:HMSoft V110000000:FFFF365C3396:-052OK+DIS0:00000000:00000000000000000000000000000000:0000000000:FFFF1A843
since it the v 110
pay attention with raw commands!
when you place eg AT+DISCE cmd which takes some time it may be that the regular scab interferes (which is the case in you logging)
before testing with raw command you should switch of the scheduler
by sensor52 u0
yes it is the v110
12:26:22 MQT: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+VERR?} 12:26:22 OK+Get:HMSoft V110
ok your software is older, there my be the reason why you get different results. We have to find a datasheet which refers to the version differences.
on the manufacture site v110 is the actual firmware http://www.jnhuamao.cn/download_rom_en.asp?id=
in this list the hm-19 have v120 http://www.jnhuamao.cn/bluetooth.asp this module with the v120 firmware have another chip, as the hm-17/19 with v110 firmware
but i cant find a version from the hm-17 that have this, only the v110
i take a look at the datasheets, the basic at commands to scan are the same to the hm-10/11 module
sure you have the hm-17 module? i have buy one, and after a lot of trubble it was a hm-19 with wrong label
the answer from the at commands are the same from the hm-10, 17, 19 i think it is possibil to make them all work.
sorry for the bad english, greet from germany
very confusing , i definitely have the hm17 (at least printed on board) with v120
in the data sheet they refer to V539 as latest revision ????
no the hm10 can't take central role only peripheral role that's the main difference.
hm19 board looks exactly the same.
that's what i have
dann schreiben wir doch besser in Deutsch.
Dein logging ist komplett anders, da muss es Formattierungs Unterschiede in der Modulausgabe geben.
du solltest die rohen Ausgaben loggen dann kann ich vergleichen wo die Unterschiede sind und das anpassen.
Viel kann es nicht sein.
merkwürdig, in deinem Link mit den ganzen Modulen gibt es das hm17 und auch hm19 sowohl mit v110 und v120
ok, your module have the cc2541 my hm-17 have the CC2640R2f my hm-19 module have a TI chip
my hm-10 (als solches verkauft) - deutsch its besser ja :D
hat einen cc2541 chip, es ist ein fake, aber nach einem firmwareflash auf die offizielle firmware kann das auch zentralle role.
hier eine ausgabe des "hm-10" über usb-ttl
OKOK+Set:1OK+Set:1OK+DISCSOK+DIS0:FFFF365C3396OK+RSSI:-048
OK+NAME:iTAG
OK+DIS1:FEF4FD96F07COK+RSSI:-081
OK+NAME:SumUp 606
OK+DISCEOK+DISISOK+DISC:00000000:00000000000000000000000000000000:0000000000:FEF4FD96F07C:-095OK+DISC:00000000:00000000000000000000000000000000:0000000000:FFFF365C3396:-047OK+DISC:00000000:00000000000000000000000000000000:0000000000:FFFF1A843296:-049OK+DISCE
der hm-17 über den komme ich leider im moment nur über die tasmota konsole da er verlötet ist gibt bei DISC? das aus 2:55:55 CMD: sensor52 s AT+DISC? 12:55:55 RSL: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+DISC?} 12:55:55 OK+DISCS 12:55:56 OK+DIS0:FFFF365C3396:-044:i 12:55:56 TAG
12:55:56 OK+DIS0:FFFF1A843 12:55:56 296:-032:iTAG
12:55:58 OK+DISCE
und DISI? 2:55:55 CMD: sensor52 s AT+DISC? 12:55:55 RSL: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+DISC?} 12:55:55 OK+DISCS 12:55:56 OK+DIS0:FFFF365C3396:-044:i 12:55:56 TAG
12:55:56 OK+DIS0:FFFF1A843 12:55:56 296:-032:iTAG
12:55:58 OK+DISCE
das sieht für mich erstmal gleich aus
oh hier nochmal richtig CMD: sensor52 s AT+DISI? 13:02:23 RSL: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+DISI?} 13:02:23 OK+DISCS 13:02:24 OK+DIS0:00 13:02:24 000000:00000000000000000000000000000000:0000000000:FFFF1A843296:-032 13:02:26 OK+DIS0:00000000:000 13:02:27 00000000000000000000000000000:0000000000:FFFF365C3396:-043 13:02:27 OK+DISCE
das ist der hm-10 den ich noch da habe https://www.ebay.de/itm/Arduino-Raspberry-PI-AT-09-Bluetooth-Modul-HM-10-BLE-CC2541-CC2540/283651995451?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m2749.l2649 das einzige was der nach dem firmwarflash nicht mehr kann ist das renew da bleibt der in einer schleife hängen bis man ihm nach dem reset ein befehl schickt
ja den hm10 habe ich auch aber meiner geht nur in peripheral role.
versuche mal die Unterschiede zwischen unseren Version zu checken melde mich später wieder
Ich fass das nochmal Formatiert zusammen. beide module über einen USB-TTL adapter abgefragt hm-10 (mit firmwareflash) chip: cc2541 wurde nach dieser anleitung geflasht: https://circuitdigest.com/microcontroller-projects/how-to-flash-the-firmware-on-cloned-hm-10-ble-module-using-arduino-uno AT+VERR? HMSoft V609
AT+ROLE1 OK+Set:1
AT+IMME1 OK+Set:1
AT+DISC?
OK+DISCSOK+DIS1:FEF4FD96F07COK+RSSI:-086
OK+NAME:SumUp 606
OK+DIS0:FFFF365C3396OK+RSSI:-062
OK+NAME:iTAG
OK+DIS0:FFFF1A843296OK+RSSI:-044
OK+NAME:iTAG
OK+DISCE
AT+DISI? OK+DISISOK+DISC:00000000:00000000000000000000000000000000:0000000000:FEF4FD96F07C:-086OK+DISC:00000000:00000000000000000000000000000000:0000000000:FFFF365C3396:-054OK+DISCE
HM-17 chip:CC2640R2f
AT+VERR? OK+Get:HMSoft V110
AT+ROLE1 OK+Set:1
AT+IMME1 OK+Set:1
AT+DISC?
OK+DISCSOK+DIS0:FFFF365C3396:-046:iTAG
OK+DIS0:FFFF1A843296:-046:iTAG
OK+DISCE
AT+DISI? OK+DISCSOK+DIS0:00000000:00000000000000000000000000000000:0000000000:FFFF1A843296:-046OK+DIS0:00000000:00000000000000000000000000000000:0000000000:FFFF365C3396:-052OK+DISCE
identisch sind die antworten nicht. aber zb bei DISI? die antwort, wenn man alles vor dem ersten : rausfiltert sind sie gleich, was in der theorie ja recht einfach gehen müsste. warum der cc2541 chip das sumup gerät sieht und der andere nicht ist mir nicht ganz klar.
egal welches von dem modulen, in der tasmota console kommt immer dieses bild (ist jetzt vom HM-17) 13:36:50 CMD: sensor52 d1 13:36:50 MQT: stat/sonoff/RESULT = {"Sensor52":debug:1} 13:36:51 DIS0 OK 13:36:51 >>00000000:000 13:36:59 hm17cmd 3 13:36:59 DISCS OK 13:37:00 DIS0 OK 13:37:00 >>00000000:000 13:37:09 hm17cmd 3 13:37:09 DISCS OK 13:37:11 DIS0 OK 13:37:11 >>00000000:000
betrifft das nur die ibeacon.ino datei? die habe ich gerade übernommen, leider immer noch das selbe bild
ja nur die iBeacon.ino. soweit ich das sehe gibt es doch nur einen Unterschied:
DISO versus DISC
dein HM17 AT+DISI? OK+DISCS OK+DIS0:00000000:00000000000000000000000000000000:0000000000:FFFF1A843296:-046 OK+DIS0:00000000:00000000000000000000000000000000:0000000000:FFFF365C3396:-052 OK+DISCE
mein hm17 OK+DISCS OK+DISC:00000000:0000000000:0000000000:52C04423F76D:-078 OK+DISC:00000000:00000000000000000000000000000000:0000000000:5C9940634CCB:-073 OK+DISC:400000000000000000000000000000000:0000000000:78A9EF4ADEBB:-066 OK+DISC:00000000:00000000000000000000000000000000:0000000000:0024E4204295:-078 OK+DISC:00000000:00000000000000000000000000000000:0000000000:52C04423F76D:-076 OK+DISC:00000000:00000000000000000000000000000000:0000000000:5C9940634CCB:-064 OK+DISCE
scheinbar ist es nur der unterschied, wenn ich das at comand manuel sende listet er mir auch die sachen. nur scheint die auswertung bzw das dekodieren der antwort irgendwie nicht richtig. ich bin kein c# profi, aber für mich liest sich zeile 192 if (!strncmp(ib->MAC,"FFFF",4) || strncmp(ib->FACID,"00000000",8)) { seltsam, wenn nicht fff oder 0000... dann, das ist richtig so?
Ja dieser Teil ist richtig. Was sagt denn dein Log jetzt. Vergleiche mal mit meinem von Oben. erst wenn der Log gleich aussieht geht es weiter
jetzt hats das teil beim flashen wieder abgeshcossen, muss es erst holen. (seit das vom steckbrett auf ne platine umgezogen ist kann ich es nicht mehr flashen solang der wemos mit dem hm-17 verbunnden ist) du meinst sicher DIS0 vs DISC? meiner schreibt eine 0 dahin wo deiner ein c hat
juhu, da tut sich was
17:05:56 CMD: sensor52 d1 17:05:56 MQT: stat/sonoff/RESULT = {"Sensor52":debug:1} 17:05:59 hm17cmd 0 17:05:59 AT OK 17:06:09 hm17cmd 3 17:06:09 DISCS OK 17:06:10 DISC: OK 17:06:10 >>00000000:00000000000000000000000000000000:0000000000:FFFF365C3396:-052 17:06:10 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-27T17:06:10","IBEACON_FFFF365C3396":{"RSSI":-52}} 17:06:12 DISC: OK 17:06:12 >>00000000:00000000000000000000000000000000:0000000000:FFFF1A843296:-063 17:06:12 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-27T17:06:12","IBEACON_FFFF1A843296":{"RSSI":-63}} 17:06:13 DISCE OK 17:06:19 hm17cmd 3 17:06:19 DISCS OK 17:06:21 DISC: OK 17:06:21 >>00000000:00000000000000000000000000000000:0000000000:FFFF1A843296:-061 17:06:21 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-27T17:06:21","IBEACON_FFFF1A843296":{"RSSI":-61}} 17:06:22 DISC: OK 17:06:22 >>00000000:00000000000000000000000000000000:0000000000:FFFF365C3396:-053 17:06:22 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-27T17:06:22","IBEACON_FFFF365C3396":{"RSSI":-53}} 17:06:23 DISCE OK 17:06:29 hm17cmd 3 17:06:29 DISCS OK
das mit dem Beepen geht so (in der console) z.B. IBEACON_FFFF000F893F 99
du musst ja die Adresse angeben
leider hält die Batterie bei den Dingern nur ca einen Monat. Diese "echten" ibeacons (ohne beeper) halten ein Jahr
https://www.ebay.de/itm/NRF51822-2V-3-3V-Bluetooth-4-0-Funkmodul-fur-ibeacon-Basisstation-YB-W-HV/283697479562?_trkparms=ispr%3D1&hash=item420dafff8a:g:TT4AAOSwaMtcnXbr&enc=AQAEAAACQBPxNw%2BVj6nta7CKEs3N0qXzzM%2Bppa7LaGtlUJmFkFx2Dyixb39xNQkLltRP1Yl44xFgHWActzdl9BdxIQ%2FJSFeMJkGRE2zyksquXDJYYlrN14JmTCCFG2lQNPMmiISPQiIDNs5%2FgE7t%2BDqQw%2FCmtp5co7yggozRg61GEs%2FjGhrvzcaVjcJYZJY73T9F6F7Bdz1HoJOc218N93yfPapR9mP%2Bfesb0%2B5JKcZ00uw620kkeokbYjTEi9E%2B5mpSbVqaS4joolfn7q%2FnbYqAtzpzHmOMtaqtuRFS2pzoKV6nXHhXbn%2FK5BHft8PQXKsZ2P1SxTmYByg4shBswpXnwddC2UvV4bPwCBgx1s6j%2FnAS5EDWQbKW3qSHYWJ67bW%2F%2Btu7Ld10ae0l94S424VIQ3cqazf8JEPY49uubxNhbaSwhd5mN9havCBtWIMmji2U88gsenDQX0yr7CS11F46fEBlOk8zrpJORriFxL%2FGoF6Uu7Y%2FbHoSiez%2BONFtuZ1lSlMLoUA2hN9jNDy9ggpYYsegxtOR0pI9qINUPAT9v7WZGrQLXlrk%2B1b5WJyOsYa%2FQPv1gC%2FiOU9pF8Vax03dbXzfXMTjlztMQxP%2BIk7D8oU4hmtqjS2zD2m%2F2z99EmyFXirYmu6rmxoBvbYZA9cAQ0j3faXzzcyuFD5G86uhIjPejj%2FA%2Fre20GU5aX8lI2fwNMQBFDw1T82nxxr8NkUJ4ADhQG5E64NVrzWWJ4Wqv75rwtXeiJ8evJWD5zpS8z1WYtaGqw%3D%3D&checksum=2836974795628aa06bdee0fd4a0987b8d70a04838aff&enc=AQAEAAACQBPxNw%2BVj6nta7CKEs3N0qXzzM%2Bppa7LaGtlUJmFkFx2Dyixb39xNQkLltRP1Yl44xFgHWActzdl9BdxIQ%2FJSFeMJkGRE2zyksquXDJYYlrN14JmTCCFG2lQNPMmiISPQiIDNs5%2FgE7t%2BDqQw%2FCmtp5co7yggozRg61GEs%2FjGhrvzcaVjcJYZJY73T9F6F7Bdz1HoJOc218N93yfPapR9mP%2Bfesb0%2B5JKcZ00uw620kkeokbYjTEi9E%2B5mpSbVqaS4joolfn7q%2FnbYqAtzpzHmOMtaqtuRFS2pzoKV6nXHhXbn%2FK5BHft8PQXKsZ2P1SxTmYByg4shBswpXnwddC2UvV4bPwCBgx1s6j%2FnAS5EDWQbKW3qSHYWJ67bW%2F%2Btu7Ld10ae0l94S424VIQ3cqazf8JEPY49uubxNhbaSwhd5mN9havCBtWIMmji2U88gsenDQX0yr7CS11F46fEBlOk8zrpJORriFxL%2FGoF6Uu7Y%2FbHoSiez%2BONFtuZ1lSlMLoUA2hN9jNDy9ggpYYsegxtOR0pI9qINUPAT9v7WZGrQLXlrk%2B1b5WJyOsYa%2FQPv1gC%2FiOU9pF8Vax03dbXzfXMTjlztMQxP%2BIk7D8oU4hmtqjS2zD2m%2F2z99EmyFXirYmu6rmxoBvbYZA9cAQ0j3faXzzcyuFD5G86uhIjPejj%2FA%2Fre20GU5aX8lI2fwNMQBFDw1T82nxxr8NkUJ4ADhQG5E64NVrzWWJ4Wqv75rwtXeiJ8evJWD5zpS8z1WYtaGqw%3D%3D&checksum=2836974795628aa06bdee0fd4a0987b8d70a04838aff
ja das mit dem peeb geht, der broker hat wohl die id noch nicht richtig übernommen oder ich hab ausgerechnet die 99 gesendet als er aktuialisierte.
die beeper werden nur genutzt wenn man sie braucht, also einschalten, in die nähe gehen bis er vom broker eine meldung bekommt zum piepsen usw... eine art anwesenheit/sicherheitsystem
jap von den dingern hab ich mir noch welche bestellt. auf der tasmota wiki seite sind die ja auch verlinkt bei aliexpress, dort bieten sie aber zwei versionen an, das evt genauer beschreiben welche version man nehmen sollte.
evt noch interesse den hm-10 zum laufen zu bringen? den gibt es ja deutlich einfacher/günstiger zu beschaffen, und das flashen ist eigentlich keine große sache falls man ein "china clone" erwischt