search

roomsense / firmware

4 stars 0 forks source link

Request for Firmware Update to Address Wi-Fi Reconnection Issue After Power Outages #3

Open Fronty72 opened 2 months ago

Fronty72 commented 2 months ago

I recently experienced two brief power outages at my home, during which I noticed that both of my RoomSense IQ devices did not reconnect to Wi-Fi once power was restored. I suspect that this occurred because the reboot process for my modem and access points took longer than the reboot of the sensors, resulting in the Wi-Fi network being unavailable when the sensors attempted to reconnect.

Although I haven't verified this, it appears that the sensors only attempt to connect to Wi-Fi once during the boot process and do not keep retrying until a connection is established.

If this is the case It would be highly beneficial if a firmware update could be provided to address this issue.

roomsense commented 2 months ago

The sensors are continuously searching for a Wi-Fi connection, indicated by the LED flashing orange and blue. So, the situation you described likely has a different cause. Please keep us updated with any new findings.

russellmilliner commented 2 months ago

My RoomSense has disconnected from wifi and not reconnected till power cycled several days in a row. It's bad enough that I now have HA monitor it for disconnect to the wifi and cycle it automatically. Shouldn't have to do this.

Fronty72 commented 2 months ago

The sensors are continuously searching for a Wi-Fi connection, indicated by the LED flashing orange and blue. So, the situation you described likely has a different cause. Please keep us updated with any new findings.

Thank you for your response. Unfortunately, the setup did not function as expected. The sensor was only flashing blue, indicating an MQTT broker connection, but it was not accessible via its fixed IP address on my WiFi network. Additionally, neither sensor appeared in my UniFi UDM client list, which suggests that the WiFi connection was not established until I rebooted both sensors. I hope this information is helpful for troubleshooting.

trentbrown13 commented 1 month ago

I have a similar issue - my roomsense lost power and since then it will not connect to my network. looking at the router log, roomsence is not requesting an ip though the LED is blinking blue/orange. At this point it is a brick and I only had it for a day

trentbrown13 commented 1 month ago

addendum, it just briefly connected but then quickly disconnected. Following is the router log. The roomsense MAC is 80:65:99:a4:fb:24

logread | grep -i 80:65:99:A4:FB:24 Thu Sep 5 13:52:40 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a4:fb:24 IEEE 802.11: associated (aid 3) Thu Sep 5 13:52:40 2024 daemon.notice hostapd: wifi2g: AP-STA-CONNECTED 80:65:99:a4:fb:24 auth_alg=sae Thu Sep 5 13:52:40 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a4:fb:24 RADIUS: starting accounting session 47B8D3251AC98ADE Thu Sep 5 13:52:40 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a4:fb:24 WPA: pairwise key handshake completed (RSN) Thu Sep 5 13:52:40 2024 daemon.notice hostapd: wifi2g: EAPOL-4WAY-HS-COMPLETED 80:65:99:a4:fb:24 Thu Sep 5 13:53:15 2024 user.info eventmgr/post: event-post.sh called with: -p info -t client/80:65:99:A4:FB:24/joined {"Port":"wifi2g"} Thu Sep 5 13:53:18 2024 local6.warn ldmd[19550]: New host 80:65:99:A4:FB:24 Thu Sep 5 13:53:18 2024 daemon.notice procd: /etc/init.d/ldmd: Added new host 80:65:99:A4:FB:24 Thu Sep 5 13:53:20 2024 daemon.info dnsmasq-dhcp[16301]: DHCPDISCOVER(br-lan) 80:65:99:a4:fb:24 Thu Sep 5 13:53:20 2024 daemon.info dnsmasq-dhcp[16301]: DHCPOFFER(br-lan) 192.168.100.173 80:65:99:a4:fb:24 Thu Sep 5 13:53:26 2024 daemon.notice hostapd: wifi2g: AP-STA-DISCONNECTED 80:65:99:a4:fb:24 Thu Sep 5 13:53:39 2024 user.info blocker: m:80:65:99:A4:FB:24 l:RoomSense_2 g:unassigned s:play to:0 type: Thu Sep 5 13:53:56 2024 user.info eventmgr/post: event-post.sh called with: -p info -t client/80:65:99:A4:FB:24/left {"Port":"wifi2g"} Thu Sep 5 13:54:02 2024 local6.warn /sbin/hubmaster[24776]: New Host: 80:65:99:A4:FB:24 Thu Sep 5 13:54:40 2024 user.crit lookupmac: Looking up 80:65:99:A4:FB:24 Thu Sep 5 17:32:47 2024 user.info blocker: m:80:65:99:A4:FB:24 l:RoomSense_2 g:unassigned s:play to:0 type:

roomsense commented 1 month ago

Based on the log, it looks like the RoomSense IQ device is briefly connecting but then disconnecting shortly after. Here are a few steps to try:

Let me know if these steps help or if the issue persists!

trentbrown13 commented 1 month ago

Hello, After several ( I mean multiple 10x) reboots, rebooting all the routers (it is a mesh network) and re-locating this roomSense to another room (it was co-located with my 2nd roomSense) I have it online and upgraded to the latest firmware. I really cannot determine what "fixed" it though I feel it is just luck on the roomSense reboots)

A couple things to note

-. This roomSense module always displays a distance value > 0 even though there is no movement in the room - my othere roomsense displays 0 distance when there is no movement in the room. I have both manualy calibrated both and used the auto calibration method, pretty much the same results for both.

I have quite a few espx devices in my home network and 2 work test networks, none of these exhibit this behavior though Blink was problematic at some time in the past but that is resolved now.

All WiFi settings are fine, all other devices (2.4, 5 and 6g) connect fine as well as WiFi6 and Wifi7.

Let me know if I can provide any more information, and I appreaciate the help! best -trent

trentbrown13 commented 1 month ago

router log of the roomSense module haveing a hard time establishing a stable connection

Sat Sep 7 18:58:09 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c IEEE 802.11: associated (aid 1) Sat Sep 7 18:58:09 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c RADIUS: starting accounting session C8406E9FDE8ECE90 Sat Sep 7 18:58:09 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c WPA: pairwise key handshake completed (RSN) Sat Sep 7 18:58:09 2024 daemon.notice hostapd: wifi2g: EAPOL-4WAY-HS-COMPLETED 80:65:99:a3:10:4c Sat Sep 7 18:58:09 2024 daemon.info dnsmasq-dhcp[26133]: DHCPDISCOVER(br-lan) 80:65:99:a3:10:4c Sat Sep 7 18:58:09 2024 daemon.info dnsmasq-dhcp[26133]: DHCPOFFER(br-lan) 192.168.100.145 80:65:99:a3:10:4c Sat Sep 7 18:58:09 2024 daemon.info dnsmasq-dhcp[26133]: DHCPREQUEST(br-lan) 192.168.100.145 80:65:99:a3:10:4c Sat Sep 7 18:58:09 2024 daemon.info dnsmasq-dhcp[26133]: DHCPACK(br-lan) 192.168.100.145 80:65:99:a3:10:4c RoomSense_1

Sat Sep 7 18:58:16 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c IEEE 802.11: associated (aid 1) Sat Sep 7 18:58:16 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c RADIUS: starting accounting session C8406E9FDE8ECE90 Sat Sep 7 18:58:16 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c WPA: pairwise key handshake completed (RSN) Sat Sep 7 18:58:16 2024 daemon.notice hostapd: wifi2g: EAPOL-4WAY-HS-COMPLETED 80:65:99:a3:10:4c Sat Sep 7 18:58:16 2024 daemon.info dnsmasq-dhcp[26133]: DHCPDISCOVER(br-lan) 80:65:99:a3:10:4c Sat Sep 7 18:58:16 2024 daemon.info dnsmasq-dhcp[26133]: DHCPOFFER(br-lan) 192.168.100.145 80:65:99:a3:10:4c Sat Sep 7 18:58:16 2024 daemon.info dnsmasq-dhcp[26133]: DHCPREQUEST(br-lan) 192.168.100.145 80:65:99:a3:10:4c Sat Sep 7 18:58:16 2024 daemon.info dnsmasq-dhcp[26133]: DHCPACK(br-lan) 192.168.100.145 80:65:99:a3:10:4c RoomSense_1

Sat Sep 7 18:58:23 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c IEEE 802.11: associated (aid 1) Sat Sep 7 18:58:23 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c RADIUS: starting accounting session C8406E9FDE8ECE90 Sat Sep 7 18:58:23 2024 daemon.info hostapd: wifi2g: STA 80:65:99:a3:10:4c WPA: pairwise key handshake completed (RSN) Sat Sep 7 18:58:23 2024 daemon.notice hostapd: wifi2g: EAPOL-4WAY-HS-COMPLETED 80:65:99:a3:10:4c Sat Sep 7 18:58:23 2024 daemon.info dnsmasq-dhcp[26133]: DHCPDISCOVER(br-lan) 80:65:99:a3:10:4c Sat Sep 7 18:58:23 2024 daemon.info dnsmasq-dhcp[26133]: DHCPOFFER(br-lan) 192.168.100.145 80:65:99:a3:10:4c Sat Sep 7 18:58:23 2024 daemon.info dnsmasq-dhcp[26133]: DHCPREQUEST(br-lan) 192.168.100.145 80:65:99:a3:10:4c Sat Sep 7 18:58:23 2024 daemon.info dnsmasq-dhcp[26133]: DHCPACK(br-lan) 192.168.100.145 80:65:99:a3:10:4c RoomSense_1

roomsense commented 1 month ago

Hello, After several ( I mean multiple 10x) reboots, rebooting all the routers (it is a mesh network) and re-locating this roomSense to another room (it was co-located with my 2nd roomSense) I have it online and upgraded to the latest firmware. I really cannot determine what "fixed" it though I feel it is just luck on the roomSense reboots)

A couple things to note

  • . This roomSense module still has issues connecting to the network, it will associate, discover, offer, request and Ack but then follow the same sequence again about 7 secs later. I seems If I just leave it alone and go do something else it will eventually accept its address, quiet down and get to work. My other roomSense module does not exhibit this behavior.

-. This roomSense module always displays a distance value > 0 even though there is no movement in the room - my othere roomsense displays 0 distance when there is no movement in the room. I have both manualy calibrated both and used the auto calibration method, pretty much the same results for both.

I have quite a few espx devices in my home network and 2 work test networks, none of these exhibit this behavior though Blink was problematic at some time in the past but that is resolved now.

All WiFi settings are fine, all other devices (2.4, 5 and 6g) connect fine as well as WiFi6 and Wifi7.

Let me know if I can provide any more information, and I appreaciate the help! best -trent

@trentbrown13 If I understood correctly one of your units is working fine while another has connectivity issues, can you identify what might differ between them? (Firmware version, location, etc.) Are they set to use dynamic or static IP addresses? It could be an IP conflict causing the issue. To ensure they don't interfere with each other, try keeping one unit off and see how the other performs.

Regarding the distance, the unit typically locks onto the last value before the room becomes unoccupied. However, the distance reading is invalid when the room is empty.

trentbrown13 commented 1 month ago

Non_Working RS.txt Working RS.txt Sorry for the long delay before replying - work and life stuff

Yes, you understand correctly, one is working fine, the other has connectivity issues that I have never seen before (I develop and test home routers for a large company and many of my client tools incorporate expressif esp8266 and esp32 devices).

In answer to your questions: 1: Both RS modules use dynamic IP addressing, and I have tried both standard dhcp and static dhcp addressing. There is no IP conflict, I have checked.

2: I tried keeping one units off to see how the other performs - same result, ie one gets an address immediatly, the other 'hesitates' for a long time.

My WiFi network is a mesh network, i have tried with both RS modules in the same room close an AP and in different rooms both close to the respective AP.

I can work with this for now though eventually I would like both comming online in about the same period of time as I am looking at coordinating both PS readings via MQTT.

thank you again!

david-sasy commented 1 month ago

I have also seen this issue on two of our three units. We also use UniFi APs. One of the Roomsense units is about 2m from a UniFi U6-Enterprise and experienced the issue. The other is about 6m from a UniFi NanoHD. No power outages have been recorded by our UPSes.

Symptom: Lost connection from the network. Solid blue light.

Workaround: Connect to Roomsense SSID, re-enter WiFi details and click connect.

Mitigation: Created a binary sensor template for each unit to monitor the amount of time since the last update of the light sensor as that is usually at least once a second. If it hasn't updated for more than 60 seconds, the helper then changes from OK (0) to Problem (1).

{{- (as_timestamp(now()) - as_timestamp(states.sensor.roomsense_iq_1_light.last_updated)) > 60 -}}

There might be a better way of doing this, but I'm pretty new to this ecosystem.

roomsense commented 1 month ago

Non_Working RS.txt Working RS.txt Sorry for the long delay before replying - work and life stuff

Yes, you understand correctly, one is working fine, the other has connectivity issues that I have never seen before (I develop and test home routers for a large company and many of my client tools incorporate expressif esp8266 and esp32 devices).

In answer to your questions: 1: Both RS modules use dynamic IP addressing, and I have tried both standard dhcp and static dhcp addressing. There is no IP conflict, I have checked.

2: I tried keeping one units off to see how the other performs - same result, ie one gets an address immediatly, the other 'hesitates' for a long time.

My WiFi network is a mesh network, i have tried with both RS modules in the same room close an AP and in different rooms both close to the respective AP.

I can work with this for now though eventually I would like both comming online in about the same period of time as I am looking at coordinating both PS readings via MQTT.

thank you again!

@trentbrown13 So, if you have two RoomSense units, with one connecting to Wi-Fi without issues and the other struggling, can you think of any differences between them? Perhaps the firmware version or their location?

roomsense commented 1 month ago

I have also seen this issue on two of our three units. We also use UniFi APs. One of the Roomsense units is about 2m from a UniFi U6-Enterprise and experienced the issue. The other is about 6m from a UniFi NanoHD. No power outages have been recorded by our UPSes.

Symptom: Lost connection from the network. Solid blue light.

Workaround: Connect to Roomsense SSID, re-enter WiFi details and click connect.

Mitigation: Created a binary sensor template for each unit to monitor the amount of time since the last update of the light sensor as that is usually at least once a second. If it hasn't updated for more than 60 seconds, the helper then changes from OK (0) to Problem (1).

{{- (as_timestamp(now()) - as_timestamp(states.sensor.roomsense_iq_1_light.last_updated)) > 60 -}}

There might be a better way of doing this, but I'm pretty new to this ecosystem.

@david-sasy I'm not sure if your issues is related to wifi connection because, a solid blue light indicates the room is vacant. The LED will flash blue and orange if there's a Wi-Fi disconnection.

david-sasy commented 1 month ago

@david-sasy I'm not sure if your issues is related to wifi connection because, a solid blue light indicates the room is vacant. The LED will flash blue and orange if there's a Wi-Fi disconnection.

Perhaps it was just a lockup of the device. The light stayed constant blue even with people within the range of the sensor and it had disconnected from the network. Either way, I see now that this is different to the issue reported by @Fronty72. If it occurs again, I'll open a specific issue with more detailed information.

gabeguz commented 2 weeks ago

I have this same issue. If I restart my wifi access point, all my roomsense devices begin flashing blue and never stop. It's like they are stuck looking for the MQTT broker and are unable to re-connect to the access point. Rebooting them fixes the issue. When they are flashing blue they are not connected to my access point and they are unreachable on the local wifi network.