April 17, 2018 at 3:06 am #1083
I have my bHyve linked with the Alexa skill to my Amazon Echo. When I ask the Amazon Echo what the next time for my bHyve to run is (which is 4/18 at 0730 pm – Wednesday Pacific Standard Time) it says “your next scheduled run time is oh four one nine at two thirty a.m.” I figured that the Alexa skill is listing what my next run time is according to GMT time which is 7 hours ahead of PST. Is there a way to fix this?Spread the love!April 18, 2018 at 1:23 pm #1104
Hello DJXPRESS, I am currently looking into this and I will let you know when I get updated.Spread the love!April 18, 2018 at 4:40 pm #1123
Can you provide me with the MAC ID of your timer?Spread the love!April 18, 2018 at 10:31 pm #1126
please provide me an email addressSpread the love!April 22, 2018 at 2:21 am #1156
email sent to supportSpread the love!April 23, 2018 at 4:49 pm #1188
Which email did you send your MAC ID to? The email to get directly to me is [email protected]Spread the love!April 23, 2018 at 4:53 pm #1191
I sent it to that email addressSpread the love!April 30, 2018 at 7:17 pm #1304grewingjrParticipant
I am in Wichita KS and am having the same issue. For me the time reported is 5 hours after the event happened, again GMT time.
Your chat support agent Robert T. was going to report this issue to your ‘server programmers’Spread the love!May 1, 2018 at 3:11 pm #1331
We are working on this right now. We appreciate your patience.Spread the love!May 4, 2018 at 11:02 am #1407
I have the same or similar problem. I’m in Baltimore, MD, which is in EDST. Timer is working fine, but my future 5:30am automatic start time is reported by Alexa is reported as 9:30am.Spread the love!May 4, 2018 at 4:39 pm #1414
I asked ask my iPhone Amazon app (which has Alexa built into it now): “Alexa, ask b-hyve when my lawn will be watered next.” She also reported 9:30am. The answer for my time zone should have been: 5:30am. So it is consistently, reporting the wrong time through Alexa for me. :-/
I should add that the time did execute at 5:30am this morning, so b-hyve is operating self-consistently otherwise.
I also just confirmed that 5:30am EDST is 9:30am GMT. So I believe you are right DJEXPRESS. Their app needs to take the date and time it gets from the b-hyve API and convert to to local Echo date and time before speaking it. Or they need to get it from b-hyve and use the home location of the actual b-hyve to determine which time zone to convert it to and then report the start time in the time zone the b-hyve lives in. The second is probably more useful. If I live in Baltimore and travel to LA and check on b-hyve to see when the next watering is with Alexa, I’d probably want it to say it’s schedule to start watering at 5:30AM EDST as opposed to 2:30AM PDT. I’m assuming that would be consistent with the interface as well, but I haven’t been in a different time zone yet to check. 😉Spread the love!May 9, 2018 at 4:44 pm #1573
Yes, that is correct. We are still working on finding out why it is reporting each unit in GMT.Spread the love!May 11, 2018 at 4:01 pm #1694
I switched to Smart Watering (instead of my manually scheduled situation I was reporting above) and noticed a different (but related issue) issue:
App currently shows 4 Smart watering events tomorrow starting at 5am. Good. Looking at the techsupport.orbitbhyve.com site for the device things generally seem to agree (i.e., programs say 4 waterings to start at 5am). However, the Next Watering Says: Programs at 02-07-2106 01:28. This is obviously an invalid value and perhaps is a special sentinel in the software to signify Smart Watering is in effect. Thought it should probably agree with the scheduled watering.
Sadly, this is the time of next watering reported by Alexa when I ask her. 🙁Spread the love!May 23, 2018 at 10:56 pm #2172
I’m finally getting the right answer from Alexa. I’m not sure exactly what fixed it. My firmware is 32. But, I believe it got corrected when I connected with Blue Tooth to the device. When I didn that, I received a message that the time in the faucet controller was way off. Perhaps it was sent to GMT event though
everything else wasn’t. It would seem that my device wasn’t really connected to the
Internet somehow, even though I could control it over WiFi and mobile internet. Anyway, I asked Alexa when itnwouldnwater next and finally it was correct, i.e. not GMT.Spread the love!May 24, 2018 at 3:09 am #2181
How did you connect via Bluetooth? My firmware is 10. Are you talking about the bHyve faucet control or the water sprinkler station/controller/timer? As my original post was regarding the 6 station Wifi sprinkler timer station.Spread the love!
- You must be logged in to reply to this topic.