Forum Replies Created
-
Posts
-
I made a typo above and can’t edit my post, I have a Meraki MR33 that the device doesn’t work with, not a “wr33”.
As far as OG/Blynk, since the OS device would stay on the wifi as long as I kept the web page on my PC open (and it seemed to actively communicate with the device), I just thought maybe if it was actively talking to blynk servers every second or two, maybe that was keeping it alive.. I do remember having some similar issues getting the device set up the first time when I didn’t enter the blynk token to start, the second time I set it up and used the token right off the hop it seemed fine.
I ripped the MR33 out and put my ASUS OnHub back in and the connection has been rock solid now. Meraki support was unable to figure out any settings that would have caused any compatibility issues. The only thing I didn’t try on the Meraki was relaxing the WPA2-AES, or changing the SSID/key but things are working great now.
Not sure if this is a known issue or not, but when I would start the system and press/hold B1 after the logo showed to invoke a factory reset, the system would reboot and get stuck on a screen that says “Hold B3 to save” I tried holding it up to 30 seconds and nothing happens. It requires a power cycle to leave and get the OS device to boot up properly.
It’s definitely not an NTP issue now, device had perfect time even though it dropped off the network last night.
I have found out that on this AP, if I keep the web UI open on my pc to the device, it’ll happily stay on the wifi for hours without an issue. But if I close the browser and check in on the IP/app an hour or so later, the device isn’t on the network (it shows the IP/port on the screen still though if I press B1).
It looks like Opengarage uses the same platform as it’s base, is this true? I can’t figure out why my OG has been rock solid (farther away from the AP), but OS drops. Maybe because of it’s constant communication with blynk?
It appears the OS device just doesn’t like the MR33 access point. I connected the OS to my phone in hotspotAP mode and the connection was live for 3+ hours even after I had no browser tab open. I connected it back up to this Cisco AP and in less than 5 minutes after being rebooted it dropped the wifi association. Going to switch off of this Meraki AP and see how things go.
Yes, Firmware 2.1.9 (3)
I had some time to try to dig into this a bit tonight. I was unable to get into the system again, so power cycled it to get it on the wifi again.
I logged into the web interface and immediately noticed that the time was wrong again. I double checked that it was set to use my router (pfSense) for NTP which it was, so disabled, ntp, set the time, re-enabled NTP and submitted changes.
In searching around on the forums it seems like weather underground went away, so I decided to check that I’m getting weather service information. I also came across a post saying that ETo is the way to go now for calculating water when precipitation happens so I enabled that.
I left the unit logged into the web page for a few hours and came back to my system. I expected it to not respond, but it was still alive, but the time on the opensprinkler said it was 8am even though it was only just after midnight (Toronto time zone). I verified the time zone is set to -4 as it should be, just like on pfsense etc. I checked the NTP server on my firewall,using a test tool to make sure it’s responding and quickly realized that the NTP KoD option was rate limiting NTP requests, so I figured maybe there is some type of issue there and disabled it. In the meantime I set the NTP IP to 0.0.0.0 because I found another post saying that using this setting would force the system to use a default NTP pool, the clock sync’d as soon as I hit save, so I’ve switched it back now to use my firewall just to see if the time gets out of sync again, and if it does I’ll try going back to 0.0.0.0 to see if that helps. I’m thinking this has something to do with time sync only because every time it seems to be disconnected from the network, the time on the display is incorrect, and when it’s rebooted it is still wrong even though it appears to do an NTP sync at boot.
I have the same issue here, even updated to the latest firmware available. I have an OS 3.0 (I think) but it has a clear case, powered by an AC/DC adapter.
If I look at the logs on my WR33 meraki access point, when the unit isn’t responding, I can see “invalid credentials” for that wireless client.
I do not have this issue on my opengarage unit (mentioning because the setup screens for wifi are identical)
Perhaps it’s attempting to use a bad auth method during a key rotation or something? Not sure how to dig into the system logs to find a corresponding entry.
