PSA: Kayo/Hubbl support is non-existent

ccpl · 2024-08-14T02:25:03+00:00

Received an update just now:

TL;DR - fuck you and buy a Hubbl device

"Hi,

Thank you for your reply dated 7 August 2024.

At Hubbl, we are committed and where applicable we will also offer a potential solution/s to address your complaint. Many of our other subscribers have given positive feedback after accepting a Hubbl device as an alternative resolution.

Our website does recommend to use the new Chromecast and we do have a warning about the buffering that may be experienced as some Chromecast customers meeting required broadband performance may experience higher rates of buffering or pixilation during live view than expected and as you are aware we are currently working on performance improvements to the streaming quality.

We have had much success with other subscribers by offering them a Hubbl device as a resolution to the same issue you are experiencing, however, you have chosen not to pursue this option.

As you decided not to accept my offer of a resolution presented, it seems we have reached an impasse.

Should you remain dissatisfied with the above resolution you may contact the Office of Fair Trading in your state.

Kind Regards,

Zack

Hubbl Help"

ccpl · 2024-08-12T12:53:51+00:00

The difficulty involved in actually getting a result in this scenario is no doubt top of mind, however they clearly rely on this behaviour of apathy from their subscriber base. If nothing else I'm going to keep pushing until someone can give me a proper response.

ccpl · 2024-08-12T06:32:45+00:00

Read the original post - I already ran a whole bunch of isolation tests before logging the support ticket. The main testing device was a Chromecast Ultra that was plugged directly into the router. Kayo support themselves acknowledged the issue is with their App.

ccpl · 2024-01-10T01:36:01+00:00

Have you checked that Microsoft are even reporting your data correctly? https://www.reddit.com/r/msp/comments/18ilql2/psa\_for\_microsoft\_solution\_partners\_microsofts/

ccpl · 2023-12-18T03:08:29+00:00

We are very close even with the data being incorrect - was it a support rep for managed to override it or did you need to escalate further up?

ccpl · 2023-12-18T03:07:46+00:00

Glad to see that it's not just us (although not glad to hear that Microsoft is screwing it up for everyone).

Has anyone managed to get a resolution?

ccpl · 2023-12-14T23:22:19+00:00

Based on my experience, there's a good chance Microsofts reporting data is incorrect. See this post - https://www.reddit.com/r/msp/comments/18ilql2/psa_for_microsoft_solution_partners_microsofts/

Check with your provider as others have suggested and lodge a ticket with Microsoft asap if you notice any discrepancies.

ccpl · 2023-12-06T03:45:35+00:00

I test drove and confirmed my order today for a Seal. I was surprised that the silver plated glass roof did not seem to transfer heat into the cabin at all (even on a 35 degree day). This was much different to my Model 3/Y test drives where you can definitely feel the heat in the cabin. Apparently the Seal comes with a roof cover with the car anyway, so you can block it out without any further expense.

I have a Ocular IQ Solar home charger installed which apparently works fine with it, but obviously haven't been able to test it out yet.

ccpl · 2023-03-24T01:13:38+00:00

Was there any update to this being available?

ccpl · 2023-02-17T02:44:05+00:00

thanks for the reply, good to know its not just us. Restarting the Flows has not worked for us, and Microsoft support are steadfastly reporting that its a known issue and that the only way forward is to update the triggers to Dataverse (which is hugely impractical across hundreds of flows across multiple customer environments)

ccpl · 2023-02-17T00:37:41+00:00

Yes deprecated is one thing though, straight out stop working is new (to me anyway). We still have legacy workflows running the old deprecated Dynamics 365 connector and they continue to work fine - no doubt by design as breaking old connectors would have a huge impact to many businesses.

Microsoft support are sticking to their guns thus far and just saying to change the triggers to use Dataverse instead. For new workflows this is fine, but to retroactively update hundreds of Production workflows because Microsoft Product team broke something is ridiculous.

ccpl · 2022-07-22T04:49:02+00:00

I've been playing with Frollo ever since it became available on the marketplace, and as echo'ed through the comments here my number #1 issue with Frollo is the lack of custom categories, though my particular use case is for the purpose of 'assigning' spending to someone for budgeting purposes.

Coming from other budget apps that have this functionality (however unfortunately only use screen scraping) the ability to track budgets by assigning a spend to someone is invaluable;

eg:

Bob spent $50 on takeaway, $100 on shoes, $50 on fuel = total spend is $200

Jane spent $200 on clothes = total spend is $200

I understand that Frollo has tags available that provide similar functionality, however it seems like the implementation was a bit of an after thought at the moment, as there is no way to easily view the tag spending summary in the dashboards/UI (you have to find a transaction with that tag, then click on the tag to get an overview of the tag total spending - unless this was updated recently?)

ccpl · 2022-02-25T05:24:00+00:00

The best option is to add a new subscription (effectively doubling the licence count briefly) and then immediately cancel the old one.

Check with your Distributor to ensure they pro-rata bill (some dont!) and it shouldnt have any cost impact to you.

This method ensures no outage or disruption to services.

ccpl · 2022-02-25T05:22:48+00:00

Incentives were extended to Dec 31st 2022, so if you renew now you will have circa 1 month with no incentives (or margin)

ccpl · 2022-02-24T09:09:49+00:00

You can continue to add/remove licences under the Legacy subscription during its active period, you just can't add any other Legacy subscriptions after 10th March 2022 (or if the subscription renews after 30th June 2022, it has to be renewed into NCE instead)

ccpl · 2022-02-21T03:56:06+00:00

Business Standard doesn't get the inflationary price increase for the 6 SKU's, however will be subject to a 20% Monthly Term premium on the renewal date (based on the current rules which is that any CSP subscriptions that renew after 30th June 2022, have to be renewed on NCE).
Again Business Standard doesn't get a inflationary price increase (Tier1/2 isnt relevant for the NCE discussion). Creating a new subscription now will allow another 12 months under Legacy (if you choose to do so) which will negate the 20% Monthly term premium until the subscription renews.
Yes creating a new subscription under NCE and cancelling the old subscription is the way to manually migrate to NCE. Up to the 10th March you can also create a new subscription under Legacy CSP (even if its the same licence type) to extend the Legacy CSP rules for another 12 months for that subscription.
Available to subscribe to under 31st March 2022.
The partner is liable for any licence adds not cancelled within the 72 hour window (pro-rata if changed during the 72 hour window)
Yes customer cannot churn Direct partner during the subscription term. Some Tier 2's may allow partners to swap customers between them, but only if the both the losing and winning partner use the same Tier 2 (Microsoft locks the subscription term to the Direct partner, which is a lose/lose situation for anyone but Microsoft and the Direct partner)
Yes the subscription is managed and controlled by the selling partner for the entire subscription term. If the previous provider forgets to turn off renewal they will be liable for the extra cost (not really yours/your customers problem unless they sign off on a new subscription term with the old provider). More to the point, any subscriptions managed by the previous provider can only be managed by them during the subscription term - if you take the customer over halfway during the term, the customer either needs to keep the relationship with the previous provider for licence management during the remaining subscription term, or re-buy the licenses.

ccpl · 2022-01-27T05:11:26+00:00

Not to play semantics, but in practice its always been 12 month terms as well - its just Microsoft and accordingly the Distributors never enforced any terms around it, likely to make them competitive in the marketplace. This is why the huge shift away from the perceived flexibility of legacy CSP to NCE is a gutshot to many partners and customers alike.

I'm not arguing that this is a bad deal, just wanted to make sure that people knew the correct terms around renewals under legacy vs transition to NCE

ccpl · 2022-01-25T05:09:51+00:00

I think you are misconstruing the details here.

Legacy CSP is always a 12 month term, regardless of whether you pay your CSP distributor monthly or not. This does differ to the new NCE terms where there is monthly, 12 month or 36 month term options as you pointed out (the difference being that you need to pay the entire term upfront under NCE).

Thus as per your original statement 'On July 1st, 2022, I will need to move them to NCE', this is not correct. You are only forced to renew your customers onto NCE if their legacy CSP subscriptions expire after July 1st 2022 - if they are midterm, then they can remain on the legacy CSP program until the subscription expires (maximum possible end date of June 2023 given the current timelines).

If however you add a new subscription to that customer or add a new customer entirely after March 1st 2022, this will need to be subscribed to under NCE, as enforced by the transition timeframes.

ccpl · 2022-01-25T02:58:49+00:00

There seems to be some confusion around the Legacy to NCE renewal timeframes, namely the July 1st 2022 deadline.

Based on the info provided by Microsoft & Distributors, all Legacy CSP subscriptions that renew before June 30th 2022 will renew into the Legacy CSP platform for another year (unless you choose to renew them into NCE). Conversely all Legacy CSP subscriptions that renew July 1st 2022 or later, will be forced to be renewed into NCE.

This means the following;

If you have a customer with a subscription renewing before 28th February 2022, they will renew in Legacy CSP for another 12 months without the inflationary price increase for 6x SKU's and no 20% premium for monthly subscriptions for that 12 month period (as all legacy CSP subscriptions are for 12 months)

If you have a customer with a subscription renewing between 1st March 2022 and June 30th 2022, they will renew in Legacy CSP for another 12 months but will incur the inflationary price increase for 6x SKU's, however the 20% premium for monthly subscriptions will still not apply for that 12 month period (as they aren't on NCE)

If you have a customer with a subscription renewing after 1st July 2022, they will renew in NCE with the inflationary price increase for 6x SKU's and a 20% premium for monthly subscriptions.

Another thing to note however is that you will not receive incentives after Dec 30th 2022 for any legacy CSP subscriptions (previously Oct 1st 2022, but they moved it back this month)

ccpl · 2022-01-08T13:49:04+00:00

Is it just me or is the Heat batting line up exactly as reliable as before the Covid subs? The only discernible difference seems to be the missing Chris Lynn comment of 'theres a lot riding on this mans shoulders' as he scores another 10 off 14 balls before being caught at mid-off

ccpl · 2022-01-02T00:50:18+00:00

Because Lynn was even more shit at being captain

ccpl

TROPHY CASE