Tagged: wifi connection
July 11, 2018 at 3:34 am #4542
recently my BHyve has had the same problem as many others and its proving very annoying. Randomly it will lose connection to WiFi and then reconnect randomly. There seems to be no particular reason for it other than there is Debug Firmware on the device(debug-0013).
Why is there debug firmware on my device? this makes no sense as debug is for troubleshooting. Can someone explain this?Spread the love!July 11, 2018 at 4:53 pm #4548rwzx3Participant
same here, every 2-3 days device goes offline and i have to power on/off very annoying that i have to keep an eye on it to make sure if its onlineSpread the love!July 12, 2018 at 5:55 pm #4578kreeveParticipant
New install yesterday, DEBUG firmware on it. Connected to wifi and it did download my initial test watering schedule, but since will not connect to wifi. I have rebooted both the router and b-hyve multiple times, repair with Bluetooth, and find the wifi and supply password. It says timeout. I have moved the wireless router to the kitchen just outside the garage where the controller is. Strong wifi signal. Did a reset on controller, still nothing. After 3 hours I gave up. Started coming the forums this morning, seeing similar issues with others. What to do?Spread the love!July 12, 2018 at 9:52 pm #4606
Hello everyone. The debug firmware is the default that our units are sent out of the factory with. Once it is connected to internet it can receive firmware updates. If you would provide me with your mac address I can do that for you. Also If you are able, edit your DNS settings on your router to 184.108.40.206 with 220.127.116.11 as a back-up for a more stable connection. If you’re having any other issues getting your device to connect just let me know.Spread the love!July 13, 2018 at 7:17 pm #4651
I would like to make a couple of observations.
First, I am at total loss to understand why a company would put DEBUG software on a consumer device in the field. By the very nature of DEBUG software it is ONLY designed to be used to troubleshoot problems under specific circumstances. If anyone at Orbit sees this, then you really need to ask some hard questions of who is developing your code and deploying it.
More generally speaking I have noticed something. When I am away from my house and connected to my works WiFi network, my device is always available. I never seem to have a connection issue. As soon as I get back to my house and connect to the same WiFi network as my device, I have connection issues. Not sure if this is meaningful, but I have now spotted this every day this week (5/5 days).
Can anyone else verify if they see the same?Spread the love!July 15, 2018 at 6:05 pm #4716SRodgersParticipant
I also have the Debug firmware and can’t get my unit back online after resetting. If I can manage to get the device reconnected please update me. If this doesn’t work I’ll have to trade up for a Rachio.
MAC Address: 44:67:55:40:a7:ec
Firmware Version: DEBUG-0013
Hardware Version: WT24-0001Spread the love!July 16, 2018 at 4:22 pm #4744wadegordenParticipant
My timer keeps disconnecting from WiFi every couple days. I have to unplug it and plug it back in to reconnect. If someone can help to resolve this issue that would be great.
Firmware version 18
Hardware version WT24-0001
MAC address 44:67:55:40:27:E1Spread the love!July 16, 2018 at 7:45 pm #4772
Now THERE is an interesting bit of info. The WT24-0001 timer for WADEGORD EN is Firmware 18 where others are DEBUG-0013…. seriously Orbit? Is there any possibility that you start putting some proper release management rigor behind your timers? Maybe some release notes somewhere?
From a philosophical perspective this is where a “free” service is starting to show problems. The initial cost of the unit has to cover not just the hardware development and software development but now has to cover the service in perpetuity. I suspect that Orbit never fully accounted for this and it is now hurting them.
After seeing how slowly Orbit is rolling out updates, how there is little to no release management and how these forums barely get touched by anyone, I am beginning to wonder whether Orbit should consider a nominal yearly fee to give its customers a good service. Maybe $20 a year after year one? Frankly, I would happily pay knowing that the service was properly managed and not about suddenly stop working and that we could expect fixes in a timely fashion.Spread the love!July 19, 2018 at 5:10 pm #4882
@wadegorden, your firmware is already up to date. You will want to edit your DNS settings on your router to 18.104.22.168 with 22.214.171.124 as a back-up for a more stable connection. There is not much else we can do from here outside of the firmware so if you continue to have problems please contact our product support line.
@SRodgers, I cannot update your firmware unless your timer is connected.Spread the love!July 19, 2018 at 5:13 pm #4883mrfirmwareParticipant
@RYAN I have noticed that at FW v18 my WT24-0001 is also losing WiFi connection almost daily. Power-cycling it immediately restores the connection. It never did that with the initial debug FW. When is v19 coming out and will it deal with this regression?
MAC Address: 44:67:55:40:66:4d
Thanks!Spread the love!July 19, 2018 at 5:38 pm #4885
hello mrfirmware, Currently I don’t have a date for when the next firmware version will be released for our indoor smart timers (hardware v WT24). Try editing your DNS settings on your router to 126.96.36.199 with 188.8.131.52 as a back-up. There is not much else I can do from here outside of firmware updates so if you continue to have problems please contact our product support line.Spread the love!July 19, 2018 at 5:44 pm #4886mrfirmwareParticipant
@RYAN I appreciate that having Google DNS is a good idea. I will make that change. However, this issue is that the WT24 is losing WiFi connectivity, not just internet connectivity. That is, it is not speaking to my router via WiFi radio. DNS does not come into the picture until *after* a WiFi connection is established. Do recall that with whatever Verizon FiOS default DNS I was using before FW v18 was installed I never had a single WiFi connection loss.Spread the love!July 20, 2018 at 3:51 pm #4961
Ryan… is there any way of rolling back the Firmware to anything prior to Debug-0013? Like a lot of people on this Forum, it looks like Debug-0013 is where the problems started. If you could roll back a device to the version immediately prior to Debug-0013, we should quickly be able to confirm whether this is Firmware related.
Also, changing DNS is not going to solve the problem. I have a business class Internet account (I work from home) and my DNS has not changed in 5 years. No other device (including my other BHyve timer, a wt25-0001 connected to the same WiFi network) has this problem.
I hate to harp on this but release notes showing the changes between whatever came before and Debug-0013 could give an indication of why this is happening.Spread the love!July 26, 2018 at 5:10 pm #5217tl319Participant
Wifi will not connect successfully. Device shows as connected to router, but exclamation point is flashing. Router shows that device is connected and can ping successfully. Tried hard reset, unplugged ribbon connector and re-connected. Changed DNS setting of router to 184.108.40.206 and 220.127.116.11.
MAC Address: 44:67:55:03:3F:8B
Firmware Version: DEBUG-0010
Hardware Version: WT25G2-0001
I need a solution.Spread the love!July 26, 2018 at 5:56 pm #5226
Hello TL319, Sorry but, I cannot update your timers firmware unless it’s connected. If the exclamation symbol is displayed that indicates that there is an issue with the router. This could just be some setting that is preventing the timer from fully connecting to your router. There is not much else I can do from here outside of firmware updates. So you may want to try calling your ISP, and our product support line.Spread the love!
- You must be logged in to reply to this topic.