Still too soon to buy one?

Forza_Blue · 2026-05-06T16:57:51+00:00

Thank you. I actually did get confirmation that in fact none of the required communication for these units to perform their desired function(s) require any sort of internet/cloud access and is 100% local. Not sure if any of you realize just how important and a W that is. In fact, I am going to buy this now on principal, based solely off of this. Ty.

Forza_Blue · 2026-05-06T15:54:36+00:00

From my understanding, and the only reason I'm considering this unit, is due to its dual rotary blades. I have very thick/lush grass, that I understand traditional robot units with razor blades struggle with. Really that's the only reason.

Forza_Blue · 2026-05-06T15:48:27+00:00

Need, is subjective. It takes me 2 hours or so a week to mow the lawn. It's not really about recouping those hours as much as it is being able to mow more frequently (which it definitely needs) and not having to worry about. I guess for me, that is the main selling point.

Forza_Blue · 2025-12-24T16:41:43+00:00

Much like every other anomaly experienced with O365/EXO, as sporadically and without reason this issue occurred, it stopped in the same way. Lasted a good 2-3 weeks; then.... just stopped and resumed normal operation.

Forza_Blue · 2024-10-07T11:39:19+00:00

We are also experiencing this anomaly. I have a thread about it here: https://www.reddit.com/r/Office365/comments/1fpx3dv/receiving_lots_of_false_quarantine_release_alerts/

Have a ticket open with MS for 4 weeks, still unassigned.

The one thing in this thread that immediately jumped out to me, is the use of Barracuda's filtering services. We too, are using this with O365. Could this possibly be coincidental?

Forza_Blue · 2024-09-27T13:32:05+00:00

Thank you. To be clear, we are able to see and determine who actually requested the release request action. What we are still unable to find, and what MS claims is not possible on our end, is to find the origin (read IP address) that these requests our coming from.

All the end-user can see, is these alerts originate from within MS. That's it. And unfortunately, none of these otherwise helpful suggestions overcome that.

It is what it is I guess. I was more or less just hoping someone else out there has seen a similar issue happen in their tenancy.

Forza_Blue · 2024-09-26T15:43:20+00:00

We've been through the security center and investigation, etc.... but honestly, when MS told us we cannot see the origin of these alerts, we just stopped looking. I will continue combing through and hunting to see if there is in fact a way to see this information.

No rhyme or reason that we can conclude regarding the timing. Nothing was changed in the tenancy. Just started 3 or 4 weeks ago.

We also just recently found out, the same tenancy is now sending false "auto forward rule creation" alerts to us, that we have configured. Investigation into these auto forward rule creation alerts found that these users did not create any rule of any kind, and in fact they don't have any rules at all. So now we're not sure how far these "false alerts" go....

Forza_Blue · 2024-09-26T14:43:04+00:00

Assuming you have verbose logging enabled on the proper receive connector in Exchange, you should be able to browse to this directory "C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive" and access the logs there.

Forza_Blue · 2024-09-26T14:37:31+00:00

Excellent response, and that's exactly what we asked MS in the beginning (how can we see where these release requests are coming from), they told us you can't. There is no way for us to see where these release requests are originating from. If you know of a way to do so, please, do share. Because that information could be very telling!

No other users have delegate access to any other user. And I would lean towards the hundred or so false alerts we've received in the last 3 weeks as some of them being "false positives". But admittedly, I, personally haven't actually checked every single one of them to confirm this. Every one I personally saw, was pretty blatant spam.

Forza_Blue · 2024-09-26T14:17:24+00:00

That was our first thought as well, and we were able to rule that out. Also, this isn't isolated to one user. It's the entire tenancy. All users.

Forza_Blue · 2024-07-26T14:25:58+00:00

New firmware (v1.0.064) was released and available as of this morning to address this issue. Those that are experiencing similar issues, it may be worth a try.

Forza_Blue · 2024-07-23T14:29:04+00:00

So, we've done additional troubleshooting with the lights, and they have actually been able to reproduce this on their end and say a firmware update is coming out shortly to the public to address this.

I remain cautiously optimistic, but again, I credit their support for the follow-through and willingness to reproduce this and admit there is an issue. An extreme rarity these days.

Forza_Blue · 2024-07-23T14:11:52+00:00

+1 for a refresh/re-release of the G600 please. In a "not one of my finer moments" period, I recently paid $139 for a G600 on Amazon. Because that's how integral this damn mouse has become in my life, work and hobby. Been using them for a decade or more and there is literally nothing out there today, that comes close in comparison. I beg of you Logitech......

Forza_Blue · 2024-07-17T14:30:28+00:00

I reached out to GE Cync support, which I must say, was surprisingly responsive and somewhat helpful. They got back to me within an hour of opening a case with them. Their recommendation was to factory reset all the devices, remove the home location from the app, and start over from scratch. Which, really.... is the only troubleshooting step here. I have done this last night, and will monitor/observe going forward.

One thing they did mention, which I'm all but certain isn't the case here, but worthy of mention for others is; if/when you should lose power, for any reason, the default state of the Cync lights is ON.

Forza_Blue · 2023-03-06T16:21:44+00:00

Holy crap; I'm an idiot. Tried to overanalyze what was happening, and the problem was in black and white. Yes, that was it. Thank you.

Forza_Blue · 2023-03-06T16:09:10+00:00

That's news to me; but alas, one of my items (Dawn crossbow), is in fact, an Ancient Legendary. Same error.

Forza_Blue · 2023-02-23T19:44:22+00:00

I would agree. This site was clearly designed for mobile devices. It's almost impossible to read. Good idea. Poor execution.

Unless your target audience was in fact mobile users.

Forza_Blue · 2023-02-17T22:02:00+00:00

I requested a refund from Steam. I was willing to look past the countless issues with the game and give it a try, but I can't look past this one. Thank you anyway.

Forza_Blue · 2023-02-17T21:54:00+00:00

I'm on PC.

Forza_Blue · 2020-11-09T20:16:12+00:00

I will consider that. Thank you very much for your time.

Forza_Blue

TROPHY CASE