lagunacomputer / homebridge-MotionSensor

HomeBridge HomeKit Plugin for arduino based PIR motion sensors
23 stars 14 forks source link

homebridge 0.4.46 #10

Open sorriso93 opened 5 years ago

sorriso93 commented 5 years ago

Hello anyone having problem with homebridge 0.4.46? I didn't change anything except homebridge and now the plugin doesn't get value change by the http page of the arduino....

sorriso93 commented 5 years ago

copy of the log

[3/16/2019, 1:01:32 AM] [PIR-TCAM] Requesting motion on "http://192.168.0.15", method GET, timeout 3000 [3/16/2019, 1:01:32 AM] [PIR-TCUC] HTTP bad response (http://192.168.0.16): read ECONNRESET [3/16/2019, 1:01:32 AM] [PIR-BALC] Requesting motion on "http://192.168.0.17", method GET, timeout 3000 [3/16/2019, 1:01:35 AM] [PIR-TCUC] Requesting motion on "http://192.168.0.16", method GET, timeout 3000 [3/16/2019, 1:01:35 AM] [PIR-TCAM] Avoid updateState as previous response does not arrived yet [3/16/2019, 1:01:35 AM] [PIR-BALC] Avoid updateState as previous response does not arrived yet [3/16/2019, 1:01:35 AM] [PIR-TCUC] HTTP bad response (http://192.168.0.16): read ECONNRESET [3/16/2019, 1:01:35 AM] [PIR-TCAM] HTTP bad response (http://192.168.0.15): ETIMEDOUT [3/16/2019, 1:01:35 AM] [PIR-BALC] HTTP bad response (http://192.168.0.17): ETIMEDOUT [3/16/2019, 1:01:37 AM] [PIR-TCUC] Requesting motion on "http://192.168.0.16", method GET, timeout 3000 [3/16/2019, 1:01:37 AM] [PIR-TCAM] Requesting motion on "http://192.168.0.15", method GET, timeout 3000 [3/16/2019, 1:01:37 AM] [PIR-BALC] Requesting motion on "http://192.168.0.17", method GET, timeout 3000 [3/16/2019, 1:01:37 AM] [PIR-TCUC] HTTP bad response (http://192.168.0.16): read ECONNRESET [3/16/2019, 1:01:40 AM] [PIR-TCUC] Requesting motion on "http://192.168.0.16", method GET, timeout 3000 [3/16/2019, 1:01:40 AM] [PIR-TCUC] HTTP bad response (http://192.168.0.16): read ECONNRESET [3/16/2019, 1:01:40 AM] [PIR-TCAM] Avoid updateState as previous response does not arrived yet [3/16/2019, 1:01:40 AM] [PIR-BALC] Avoid updateState as previous response does not arrived yet [3/16/2019, 1:01:40 AM] [PIR-TCAM] HTTP bad response (http://192.168.0.15): ETIMEDOUT [3/16/2019, 1:01:40 AM] [PIR-BALC] HTTP bad response (http://192.168.0.17): ETIMEDOUT [3/16/2019, 1:01:42 AM] [PIR-TCUC] Requesting motion on "http://192.168.0.16", method GET, timeout 3000 [3/16/2019, 1:01:42 AM] [PIR-TCAM] Requesting motion on "http://192.168.0.15", method GET, timeout 3000 [3/16/2019, 1:01:42 AM] [PIR-BALC] Requesting motion on "http://192.168.0.17", method GET, timeout 3000 [3/16/2019, 1:01:42 AM] [PIR-TCUC] HTTP bad response (http://192.168.0.16): read ECONNRESET [3/16/2019, 1:01:45 AM] [PIR-TCUC] Requesting motion on "http://192.168.0.16", method GET, timeout 3000 [3/16/2019, 1:01:45 AM] [PIR-TCUC] HTTP bad response (http://192.168.0.16): read ECONNRESET [3/16/2019, 1:01:45 AM] [PIR-TCAM] Avoid updateState as previous response does not arrived yet [3/16/2019, 1:01:45 AM] [PIR-BALC] Avoid updateState as previous response does not arrived yet

if I go to page http://192.168.0.16 I get correct response... {"Value":0} or {"Value":1} if the sensor detect movements...