Yurik72
commented
3 years ago Lets's try to update wolfssl , with latest version from archive, than let me know
Closed mgx0 closed 3 years ago
Yurik72
commented
3 years ago Lets's try to update wolfssl , with latest version from archive, than let me know
mgx0
commented
3 years ago you mean zip archive from ESPHap library? there are two zip files or do you mean download newest from wolfssl github?
with wolfssl from wolfSSL_3_13_0.rar compiles and there is an issue above
with wolfssl from wolfSSL.rar there is a compilation error. This is afaik due to the patch that you have written in instructions
#include <esp_system.h>
^
compilation terminated.
Compiling .pio/build/nodemcuv2/libb0c/ESPHap/accessories.c.o
Compiling .pio/build/nodemcuv2/libb0c/ESPHap/arduino_homekit_server.cpp.o
Compiling .pio/build/nodemcuv2/libb0c/ESPHap/bench.c.o
*** [.pio/build/nodemcuv2/libb0c/ESPHap/aa.c.o] Error 1
In file included from lib/wolfSSL/wolfssl/wolfcrypt/settings.h:213:0,
from lib/wolfSSL/wolfssl/wolfcrypt/types.h:29,
from lib/wolfSSL/wolfssl/wolfcrypt/hash.h:29,
from lib/ESPHap/arduino_homekit_server.cpp:19:
lib/wolfSSL/user_settings.h:38:24: fatal error: esp_system.h: No such file or directoryYes zip archive
Sent from my iPhone
On 24 Mar 2021, at 11:19, mgx0 @.***> wrote:
you mean zip archive from ESPHap library? there are two zip files or do you mean download newest from wolfssl github?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Yurik72
commented
3 years ago mgx0
commented
3 years ago nope, still doesn't pair, connection is closed as soon I confirm the code
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 7
cnt
connected with S2, channel 11
dhcp client start...
...ip:10.0.0.235,mask:255.255.255.0,gw:10.0.0.1
.
IP address:
10.0.0.235
Free heap: 34144
init_hap_storage>>> HomeKit: init_storage_ex size 0x1c1
>>> Home Integration: hap_services added chararacteristic 0: 23
>>> Home Integration: hap_services added chararacteristic 1: 25
>>> Home Integration: homekit_is_paired 0
>>> HomeKit: Update the CPU to run at 160MHz
>>> HomeKit: Free heap: 32376
>>> server_new: WiFiServer begin at port: 5556
>>> HomeKit: Starting server
>>> HomeKit: storage init 0
>>> HomeKit: Using existing accessory ID: 11:2A:28:A6:CE:A5
>>> HomeKit: find pairings
>>> HomeKit: Preinit pairing context
>>> crypto_srp_new: crypto_srp_new
>>> crypto_srp_new: Initializing SRP
>>> arduino_homekit_preinit: Free heap: 27744
>>> HomeKit: Using user-specified password: 111-11-111
>>> HomeKit: Free heap: 26032
>>> HomeKit: Calculating public key len=384
pm open,type:2 0
>>> HomeKit: Calculating public key result 0
>>> HomeKit: arduino_homekit_preinit success
>>> HomeKit: Configuring mDNS
>>> HomeKit: Wifi Sleep type:2
sleep disable
>>> HomeKit: Set Wifi Sleep type :0
>>> HomeKit: MDNS.begin: SHT-112A, IP: 10.0.0.235
>>> homekit_mdns_init: Accessory Setup ID = YK72
>>> HomeKit: Init server over
>>> HomeKit: WiFiServer receives a new client (current 0, max 8)
>>> HomeKit: Got new client connection: local 10.0.0.235:5556, remote 10.0.0.213:56222
>>> HomeKit: [Client 1073700148] Got client content from the cache 0
>>> HomeKit: [Client 1073700148] new client accepted
>>> homekit_client_process: [Client 1073700148] Reading 126 bytes
>>> homekit_server_on_message_complete: http_parser message_complete
>>> homekit_server_on_pair_setup: Pair Setup
>>> homekit_server_on_pair_setup: Free heap: 23776
>>> tlv_debug: Got following TLV values:
>>> tlv_debug: Type 0 value (1 bytes): \x00
>>> tlv_debug: Type 6 value (1 bytes): \x01
>>> HomeKit: [Client 1073700148] Pair Setup Step 1/3
>>> homekit_server_on_pair_setup: Free heap: 23704
>>> send_tlv_response: [Client 1073700148] Sending TLV response
>>> tlv_debug: Got following TLV values:
>>> tlv_debug: Type 3 value (384 bytes): x\xF3\xB6\x1FPT6\xFA␡$\x89\xD3\x91\x95k\xCF\xED\xD3^N\x09` \xBD\x10\xB4\x0As\xAA|\xBB2r\xFD\x02\xCEtC\x9AK\x83\xB0\xCF\xE1\x91_\xB1\x06u_\xC7H\x0F\xFDo\x93R\x112\x01\x81`\xA8V\x0C\x8A_Y\x02v\x97V\xDB\x194o\xA8\xF0\xF3\x08\xB0\\\x9BV\xC0\xC2}\xE0\x8F\x1D\xE6\x84\xBB\xAF\xAB3e#\xDC\x8D&\xC4i<\xD1\x94|\xF8Z\xF62;\xE7`+\xD6\x1F\x01\xF6/+\x9B\xEB[\xDA\xAA\xB1~\xDFD(9\x01\xB6J\xA3\xB6m5A\xC1(\xD7\xE5\xEE\xF9\xBAc\xF2\x1D+\xFF\xD6\x98\xC5\xFE\x8A\xFD\xF5\x05\xB4\xDB[a\x0B\xD5\x86Z]\xD9\x9B\x10\xEB;\x88\x9FT\x95p\xC9\x92\x142\xD1\x85\xF1\xBF\x1BM'4\\e\xDEeJ\x01\x04%\xAC(\x16\x1F\xBC\xC00{\xAE\x00\x8C\xB8\x8B\x95\xC9\x17\x8A\x04Ykx\xEC(7\xC8\xB4Rz\xA8\xAE\xAE\xEA\xB8\xA7\xA7N\xB6&\xAA^[\xA3\xC6?\x17\xEAc_,\xA83\x0C\xC1\x95^q\xEB\xA6\x88\x0E\x8E'~\xE1\x8F\x9B\xFB~cx*#&\xF2\xDF\xD5tp\x05\xB9G\xBBj\xA3qq\xDB\xDA\x13\xFF\xAD\x06\x875\xD0\xD7P\xAB@o\x1F\x16M\xB2\x087\xDF\x90-\x1F}\x01\xF7\xB0\xEC\xEB\xC6lq\xA7\\\xA7=Fk\x0C\x09\x9Bs\x96\x93N\xA3\x09\xBB\xAD\xF8b\x95s\xD5\x18\xD80\\\xCE\xE1\xA5-}\xF6\xD5u\xA76\xEEmq=\xA8\xB7\x08&\xAA\xB4[\x037\xE0\x08\xA8 .\x14j\x99\xC7:]~@\xBA\x97R]
>>> tlv_debug: Type 2 value (16 bytes): \xB0kz\xFE=y2ET\x94\x85-\x18\x9DO\xE0
>>> tlv_debug: Type 6 value (1 bytes): \x02
>>> client_send: [Client 1073700148] send data size=513, encrypted=false
>>> client_send: [Client 1073700148] Sending payload: HTTP/1.1 200 OK\x0D\x0AContent-Type: application/pairing+tlv8\x0D\x0AContent-Length: 409\x0D\x0AConnection: keep-alive\x0D\x0A\x0D\x0A\x03\xFFx\xF3\xB6\x1FPT6\xFA␡$\x89\xD3\x91\x95k\xCF\xED\xD3^N\x09` \xBD\x10\xB4\x0As\xAA|\xBB2r\xFD\x02\xCEtC\x9AK\x83\xB0\xCF\xE1\x91_\xB1\x06u_\xC7H\x0F\xFDo\x93R\x112\x01\x81`\xA8V\x0C\x8A_Y\x02v\x97V\xDB\x194o\xA8\xF0\xF3\x08\xB0\\\x9BV\xC0\xC2}\xE0\x8F\x1D\xE6\x84\xBB\xAF\xAB3e#\xDC\x8D&\xC4i<\xD1\x94|\xF8Z\xF62;\xE7`+\xD6\x1F\x01\xF6/+\x9B\xEB[\xDA\xAA\xB1~\xDFD(9\x01\xB6J\xA3\xB6m5A\xC1(\xD7\xE5\xEE\xF9\xBAc\xF2\x1D+\xFF\xD6\x98\xC5\xFE\x8A\xFD\xF5\x05\xB4\xDB[a\x0B\xD5\x86Z]\xD9\x9B\x10\xEB;\x88\x9FT\x95p\xC9\x92\x142\xD1\x85\xF1\xBF\x1BM'4\\e\xDEeJ\x01\x04%\xAC(\x16\x1F\xBC\xC00{\xAE\x00\x8C\xB8\x8B\x95\xC9\x17\x8A\x04Ykx\xEC(7\xC8\xB4Rz\xA8\xAE\xAE\xEA\xB8\xA7\xA7N\xB6&\xAA^[\xA3\xC6?\x17\xEAc_,\xA83\x0C\xC1\x95^q\x03\x81\xEB\xA6\x88\x0E\x8E'~\xE1\x8F\x9B\xFB~cx*#&\xF2\xDF\xD5tp\x05\xB9G\xBBj\xA3qq\xDB\xDA\x13\xFF\xAD\x06\x875\xD0\xD7P\xAB@o\x1F\x16M\xB2\x087\xDF\x90-\x1F}\x01\xF7\xB0\xEC\xEB\xC6lq\xA7\\\xA7=Fk\x0C\x09\x9Bs\x96\x93N\xA3\x09\xBB\xAD\xF8b\x95s\xD5\x18\xD80\\\xCE\xE1\xA5-}\xF6\xD5u\xA76\xEEmq=\xA8\xB7\x08&\xAA\xB4[\x037\xE0\x08\xA8 .\x14j\x99\xC7:]~@\xBA\x97R]\x02\x10\xB0kz\xFE=y2ET\x94\x85-\x18\x9DO\xE0\x06\x01\x02
>>> homekit_server_on_pair_setup: [Client 1073700148] Server on pair setup end
>>> homekit_client_process: [Client 1073700148] Reading 536 bytes
>>> homekit_client_process: [Client 1073700148] Reading 43 bytes
>>> HomeKit: [Client 1073700148] Connection: close received, client will be disconnected
>>> HomeKit: [Client 1073700148] Closing client connection
>>> homekit_server_close_client: [Client 1073700148] The sockect is stoped
>>> HomeKit: Free saved_preinit_pairing_context
>>> HomeKit: [Client 0] Clear the pairing context
>>> HomeKit: [Client 0] client content free
>>> HomeKit: Preinit pairing context
>>> crypto_srp_new: crypto_srp_new
>>> crypto_srp_new: Initializing SRP
>>> arduino_homekit_preinit: Free heap: 25400
>>> HomeKit: Using user-specified password: 111-11-111
>>> HomeKit: Free heap: 23688
>>> HomeKit: Calculating public key len=384
>>> HomeKit: Calculating public key result 0
>>> HomeKit: arduino_homekit_preinit successYes I see a log will try to investigate, this is first time I’m met
HomeKit: [Client 1073700148] Connection: close received, client will be disconnected
Apple sends response with Connection:Close header. However it should continue to asking available accessories….
From: mgx0 @.> Sent: Wednesday, March 24, 2021 2:33 PM To: Yurik72/ESPHap @.> Cc: Yurik72 @.>; Comment @.> Subject: Re: [Yurik72/ESPHap] Cannot pair with esp8266 (#83)
nope, still doesn't pair, connection is closed as soon I confirm the code
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 7
cnt
connected with S2, channel 11
dhcp client start...
...ip:10.0.0.235,mask:255.255.255.0,gw:10.0.0.1
.
IP address:
10.0.0.235
Free heap: 34144
init_hap_storage>>> HomeKit: init_storage_ex size 0x1c1
Home Integration: hap_services added chararacteristic 0: 23
Home Integration: hap_services added chararacteristic 1: 25
Home Integration: homekit_is_paired 0
HomeKit: Update the CPU to run at 160MHz
HomeKit: Free heap: 32376
server_new: WiFiServer begin at port: 5556
HomeKit: Starting server
HomeKit: storage init 0
HomeKit: Using existing accessory ID: 11:2A:28:A6:CE:A5
HomeKit: find pairings
HomeKit: Preinit pairing context
crypto_srp_new: crypto_srp_new
crypto_srp_new: Initializing SRP
arduino_homekit_preinit: Free heap: 27744
HomeKit: Using user-specified password: 111-11-111
HomeKit: Free heap: 26032
HomeKit: Calculating public key len=384
pm open,type:2 0
HomeKit: Calculating public key result 0
HomeKit: arduino_homekit_preinit success
HomeKit: Configuring mDNS
HomeKit: Wifi Sleep type:2
sleep disable
HomeKit: Set Wifi Sleep type :0
HomeKit: MDNS.begin: SHT-112A, IP: 10.0.0.235
homekit_mdns_init: Accessory Setup ID = YK72
HomeKit: Init server over
HomeKit: WiFiServer receives a new client (current 0, max 8)
HomeKit: Got new client connection: local 10.0.0.235:5556, remote 10.0.0.213:56222
HomeKit: [Client 1073700148] Got client content from the cache 0
HomeKit: [Client 1073700148] new client accepted
homekit_client_process: [Client 1073700148] Reading 126 bytes
homekit_server_on_message_complete: http_parser message_complete
homekit_server_on_pair_setup: Pair Setup
homekit_server_on_pair_setup: Free heap: 23776
tlv_debug: Got following TLV values:
tlv_debug: Type 0 value (1 bytes): \x00
tlv_debug: Type 6 value (1 bytes): \x01
HomeKit: [Client 1073700148] Pair Setup Step 1/3
homekit_server_on_pair_setup: Free heap: 23704
send_tlv_response: [Client 1073700148] Sending TLV response
tlv_debug: Got following TLV values:
tlv_debug: Type 3 value (384 bytes): x\xF3\xB6\x1FPT6\xFA␡$\x89\xD3\x91\x95k\xCF\xED\xD3^N\x09` @.***\x1F\x16M\xB2\x087\xDF\x90-\x1F}\x01\xF7\xB0\xEC\xEB\xC6lq\xA7\\xA7=Fk\x0C\x09\x9Bs\x96\x93N\xA3\x09\xBB\xAD\xF8b\x95s\xD5\x18\xD80\\xCE\xE1\xA5-}\xF6\xD5u\xA76\xEEmq=\xA8\xB7\x08&\xAA\xB4[\x037\xE0\x08\xA8 .\x14j\x99\xC7:]~@\xBA\x97R]
tlv_debug: Type 2 value (16 bytes): \xB0kz\xFE=y2ET\x94\x85-\x18\x9DO\xE0
tlv_debug: Type 6 value (1 bytes): \x02
client_send: [Client 1073700148] send data size=513, encrypted=false
client_send: [Client 1073700148] Sending payload: HTTP/1.1 200 OK\x0D\x0AContent-Type: application/pairing+tlv8\x0D\x0AContent-Length: 409\x0D\x0AConnection: keep-alive\x0D\x0A\x0D\x0A\x03\xFFx\xF3\xB6\x1FPT6\xFA␡$\x89\xD3\x91\x95k\xCF\xED\xD3^N\x09` @.***\x1F\x16M\xB2\x087\xDF\x90-\x1F}\x01\xF7\xB0\xEC\xEB\xC6lq\xA7\\xA7=Fk\x0C\x09\x9Bs\x96\x93N\xA3\x09\xBB\xAD\xF8b\x95s\xD5\x18\xD80\\xCE\xE1\xA5-}\xF6\xD5u\xA76\xEEmq=\xA8\xB7\x08&\xAA\xB4[\x037\xE0\x08\xA8 .\x14j\x99\xC7:]~@\xBA\x97R]\x02\x10\xB0kz\xFE=y2ET\x94\x85-\x18\x9DO\xE0\x06\x01\x02
homekit_server_on_pair_setup: [Client 1073700148] Server on pair setup end
homekit_client_process: [Client 1073700148] Reading 536 bytes
homekit_client_process: [Client 1073700148] Reading 43 bytes
HomeKit: [Client 1073700148] Connection: close received, client will be disconnected
HomeKit: [Client 1073700148] Closing client connection
homekit_server_close_client: [Client 1073700148] The sockect is stoped
HomeKit: Free saved_preinit_pairing_context
HomeKit: [Client 0] Clear the pairing context
HomeKit: [Client 0] client content free
HomeKit: Preinit pairing context
crypto_srp_new: crypto_srp_new
crypto_srp_new: Initializing SRP
arduino_homekit_preinit: Free heap: 25400
HomeKit: Using user-specified password: 111-11-111
HomeKit: Free heap: 23688
HomeKit: Calculating public key len=384
HomeKit: Calculating public key result 0
HomeKit: arduino_homekit_preinit success
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Yurik72/ESPHap/issues/83#issuecomment-805783201 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDREXLA7YRROQRL2OJZ7TDTFHLXVANCNFSM4ZWX5CNQ . https://github.com/notifications/beacon/AKDREXP6N7MPNODNNJLUXDLTFHLXVA5CNFSM4ZWX5CN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGADUNII.gif
BbIKTOP
commented
3 years ago Just wait a bit more, phone will try to connect again later. Sometimes it connects on the first attempt, sometimes on the second or third. Also, please make sure you have esp set to frequency 160 and have updated wolfssl
Yurik72
commented
3 years ago Frequency is set 160 by library.
Maybe yes try wait for the second attempts. Which IOS you are using
From: Viktr @.> Sent: Wednesday, March 24, 2021 3:43 PM To: Yurik72/ESPHap @.> Cc: Yurik72 @.>; Comment @.> Subject: Re: [Yurik72/ESPHap] Cannot pair with esp8266 (#83)
Just wait a bit more, phone will try to connect again later. Sometimes it connects on the first attempt, sometimes on the second or third. Also, please make sure you have esp set to frequency 160 and have updated wolfssl
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Yurik72/ESPHap/issues/83#issuecomment-805832140 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDREXOTKSYCGQLQ32FKCLLTFHT55ANCNFSM4ZWX5CNQ . https://github.com/notifications/beacon/AKDREXML2K2PD76QAFIUXEDTFHT55A5CNFSM4ZWX5CN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGAEALTA.gif
mgx0
commented
3 years ago 14.4.1 but it was like this on okder versions too. I'll keep trying
On 24 Mar 2021, at 14:46, Yurik72 @.***> wrote:
Frequency is set 160 by library.
Maybe yes try wait for the second attempts. Which IOS you are using
From: Viktr @.> Sent: Wednesday, March 24, 2021 3:43 PM To: Yurik72/ESPHap @.> Cc: Yurik72 @.>; Comment @.> Subject: Re: [Yurik72/ESPHap] Cannot pair with esp8266 (#83)
Just wait a bit more, phone will try to connect again later. Sometimes it connects on the first attempt, sometimes on the second or third. Also, please make sure you have esp set to frequency 160 and have updated wolfssl
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Yurik72/ESPHap/issues/83#issuecomment-805832140 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDREXOTKSYCGQLQ32FKCLLTFHT55ANCNFSM4ZWX5CNQ . https://github.com/notifications/beacon/AKDREXML2K2PD76QAFIUXEDTFHT55A5CNFSM4ZWX5CN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGAEALTA.gif
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Yurik72
commented
3 years ago Ok, suggestion from Victor.
Restart HomeApp on phone
From: mgx0 @.> Sent: Wednesday, March 24, 2021 3:48 PM To: Yurik72/ESPHap @.> Cc: Yurik72 @.>; Comment @.> Subject: Re: [Yurik72/ESPHap] Cannot pair with esp8266 (#83)
14.4.1 but it was like this on okder versions too. I'll keep trying
On 24 Mar 2021, at 14:46, Yurik72 @. <mailto:@.> > wrote:
Frequency is set 160 by library.
Maybe yes try wait for the second attempts. Which IOS you are using
From: Viktr @. <mailto:@.> > Sent: Wednesday, March 24, 2021 3:43 PM To: Yurik72/ESPHap @. <mailto:@.> > Cc: Yurik72 @. <mailto:@.> >; Comment @. <mailto:@.> > Subject: Re: [Yurik72/ESPHap] Cannot pair with esp8266 (#83)
Just wait a bit more, phone will try to connect again later. Sometimes it connects on the first attempt, sometimes on the second or third. Also, please make sure you have esp set to frequency 160 and have updated wolfssl
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Yurik72/ESPHap/issues/83#issuecomment-805832140 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDREXOTKSYCGQLQ32FKCLLTFHT55ANCNFSM4ZWX5CNQ . https://github.com/notifications/beacon/AKDREXML2K2PD76QAFIUXEDTFHT55A5CNFSM4ZWX5CN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGAEALTA.gif
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Yurik72/ESPHap/issues/83#issuecomment-805836362 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDREXO5JOEMXONZBVLWEOLTFHURRANCNFSM4ZWX5CNQ . https://github.com/notifications/beacon/AKDREXNPPSCGODAGHS4U7STTFHURRA5CNFSM4ZWX5CN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGAEBMSQ.gif
BbIKTOP
commented
3 years ago I have first connect always failed like that. Then, there's a second one, which is about 90% successful. Sometimes 3rd or 4th, on 1% of attempts, I have to relaunch home.app and then it works.
mgx0
commented
3 years ago and for ESP8266 I should use wolfSSL_3_13_0.rar which is included in the library, is that correct?
Yurik72
commented
3 years ago Yes wolfSSL_3_13_0.rar works for both ESP8266/ESP32
From: mgx0 @.> Sent: Wednesday, March 24, 2021 4:03 PM To: Yurik72/ESPHap @.> Cc: Yurik72 @.>; Comment @.> Subject: Re: [Yurik72/ESPHap] Cannot pair with esp8266 (#83)
and for ESP8266 I should use wolfSSL_3_13_0.rar which is included in the library, is that correct?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Yurik72/ESPHap/issues/83#issuecomment-805848182 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDREXI2XKD6UQOY67KCEHDTFHWKRANCNFSM4ZWX5CNQ . https://github.com/notifications/beacon/AKDREXNP3CXS6VGDEI5P233TFHWKRA5CNFSM4ZWX5CN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGAEEI5Q.gif
mgx0
commented
3 years ago good, perfect. awesome job man. And Viktor thank you too 😁 this is the future!
Yurik72
commented
3 years ago Closed, since is not library problem
alisadeghy
commented
2 years ago I'm encountering the same problem and I did whatever you've discussed about in this issue but it did not fixed. I should try like a million times to pair one time! Help! :(
Yurik72
commented
2 years ago Hi , first of all, please be 100% sure , that you are using latest version, then attach logs, Problem is solved 1 year ago, therefore I do not see any obstacles
Sent from my iPhone
On 5 Sep 2021, at 19:25, alisadeghy @.***> wrote:
I'm encountering the same problem and I did whatever you've discussed about in this issue but it did not fixed. I should try like a million times to pair one time! Help! :(
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
alisadeghy
commented
2 years ago I'm pretty much sure about the libraries. ESPHap: 1.1.0 ESP8266: 3.0.2
Log: ....... IP address: 192.168.1.100 Free heap: 35424 init_hap_storage>>> HomeKit: init_storage_ex size 0x1c1
Home Integration: hap_services added chararacteristic 0: 23 Home Integration: hap_services added chararacteristic 1: 25 Home Integration: homekit_is_paired 0 HomeKit: Update the CPU to run at 160MHz HomeKit: Free heap: 33680 HomeKit: Starting server HomeKit: storage init 0 HomeKit: Using existing accessory ID: E8:FF:B5:39:9A:E4 HomeKit: find pairings HomeKit: Preinit pairing context HomeKit: Using user-specified password: 111-11-111 HomeKit: Free heap: 27336 HomeKit: Calculating public key len=384 HomeKit: Calculating public key result 0 HomeKit: arduino_homekit_preinit success HomeKit: Configuring mDNS HomeKit: Wifi Sleep type:2 HomeKit: Set Wifi Sleep type :0 HomeKit: MDNS.begin: ES-E8FF, IP: 192.168.1.100 HomeKit: Init server over HomeKit: WiFiServer receives a new client (current 0, max 8) HomeKit: Got new client connection: local 192.168.1.100:5556, remote 192.168.1.101:53203 HomeKit: [Client 1073699100] Got client content from the cache 0 HomeKit: [Client 1073699100] new client accepted HomeKit: [Client 1073699100] Pair Setup Step 1/3 HomeKit: [Client 1073699100] Connection: close received, client will be disconnected HomeKit: [Client 1073699100] Closing client connection HomeKit: Free saved_preinit_pairing_context HomeKit: [Client 0] Clear the pairing context HomeKit: [Client 0] client content free HomeKit: Preinit pairing context HomeKit: Using user-specified password: 111-11-111 HomeKit: Free heap: 25552 HomeKit: Calculating public key len=384 HomeKit: Calculating public key result 0 HomeKit: arduino_homekit_preinit success HomeKit: WiFiServer receives a new client (current 0, max 8) HomeKit: Got new client connection: local 192.168.1.100:5556, remote 192.168.1.101:53204 HomeKit: [Client 1073700100] Got client content from the cache 0 HomeKit: [Client 1073700100] new client accepted HomeKit: [Client 1073700100] Pair Setup Step 1/3 HomeKit: [Client 1073700100] Connection: close received, client will be disconnected HomeKit: [Client 1073700100] Closing client connection HomeKit: Free saved_preinit_pairing_context HomeKit: [Client 0] Clear the pairing context HomeKit: [Client 0] client content free HomeKit: Preinit pairing context HomeKit: Using user-specified password: 111-11-111 HomeKit: Free heap: 25064
and over and over again
alisadeghy
commented
2 years ago I also updated the CPU to run at 160 MHz as well but no luck.
Yurik72
commented
2 years ago Hi you don’t, need to update CPU clock, it’s done automatically insight library, ok Could you please copy latest version 1.1 from the master, without updating from arduino, since latest version more then 6 month not any blame about pairing on esp8266, So delete library manually from your library folder and copy directly from the master
Sent from my iPhone
On 5 Sep 2021, at 21:09, alisadeghy @.***> wrote:
I also updated the CPU to run at 160 MHz as well but no luck.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
alisadeghy
commented
2 years ago Copied from master, but still the same log.
Yurik72
commented
2 years ago Ok , looks like not version issue Apple closes connection after first step, could you send me your sketch
Sent from my iPhone
On 5 Sep 2021, at 22:30, alisadeghy @.***> wrote:
Copied from master, but still the same log.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
alisadeghy
commented
2 years ago I use sketches from library example, didn't change anything except SSID and password.
`/* ESPHap example EspHapLed for ESP8266
This example for ESPHap shows how to control a LED with Apple Home app. It implements accessory type "light bulb".
This example code is part of the public domain */
const char* ssid = "***"; const char* password = "***";
const int identity_led=2; const int led_gpio = 4;
extern "C"{
}
homekit_service_t hapservice={0}; String pair_file_name="/pair.dat"; //esp8266::MDNSImplementation::MDNSResponder MDNS1;
LOCAL os_timer_t callbacktimer;
void setup() { disable_extra4k_at_link_time(); Serial.begin(115200); delay(10);
// We start by connecting to a WiFi network if (!SPIFFS.begin(true)) {
// Serial.print("SPIFFS Mount failed");
} if (!SPIFFS.begin()) {
Serial.print("SPIFFS Mount failed");
}Serial.println(ssid);WiFi.mode(WIFI_STA); WiFi.begin((char)ssid, (char)password);
WiFi.begin(ssid, password);while (WiFi.status() != WL_CONNECTED) {
delay(500);
Serial.print(".");
}
Serial.println("");// Serial.println("WiFi connected"); Serial.println("IP address: "); Serial.println(WiFi.localIP());
pinMode(led_gpio,OUTPUT); ///setup identity gpio // hap_set_identity_gpio(identity_led); //identity_led=2 will blink on identity
/// now will setup homekit device
//this is for custom storaage usage
// In given example we are using \pair.dat file in our spiffs system
//see implementation below
Serial.print("Free heap: ");
Serial.println(system_get_free_heap_size());
init_hap_storage();
set_callback_storage_change(storage_changed);
/// We will use for this example only one accessory (possible to use a several on the same esp)
//Our accessory type is light bulb, Apple interface will proper show that
hap_setbase_accessorytype(homekit_accessory_category_lightbulb);
/// init base properties
hap_initbase_accessory_service("ES","Yurik72","0","EspHapLed","1.0");//we will add only one light bulb service and keep pointer for nest using hapservice= hap_add_lightbulb_service("Led",led_callback,(void*)&led_gpio);
//and finally init HAP
hap_init_homekit_server();}
void loop() {
hap_homekit_loop(); //delay(2); return; }
void init_hap_storage(){ Serial.print("init_hap_storage");
File fsDAT=SPIFFS.open(pair_file_name, "r"); if(!fsDAT){ Serial.println("Failed to read pair.dat"); return; } int size=hap_get_storage_size_ex(); char* buf=new char[size]; memset(buf,0xff,size); int readed=fsDAT.readBytes(buf,size); // Serial.print("Readed bytes ->"); // Serial.println(readed); hap_init_storage_ex(buf,size); fsDAT.close(); delete []buf; }
void storage_changed(char * szstorage,int bufsize){
SPIFFS.remove(pair_file_name); File fsDAT=SPIFFS.open(pair_file_name, "w+"); if(!fsDAT){ Serial.println("Failed to open pair.dat"); return; } fsDAT.write((uint8_t*)szstorage, bufsize);
fsDAT.close(); } //can be used for any logic, it will automatically inform Apple about state changes void set_led(bool val){ Serial.println("set_led"); digitalWrite(led_gpio, val?HIGH:LOW); //we need notify apple about changes
if(hapservice){ Serial.println("notify hap"); //getting on/off characteristic homekit_characteristic_t * ch= homekit_service_characteristic_by_type(hapservice, HOMEKIT_CHARACTERISTIC_ON); if(ch){ Serial.println("found characteristic"); if(ch->value.bool_value!=val){ //wil notify only if different ch->value.bool_value=val; homekit_characteristic_notify(ch,ch->value); } } } }
void led_callback(homekit_characteristic_t ch, homekit_value_t value, void context) { Serial.println("led_callback"); set_led(ch->value.bool_value); }`
alisadeghy
commented
2 years ago One question, does this whole thing need internet connection to access anything from any server, like Apple or something?
BbIKTOP
commented
2 years ago One question, does this whole thing need internet connection to access anything from any server, like Apple or something?
Sorry for my intrusion, but yes, sure, as hap works thru the apple servers, internet connection is definitely required. Or, what do you think, how could your accessory update its state in your home.app then?
alisadeghy
commented
2 years ago I don't know, maybe in a local communication between accessory and Apple device! I'm not that much into these Home Kit BTW, so it might be the problem, cause I live in Iran and we are banned from so many things over the internet!
alisadeghy
commented
2 years ago To be clear I could pair a couple of times with exact same ESP8266 and internet connection and everything but suddenly this "Connection Close" thing started to show up!
Yurik72
commented
2 years ago You don’t need internet connection for pairing, everything runs locally and not any communication to ‘Apple’ server , it just phone and esp building handshake….
Sent from my iPhone
On 5 Sep 2021, at 22:59, Viktr @.***> wrote:
One question, does this whole thing need internet connection to access anything from any server, like Apple or something?
Sorry for my intrusion, but yes, sure, as hap works thru the apple servers, internet connection is definitely required. Or, what do you think, how could your accessory update its state in your home.app then?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
alisadeghy
commented
2 years ago Ok then it's not the issue 🤷🏻♂️
Yurik72
commented
2 years ago Pairing itself not requires any internet connection, as well as normal communication !!!l I think issue could be related to network environment , but exact answer we can find only sniffering (for instance using ware shark), communication broken exactly after 1 stage, means we need understand who is doing that, if device replying yes or not.. any other logical validation are one the second an third stages
Sent from my iPhone
On 5 Sep 2021, at 23:07, alisadeghy @.***> wrote:
To be clear I could pair a couple of times with exact same ESP8266 and internet connection and everything but suddenly this "Connection Close" thing started to show up!
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Yurik72
commented
2 years ago See previous answer , maybe other things are changed , port blocking .. etc…
Sent from my iPhone
On 5 Sep 2021, at 23:16, alisadeghy @.***> wrote:
issue
alisadeghy
commented
2 years ago I completely changed the network environment, made a hotspot via my laptop and connected ESP and phone to that, no luck. Same thing happened.
alisadeghy
commented
2 years ago Also started over on a fresh computer with fresh install of IDE and libraries, thought it might be a file corruption somewhere in other libraries or an interference, still doesn't work. I will get another ESP6288 and an ESP32, hopefully the problem will be solved. Thanks for the time and if any ring bells please let me know. 🙏🏻
alisadeghy
commented
2 years ago Alright, I tried 3 more ESP8266s and they work just fine, I don't know what happened to this board but it won't work with this library anymore, although it works with another Homekit library and every other sketch! Any tip to make it work? Like flashing with new firmware or something?
Hello,
where can do a change? I'm experiencing pairing problem on 8266, EspHapLed example
the line
Connection: close received, client will be disconnectedcomes when right after I press "Continue" after entering the pairing code. I have tried on NodeMCU clones, ESP-12E/FI'm currently using latest version of the library. is there any debug I can enable to provide more information?
thanks