Official Repo for the Everything Presence One sensor!

HTML 36.25% Ruby 1.42% SCSS 12.71% C++ 49.54% Python 0.07%

everything-presence-one's People

Contributors

Stargazers

Watchers

everything-presence-one's Issues

lux sensor - accuracy

Trying to understand what the lux sensor is telling me. Your documentation states "Illuminance is measured from the on-board light sensor in lux.".

Looking at https://en.wikipedia.org/wiki/Lux they give some examples of lux values:

I'm showing 0.9 lx in my front entrance, seems way brighter than a full moon at night.

Here is your example in the docs:

Were you sitting in the dark with that device?

My living room, shows 12.0 lx in a room full of windows, shades open, bright sunny spring day here. According to the Wiki, a 20 starts Public areas with dark surrounding. I'm not even close to that value.

Scratching my head on what to do with this. Seems like a multiplier is off/needed maybe? The values are so low I can't make decent automatons based on these values.

I'm using the provided 3D printed cases, openings are not blocked.

proper way to power from 5v headers

i havent been able to successfully power up the sensor using direct 5v.

I'm looking to do a fairly permanent installation where usb-c wont be convenient, so i'm hoping to use the headers instead. i switched the jumper based on my understanding from https://shop.everythingsmart.io/en-us/products/everything-presence-one-kit, but didn't find more specific details in https://everythingsmarthome.github.io/everything-presence-one/ to confirm that i was approaching it correctly.

i'm using a 5v, 1500 mA power supply with a barrel adapter to connect the dupont wires to the headers. i do see the led on the mmWave board come on briefly, but it doesn't see to boot fully. if i switch the jumper back and connect to usb-c power again, it boots fully without trouble.

is there something that i am unknowingly just doing wrong? how can i investigate further?

Issue updating via ESPHome

Issue: Updating via ESPHome running in HA fails with an error, 'ERROR Error sending data: [Errno 104] Connection reset by peer'

Hardware: Wifi 2.4 access point within 12 feet of P1 device, which is active and connected fine.

Symptoms: Requesting a device update via ESPHome in HA, the device compiles and assembles the bin file successfully and begins uploading, at which point it fails. See attached logs.

I'm going to try a beefier power supply for the P1 sensor in case this is relevant - any other reasons this could occur?
logs_update-all.txt

Monitor battery level when using external battery pack

Hello,

How can I monitor battery level when EPO is plugged to powerbank like supply ?

Couldn't update / setup the sensor on M1 Mac or Macbook 14 Pro with Mac OS 13 & Chrome

Hi,

Received the sensor today and couldn't get it to update on an M1 or a Macbook 14 Pro.
They both "connected" and i got the initial menu pop up - but the install failed on both. Was keen to get it working - so tried my son's windows laptop and that worked first time.

Just mention it here incase others see issues. Happy to troubleshoot further now I know it works.

thanks for the kit - looks superb. Excited to get it working now.

License for code?

First up great project. Thanks for the code. Would you mind sticking a License on the repo so I can credit and use similar license for my mashup of your code. I have one EP1 and a bunch of other with only mmWave module that I assembled based of your initial video. So I need to maintain a separate repo for it.
I've credited this repo, but having a License file makes it more transparent. In FOSS terms not having a license file makes the code 'unlicensed' and thus cannot be used elsewhere.

MIT/Apache2.0/GPL3.0 whatever suits your fancy, I'll just follow the same license model.

Light intensity bh1750 sensor fails to communicate

Hello!

Im having an issue with the bh1750 sensor. No data is being reported to Home Assistant and when looking at the logs, im getting the following error on boot.

[E][bh1750.sensor:121]: Communication with BH1750 failed!

This has happened with both 2023.3.1 and previous firmware versions.

PoE Ethernet Support

I've been messing around with esp32 boards lately and I came across the ESP32-POE-ISO, an ESP32 that can be powered by PoE. This has me wondering. Would it be possible to build a EP1 using this board? I like the concept of the EP1 but I hate adding more wifi devices to my network. Also if I'm going to run a cable to power the EP1 it may as well also handle data... What are the thoughts on being able to make a PoE EP1? I may take a stab at DIYing.

Firmware Update 2023.2.3 won't install

When trying to install the 2023.2.3 Firmware update, it says it's installing but when it 'finishes' it just offers to install the update again and shows the old version as installed. Watching the log in ESPHome, the OTA download starts after 2 or 3 minutes but never gets past about 10% before it seems to time out. What am I doing wrong? Thanks in advance!

naming of entries becomes very convoluted when there is more than 1 device

The naming of entities becomes very confusing when there is more than 1 EP1 device in HA.

Recommend using $name or ${name} in front of all switches and sensors. example below.

substitutions:
name: "living-room-ep1-sensor"
room: "living-room"
friendly_name: "Everything Presence One"
project_name: "Everything Smart Technologies.Everything Presence One"
project_version: "1.0.3"
temperature_offset: "-3"

esphome:
name: "${name}"
name_add_mac_suffix: False
project:
name: "${project_name}"
version: "${project_version}"

esp32:
board: esp32dev

logger:

api:

ota:
password:

wifi:
ssid:
password:

captive_portal:

improv_serial:

esp32_improv:
authorizer: none

dashboard_import:
package_import_url: github://everythingsmarthome/presence-one/everything-presence-one.yaml@main
import_full_config: false

light:

platform: status_led
name: "${name} ESP32 Status LED"
pin: GPIO32

i2c:
sda: 26
scl: 25
scan: true

sensor:

platform: shtcx
temperature:
name: "${room} Temperature"
filters:
offset: ${temperature_offset}
humidity:
name: "${room} Humidity"
address: 0x70
update_interval: 60s
platform: bh1750
name: "${room} Illuminance"
address: 0x23
update_interval: 30s

binary_sensor:

platform: gpio
name: ${room} mmWave
id: mmwave
device_class: occupancy
pin:
number: GPIO15
mode: INPUT_PULLDOWN
platform: gpio
pin:
number: 33
mode: INPUT_PULLDOWN
name: ${room} PIR
id: pir_motion_sensor
device_class: motion
filters:
- delayed_off: 10s
platform: template
name: ${room} Occupancy
id: occupancy
device_class: occupancy
filters:
- delayed_off: 15s
  lambda: |-
  if ( id(mmwave).state or id(pir_motion_sensor).state) {
  return true;
  }
  else if (id(mmwave).state == 0 and id(pir_motion_sensor).state == 0) {
  return false;
  }
  else {
  return id(occupancy).state;
  }
  uart:
  id: uart_bus
  tx_pin: GPIO13
  rx_pin: GPIO14
  baud_rate: 115200
  debug:
  direction: BOTH
  dummy_receiver: true
  after:
  delimiter: "\n"
  sequence:
- lambda: UARTDebug::log_string(direction, bytes);

switch:

platform: safe_mode
internal: false
name: $name Safe Mode
platform: template
name: "${name} mmWave Sensor"
id: "mmwave_sensor"
optimistic: true
restore_state: true
assumed_state: true
turn_on_action:
- uart.write: "sensorStart"
- delay: 1s
  turn_off_action:
- uart.write: "sensorStop"
- delay: 1s
platform: template
name: "${name} mmWave LED"
id: "mmwave_led"
optimistic: true
restore_state: true
assumed_state: true
turn_on_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: "setLedMode 1 0"
- delay: 1s
- uart.write: "saveConfig"
- delay: 3s
- switch.turn_on: mmwave_sensor
  turn_off_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: "setLedMode 1 1"
- delay: 1s
- uart.write: "saveConfig"
- delay: 3s
- switch.turn_on: mmwave_sensor
platform: template
name: "${name} uart_presence_output"
id: "uart_presence_output"
optimistic: true
restore_state: true
assumed_state: true
turn_on_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: "setUartOutput 1 1"
- delay: 1s
- uart.write: "saveConfig"
- delay: 3s
- switch.turn_on: mmwave_sensor
  turn_off_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: "setUartOutput 1 0"
- delay: 1s
- uart.write: "saveConfig"
- delay: 3s
- switch.turn_on: mmwave_sensor
platform: template
name: "${name} uart_target_output"
id: "uart_target_output"
optimistic: true
restore_state: true
assumed_state: false
turn_on_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: "setUartOutput 2 1 1 1"
- delay: 1s
- uart.write: "saveConfig"
- delay: 3s
- switch.turn_on: mmwave_sensor
  turn_off_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: "setUartOutput 2 0"
- delay: 1s
- uart.write: "saveConfig"
- delay: 3s
- switch.turn_on: mmwave_sensor

number:

platform: template
name: $name mmWave Distance
id: mmwave_distance
min_value: 0
max_value: 800
initial_value: 315
optimistic: true
step: 15
restore_value: true
unit_of_measurement: cm
mode: box
set_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: !lambda int cm = (int)ceil(x / 15.0);
  std::string cms = "detRangeCfg -1 0 " + to_string(cm);
  return std::vector(cms.begin(), cms.end());
- delay: 1s
- uart.write: "saveCfg 0x45670123 0xCDEF89AB 0x956128C6 0xDF54AC89"
- delay: 1s
- switch.turn_on: mmwave_sensor
platform: template
name: $name mmWave Off Latency
id: mmwave_latency
min_value: 0
max_value: 65000
initial_value: 12500
optimistic: true
step: 25
restore_value: true
unit_of_measurement: ms
mode: box
set_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: !lambda int ms = (int)ceil(x / 25.0);
  std::string mss = "outputLatency -1 0 " + to_string(ms);
  return std::vector(mss.begin(), mss.end());
- delay: 1s
- uart.write: "saveCfg 0x45670123 0xCDEF89AB 0x956128C6 0xDF54AC89"
- delay: 1s
- switch.turn_on: mmwave_sensor
platform: template
name: $name mmWave Sensitivity
id: mmwave_sensitivity
min_value: 0
max_value: 9
initial_value: 7
optimistic: true
step: 1
restore_value: true
set_action:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write:
  !lambda std::string mss = "setSensitivity " + to_string((int)x);
  return std::vector(mss.begin(), mss.end());
- delay: 1s
- uart.write: "saveConfig"
- delay: 1s
- switch.turn_on: mmwave_sensor

button:

platform: restart
name: Restart $name
platform: template
name: "${name} Factory Reset mmWave"
id: "factory_reset_mmwave"
on_press:
- switch.turn_off: mmwave_sensor
- delay: 1s
- uart.write: "resetCfg"
- delay: 3s
- switch.turn_on: mmwave_sensor

Firmware Upgrade - Linux

First time trying to use ESP Home with Linux. I think my issues is just lack of documentation on the Updating page.

Upon clicking the blue [CONNECT] button, I get a dialog box of serial ports, but none of them have anything listed as connected. An image of what to expect when everything is connected here would be helpful!

Best guess way to determine chip type and USB port connected too on Linux:

$ sudo dmesg | grep uart
 
[224037.060960] usbserial: USB Serial support registered for ch341-uart
[224037.060973] ch341 1-1:1.0: ch341-uart converter detected
[224037.061394] usb 1-1: ch341-uart converter now attached to ttyUSB0

$ lsusb | grep serial

Bus 001 Device 012: ID 1a86:7523 QinHeng Electronics CH340 serial converter

Upon selecting USB Serial (ttyUSB0) serial port and clicking [Connect] button I get a message:

Failed to execute 'open' on 'SerialPort': Failed to open serial port.

To troubleshoot this, check the permissions of the USB device:

$ ls -l /dev/ttyUSB0

crw-rw---- 1 root uucp 188, 0 Mar 10 13:51 /dev/ttyUSB0

Need to be a member of group uucp to read/write to this USB device.
Add yourself to this group, to add myself (rich) to this group:

$ sudo usermod -aG uucp rich

Need to logout and back in again for the new group membership to take effect
Confirm you are a member of the group now:

$ groups
 
sys network power uucp lp wheel rich

Now access the link via Chrome, click blue [CONNECT] button, select USB Serial (ttyUSB0) serial port and clicking [Connect] button and now it should be able to connect:

Success! drivers are included in the Linux kernel, I'm using kernel 6.1.12. Just permissions prevent you from connecting to the USB device.

Adding a 5v sensor?

I'm interested in adding a PMSA003 dust sensor to my Everything Presence One. I realize that I'll have to extend the config to support this (I'm a developer, and experienced with ESPHome, so no problem there), and I'll need a custom case (got a 3D printer, so also no problem).

All I need to drive the AQI sensor is 5 volts and a single IO. But the breakout header only has 3.3v (plus ground and the spare IOs).

I assume that the 5v headers at the bottom of the board are inputs (when the jumper selects v5 direct instead of USB). Without examining the schematic I'm not sure if that header also provides 5v out when powered by USB (as I intend to do).

Perhaps it would be safer for me to tap the 5v on the microwave header that I'm not using (there are two of them)?

Thanks in advance for advice for tapping 5v.

Could not update firmware: Failed to open serial port

Hi !

I got an EP1 (Everything Presence One) from Everything Smart Home (Hardware overview), and trying to update via the official tool, using ESP Web Tools, here, but it's not working.

How to reproduce

Go to the firmware installation page: https://everythingsmarthome.github.io/everything-presence-one/updating.html
Click connect
Chrome is displaying this dialog:
Whenever I chose the first or the second option, I got the same Javascript error, with no console logging: Failed to execute 'open' on 'SerialPort': Failed to open serial port.

I also tried on official ESP tools here:

==> With the same results.

Environnement

Windows 10 Entreprise 21H2
Chrome 111
Edge 110
The cable is passing data + power, verified by connecting an Android phone to my machine.

Additional informations
I think the COM3 line while selectiong serial ports was not there at first. Then, Windows installed some kind of driver when I plugged in the EP1, then the line appear.
When having this troubleshouting dialog, I installed CP2102 drivers, but it did not change, even after a reboot. I don't know what kind of chip it is, and I think it would be written in the EP1 doc if I needed to install a driver.

Thanks

EP1 keeps going offline / unavailable

Even after updating to the latest firmware (firmware: 2023.2.4) per #1, my EP1 keeps going offline. I have 2 of the sensors and both have the same issues of going offline. I've tried switching power adapters and issue still persists.

ESPHome yaml:

substitutions:
  name: everything-presence-one-de99b4
packages:
  Everything_Smart_Technologies.Everything_Presence_One: github://everythingsmarthome/presence-one/everything-presence-one.yaml
esphome:
  name: ${name}
  name_add_mac_suffix: false


wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

I'm seeing mDNS issues, WiFi authentication issues and connection rests and reboots in the logs - the WiFi credentials are valid so I'm unsure as to why it's having trouble connecting. Not sure how to fully remediate (FYI - I also have 2 HA instances currently running right now).

[D][sensor:127]: ' Temperature': Sending state 23.53969 °C with 1 decimals of accuracy
[D][sensor:127]: ' Humidity': Sending state 29.01123 % with 1 decimals of accuracy
[D][api.connection:918]: Home Assistant 2023.3.0 (::FFFF:192.168.1.99): Connected successfully
[D][api.connection:918]: ESPHome Logs 2023.2.4 (::FFFF:192.168.1.199): Connected successfully
[D][api:102]: Accepted ::FFFF:192.168.1.199
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.1lx
[D][sensor:127]: ' Illuminance': Sending state 5.09350 lx with 1 decimals of accuracy
[W][api.connection:081]: ESPHome Logs 2023.2.4 (::FFFF:192.168.1.199): Connection reset
[W][api.connection:083]: Home Assistant 2023.3.0 (::FFFF:192.168.1.199): Connection closed
[W][api.connection:081]: Home Assistant 2023.3.0 (::FFFF:192.168.1.99): Connection reset
[D][api:102]: Accepted ::FFFF:192.168.1.199
[D][api:102]: Accepted ::FFFF:192.168.1.99
[D][api.connection:918]: Home Assistant 2023.3.0 (::FFFF:192.168.1.99): Connected successfully
[D][api.connection:918]: Home Assistant 2023.3.0 (::FFFF:192.168.1.199): Connected successfully
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.4lx
[D][sensor:127]: ' Illuminance': Sending state 5.43307 lx with 1 decimals of accuracy
[D][esp-idf:000]: E (2433428) MDNS_Networking: Cannot allocate memory (line: 131, free heap: 528 bytes)

[D][esp-idf:000]: E (2433430) MDNS_Networking: Cannot allocate memory (line: 131, free heap: 640 bytes)

[D][esp-idf:000]: E (2433442) MDNS_Networking: Cannot allocate memory (line: 131, free heap: 644 bytes)

[D][esp-idf:000]: E (2433455) MDNS: Cannot allocate memory (line: 216, free heap: 676 bytes)

[D][esp-idf:000]: E (2433467) MDNS_Networking: Cannot allocate memory (line: 131, free heap: 680 bytes)

[D][api.connection:159]: Home Assistant 2023.3.0 (::FFFF:192.168.1.99) requested disconnected
[D][api:102]: Accepted ::FFFF:192.168.1.99
[D][api.connection:918]: Home Assistant 2023.3.0 (::FFFF:192.168.1.99): Connected successfully
[D][shtcx:100]: Got temperature=26.53°C humidity=24.01%
[D][sensor:127]: ' Temperature': Sending state 23.53168 °C with 1 decimals of accuracy
[D][sensor:127]: ' Humidity': Sending state 29.01276 % with 1 decimals of accuracy
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.7lx
[D][sensor:127]: ' Illuminance': Sending state 5.65945 lx with 1 decimals of accuracy
[D][api:102]: Accepted ::FFFF:192.168.1.199
[D][api.connection:918]: ESPHome Logs 2023.2.4 (::FFFF:192.168.1.199): Connected successfully
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.3lx
[D][sensor:127]: ' Illuminance': Sending state 5.31988 lx with 1 decimals of accuracy
[D][api:102]: Accepted ::FFFF:192.168.1.99
[D][shtcx:100]: Got temperature=26.52°C humidity=24.10%
[D][sensor:127]: ' Temperature': Sending state 23.52367 °C with 1 decimals of accuracy
[D][sensor:127]: ' Humidity': Sending state 29.09515 % with 1 decimals of accuracy
[W][api.connection:083]: Home Assistant 2023.3.0 (::FFFF:192.168.1.99): Connection closed
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.4lx
[D][sensor:127]: ' Illuminance': Sending state 5.43307 lx with 1 decimals of accuracy
[W][api.connection:071]: Home Assistant 2023.3.0 (::FFFF:192.168.1.99): Socket operation failed: SOCKET_WRITE_FAILED errno=104
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:85:48[redacted] reason='Beacon Timeout'
[W][wifi:125]: WiFi Connection lost... Reconnecting...
[W][wifi:585]: Restarting WiFi adapter...
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[D][esp32_improv.component:201]: Setting Improv to start
[W][api.connection:058]: Home Assistant 2023.3.0 (::FFFF:192.168.1.199): Network unavailable, disconnecting
[D][esp32_improv.component:076]: Service started!
[W][wifi_esp32:491]: Event: Disconnected ssid='Pretty Fly for a WiFi' reason='Probe Request Unsuccessful'
[W][wifi:549]: Error while connecting to network.
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.5lx
[D][sensor:127]: ' Illuminance': Sending state 5.54626 lx with 1 decimals of accuracy
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -70 dB
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -36 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (A6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (AE:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - 'HOME-E82B-2.4'[redacted] (10:33:BF:59:D9:AE) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (7C:9A:54:13:78:19) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (38:3F:B3:E7:D9:2E) [redacted]▂▄▆█
[D][wifi:450]: - 'Fios-B8H6M_EXT'[redacted] (50:D4:F7:18:36:7A) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (38:3F:B3:E7:D9:30) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (38:3F:B3:E7:D9:32) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (4A:4B:D4:76:F2:25) [redacted]▂▄▆█
[D][wifi:450]: - 'Fios-tyBQ9'[redacted] (04:A2:22:F9:B2:23) [redacted]▂▄▆█
[D][wifi:450]: - 'Restricted Airspace'[redacted] (14:22:3B:1F:14:0A) [redacted]▂▄▆█
[D][wifi:450]: - 'batteries_not_included'[redacted] (10:78:5B:48:6F:61) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:559]: WiFi network can not be found anymore.
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:559]: WiFi network can not be found anymore.
[W][wifi_esp32:491]: Event: Disconnected ssid='Pretty Fly for a WiFi' reason='Probe Request Unsuccessful'
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -69 dB
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -37 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (B6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (A6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (AE:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (2E:87:BA:74:23:EB) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (10:33:BF:59:D9:B3) [redacted]▂▄▆█
[D][wifi:450]: - 'HOME-E82B-2.4'[redacted] (10:33:BF:59:D9:AE) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (CC:32:E5:19:68:6A) [redacted]▂▄▆█
[D][wifi:450]: - 'Batcave'[redacted] (3C:BD:C5:AC:6C:69) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (38:3F:B3:E7:D9:30) [redacted]▂▄▆█
[D][wifi:450]: - 'Leonidas'[redacted] (38:8B:59:BC:9C:5C) [redacted]▂▄▆█
[D][wifi:450]: - 'Brooklyn's Castle'[redacted] (3C:BD:C5:82:AD:86) [redacted]▂▄▆█
[D][wifi:450]: - 'Verizon_RN4P9Z'[redacted] (3C:BD:C5:82:7A:71) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:549]: Error while connecting to network.
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:62:70[redacted] reason='Authentication Failed'
[W][wifi:565]: Connecting to WiFi network failed. Are the credentials wrong?
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:62:70[redacted] reason='Auth Expired'
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -36 dB
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -68 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (A6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (2E:87:BA:74:23:EA) [redacted]▂▄▆█
[D][wifi:450]: - 'HOME-E82B-2.4'[redacted] (10:33:BF:59:D9:AE) [redacted]▂▄▆█
[D][wifi:450]: - 'Posh_Pagoda'[redacted] (B8:F8:53:AE:64:FE) [redacted]▂▄▆█
[D][wifi:450]: - 'Brooklyn's Castle'[redacted] (3C:BD:C5:82:AD:86) [redacted]▂▄▆█
[D][wifi:450]: - 'Fios-tyBQ9'[redacted] (04:A2:22:F9:B2:23) [redacted]▂▄▆█
[D][wifi:450]: - 'Fios-8jNF7'[redacted] (3C:BD:C5:21:77:9B) [redacted]▂▄▆█
[D][wifi:450]: - 'batteries_not_included'[redacted] (10:78:5B:48:6F:61) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:549]: Error while connecting to network.
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:565]: Connecting to WiFi network failed. Are the credentials wrong?
[D][wifi:386]: Starting scan...
[D][shtcx:100]: Got temperature=26.52°C humidity=24.17%
[D][sensor:127]: ' Temperature': Sending state 23.51833 °C with 1 decimals of accuracy
[D][sensor:127]: ' Humidity': Sending state 29.17145 % with 1 decimals of accuracy
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.7lx
[D][sensor:127]: ' Illuminance': Sending state 5.65945 lx with 1 decimals of accuracy
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -69 dB
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -36 dB
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (A6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (B6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (AE:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (10:33:BF:59:D9:B1) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (2E:87:BA:74:23:EA) [redacted]▂▄▆█
[D][wifi:450]: - 'BatGuest'[redacted] (62:BD:C5:AC:6C:6A) [redacted]▂▄▆█
[D][wifi:450]: - 'Brooklyn's Castle'[redacted] (3C:BD:C5:82:AD:86) [redacted]▂▄▆█
[D][wifi:450]: - 'Leonidas'[redacted] (38:8B:59:BC:9C:5C) [redacted]▂▄▆█
[D][wifi:450]: - 'NVR9ca3a977fcda'[redacted] (9C:A3:A9:77:FC:DA) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:85:48[redacted] reason='Association Leave'
[W][wifi:570]: WiFi Unknown connection status 0
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi_esp32:491]: Event: Disconnected ssid='Pretty Fly for a WiFi' reason='Probe Request Unsuccessful'
[W][wifi:549]: Error while connecting to network.
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -37 dB
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -68 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (B6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (A6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (AE:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - 'Lexi’s House'[redacted] (D2:32:E5:19:68:6A) [redacted]▂▄▆█
[D][wifi:450]: - 'BatGuest'[redacted] (62:BD:C5:AC:6C:6A) [redacted]▂▄▆█
[D][wifi:450]: - 'Leonidas'[redacted] (38:8B:59:BC:9C:5C) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (4A:4B:D4:76:F2:21) [redacted]▂▄▆█
[D][wifi:450]: - 'Gabaflea'[redacted] (48:4B:D4:75:F2:24) [redacted]▂▄▆█
[D][wifi:450]: - 'Verizon_PCS7GH'[redacted] (3C:BD:C5:A1:64:B4) [redacted]▂▄▆█
[D][wifi:450]: - 'CD63F'[redacted] (70:F2:20:2E:F5:81) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:559]: WiFi network can not be found anymore.
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:85:48[redacted] reason='Association Failed'
[W][wifi:549]: Error while connecting to network.
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -68 dB
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -36 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (AE:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (B6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (2E:87:BA:74:23:EA) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (2E:87:BA:74:23:EB) [redacted]▂▄▆█
[D][wifi:450]: - 'Batcave'[redacted] (3C:BD:C5:AC:6C:69) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (4A:4B:D4:76:F2:21) [redacted]▂▄▆█
[D][wifi:450]: - 'Gabaflea'[redacted] (48:4B:D4:75:F2:24) [redacted]▂▄▆█
[D][wifi:450]: - 'Posh_Pagoda'[redacted] (B8:F8:53:AE:64:FE) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:565]: Connecting to WiFi network failed. Are the credentials wrong?
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:565]: Connecting to WiFi network failed. Are the credentials wrong?
[I][wifi:141]: Starting fallback AP!
[C][wifi:210]: Setting up AP...
[C][wifi:212]:   AP SSID: 'everything-presence-one-de99b4'
[C][wifi:213]:   AP Password: ''
[C][wifi:222]:   IP Address: 192.168.4.1
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:62:70[redacted] reason='Auth Expired'
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -36 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (A6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (10:33:BF:59:D9:B1) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (4A:4B:D4:76:F2:25) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (4A:4B:D4:76:F2:27) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (4A:4B:D4:76:F2:21) [redacted]▂▄▆█
[D][wifi:450]: - 'Gabaflea'[redacted] (48:4B:D4:75:F2:24) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (38:3F:B3:E7:D9:2E) [redacted]▂▄▆█
[D][wifi:450]: - 'Posh_Pagoda'[redacted] (B8:F8:53:AE:64:FE) [redacted]▂▄▆█
[D][wifi:450]: - 'Guests of Leonidas'[redacted] (3A:8B:59:BC:9C:5C) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (38:3F:B3:E7:D9:32) [redacted]▂▄▆█
[D][wifi:450]: - 'Leonidas'[redacted] (38:8B:59:BC:9C:5C) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:549]: Error while connecting to network.
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:565]: Connecting to WiFi network failed. Are the credentials wrong?
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.7lx
[D][sensor:127]: ' Illuminance': Sending state 5.65945 lx with 1 decimals of accuracy
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -70 dB
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -35 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (AE:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (B6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (2E:87:BA:74:23:EA) [redacted]▂▄▆█
[D][wifi:450]: - 'Fios-tyBQ9'[redacted] (04:A2:22:F9:B2:23) [redacted]▂▄▆█
[D][wifi:450]: - 'NETGEAR24'[redacted] (10:DA:43:8F:E1:FC) [redacted]▂▄▆█
[D][wifi:450]: - 'Brooklyn's Castle'[redacted] (3C:BD:C5:82:AD:86) [redacted]▂▄▆█
[D][wifi:450]: - 'Fios-B8H6M_EXT'[redacted] (50:D4:F7:18:36:7A) [redacted]▂▄▆█
[D][wifi:450]: - 'batteries_not_included'[redacted] (10:78:5B:48:6F:61) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:85:48[redacted] reason='Association Leave'
[W][wifi:570]: WiFi Unknown connection status 0
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi_esp32:491]: Event: Disconnected ssid='Pretty Fly for a WiFi' reason='Probe Request Unsuccessful'
[W][wifi:549]: Error while connecting to network.
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -38 dB
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -69 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (A6:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (AE:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - 'BatGuest'[redacted] (62:BD:C5:AC:6C:6A) [redacted]▂▄▆█
[D][wifi:450]: - 'AJ201 2.4'[redacted] (3C:BD:C5:0C:B3:02) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (2E:87:BA:74:23:EA) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (2E:87:BA:74:23:EB) [redacted]▂▄▆█
[D][wifi:450]: - 'Cornell09'[redacted] (D6:32:E5:19:68:6A) [redacted]▂▄▆█
[D][wifi:450]: - 'Yankeeman30187'[redacted] (7C:9A:54:13:78:14) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (38:3F:B3:E7:D9:30) [redacted]▂▄▆█
[D][wifi:450]: - 'Brooklyn's Castle'[redacted] (3C:BD:C5:82:AD:86) [redacted]▂▄▆█
[D][wifi:450]: - 'Fios-B8H6M_EXT'[redacted] (50:D4:F7:18:36:7A) [redacted]▂▄▆█
[D][wifi:450]: - 'NETGEAR24'[redacted] (10:DA:43:8F:E1:FC) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:559]: WiFi network can not be found anymore.
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:85:48[redacted] reason='Authentication Failed'
[W][wifi:565]: Connecting to WiFi network failed. Are the credentials wrong?
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:85:48[redacted] reason='Auth Expired'
[D][wifi:386]: Starting scan...
[D][shtcx:100]: Got temperature=26.48°C humidity=24.35%
[D][sensor:127]: ' Temperature': Sending state 23.48361 °C with 1 decimals of accuracy
[D][sensor:127]: ' Humidity': Sending state 29.34998 % with 1 decimals of accuracy
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'Pretty Fly for a WiFi' (92:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:446]:     Channel: 6
[D][wifi:447]:     RSSI: -36 dB
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:85:48) [redacted]▂▄▆█
[D][wifi:450]: - 'KaChang'[redacted] (22:87:BA:74:23:70) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (22:87:BA:74:23:77) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (AE:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - 'Kosen-Rufu'[redacted] (A8:70:5D:AF:80:98) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (96:3B:AD:B4:62:70) [redacted]▂▄▆█
[D][wifi:450]: - 'BatGuest'[redacted] (62:BD:C5:AC:6C:6A) [redacted]▂▄▆█
[D][wifi:450]: - ''[redacted] (7C:9A:54:13:78:17) [redacted]▂▄▆█
[D][wifi:450]: - 'Guests of Leonidas'[redacted] (3A:8B:59:BC:9C:5C) [redacted]▂▄▆█
[D][wifi:450]: - 'Leonidas'[redacted] (38:8B:59:BC:9C:5C) [redacted]▂▄▆█
[D][wifi:450]: - 'Restricted Airspace'[redacted] (14:22:3B:1F:14:0A) [redacted]▂▄▆█
[D][wifi:450]: - 'Fios-8jNF7'[redacted] (3C:BD:C5:21:77:9B) [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'Pretty Fly for a WiFi'...
[W][wifi:549]: Error while connecting to network.
[W][wifi_esp32:494]: Event: Disconnected ssid='Pretty Fly for a WiFi' bssid=92:3B:AD:B4:85:48[redacted] reason='Authentication Failed'
[W][wifi:565]: Connecting to WiFi network failed. Are the credentials wrong?
[D][bh1750.sensor:159]: ' Illuminance': Got illuminance=5.9lx
[D][sensor:127]: ' Illuminance': Sending state 5.88583 lx with 1 decimals of accuracy
[D][wifi:386]: Starting scan...
[D][esp-idf:000]: E (2655447) MDNS: Cannot allocate memory (line: 216, free heap: 400 bytes)

[D][esp-idf:000]: E (2655450) 
abort() was called at PC 0x401ed3d3 on core 1


Backtrace:0x40083c19:0x3ffcd8100x4009364d:0x3ffcd830 0x40098d89:0x3ffcd850 0x401ed3d3:0x3ffcd8d0 0x401ed41a:0x3ffcd8f0 0x401ee493:0x3ffcd910 0x401ece1a:0x3ffcd930 0x401ecde9:0x3ffcd950 0x401f1423:0x3ffcd970 0x400f50d1:0x3ffcd9c0 0x400d9a37:0x3ffcda00 0x400d9a42:0x3ffcda20 0x40207971:0x3ffcda40 0x40207a31:0x3ffcda60 0x400e8010:0x3ffcda80 0x400ea976:0x3ffcdab0 0x400f9025:0x3ffcdad0 




ELF file SHA256: 0000000000000000

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

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13132
load:0x40080400,len:3036
entry 0x400805e4
[I][logger:258]: Log initialized
[C][ota:469]: There have been 0 suspected unsuccessful boot attempts.
[D][esp32.preferences:113]: Saving 1 preferences to flash...
[D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[I][app:029]: Running through setup()...
[I][i2c.arduino:175]: Performing I2C bus recovery
[C][uart.arduino_esp32:077]: Setting up UART...
[    90][E][HardwareSerial.cpp:525] setRxBufferSize(): RX Buffer can't be resized when Serial is already running.

See below for full logs
esp-web-tools-logs.txt

Documentation title is under webview

The doc title/name is a bit hidden by the browser UI because the text is too big or the container is too small

Screenshot

mmWave False Positives

I've been using a PresenceOne for a couple of months with great success - being able to set the detect distance for mmwave has been a game changer in handling accurate room presence, without "bleeding" over into other rooms when doors are open.

However, recently I'm seeing frequent false positives on the mmWave sensor - around 5 an hour in the middle of the night. Now I realise that these sensors need some adjustments, but I had already done that and had it working perfectly. Here's a quick summary of the setup though.

The sensor is facing into a medium sized room with no windows in its LOS. The distance is set to be within the room only. I'm getting these false positive in the middle of the night when everyone is in bed, and we have no pets. No ceiling fans or other things designed to move.

I have tried turning the sensitivity down, but even at 4 I'm still getting them. The PIR isn't triggering, plus I have a different mmWave sensor in a different part of what are adjoining areas, and that's not triggering either.

The only change is that I recently put the sensor into its case - when I originally ordered it I stupidly missed the case off, so it was working without for a while. I've checked that the firmware is relatively up to date (2022.12.3), though haven't checked today.

So now I'm stumped. As I write this I realise that an obvious test would be to face the sensor up against a wall, as that would eliminate any question of it triggering based on actual movement. I'll do that now and report back, but in the meantime does anyone have any ideas?

Update
Having left the sensor facing a wall for the last hour its triggered 19 times. Anything else I should be trying, or does it seem like a faulty sensor?

EP1 is unable to connect to hidden WiFi networks

My IoT SSID is normally hidden, I had to make it visible to connect the EP1s to it. Would like to keep it hidden for the future.

If I change the network to hidden, EP1s cannot connect to it anymore.
Keep in mind the configs are not changing on the EP1s, all I do is toggle the SSID between hidden and public and the EP1s are only able to connect to the public version.
There are 50 Shelly devices and a dozen other assorted IoT devices on this network so I think this is only a problem on the EP1 side.

What is the first thing to check so I can resolve this?

Does mmWave sensor "detect" through glass (windows) ?

My EP1 is about 16 feet (~4.8m) from a window, but it is looking directly at it. The mmWave detector is constantly flapping on and off:

I'm wondering if it can see movement of the trees right outside the window?? I'm home alone, and fairly confident my house is not haunted. However, there seems to be a dance club in my living room when I'm not looking.

mmWave off-latency: 15 seconds
mmWave sensitivity: 6
mmWave distance: 375cm (~12 feet)

These values seem to make sense. My thought is to reduce sensitivity even more. (Wow, these sensors are fantastic!)

Is there a way to get information on where it senses movement? (direction / distance / etc)

Raw sensor value from mmWave

Hey @EverythingSmartHome, just got 13 EP1s and I'm trying to fine tune the mmWave thresholds. This process would be a lot easier if I could see the raw motion value from the mmWave sensor to see how the different units compare and are reporting, and set the threshold sensitivity more easily.
Can a sensor for this be exposed?

PIR sensitivity?

Was curious if the Panasonic has an adjustment for this? I have an open floor concept so being able to turn it down just a smidge would probably clear up a lot of false triggers.

Support for external ESPHome installs

Hi, I keep getting errors with ESPHome

INFO Reading configuration /config/everything-presence-one-e01da0.yaml...
WARNING GPIO15 is a Strapping PIN and should be avoided.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
Failed config

dashboard_import: [source /config/.esphome/packages/0c0347a4/everything-presence-one.yaml:46]
  package_import_url: github://everythingsmarthome/presence-one/everything-presence-one.yaml@main
  
  [import_full_config] is an invalid option for [dashboard_import]. Please check the indentation.
  import_full_config: False

EDIT: not sure why I'm getting this now. Whether its the ESPHome version or what, I have ESPHome installed seperately to HA at the moment (going to change once my HA Yellow POE finally arrives)

Occupancy stuck in detected when mmWave turned off while in detected state

I needed to disable mmWave sensor whilst 3D printer was running in my garage as kept it detected and the lights on incorrectly, so added logic in HA to turn off mmWave sensor whilst 3D printer was running. However this did not turn off the lights as expected, on investigation after turning off the mmWave sensor it remains at it's last state, which in my case is usually "detected". This in turn kept the Occupancy sensor from switching off also.

3 options to solve this

Clear the sensor somehow after issuing a "sensorStop".
Add a template binary sensor which would be the "mmWave" sensor, a proxy essentially which would be set on any changes from the mmWave but could also be cleared when mmWave disabled using "publish_state".
Modify the logic to the Occupancy sensor to ignore the mmWave when it is disabled.

I investigated if there is any way to clear the sensor when it gets switched off and the mmWave docs didn't show anything. I was going to try the mmWave reset command after the "sensorStop" command but was unsure what this would actually do as the DFRobot wiki isn't very detailed on that. So without further investigation into option 1, option 3 seems the lowest impact change, have modified the Occupancy lambda to the following code

    lambda: |-
      bool newState = id(occupancy).state;
      if( id(mmwave_sensor).state)
      {
        if ( id(mmwave).state or id(pir_motion_sensor).state) {
          newState = true;
        } 
        else if (id(mmwave).state == 0 and id(pir_motion_sensor).state == 0) {
          newState = false;
        } 
      }
      else
      {
         newState = id(pir_motion_sensor).state;
      }
      return newState;

Unable to update

I received my sensors today.
I'm able to add the sensor to HA, but get an error when trying to update under ESPHome.

INFO Reading configuration /config/esphome/everything-presence-one-6f2414.yaml...
WARNING GPIO15 is a Strapping PIN and should be avoided.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
Failed config

dashboard_import: [source /config/esphome/.esphome/packages/0c0347a4/everything-presence-one.yaml:46]
  package_import_url: github://everythingsmarthome/presence-one/everything-presence-one.yaml@main
  
  [import_full_config] is an invalid option for [dashboard_import]. Please check the indentation.
  import_full_config: False [source /config/esphome/.esphome/packages/0c0347a4/everything-presence-one.yaml:47]

This is the yaml:

substitutions:
  name: ep1
packages:
  Everything_Smart_Technology.Everything_Presence_One: github://everythingsmarthome/presence-one/everything-presence-one.yaml@main
esphome:
  name_add_mac_suffix: false


wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

WiFi signal strength sensor

Would be great for the EP1 to expose a WiFi signal strength (RSSI) sensor to HA. Good for debugging dead zones or interference. Shelly relays do this and it's a really nice feature to have.

Edit: I know this can be seen in the EP1 logs if directly connected but getting the sensor in HA means history logging for it, which is a benefit since trends can be noticed at different times of day/week then.

2 Devices stuck in boot loop after Installing firmware for Home Assistant

Received my 2 everything presence ones today, and ran the Home assistant installer. When trying to connect to wifi, a list of wifi networks is not populated, and when manually entering in the SSID/PW, it connects forever. When looking at the logs, it has the following error and then reboots, and gets the same error again.

Full error: error.txt

[C][improv_serial:032]: Improv Serial:

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


Backtrace:0x40083c19:0x3ffebbf00x4009364d:0x3ffebc10 0x40098d89:0x3ffebc30 0x401ed4ef:0x3ffebcb0 0x401ed536:0x3ffebcd0 0x401ee5af:0x3ffebcf0 0x401ecf36:0x3ffebd10 0x401ecf05:0x3ffebd30 0x400f04de:0x3ffebd50 0x400ef7ea:0x3ffebd70 0x400efae0:0x3ffebec0 





ELF file SHA256: 0000000000000000

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

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

Problems with naming in ESPHome

Firstly, please excuse my ignorance.

I am trying to change the default names in ESPHome so I can try to match with meaningful names in HA. Whatever way I try to rename the device in ESPHome (via the rename option or using the substitution in YAML, it does a load of stuff then just tells me it can't resolve the name and more and the device then just appears offline.

Also it seems to keep finding the old name and asking me to adopt it again, but then tells me it doesn't exist. Even if I remove and re-install ESPHome, I seem to need to manually delete all the files before I do so, or all the naff config is still there.

Guess I am just being daft.

Right way to do updates?

I got the sensor installed and working. I've had some issues with the sensor crashing howeever, and I see others have resolved that by updating the firmware. However at that point I get a bit stuck.
"
I've tried using the Update button in the sensor's webUI - not specifying a file. It seemed to do something, and if I hit the Update button again it says "Update successful", but its still reporting 2022.11 in the decice screen in HA so I'm not confident that's worked. I'm still getting the sensor locking up.

Others have referenced updating via USB, but I'm not sure how to actually do that. I have ESPHome already running (in Docker) from some testing I did last year, but I've not done much with it. If I fire that up I can onboard a new device, but not sure if that's what I should be doing, as usually that would build new custom firmware, no?

Any chance of a quick summary on the right way to do both OTA and USB based updates?

Two mmw sensors with the free GPIOs - Possible?

The angles of the mmw sensors (40°/100°) are very narrow and for my use case this does really bad. So I want to add another mmw sensor. Is there any reason to assume I couldn't add another mmw sensor with the free GPIOs 18/19/22/23?

Has anybody done it? I'm not exactly fluent with ESP32s, meaning I can't tell if I can have another UART on that GPIOs, but apart from that I'd assume with proper copying and renaming of the mmw code elements in the yaml, this should totally work.

Please let me know, if there is any work already done on this, or stop me if the endeavor is futile.

Expansion Header Details

Can you provide details on the pinout of the expansion header.

mmWave LED constantly flashing

This. It is constantly flashing. Changing the "mmWave LED" switch has no effect whatsoever.

mmWave led turning back on (randomly?)

Hello,

Great product, love the combined sensors in one box.
I have 3x EP1s in different rooms. I've turned all leds off (including mmWave) for all of them.
For some reasons, the mmWave led turns back on again randomly (didn't find the pattern/trigger yet).
It doesn't happen to all 3 at the same time - but it happened to all 3 over time (hope it makes sense).
Any idea what it could come from? Any other idea to force it off?
Thanks

PIR false positives

Hi,

I am suffering from constant false positives from the PIR sensor. This happens about once every hour.
The room is my office, there are no pets in the house. I cannot see anything that moves. What could cause this? Is there any way to influence the sensitivity of the PIR sensor?

False positives

Getting regular false positives from both the PIR and mmWave sensor. I'm all the way down to 5 in sensitivity of the mmWave sensor. The interval detection is everything between 30 min and roughly 1h. On higher sensitivity the detection interval increases to everything between 1 and 5 min.

I've set up two EP1, one in the living room and one in the bedroom. We have no pets or anything else that moves. Everything should be completely motionless. Does anyone else have these issues or perhaps any suggestions?

EP1 as bluetooth proxy for home assistant?

Does the hardware include bluetooth w/active scanning? I was thinking of also using this wonderful device as a BT proxy for some of my home assistant needs.

Is BT enabled?

WiFi unreliable

I'm not sure if this is the same thing as #1 but I'm having a bad time getting my sensor setup. I was getting disconnects even when connecting to its wifi network to choose the SSID, and once I eventually got through that, I'm seeing really terrible performance on my main network:

64 bytes from 10.0.88.167: icmp_seq=5 ttl=255 time=3904.011 ms
64 bytes from 10.0.88.167: icmp_seq=6 ttl=255 time=2905.910 ms
64 bytes from 10.0.88.167: icmp_seq=7 ttl=255 time=1904.328 ms
64 bytes from 10.0.88.167: icmp_seq=8 ttl=255 time=901.799 ms
64 bytes from 10.0.88.167: icmp_seq=9 ttl=255 time=5.123 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
64 bytes from 10.0.88.167: icmp_seq=12 ttl=255 time=3049.849 ms
64 bytes from 10.0.88.167: icmp_seq=13 ttl=255 time=2099.600 ms
64 bytes from 10.0.88.167: icmp_seq=14 ttl=255 time=1095.164 ms
64 bytes from 10.0.88.167: icmp_seq=15 ttl=255 time=92.496 ms
64 bytes from 10.0.88.167: icmp_seq=16 ttl=255 time=1465.333 ms

My network is UniFi (UAP-AC-AP-Pro access points and a UDM SE controller), I'm about 3-4 metres from the AP the sensor is connected to, and when I did the initial setup I had the sensor next to the computer that was connecting to it.

Edit: I did an update using web.esphome.io. I think it updated correctly, but it doesn't seem to be helping.
[I][app:102]: ESPHome version 2022.12.3 compiled on Jan 2 2023, 16:25:05

ESPresense

Is it possible to install ESPresence as firmware? Which setting do I have to use to get the radar and the IR working?

I am a little disappointed that MQTT is not supported and I do not use Home Assistant. ESPresence has MQTT built in.

I also don't want to recompile the firmware of ESPHome just to enable MQTT.

OTA Updates

I have two EP1s that I am trying to update to the latest version of ESPHome. They are currently on version 2023.3.2 and I'm trying to update them over the air to 2023.4.1. When I press the safe mode button, the device reboots but it doesn't appear that anything else changes. The OTA update states the update failed because the client resets the connection.

Logs are attached. The logs are from after the Safe Mode button was pressed. What am I missing?

logs_everything-presence-one-6f1878_logs (1).txt

Manual for "editing ESP home code" kinda "interrupted"...

I have successfully added the sensor to my HA, but I want to edit the code now. Sure I have ESP-home installed and built a couple of my own devices with ESPs. However I am unsure, how I proceed now with the yaml file here on GitHub.

Is there a pretty way, to "transfer" my existing EPO from a "blind" installation as per the manual, to one where it actually shows up in ESP-home and the ability to edit the code?

Or do I just have to reflash it with the yaml here on github?

mmWave module failure

I have 5 EP1, of which one has a mmWave module that will not show activity, I have moved it between different devices and got the same results.
Now that the new version of the firmware no longer exposes the factory reset mmWave firmware, I don't have any way to see if that will do anything to resolve this.

Problems updating w/ VLAN - SOLVED

I have my EP1 on a different vlan than Home Assistant, and so updates were never able to resolve the .local host.

The simple solution is to set a static address, documented here.

The "trick" is to first reserve the static ip address for the EP1 in your router, reconnect the device so it shows the correct IP, and then add the static configuration in ESPHOME. Pressing install will finish the process.

Sensors appear to crash and reboot regularly

I have just started using my everything presence one sensors (I have 2). As I was trying to set them up I noticed that every so often the sensors and their entities become unavailable in Home Assistant repeatedly, usually disappearing once every few minutes. There doesn't seem to be rhyme or reason for when they start becoming unavailable. To give you an idea, this is what one of the sensor's mmwave entities looks like for me:

After ruling out my USB-C cables and chargers, and not getting much info from the wireless logs, I hooked one of the sensors to my HA server and checked the logs over USB instead. This revealed what appear to be crashes resulting in reboots, for example:

[23:14:11][D][esp-idf:000]: fail to alloc timer, type=6
[23:14:11][D][esp-idf:000]: 
[23:14:11]
[23:14:11]abort() was called at PC 0x401f0c87 on core 1
[23:14:11]
[23:14:11]ELF file SHA256: 0000000000000000
[23:14:11]
[23:14:11]Backtrace: 0x40090060:0x3ffcd1e0 0x400902dd:0x3ffcd200 0x401f0c87:0x3ffcd220 0x401f0cce:0x3ffcd240 0x401f05e9:0x3ffcd260 0x401f06c0:0x3ffcd280 0x401f12c9:0x3ffcd2a0 0x401f1402:0x3ffcd2c0 0x401f152d:0x3ffcd300 0x400dedc7:0x3ffcd320 0x400deddb:0x3ffcd340 0x400df0d8:0x3ffcd360 0x400df28f:0x3ffcd3b0 0x400e71f5:0x3ffcd440 0x400e688d:0x3ffcd480 0x400ee319:0x3ffcd4c0 0x400e6a20:0x3ffcd4e0 0x401fbcf9:0x3ffcd500 0x401fbdd5:0x3ffcd520 0x400ecc26:0x3ffcd540 0x400efbc2:0x3ffcd570 0x400fff34:0x3ffcd590 0x40091352:0x3ffcd5b0
WARNING Found stack trace! Trying to decode it
WARNING Decoded 0x40090060: invoke_abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/panic.c:715
WARNING Decoded 0x400902dd: abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/panic.c:715
WARNING Decoded 0x401f0c87: __cxxabiv1::__terminate(void (*)()) at /builds/idf/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/eh_terminate.cc:112
WARNING Decoded 0x401f0cce: std::terminate() at /builds/idf/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/eh_terminate.cc:112
WARNING Decoded 0x401f05e9: __cxa_allocate_exception at /builds/idf/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/eh_alloc.cc:313
WARNING Decoded 0x401f06c0: operator new(unsigned int) at /builds/idf/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/new_op.cc:54
WARNING Decoded 0x401f12c9: __gnu_cxx::new_allocator<char>::allocate(unsigned int, void const*) at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/build/build-cc-gcc-final/xtensa-esp32-elf/libstdc++-v3/include/bits/basic_string.h:281
 (inlined by) std::allocator_traits<std::allocator<char> >::allocate(std::allocator<char>&, unsigned int) at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/build/build-cc-gcc-final/xtensa-esp32-elf/libstdc++-v3/include/bits/alloc_traits.h:360
 (inlined by) std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned int&, unsigned int) at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/build/build-cc-gcc-final/xtensa-esp32-elf/libstdc++-v3/include/bits/basic_string.tcc:157
WARNING Decoded 0x401f1402: std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_mutate(unsigned int, unsigned int, char const*, unsigned int) at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/build/build-cc-gcc-final/xtensa-esp32-elf/libstdc++-v3/include/bits/basic_string.h:281
WARNING Decoded 0x401f152d: std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::push_back(char) at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/build/build-cc-gcc-final/xtensa-esp32-elf/libstdc++-v3/include/bits/basic_string.h:281
WARNING Decoded 0x400dedc7: std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+=(char) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Polyfills/safe_strcmp.hpp:21
 (inlined by) ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void>::write(unsigned char) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Serialization/Writers/StdStringWriter.hpp:28
 (inlined by) ArduinoJson6185_D1::CountingDecorator<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >::write(unsigned char) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Serialization/CountingDecorator.hpp:17
WARNING Decoded 0x400deddb: ArduinoJson6185_D1::TextFormatter<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >::writeRaw(char) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Polyfills/safe_strcmp.hpp:21
 (inlined by) ArduinoJson6185_D1::TextFormatter<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >::writeString(char const*) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Json/TextFormatter.hpp:39
WARNING Decoded 0x400df0d8: ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >::visitObject(ArduinoJson6185_D1::CollectionData const&) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Polyfills/safe_strcmp.hpp:21
 (inlined by) ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >::result_type ArduinoJson6185_D1::VariantData::accept<ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> > >(ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >&) const at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Variant/VariantData.hpp:49
WARNING Decoded 0x400df28f: ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >::result_type ArduinoJson6185_D1::variantAccept<ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> > >(ArduinoJson6185_D1::VariantData const*, ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >&) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Polyfills/safe_strcmp.hpp:21
 (inlined by) ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >::result_type ArduinoJson6185_D1::VariantConstRef::accept<ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> > >(ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >&) const at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Variant/VariantRef.hpp:245
 (inlined by) ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >::result_type ArduinoJson6185_D1::JsonDocument::accept<ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> > >(ArduinoJson6185_D1::JsonSerializer<ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >&) const at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Document/JsonDocument.hpp:20
 (inlined by) unsigned int ArduinoJson6185_D1::doSerialize<ArduinoJson6185_D1::JsonSerializer, ArduinoJson6185_D1::BasicJsonDocument<ArduinoJson6185_D1::DefaultAllocator>, ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void> >(ArduinoJson6185_D1::BasicJsonDocument<ArduinoJson6185_D1::DefaultAllocator> const&, ArduinoJson6185_D1::Writer<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void>) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Serialization/serialize.hpp:15
 (inlined by) unsigned int ArduinoJson6185_D1::serialize<ArduinoJson6185_D1::JsonSerializer, ArduinoJson6185_D1::BasicJsonDocument<ArduinoJson6185_D1::DefaultAllocator>, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >(ArduinoJson6185_D1::BasicJsonDocument<ArduinoJson6185_D1::DefaultAllocator> const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Serialization/serialize.hpp:22
 (inlined by) unsigned int ArduinoJson6185_D1::serializeJson<ArduinoJson6185_D1::BasicJsonDocument<ArduinoJson6185_D1::DefaultAllocator>, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >(ArduinoJson6185_D1::BasicJsonDocument<ArduinoJson6185_D1::DefaultAllocator> const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&) at /data/everything-presence-one-d53318/.piolibdeps/everything-presence-one-d53318/ArduinoJson/src/ArduinoJson/Json/JsonSerializer.hpp:115
 (inlined by) esphome::json::build_json[abi:cxx11](std::function<void (ArduinoJson6185_D1::ObjectRef)> const&) at /config/esphome/.esphome/build/everything-presence-one-d53318/src/esphome/components/json/json_util.cpp:53
WARNING Decoded 0x400e71f5: esphome::web_server::WebServer::switch_json[abi:cxx11](esphome::switch_::Switch*, bool, esphome::web_server::JsonDetail) at /config/esphome/.esphome/build/everything-presence-one-d53318/src/esphome/components/web_server/web_server.cpp:87
WARNING Decoded 0x400e688d: esphome::web_server::ListEntitiesIterator::on_switch(esphome::switch_::Switch*) at /config/esphome/.esphome/build/everything-presence-one-d53318/src/esphome/components/web_server/list_entities.cpp:48
WARNING Decoded 0x400ee319: esphome::ComponentIterator::advance() at /config/esphome/.esphome/build/everything-presence-one-d53318/src/esphome/core/component_iterator.cpp:200
WARNING Decoded 0x400e6a20: non-virtual thunk to esphome::web_server::WebServer::loop()
WARNING Decoded 0x401fbcf9: esphome::Component::call_loop() at /config/esphome/.esphome/build/everything-presence-one-d53318/src/esphome/core/component.cpp:150
WARNING Decoded 0x401fbdd5: esphome::Component::call() at /config/esphome/.esphome/build/everything-presence-one-d53318/src/esphome/core/component.cpp:150
WARNING Decoded 0x400ecc26: esphome::Application::loop() at /config/esphome/.esphome/build/everything-presence-one-d53318/src/esphome/core/application.cpp:74
WARNING Decoded 0x400efbc2: loop() at /config/esphome/.esphome/build/everything-presence-one-d53318/src/esphome/core/gpio.h:62
WARNING Decoded 0x400fff34: loopTask(void*) at /data/cache/platformio/packages/framework-arduinoespressif32/cores/esp32/main.cpp:23
WARNING Decoded 0x40091352: vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)
[23:14:13]
[23:14:13]Rebooting...

I've attached a log with several such crashes here:
logs_everything-presence-one.txt

Would love to know if there's anything this points at that I'm doing wrong or should set up differently. I don't feel like I can trust these sensors right now if they can drop off and become unavailable at any time.

Release Notes

Would it be possible to get a CHANGELOG.md or use GitHub Releases for firmware updates? The frequent updates are great, but it'd be nice to know what each update changes to judge if it's worth me grabbing the device and plugging it in (Unless OTA updates are a thing and I've simply not noticed).

Entity Naming

First off, thanks for the awesome sensor pod! I've run into a bit of an annoyance with the naming of the entities, and I'm struggling to find a robust way to fix it. I have several EP1's, and they all expose e.g. sensor.humidity. When I add a second device it becomes sensor.humidity_1. Do you have a recommended way to name these entities based on the device name? E.g. if I have one named ep1_office I'd like the entities to become e.g. sensor.ep1_office_humidity. I've looked into hass-cli for bulk renaming the roughly 100 entities I have, but it would require writing a python script to be able to cross reference the device IDs to the entities.

Any pointers would be appreciated!

Edit: This is probably a duplicate of #4

EP1 not adding to ESPHome Dashboard

Hi,

I've added two EP1's to my HA,, they both were automatically discovered by mDNS and added to via ESPHome integration and I can see both devices and their associated sensors, so all good from that perspective. However, neither device was added to the ESPHome dashboard, the documentation says to install the addon, but that was already installed (I've used it for some time). I tried deleting both EP1 devices from the Intergrations page and then readding them both manually, which added them back ok but still not showing in the dashboard. Any ideas?

James

P.S. The main reason I want this it so I can change the code to calibrate the humidity sensor, I've got 3 separate humidity sensors in the same room and they are all wildly different from each other.

Component esp32_improv cannot be used together with component esp32_ble_tracker

Hello,

Thanks for this awesome project. I've been having lots of fun while tinkering with it.

On the webshop it says:

"The ESP32 also provides Bluetooth tracking capabilities, along with the brand new [Bluetooth Proxy] feature in Home Assistant and ESPHome - this allows for extending Home Assistant's Bluetooth range by using remote ESP32's around your house - a function that is a match made in heaven for this board!"

However I get a compiling error when I try to configure the Bluetooth Proxy using the ESPHome version 2022.12.3 and the recommended configuration. So adding these lines to the default config.

esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: true

bluetooth_proxy:
  active: true

Gives the following error while compiling.

Failed config

esp32_improv: [source /config/esphome/.esphome/packages/f43db209/everything-presence-one.yaml:43]
  
  Component esp32_improv cannot be used together with component esp32_ble_tracker.
  authorizer: none
esp32_ble_server: None
  {}
esp32_ble: None
  {}
Component esp32_ble_server cannot be used together with component esp32_ble_tracker

Component esp32_ble cannot be used together with component esp32_ble_tracker

Should this be changed in the configuration file hosted on this GitHub? Or should I, as a user, make a copy of this GitHub config and adept these changes to add the bluetooth proxy functionality?

No Home Assistant how-to?

My two sensors arrived today, yay!
I remember watching a Youtube video were you were saying non-HA users could expect to connect the Everything Presence One through MQTT. But being totally unfamiliar with ESPHome, I don't know where to begin?

First off, I assume it's possible to get signals without having Home Assistant running as a middleman, but maybe that's wrong?

I have found the IP of my sensors, Fing reports no open ports. As far as I understand from the documentation on ESPHome, MQTT needs to be enabled manually? I read about a ESPHome dashboard, but it's hard to reach without having Home Assistant?

I have a MQTT broker running on Docker through Synology NAS, and hope to use Homey instead of HA for handling the sensor.
But I probably need to tell the sensor the Broker IP?

There is a ESPHome project public on the Homey app store that was updated 2 weeks ago. They suggest port 6053 when connecting. I thought maybe that could be my "way in". Even get around using MQTT...But can't connect.
Through the console through your update-button I was able to read the log saying:
[D][api.connection:918]: homey (::FFFF:192.168.50.60): Connected successfully
[W][api.connection:083]: homey (::FFFF:192.168.50.60): Connection closed

Inside Homey I get this error: "Cannot read properties of undefined (reading 'deserializeBinary')"

I understand if you can't help with Homey specific projects for ESPHome, just thought it was helpful knowing MQTT isn't our only option. But I am grateful for any hints and paths to take to get me going (except the obvious "just use HA" of course..).
Can I use the console to open ports or enable MQTT?

Temperature offset not working

First off thanks for producing this device, it is exactly what I need to control things in my home office. (Apologies if this is not the place for support.)

I am trying to get the temperature a bit more accurate using the offset but it doesn't seem to work (the docs say this is in the advance section but I couldn't find it so I might have missed something). All I have done so far is add this to the existing settings and installed it using ESPHome (over air connection).

substitutions:
temperature_offset: "-3"

I have downloaded the yaml and I can see it is still set.

Any suggestions?

support for BLE proxy.

Since ESPHome 2023.2.0 currently allow esp32_improv and bluetooth_proxy at the same time, is it possible include this configuration in the stock firmware?, in order to keep the OTA update without using custom configuration

mmwave false positive - sensitivity 1

I am receiving many false positives on the mmWave sensor, is it faulty? I have tuned it down to sensitivity 1, the distance is 3m, off 30 sec, location in a bathroom without windows and a large mirror.....

Everything_Presence_One
by Everything_Smart_Technology
Firmware: 2023.3.0 (Mar 16 2023, 11:06:07)
Hardware: 1.1.3

additional YAML in ESPHOME from stock

esp32_ble_tracker:
scan_parameters:
interval: 1100ms
window: 1100ms
active: true

bluetooth_proxy:
active: true

sensor:

platform: wifi_signal
name: "${room} Wi-Fi"
update_interval: 600s

Does the EP1 work with any USB-C cable and power adapter/phone charger?

Does the EP1 work with any USB-C cable (USB-A to USB-C, USB-C to USB-C, USB2.0, and USB3.0) and power adapter/phone charger? Can someone recommend some known good ones on Amazon US? Thank you.

Edit: Would something like this work with EP1?

everythingsmarthome / everything-presence-one Goto Github PK

everything-presence-one's People

Contributors

Stargazers

Watchers

Forkers

everything-presence-one's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs