I'm getting this error for a 2nd voice pe i have. Everything works fine but i suspect this is somehow related to bluetooth? i onboarded via companion app. there isnt much info in this error at all refering to "Bridge" . Could it possibely be a bluetooth proxy i have setup for ha as ha os doesnt have bluetooth on the server natively.
#Attempts to (re)connect to bridge failed - This might be an indication of connection issues.
scenic nest
timid stag
I'm getting this error for a 2nd voice pe i have. Everything works fine but i su...
if your having trouble onboarding you can plug it into desktop
reinstall firmware using this tool - https://esphome.github.io/home-assistant-voice-pe/
and then you will be able to set the wifi creds after flashing.
that way its on your wifi network and the esphome integration will find it
scenic nest
if your having trouble onboarding you can plug it into desktop
reinstall firmwar...
thing is it's completely installed and working fine. i just keep getting this error randomly throughout the day
this error has logged over 200 times since yesterday
timid stag
can you post the full error?
although i would still probably recommend removing it from HA, reinstalling the firmware, and re adding it
a reset of everything solves a lot of problems by its nature
scenic nest
i cleared them but i'll post again when it pops back up. the catch is after onboarding, i took control and put the yaml in there from git and added code for external speakers, but thats just a uri bit. i know it's not that because the other pe has the exact code and doesn't throw it off.
timid stag
i gotcha, lets see if it replicated with a fresh install without it being adopted and modified
just because its more of a "known state"
scenic nest
just because its more of a "known state"
sorry for the delayed response, been working a lot lately. this is the full error. which sounds like the hue bridge? but i checked and the bridge is a different ip. ip stated in this error is the voice. not sure why this is
Logger: aiohue.v2[192.168.xx.xx].events
Source: runner.py:154
First occurred: 7:57:16 PM (1 occurrence)
Last logged: 7:57:16 PM
540 Attempts to (re)connect to bridge failed - This might be an indication of connection issues
timid stag
sorry for the delayed response, been working a lot lately. this is the full erro...
the voice pe has nothing to do with the the hue bridge
scenic nest
but doesnt aiohue relate to the hue bridge?
timid stag
but how is this related to voice.
all i am seeing is a error with the hue bridge? but you are saying its a voice issue?
scenic nest
the ip stated in the error is the ip of the voice pe
doesn't make sense
the bridge has a completely different ip
thats why i'm baffled
timid stag
sounds like the hue integration is for some reason trying to connect to the vpe
what type of install of HA are you running? and which version?
scenic nest
most up to date, not beta. running ha in proxmox vm
correct me if wrong but doesn't the bridge have bluetooth? or is it just zigbee
timid stag
its failing to connect to the bridge at that ip because its not at that ip. this seems to be an issue with hue integration and not the VPE. i would try removing and readding it.
to my knowledge the hue bridge is just a wifi zigbee coordinator?
scenic nest
thats what i thought
tried finding an issue online but nothing. i'm still on the original version of ha from when i started and not sure if something is somehow botched from ..god knows what lol. yea i'll try resetting the vpe and doing this again.i used the latest yaml from github from official repo though
timid stag
theres a couple of old issues that seem to imply that the bridge can sometimes braodcast ovthe wrong ip over discovery
try rebooting the bridge
scenic nest
already tried that
timid stag
tried finding an issue online but nothing. i'm still on the original version of ...
from what you are describing this has nothing to do with the VPE
it just happened that the wrong ip it chose was the vpe
timid stag
then i think someone is mishaving somewhere and it may sort itself out eventually
can just ignore the error
scenic nest
i've been on a mission to get rid of all errors in the logs lol..hell is that even possible
timid stag
could try turning off all your network gear and bridge etc... and bringing it all back up to clear all the network caches on everything
scenic nest
yea
timid stag
i've been on a mission to get rid of all errors in the logs lol..hell is that ev...
lol, probably not 😛 i have a bunch of errors and stuff in mine that dont make any difference to me
if stuff is working then i wouldn't fuss over some random errors in the log
scenic nest
i've been wanting to upgrade my network anyway and get rid of this tp link garbage. my network for w/e reason seems to reboot around 4am even though i don't schedule it. off topic question. i want to consolidate all the ethernet to a central location. is it worth setting upvlans or just doing an unmanaged switch and saying to hell with it
timid stag
unless you have a specific reason then you don't need vlans. they cause more trouble than they are worth for most people.
"but someone said i need it because it makes me more secure"....is not a reason
scenic nest
my main thing was worrying about some of the iot phoning home
timid stag
there are very specific situations where its useful but realistically if your asking then you dont have that situation
timid stag
my main thing was worrying about some of the iot phoning home
use zigbee/zwave devices or dont buy devices you dont trust 😛
scenic nest
just sunk 200 bucks on a zwave lock to get rid of eufys wifi only junk
timid stag
if theres specific devices you want to block from internet connection then you can do that on a router without having a vlan