ReachView beta v2.2.5

Have a couple Reach units back in the Shop for a refurb process so back to testing Beta. Here’s the latest from a systems integrator POV:

  • Setup Reach on a network with internet access so we can pull latest firmware and pass time sync. Upgrade process went really well. Smooth. Nice job!
  • Change Reach wireless network to match field network SSID and PSK. Shut down and move to Shop.
  • Bring Reach units back up in shop on field network with no internet. Failed Time Sync since we are indoors with no internet, and can not get to web interface. Could probably live with that if we assume they are going to work right once outside.
  • Here’s the issue: If you turn off the field network so the Reach units will broadcast their AP it does not do any good. Can not get them to assign an IP to a laptop trying to connect via Reach AP. Only solution seems to be provide time sync via antenna. So not sure if DHCP service is being blocked by time sync?
    -The other issue is if you have the Reach connected in an integrated system that powers up at same time: If the network is not available before Reach does it’s WiFi checks (the AP it connects to takes longer to boot), it will start to broadcast it’s AP and the only way to get it back on the right network is a power cycle of the Reach. A bit hard to do if it’s tucked inside an enclosure with no on/off specifically for the Reach. And can’t ssh for a reboot since it’s hung on failed time sync. Is there some way we can run a timer to restart the system checks if it’s hung on time sync? Say if no time sync after 30 seconds then reboot and try again?

I think the new Reach Beta works awesome if you have met all the requirements. But if something is not right, such as initial indoor setup, it becomes very hard to get back into the system for troubleshooting etc. Am I the only one having this issue?

Thanks!