#I need some help with the $13 voice
1 messages ยท Page 1 of 1 (latest)
ok i'm over here now
in assist setting what do you have in the wakeword box? is it openwakeword and whatever your chosen word is?
Yeah it's there but the logs for the openwakeword docker don't go past "Server Ready"
from the ESPHome integration, did the device respond to switching the use listen light switch ?
Yeah. It also detects if power is lost.
so it's the pipeline not establishing , which will be network related , really could do with getting ESPHome logs from the device
For clarity sake. The rest of the pioeline is confirmed to be working.
Also there are no logs to speak of.
It's just the boot sequence.
can you paste what logs it does produce
I (29) boot: compile time 02:06:53
I (29) boot: Multicore bootloader
I (32) boot: chip revision: v1.1
I (36) boot.esp32: SPI Speed : 40MHz
I (40) boot.esp32: SPI Mode : DIO
I (45) boot.esp32: SPI Flash Size : 4MB
I (49) boot: Enabling RNG early entropy source...
I (55) boot: Partition Table:
I (58) boot: ## Label Usage Type ST Offset Length
I (66) boot: 0 otadata OTA data 01 00 00009000 00002000
I (73) boot: 1 phy_init RF data 01 01 0000b000 00001000
I (80) boot: 2 app0 OTA app 00 10 00010000 001c0000
I (88) boot: 3 app1 OTA app 00 11 001d0000 001c0000
I (103) boot: End of partition table
I (107) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=3fe2ch (261676) map
I (210) esp_image: segment 1: paddr=0004fe54 vaddr=3ffbdb60 size=001c4h ( 452) load
I (211) esp_image: segment 2: paddr=00050020 vaddr=400d0020 size=10d5d0h (1103312) map
I (615) esp_image: segment 3: paddr=0015d5f8 vaddr=3ffbdd24 size=04bc0h ( 19392) load
I (623) esp_image: segment 4: paddr=001621c0 vaddr=40080000 size=1ec2ch (125996) load
I (690) boot: Loaded app from partition at offset 0x10000
I (690) boot: Disabling RNG early entropy source...
I (702) cpu_start: Multicore app
I (702) cpu_start: Pro cpu up.
I (702) cpu_start: Starting app cpu, entry point is 0x40082c7c
I (0) cpu_start: App cpu up.
I (722) cpu_start: Pro cpu start user code
I (722) cpu_start: cpu freq: 160000000
I (722) cpu_start: Application information:
I (727) cpu_start: Project name: m5stack-atom-echo
I (732) cpu_start: App version: 2024.2.1
I (737) cpu_start: Compile time: Feb 29 2024 02:05:45
I (744) cpu_start: ELF file SHA256: 18abbb8930238fb0...
I (750) cpu_start: ESP-IDF: 4.4.6
I (754) cpu_start: Min chip rev: v0.0
I (759) cpu_start: Max chip rev: v3.99
I (764) cpu_start: Chip rev: v1.1
I (769) heap_init: Initializing. RAM available for dynamic allocation:
I (776) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (782) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (794) heap_init: At 3FFCBAE0 len 00014520 (81 KiB): DRAM
I (800) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (807) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (807) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (813) heap_init: At 4009EC2C len 000013D4 (4 KiB): IRAM
I (821) spi_flash: detected chip: gd
I (823) spi_flash: flash io: dio
I (829) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.```
and nothing after that
ok , it should then go on to show the esphome component setup dump and then show the log events as they happen, they appear to stop before the esphome side kicks in.
have you changed the HA docker network mode?
Just spent 10 minutes trying to diagnose a missing ";" in the ngix config... ๐ข
It's in host mode now.
ok , see if by saying the wakeword the lights on the device change and the assist in progress shows active
i'm just quickly editing the webinstaller config , so that you can manually add it to the esphome dash and see if you can get OTA logs that way
So it works.
ok cool , so network mode sorted it
I'm assuming this is expected cause wifi sucks but the audio output cuts out.
Also it's still not showing up in ESPhome.
The logs end in the same place as well.
ok if you create a new device in the dashboard, it doesnt matter what option you choose for the board etc. when it gets to the encryption key screen, click 'skip' then edit the card it creates , delete everything and paste in the full code from the link below, then before saving and uploading, change the name so that it is exactly the same as the device name in HA , then you should be good to go. if you dont get the names the same or you want to rename it. then delete the device from the integration first. install the new firmware then re-add to HA
So it's working but still not shwoing up in ESPHome.
Does that also need to be in Host mode?
no , only HA ... did you follow the steps above to manually add it ?
As far as I'm aware. Checking for a typo or other atm.
if you manually add it to the dashboard .. then it should just be there , whether it is talking to the device or not, the card will still show in the dash
Oh sorry I misunderstood.
It shows up but shows as offline.
ok , in that case ... can you find the ip address of the device.. from your router
Got it.
and change the following in the config
wifi:
sorry hit enter too soon ๐
wifi:
ssid !secret wifi_ssid
password: !secret wifi_password
use_address: xxx.xxx.xxx.xxx
adding the use address and the ip
Sorry for the delay, life happened.
So everything is working. I got the echos on a different vlan as well :D.
The only issue is that on the ESPHome dash (docker) the device still reports offline but that is such a minor issue that it doesn't really matter.
Thanks for the help. Link your paypal or other preferred system.
Massive legend you are.
no worries, glad you are sorted. ๐
So I got my managed switch and I would like to now put my IoT stuff on a separate VLAN to HA and other services.
I've got everything (I think) set up and I've made a firewall rule so that ESP devices can only communicate to one device on the other VLAN (the HA server).
But voice assist don't work. The devices connect to HA and I can toggle the LED for example.
For clarity's sake, if the device is on the same VLAN as HA it works 100%.
Any pointers?
sounds possibly a UDP issue , if you check in HA >>settings>> system>> logs do you see anything logged that may be related ?
Logger: homeassistant.components.esphome.manager
Source: components/esphome/manager.py:339
integration: ESPHome (documentation, issues)
First occurred: 21:52:57 (1 occurrences)
Last logged: 21:52:57
Voice assistant UDP server was not stopped.
HA needs access to ALL udp ports, this will change in the 2024.5.0 release of HA where it will move over to using the ESPHome native API but for now it still needs to access all udp ports
I think it does tho. Check DM can't send images in threads apparently.