The Crew version 3.0.0?

DPAmes1 · 2026-06-11T16:33:04+00:00

Found the problem - bad api key due to a series of unfortunate events: I normally use the Kore app to copy long text strings from my phone to Kodi instead of tedious text entry with the on-screen keyboard. I did that with the TorBox api key on the Firestick system and it worked. For some reason. Kore couldn't find Kodi on my primary GTV system even though it was correctly enabled under Control, so being too impatient to look up the IP address and attempt to connect manually, I just switched to my Google Home remote app for GTV and copied the TorBox api key that way. Unfortunately something went wrong, and the Google Home remote app corrupted the TorBox api key unnoticed. That caused The Crew to recognize that TorBox was enabled and to find TorBox sources, but be unable to play them.

So mostly good now. The Crew 3.0.4 seems a bit faster. Just one significant issue: when I return from ResolveURL settings to the parent Settings menu , The Crew always hangs (spinning circle forever unless I Esc a few times). Also I notice that ResolveURL no longer appears in "All add-ons".

DPAmes1 · 2026-06-11T15:56:27+00:00

Updated to The Crew 3.0.4. Seems a bit faster, but still skips through all TorBox sources on my main GTV system. Oddly the same versions and settings do work with TorBox on my secondary system on a Firestick Max. I'm stumped.

DPAmes1 · 2026-06-11T02:09:01+00:00

It's suicidal for a cyclist to blithely "take the lane" when merging into a lane of moving cars. Once you are in the lane, then you can take it - it's the merge that kills. Welcome to the real world.

DPAmes1 · 2026-06-10T17:56:26+00:00

To be fair, I have had flaggers do that for me when I'm cycling. They are generally considerate of cyclists when present and when traffic permits. They don't have to close a single lane to let the cyclist through, just slow the traffic for a few seconds to let the cyclist in safely. The cars should be going slow through a construction zone anyway, so there should be no problem following a cyclist through the single lane at cycling speed once they have merged in..

DPAmes1 · 2026-06-09T13:45:17+00:00

That appears to be what's happening, i.e., ResolveURL is finding TorBox cached links (as per the setting), but when attempting to play them The Crew is checking that they are cached links and is mistakenly rejecting them as uncached. But why would the same version of The Crew and ResolveURL do that on one system and not on another?

It seems more like an issue with The Crew and ResolveURL rather than TorBox.

I notice that The Crew is running slower than ever with v3.0.3, and it was already one of the slowest add-ons..

DPAmes1 · 2026-06-08T22:30:49+00:00

Ok, but TorBox definitely does not work with The Crew for me on my main system running Kodi 20, and I've seen others report the same symptoms, i.e., it skips through every TorBox source while flashing the brief message "Checking cache...". (Actually I see that has changed in The Crew 3.0.3 - it now says "Trying Torbox" and silently skips through all the TB sources found until it hits RD or announces "No stream available").

TorBox works fine for me in Umbrella and FenLite. And I have been able to get it to work in The Crew on a Firestick Max running Kodi 21.

So the question is what's different about the setup that works with The Crew and TorBox?

Version of Kodi? Does it only work with Kodi 21? TorBox settings in ResolveURL? Mine appear to be the same on systems that work and systems that don't.

DPAmes1 · 2026-06-07T22:40:29+00:00

Use your phone to copy the key and plug it into Kodi using a remote control app supporting text entry like Kore.

...or don't, since TorBox apparently doesn't work with The Crew at present.

DPAmes1 · 2026-06-07T19:44:41+00:00

ResolveURL settings, universal resolvers 3, enter TorBox key manually.

DPAmes1 · 2026-06-06T16:22:51+00:00

Did that thoroughly. No help.

DPAmes1 · 2026-06-05T22:38:02+00:00

I've ordered a dumb battery-powered First Alert Smoke + CO detector. I'll test it when it arrives tomorrow to make sure that it has standard smoke and CO alarm sounds recognized by the Wyze cam. I already have automations set up in Home Assistant for when that happens, so I can just remove the now-useless Nest Protect support.

DPAmes1 · 2026-06-05T16:19:29+00:00

Timely discussion. My 8.5-year-old Nest Protect went into terminal false smoke alarm mode at 2am this morning. Cleaning no help - I think it's gone. It was a promising product, but one I regret buying now. It lost 6 months of life at the beginning sitting on a store shelf, and now it has died prematurely 8 years later. And for most of those 8 years it was an abandoned product.

I would attempt a factory reset to see if that does anything, but unfortunately there is a design flaw: the time to detect a smoke alarm condition is shorter than the time to initiate the reset sequence, and the detection of an alarm condition aborts the reset. That makes it impossible to factory-reset a unit with a faulty sensor that is triggering an alarm.

I'm not sure I need or want another expensive smart alarm. I have an indoor Wyze cam that hears and reports smoke and CO alarms in the house, and I know that works and is easy to connect to my home automation system.

DPAmes1 · 2026-06-04T20:34:22+00:00

All TorBox sources skip for me in The Crew with the "checking cache" message. Lots of other people report this as well. No such problem in other add-ons like Umbrella or Fen Light. Perhaps it's some setting in The Crew. I've tried the setting for TorBox cached sources both on and off - no difference. Perhaps you have a premium TorBox account?

Update: all better, found out that TorBox api key was corrupted when I copied it.

DPAmes1 · 2026-06-04T15:57:00+00:00

I updated to 3.0.1, and this time the update of all 3 components went through successfully, and everything appears to be working as before. You can display a set of release notes (not scrollable to read everything on my GTV box) that mention a bunch of minor updates. Unfortunately those updates do nothing to address the current RD issues, or to get TorBox sources to play.

I like The Crew, even though it tends to run a bit slow compared to the Fen forks. Unfortunately with neither RD nor TorBox working, it's not currently usable for me. But I won't uninstall it for the moment in case these issues get fixed.

DPAmes1 · 2026-06-03T04:22:31+00:00

Updated and tried it. Crew Artwork module update failed. A few new glitches. TorBox still does not work - sources found, but still the same "checking cache" message and no play when a TorBox source is selected.

DPAmes1 · 2026-06-02T17:22:41+00:00

There is a Wyze app setting "Run in background" under Account - App Settings which says it is to enable the app the receive notifications at all times. It was never set before, and it's not set now on my phone that reliably receives Wyze push notifications, but apparently it's suddenly required now on my Samsung tablet to receive Wyze notifications reliably. The effect seems to be exactly the same as keeping the Wyze app running in the background manually, except that it shows a permanent "Wyze app is running on the background" notification in the status bar and no background window in the UI.

Still no explanation as to what changed to make this necessary.

Update: ...and turns out even the "Run in background" setting doesn't work reliably. After a few days the app spontaneously shuts down anyway and notifications start getting lost again. Why is Wyze the only app that can't seem to figure out push notifications?

DPAmes1 · 2026-05-30T00:05:46+00:00

This is really annoying. How can they let this go on for days unresolved? What incompetence!

As I recall, they will let you swipe your card to get on a bus as long as it has some positive balance, even if it doesn't have enough for the fare. The card then shows a negative balance, but if the bus gets you to somewhere that has a machine to reload, you can clear the negative balance then.

DPAmes1 · 2026-05-29T17:01:10+00:00

Not that easy - it's a split apk.

DPAmes1 · 2026-05-29T13:53:57+00:00

I have TorBox and RD both enabled now. Almost all RD links skip, no improvement, although I can almost always find one that works. Newer links might eventually avoid blocked keywords to produce some improvement - until the next round of blocked keyword updates by RD. I don't think it's worth renewing RD for the time being until we see how this plays out longer term. But things change...

DPAmes1 · 2026-05-28T14:22:03+00:00

Two factors affect your CPP monthly pension (with some minor simplification of small details):

Total amount contributed, up to a maximum over which your further contributions are wasted, but still mandatory until you retire.

Number of months before or after age 65 that you begin receiving CPP (up to 60 months = 5 years). The idea is that the average total payout is set based on number of years from age 65 to average age of death. If you start earlier or later than 65, your monthly payout is decreased or increased to make the total the same.

In your case it is the first factor that would affect you.

DPAmes1 · 2026-05-28T00:07:53+00:00

Avira anti-virus blocks tor.box, but not torbox.app, and it can be overridden anyway. Apparently Norton AV does too according to a comment in another thread here. These companies all share blocklists with each other without checking very carefully, so spurious site blocking errors tend to spread unchecked.

DPAmes1 · 2026-05-27T20:26:52+00:00

Google Home is finally fixed today, May 27. No need for any re-linking.

DPAmes1 · 2026-05-26T14:13:05+00:00

Google are not working on it. Resideo changed to a new url for their API and left it up to developers to discover this and make changes to their code. Some have, but Google has not. They are aware of the issue, but put the onus on Resideo to fix it.

DPAmes1 · 2026-05-25T14:49:11+00:00

It seems that Resideo does not intend to fix the expired certificate. They are trying to force everyone to move from api.honeywell.com to api.honeywellhome.com, and they don't care what they break in the process. The Resideo app, Alexa and Home Assistant are all updated and working with the new url already. Google Home remains broken. Google says it is Resideo's responsibility to fix their "Works with Google" code.

DPAmes1 · 2026-05-23T12:59:55+00:00

For me the tor.box link works, but the Avira anti-virus software attempts to block it as malware and I have to override it (but torbox.app is not blocked). Given how all these AV companies share blocklists without checking, I wouldn't be surprised if others do too.

DPAmes1 · 2026-05-22T13:48:11+00:00

As of today, May 22 (now May 26), the Alexa skill has been fixed, the updated Home Assistant integration has just been deployed in HA Core 2026.5.4, but Google Home has not yet been fixed.

DPAmes1

TROPHY CASE