Emporia Energy Community › Support Center › Hardware and Installation › Power outage and now new behavior..
- This topic has 3 replies, 2 voices, and was last updated 1 year, 3 months ago by
emporiacs.
-
AuthorPosts
-
-
partcrash
MemberI have had my Vue 2 for close to an year now. Very useful and I have spent countless hours using it to optimize my power consumption – the tool in priceless. During the year I have lost power a few times and every time either the Vue has recovered on its own or it I had to reset the WiFi settings through the app. No problem there.
However, I lost power yesterday and I have tried to reconnect the Vue 2, but no success. I can go through the Wifi reset menu in the app and it would complete successfully. However, the monitor stays connected for roughly 20 seconds then disconnects. After 10-15 seconds reconnects and the disconnects again after 20 seconds. Rinse and repeat. Every time it disconnects it also beeps. Nothing has changed in my Wifi environment. I have restarted my router, I have connected the monitor to my phone hotspot- same behavior. Wifi signal is strong. It seems that the behavior is unaffected by which wifi network it connects to.
Pinging it constantly results in this:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.139: bytes=32 time=24ms TTL=255
Reply from 192.168.1.139: bytes=32 time=15ms TTL=255
Reply from 192.168.1.139: bytes=32 time=21ms TTL=255
Reply from 192.168.1.139: bytes=32 time=165ms TTL=255
Reply from 192.168.1.139: bytes=32 time=55ms TTL=255
Reply from 192.168.1.139: bytes=32 time=67ms TTL=255
Reply from 192.168.1.139: bytes=32 time=86ms TTL=255
Reply from 192.168.1.139: bytes=32 time=16ms TTL=255
Reply from 192.168.1.139: bytes=32 time=5ms TTL=255
Reply from 192.168.1.139: bytes=32 time=110ms TTL=255
Reply from 192.168.1.139: bytes=32 time=56ms TTL=255
Reply from 192.168.1.139: bytes=32 time=65ms TTL=255
Reply from 192.168.1.139: bytes=32 time=81ms TTL=255
Reply from 192.168.1.139: bytes=32 time=8ms TTL=255
Reply from 192.168.1.139: bytes=32 time=17ms TTL=255
Reply from 192.168.1.139: bytes=32 time=24ms TTL=255
Reply from 192.168.1.139: bytes=32 time=202ms TTL=255
Reply from 192.168.1.139: bytes=32 time=12ms TTL=255
Reply from 192.168.1.139: bytes=32 time=59ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.139: bytes=32 time=15ms TTL=255
Reply from 192.168.1.139: bytes=32 time=100ms TTL=255
Reply from 192.168.1.139: bytes=32 time=124ms TTL=255
Reply from 192.168.1.139: bytes=32 time=36ms TTL=255
Reply from 192.168.1.139: bytes=32 time=252ms TTL=255
Reply from 192.168.1.139: bytes=32 time=90ms TTL=255
Reply from 192.168.1.139: bytes=32 time=3ms TTL=255
Reply from 192.168.1.139: bytes=32 time=15ms TTL=255
Reply from 192.168.1.139: bytes=32 time=98ms TTL=255
Reply from 192.168.1.139: bytes=32 time=126ms TTL=255
Reply from 192.168.1.139: bytes=32 time=114ms TTL=255
Reply from 192.168.1.139: bytes=32 time=31ms TTL=255
Reply from 192.168.1.139: bytes=32 time=40ms TTL=255
Reply from 192.168.1.139: bytes=32 time=61ms TTL=255
Reply from 192.168.1.139: bytes=32 time=68ms TTL=255
Reply from 192.168.1.139: bytes=32 time=87ms TTL=255
Reply from 192.168.1.139: bytes=32 time=131ms TTL=255
Reply from 192.168.1.139: bytes=32 time=120ms TTL=255
Reply from 192.168.1.139: bytes=32 time=26ms TTL=255
Reply from 192.168.1.139: bytes=32 time=48ms TTL=255and so on…
Can I get some help please? I love the thing especially when it works 🙂
I did not see a hardware factory reset… I also tried deleting it from the app and adding it again- same behavior.
Thank you
-
This topic was modified 1 year, 3 months ago by
partcrash.
-
This topic was modified 1 year, 3 months ago by
-
partcrash
MemberI just realized that after the drop of connection and the beep the time to reconnect to the wifi is exactly the same as when simply powering the device on… therefore I am thinking it is just stuck in a 30 sec or so reboot loop…
I am running firmware Vue2-434 and my Serial ends in 75D0
Thank you
-
This reply was modified 1 year, 3 months ago by
partcrash.
-
This reply was modified 1 year, 3 months ago by
-
partcrash
MemberAfter short chat with support it appears the device got damaged during the power outage and needs replacement.
Thank you for timely response and resolution.
-
-
-
AuthorPosts
- You must be logged in to reply to this topic.