search

gemu2015 / Sonoff-Tasmota

Tasmota Fork TCS34725,PN532_i2,ccc1101 Moritz support,m5stack 4,7 epaper, hotplug drivers
GNU General Public License v3.0
24 stars 19 forks source link

Keyfob not working #16

Open lacrimosa2k2 opened 4 years ago

lacrimosa2k2 commented 4 years ago

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

(Please, remember to close the issue when the problem has been addressed)

gemu2015 commented 4 years ago

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

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

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

Bildschirmfoto 2019-12-27 um 09 43 38
lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

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

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

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

lacrimosa2k2 commented 4 years ago

yes it is the v110

12:26:22 MQT: stat/sonoff/RESULT = {"Sensor52":hm17cmd:AT+VERR?} 12:26:22 OK+Get:HMSoft V110

gemu2015 commented 4 years ago

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.

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

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.

Bildschirmfoto 2019-12-27 um 12 42 23 Bildschirmfoto 2019-12-27 um 12 42 53

that's what i have

Bildschirmfoto 2019-12-27 um 12 39 43
gemu2015 commented 4 years ago

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.

gemu2015 commented 4 years ago

merkwürdig, in deinem Link mit den ganzen Modulen gibt es das hm17 und auch hm19 sowohl mit v110 und v120

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

du hast dich vertippt hast 2 mal disc? abgeschickt

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

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

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

hab eine neue Version auf Github gestellt. Versuchs mal damit

lacrimosa2k2 commented 4 years ago

betrifft das nur die ibeacon.ino datei? die habe ich gerade übernommen, leider immer noch das selbe bild

gemu2015 commented 4 years ago

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

lacrimosa2k2 commented 4 years ago

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?

gemu2015 commented 4 years ago

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

gemu2015 commented 4 years ago

oh war noch ein Fehler drin, Versuchs jetzt nochmal

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

ja, ist nur dieser Unterschied, hatte es aber falsch korrigiert vorhin

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

das mit dem Beepen geht so (in der console) z.B. IBEACON_FFFF000F893F 99

du musst ja die Adresse angeben

gemu2015 commented 4 years ago

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

lacrimosa2k2 commented 4 years ago

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

gemu2015 commented 4 years ago

warum die auch hier wieder was anders machen ist mir ein Rätsel. nach DISI kommt da statt DISCS DISIS sonst ist alles gleich bau dir das direkt ein.

werde auch mal versuchen meinen zu Flaschen.

gemu2015 commented 4 years ago

ok ist auf GitHub

lacrimosa2k2 commented 4 years ago

super, werd es morgen mal testen mit einem anderen aufbau.

könnte man das nicht anhand der version mehr oder weniger einstellen wie die antworten verarbeitet werden? nur so eine idee

welcher von den nrf chips ist den eig der richtige bei aliexpress, die chinesisch-deutsch übersetzung verstehe ich mal garnicht https://de.aliexpress.com/item/32885909449.html?spm=a2g0o.productlist.0.0.76004832Hfv6v5&algo_pvid=4b3b6ba8-5607-405d-a287-e974ff95412c&algo_expid=4b3b6ba8-5607-405d-a287-e974ff95412c-0&btsid=b55e7608-ea87-448e-a059-f835093ba95b&ws_ab_test=searchweb0_0,searchweb201602_1,searchweb201603_53 einmal beacon und einmal locate rssi

lacrimosa2k2 commented 4 years ago

HM-10 mit Firmware V609 funktioniert auch.

ein kleines problem noch was ich bis jetzt nicht rausbekommen habe, der hm-17 sitzt bei mir auf einer "adapterplatine" die an einem wemos an 5v hängt rx an tx usw, wenn man das ganze angeschlossen hat wollte der hm-17 nicht starten, testeweise hab ich einen spannungsteiler bei rx auf den hm-17 gesetzt, nun hat sich das ganze verlagert und der wemos startet nicht mehr, gibt es da einen trick? edit: gelöst bei hm-17 auf adapterplatine muss die verkabelung tx-tx und rx-rx sein und in der config umdrehen, schon klappt es ohne zickerreien

gemu2015 commented 4 years ago

danke für das Doku update . Die neue xsns_52_ibeacon.ino Version ist gerade bei Tasmota im pr.

lacrimosa2k2 commented 4 years ago

Gern doch. kleine frage am rande, kann es sein das diese anhänger die piepsen können eine mieserable reichweite haben? mit frischen batterien ist nach 3m freie distanz schluss

gemu2015 commented 4 years ago

ja die Reichweite is nicht sehr hoch. die Orientierung der Antenne des hm17 spielt aber eine Rolle Habe festgestellt dass mein iPhone (app nRF Connect) mit den Buttons eine deutlich höhere Reichweite hat.

lacrimosa2k2 commented 4 years ago

ich hab jetzt zu dem HM-10 gewechselt da er eine merklich bessere reichweite hat, er hat auch eine invertet-F antenne, der HM-17 hat nur eine "einfache"

ein problem scheint noch zu bestehen beim decodieren der antwort (hat der HM-17 auch gemacht) grafik es scheint als ob er sich manchmal antworten verschluckt und an teile des at komandos an den string anhängt, habe jetzt leider nur die daten in meinem broker.

Broker: `

sonoff.0 2019-12-30 08:57:18.506 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T08:57:18","IBEACONf#�ff�v6��v":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 08:56:48.099 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T08:56:47","IBEACONf#�ff�v6��v":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 08:53:44.317 info (25315) new object created: sonoff.0.Sicherungskasten.IBEACON_+3�f#�ff�v6�_RSSI
sonoff.0 2019-12-30 08:43:38.503 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T08:43:38","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 08:43:08.144 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T08:43:07","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 07:51:28.468 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T07:51:28","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 07:50:58.273 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T07:50:57","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 07:13:05.416 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T07:13:05","IBEACONf#�ff�v6��v":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 07:12:34.919 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T07:12:34","IBEACONf#�ff�v6��v":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 07:07:38.428 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T07:07:38","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 07:07:08.120 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T07:07:07","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 06:42:28.461 warn (25315) Cannot parse data "SENSOR": {"Time":"2019-12-30T06:42:28","IBEACON�fF�f�6���":{"RSSI":0}}_ - SyntaxError: Unexpected token  in JSON at position 46
sonoff.0 2019-12-30 06:41:58.053 warn (25315) Cannot parse data "SENSOR": {"Time":"2019-12-30T06:41:57","IBEACON�fF�f�6���":{"RSSI":0}}_ - SyntaxError: Unexpected token  in JSON at position 46
sonoff.0 2019-12-30 05:49:45.367 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T05:49:45","IBEACON6�6�6����":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 42
sonoff.0 2019-12-30 05:49:14.709 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T05:49:14","IBEACON6�6�6����":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 42
sonoff.0 2019-12-30 05:35:58.413 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T05:35:58","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 05:35:28.016 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T05:35:27","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 04:45:18.406 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T04:45:18","IBEACONf#�ff�v6��v":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 04:44:47.951 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T04:44:47","IBEACONf#�ff�v6��v":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 04:38:28.408 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T04:38:28","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 04:37:58.011 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T04:37:58","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 03:43:38.379 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T03:43:38","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 03:43:07.973 warn (25315) Cannot parse data "SENSOR": _{"Time":"2019-12-30T03:43:08","IBEACONf#�ff�v6���":{"RSSI":0}} - SyntaxError: Unexpected token  in JSON at position 49
sonoff.0 2019-12-30 03:19:47.975 info (25315) new object created: sonoff.0.Sicherungskasten.IBEACON_029D7B43D:-0_RSSI

`

Tasmota Log: ` 08:43:24 MQT: tele/sonoff/STATE = {"Time":"2019-12-30T08:43:24","Uptime":"0T14:00:13","UptimeSec":50413,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:06"}} 08:43:24 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:43:24","Switch1":"ON","COUNTER":{"C1":1055200},"DHT11":{"Temperature":20.3,"Humidity":32.0},"TempUnit":"C"} 08:43:38 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:43:38","IBEACONf#�ff�v6���":{"RSSI":0}} 08:48:24 MQT: tele/sonoff/STATE = {"Time":"2019-12-30T08:48:24","Uptime":"0T14:05:13","UptimeSec":50713,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":100,"Signal":-43,"LinkCount":1,"Downtime":"0T00:00:06"}} 08:48:24 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:48:24","Switch1":"ON","COUNTER":{"C1":1055200},"DHT11":{"Temperature":20.3,"Humidity":32.0},"TempUnit":"C"} 08:53:24 MQT: tele/sonoff/STATE = {"Time":"2019-12-30T08:53:24","Uptime":"0T14:10:13","UptimeSec":51013,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:06"}} 08:53:24 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:53:24","Switch1":"ON","COUNTER":{"C1":1055200},"DHT11":{"Temperature":20.3,"Humidity":31.0},"TempUnit":"C"} 08:53:44 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:53:44","IBEACON+3�f#�ff�v6�":{"RSSI":0}} 08:54:14 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:54:14","IBEACON_+3�f#�ff�v6�":{"RSSI":0}} 08:56:47 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:56:47","IBEACON_f#�ff�v6��v":{"RSSI":0}} 08:57:18 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:57:18","IBEACON_f#�ff�v6��v":{"RSSI":0}} 08:58:24 MQT: tele/sonoff/STATE = {"Time":"2019-12-30T08:58:24","Uptime":"0T14:15:13","UptimeSec":51313,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":100,"Signal":-45,"LinkCount":1,"Downtime":"0T00:00:06"}} 08:58:24 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T08:58:24","Switch1":"ON","COUNTER":{"C1":1055200},"DHT11":{"Temperature":20.5,"Humidity":31.0},"TempUnit":"C"} 09:03:24 MQT: tele/sonoff/STATE = {"Time":"2019-12-30T09:03:24","Uptime":"0T14:20:13","UptimeSec":51613,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:06"}} 09:03:24 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T09:03:24","Switch1":"ON","COUNTER":{"C1":1055200},"DHT11":{"Temperature":20.5,"Humidity":31.0},"TempUnit":"C"} 09:08:24 MQT: tele/sonoff/STATE = {"Time":"2019-12-30T09:08:24","Uptime":"0T14:25:13","UptimeSec":51913,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:06"}} 09:08:24 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T09:08:24","Switch1":"ON","COUNTER":{"C1":1055200},"DHT11":{"Temperature":20.5,"Humidity":31.0},"TempUnit":"C"} 09:13:24 MQT: tele/sonoff/STATE = {"Time":"2019-12-30T09:13:24","Uptime":"0T14:30:13","UptimeSec":52213,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"0011001000110011","BSSId":"00:17:13:15:65:98","Channel":1,"RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:06"}} 09:13:24 MQT: tele/sonoff/SENSOR = {"Time":"2019-12-30T09:13:24","Switch1":"ON","COUNTER":{"C1":1055200},"DHT11":{"Temperature":20.6,"Humidity":31.0},"TempUnit":"C"}

09:49:27 DISIS OK 09:49:29 DISC: OK 09:49:29 >>00000000:0000000000000000000000000000000f�Vf##�F&##�Vf���V�OK+ 09:49:42 hm17cmd 3 09:49:42 DISIS OK 09:49:43 DISC: OK 09:49:43 >>00000000:00000000000000000000000000000000:0000000000:FEF4FD96F07C:-084 09:49:45 DISC: OK 09:49:45 >>00000000:00000000000000000000000000000000:0000000000:5FDD04BDD656:-095 `

hatte irgendwo noch gelesen das die firmware auch unterschiedliche kommunikation erwartet, der eine nichts, der andere wieder NL und der nächste NL&CR, ich find nur die seite nicht wieder wo das stand

Jason2866 commented 4 years ago

Hallo, habe nun einen Clon Hm-10 auf die Version 609 geflasht. Ich bräuchte (bin kein Programmierer) eine kleine Anleitung wie ich den HM-10 in den Such Modus bringe das er Beacons anzeigt. Das initialisieren scheint geklappt zu haben:

17:33:08 CMD: sensor52 1
17:33:08 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":hm17cmd:1}
17:33:16 CMD: Sensor52 2
17:33:16 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":hm17cmd:2}

Danke!

funnyfrish commented 4 years ago

Wie hast du die hm10 geflasht? Woher die firmware? Bei mir will es irgendwie nicht funktionieren.

Jason2866 notifications@github.com schrieb am Mi., 29. Jan. 2020, 17:39:

Hallo, habe nun einen Clon Hm-10 auf die Version 609 geflasht. Ich bräuchte (bin kein Programmierer) eine kleine Anleitung wie ich den HM-10 in den Such Modus bringe das er Beacons anzeigt. Das initialisieren scheint geklappt zu haben:

17:33:08 CMD: sensor52 1

17:33:08 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":hm17cmd:1}

17:33:16 CMD: Sensor52 2

17:33:16 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":hm17cmd:2}

Danke!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gemu2015/Sonoff-Tasmota/issues/16?email_source=notifications&email_token=AAXWP64VFELOWUPKSZHDYFDRAGWKZA5CNFSM4J7NGRJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKH4COY#issuecomment-579846459, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXWP62QYZLCPCZ3VAAW3ZTRAGWKZANCNFSM4J7NGRJQ .

lacrimosa2k2 commented 4 years ago

Hallo, habe nun einen Clon Hm-10 auf die Version 609 geflasht. Ich bräuchte (bin kein Programmierer) eine kleine Anleitung wie ich den HM-10 in den Such Modus bringe das er Beacons anzeigt. Das initialisieren scheint geklappt zu haben:

17:33:08 CMD: sensor52 1
17:33:08 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":hm17cmd:1}
17:33:16 CMD: Sensor52 2
17:33:16 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":hm17cmd:2}

Danke!

was sagt den die debug ausgabe? (muss im script aktiviert werden vor dem kompilieren)

Jason2866 commented 4 years ago

@funnyfrish https://github.com/Jason2866/CCLoader

gemu2015 commented 4 years ago

@Jason2866

define IBEACON_DEBUG

und dann sensor52 d1 schaltet den debug mode ein. In der Konsole sieht man dann welche Befehle gesendet werden und welche Geräte gefunden werden

Jason2866 commented 4 years ago

Danke :-) Der HM-10 (clone) funktioniert auch mit der neuesten firmware v.707

16:17:26 CMD: sensor52 1
16:17:26 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":hm17cmd:1}
16:17:35 CMD: Sensor52 2
16:17:35 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":hm17cmd:2}
16:17:42 CMD: sensor52 d1
16:17:42 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":debug:1}
16:17:43 hm17cmd 3
16:17:44 DISIS OK
16:17:45 DISC: OK
16:17:45 >>00000000:00000000000000000000000000000000:0000000000:DB2592AEA2A3:-086
16:17:45 DISC: OK
16:17:45 >>00000000:00000000000000000000000000000000:0000000000:C54A74D1D3E5:-048
16:17:46 DISC: OK
16:17:46 >>00000000:00000000000000000000000000000000:0000000000:A4C1384284FC:-044
16:17:47 DISCE OK
16:17:54 hm17cmd 3
16:17:54 DISIS OK
16:17:55 DISC: OK
16:17:55 >>00000000:00000000000000000000000000000000:0000000000:C54A74D1D3E5:-050
16:17:56 DISC: OK
16:17:56 >>00000000:00000000000000000000000000000000:0000000000:DB2592AEA2A3:-086
16:17:57 DISCE OK
16:18:04 hm17cmd 3
16:18:04 DISIS OK
16:18:04 DISC: OK
16:18:04 >>00000000:00000000000000000000000000000000:0000000000:DB2592AEA2A3:-086
16:18:05 DISC: OK
16:18:05 >>00000000:00000000000000000000000000000000:0000000000:C54A74D1D3E5:-049
16:18:06 DISC: OK
16:18:06 >>00000000:00000000000000000000000000000000:0000000000:A4C1384284FC:-043
16:18:07 DISCE OK
16:18:13 hm17cmd 3
16:18:14 DISIS OK
16:18:14 DISC: OK
16:18:14 >>00000000:00000000000000000000000000000000:0000000000:C54A74D1D3E5:-049
16:18:16 DISC: OK
16:18:16 >>00000000:00000000000000000000000000000000:0000000000:A4C1384284FC:-044
16:18:17 DISCE OK
16:18:24 hm17cmd 3
16:18:24 DISIS OK
16:18:24 DISC: OK
16:18:24 >>00000000:00000000000000000000000000000000:0000000000:FFFFC0209126:-035
16:18:24 MQT: tele/sonoff-6111ED/SENSOR = {"Time":"2020-01-30T16:18:24","IBEACON_FFFFC0209126":{"RSSI":-35}}
16:18:25 DISC: OK
16:18:25 >>00000000:00000000000000000000000000000000:0000000000:A4C1384284FC:-043
16:18:25 DISC: OK
16:18:25 >>00000000:00000000000000000000000000000000:0000000000:C54A74D1D3E5:-050
16:18:26 DISC: OK
16:18:26 >>00000000:00000000000000000000000000000000:0000000000:DB2592AEA2A3:-086
16:18:27 DISCE OK
16:18:34 hm17cmd 3
16:18:34 DISIS OK
16:18:35 DISC: OK
16:18:35 >>00000000:00000000000000000000000000000000:0000000000:C54A74D1D3E5:-049
16:18:35 DISC: OK
16:18:35 >>00000000:00000000000000000000000000000000:0000000000:A4C1384284FC:-043
16:18:35 DISC: OK
16:18:35 >>00000000:00000000000000000000000000000000:0000000000:DB2592AEA2A3:-087
16:18:37 DISCE OK
16:18:43 hm17cmd 3
16:18:44 DISIS OK
16:18:44 DISC: OK
16:18:44 >>00000000:00000000000000000000000000000000:0000000000:C54A74D1D3E5:-049
16:18:45 DISC: OK
16:18:45 >>00000000:00000000000000000000000000000000:0000000000:DB2592AEA2A3:-086
16:18:45 DISC: OK
16:18:45 >>00000000:00000000000000000000000000000000:0000000000:A4C1384284FC:-044
16:18:47 DISC: OK
16:18:47 >>00000000:00000000000000000000000000000000:0000000000:FE01BA254A92:-088
16:18:47 DISCE OK
16:18:50 CMD: sensor52 d0
16:18:50 MQT: stat/sonoff-6111ED/RESULT = {"Sensor52":debug:0}
16:18:54 MQT: tele/sonoff-6111ED/SENSOR = {"Time":"2020-01-30T16:18:54","IBEACON_FFFFC0209126":{"RSSI":-36}}
16:19:06 MQT: tele/sonoff-6111ED/SENSOR = {"Time":"2020-01-30T16:19:06","IBEACON_FFFFC0209126":{"RSSI":-47}}
16:19:15 MQT: tele/sonoff-6111ED/SENSOR = {"Time":"2020-01-30T16:19:15","IBEACON_FFFFC0209126":{"RSSI":-50}}
funnyfrish commented 4 years ago

bei dem befehl Sensor52 1 und sensor52 2 stürzt mein wemos und auch dernodemcu ab. Ich bekomme dann folgende Fehlermeldung: :56:28 MQT: tele/tasmota/INFO1 = {"Module":"Sonoff Basic","Version":"8.1.0(tasmota)","FallbackTopic":"cmnd/DVES_532472_fb/","GroupTopic":"cmnd/tasmotas/"} 20:56:28 MQT: tele/tasmota/INFO2 = {"WebServerMode":"Admin","Hostname":"tasmota-1138","IPAddress":"192.168.1.187"} 20:56:28 MQT: tele/tasmota/INFO3 = {"RestartReason":{"Exception":28,"Reason":"Exception","EPC":["4020f4f5","00000000","00000000"],"EXCVADDR":"00000000","DEPC":"00000000","CallChain":["4021f25b","4021f434","4022cc84","4020f7ea","4027ca78","4027c70c","4027c820","4020f810","4027c820","402029f4","4021fe80","40247290","4023edb4","40216c41","401016d3","40101448","401016d3","4023ec10","40232f04","4021ffa4","4021fee4","402283a1","4022ddd9","40240884","4023ff21","4020fa40","4022fabc","40240884","40201378","40243da6","40201378"]}} 20:56:28 MQT: stat/tasmota/RESULT = {"POWER":"OFF"}

Hat jemand eine idee woran das liegen könnten? der HM10 ist über rx/tx verbunden und die nodemcu wird über die pinleiste eingespeist

lacrimosa2k2 commented 4 years ago

bei dem befehl Sensor52 1 und sensor52 2 stürzt mein wemos und auch dernodemcu ab. Ich bekomme dann folgende Fehlermeldung: :56:28 MQT: tele/tasmota/INFO1 = {"Module":"Sonoff Basic","Version":"8.1.0(tasmota)","FallbackTopic":"cmnd/DVES_532472_fb/","GroupTopic":"cmnd/tasmotas/"} 20:56:28 MQT: tele/tasmota/INFO2 = {"WebServerMode":"Admin","Hostname":"tasmota-1138","IPAddress":"192.168.1.187"} 20:56:28 MQT: tele/tasmota/INFO3 = {"RestartReason":{"Exception":28,"Reason":"Exception","EPC":["4020f4f5","00000000","00000000"],"EXCVADDR":"00000000","DEPC":"00000000","CallChain":["4021f25b","4021f434","4022cc84","4020f7ea","4027ca78","4027c70c","4027c820","4020f810","4027c820","402029f4","4021fe80","40247290","4023edb4","40216c41","401016d3","40101448","401016d3","4023ec10","40232f04","4021ffa4","4021fee4","402283a1","4022ddd9","40240884","4023ff21","4020fa40","4022fabc","40240884","40201378","40243da6","40201378"]}} 20:56:28 MQT: stat/tasmota/RESULT = {"POWER":"OFF"}

Hat jemand eine idee woran das liegen könnten? der HM10 ist über rx/tx verbunden und die nodemcu wird über die pinleiste eingespeist

kannst du den hm über serial sauber ansprechen (usb-ttl am pc) und die version abfragen?

funnyfrish commented 4 years ago

ja das funktioniert. ist eine original HM10. Habs geflasht. Version ist HMSoft V707

Aber da stürzt Tasmota ab und macht dann ein neustart. Wieso schmiert Tasmota ab wenn ich sensor52 befehle auf der weboberflöche in die console eingebe?. Habs mit wemos und nodemcu getestet.

lacrimosa2k2 commented 4 years ago

ja das funktioniert. ist eine original HM10. Habs geflasht. Version ist HMSoft V707

Aber da stürzt Tasmota ab und macht dann ein neustart. Wieso schmiert Tasmota ab wenn ich sensor52 befehle auf der weboberflöche in die console eingebe?. Habs mit wemos und nodemcu getestet.

was sagt der hm den wenn du ihn per serial manuel in den master mode schubst mit AT+ROLE1 und AT+IMME1 da müsste er ok sagen

funnyfrish commented 4 years ago

bei AT+ROLE1 ->OK+Set:1 AT+IMME1 ->OK+Set:1

Wenn Ich Sensor 52 2 ausführe dann schmiert mein ESP ab und es erscheint folgende Meldung:

 {"RestartReason":{"Exception":28,"Reason":"Exception","EPC":["4020f4f5","00000000","00000000"],"EXCVADDR":"00000000","DEPC":"00000000","CallChain":["4021f25b","4021f434","4022cc84","4020f7ea","4027ca78","4027c70c","4027c820","4020f810","4027c820","402029f4","4021fe80","40247290","4023edb4","40216c41","401016d3","40101448","401016d3","4023ec10","40232f04","4021ffa4","4021fee4","402283a1","4022ddd9","40240884","4023ff21","4020fa40","4022fabc","40240884","40201378","40243da6","40201378"]}}
20:56:28 MQT: stat/tasmota/RESULT = {"POWER":"OFF"}
lacrimosa2k2 commented 4 years ago

den exp code kann ich dir nicht entschlüsseln. rx und tx in der config eingetragen? auch mal vertauscht probiert? debug modus eingeschaltet, wenn er startet müsstest du dann die befehle sehen die gesendet/empfangen werden wen du role und imme einmal gesendet hast musst du es im tasmoate oder sonstwo nicht nochmal machen mit sensor521 und 2, der hm merkt sich diese einstellung

serial log muss deaktiviert werden