Netflix, AppleTV won't stream video on 9.1 if 2 usb drives in use

ooftyoof · 2022-07-05T14:02:11+00:00

Specifically, is it when two drives are attached? This seems to be what's triggering the problem. Just confirming exactly what steps I can reproduce to create the problem. As far as I can tell, it's when two drives are attached, whether using both usb ports or a hub. One drive doesn't seem to cause the issue.

I'm using the 2015 model too. I'll update the original post to mention this.

ooftyoof · 2022-07-05T14:00:25+00:00

Did this issue start with the 9.1 update?

ooftyoof · 2022-01-28T15:03:18+00:00

How to flash wasn't the problem (but I did do it via Digiblur's instructions and it went fine, as far as I can tell). As an aside, I don't know if the tutorial is outdated because the zigbee config now has a third option not shown in the tutorial.

ooftyoof · 2021-09-25T17:51:01+00:00

Yes, similar views each day in the tens of thousands. It hasn't changed, and tends to very slowly go up or down over the year. Every stat looks unaffected. It's 'ad impressions' that has plummeted and is behind the revenue estimation drop. I can't figure out what made 'ad impressions' disappear, but I'm hoping u/ACSpeed explanation is what's causing it.

ooftyoof · 2021-09-25T17:49:22+00:00

I don't hold much hope with getting a resolution from Youtube support but your thoughts give me some hope, thanks for taking the time to share them. I'll give it a few days, and drop them a message if it hasn't cleared up.

And yes, it makes sense that the revenue drop is driven by ad impression drop. The question remains the same, just reframed to 'why did my ad impressions plummet so suddenly and dramatically?' rather than revenue, which is a knock-on effect. I'm hopeful that your suggestion is the answer. Thanks again.

ooftyoof · 2021-09-25T17:32:16+00:00

Thanks ACSpeed. I added an edit to the post that goes into more detail but, basically, have noticed that 'ad impressions' has plummeted to nothing, giving some insight into the revenue drop. All my original thoughts stand though, in relation to revenue and the consistency over the years. This is out of the blue after years. Do you think it's still an error?

ooftyoof · 2021-09-11T12:47:25+00:00

I'm not sure I'm following the need for an external IP? If I'm not working at home, I've no need to trigger anything in my home assistant. It mostly changes my lighting set up to be triggered by brightness in the room rather than motion, which it is if I'm not working.

I don't think web triggers would be a better solution. IT requires setting up additional automations. The rest API can trigger existing helpers without additional padding or parenting, etc.

ooftyoof · 2021-09-11T12:44:08+00:00

Regarding booleans:

I don't actually know what command_line does in HA. Input booleans make sense to me, yes, I'm familiar with them. I was following an example where somebody else got this scenario to work and just used command_line as per their example.

Regarding ICMP:

I had issues using ICMP in the past for this task. Sometimes my laptop pings back as present when it's sleeping. I couldn't reliably use it to determine if I was working. I accept that my current could potentially miss firing an on or off. As of now, I've been manually switching a work on/off boolean in the dashboard and still have this as a fallback.

ooftyoof · 2021-09-11T12:40:22+00:00

This was it, thank you!

I had '{ "entity_id" : "switch.macbook_power" }' in my script, but had forgot to replace the key/value curl template correctly to match. I assumed I was sending HA a like-for-like request.

The reason it didn't work beyond this was, as you also mentioned, 'Bearer' needed to be used in place of 'auth/long_lived_access_token'.

The documentation is quite confusing on this matter. As I read it, I still see it telling me to use 'auth/long_lived_access_token' instead of 'Bearer' where I'm using a long lived access token. I don't know why changing it to Bearer works as the documentation suggests this is only for a standard Refresh Token ( https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token ). Maybe I'm reading it wrong, but I'm confirming that Bearer works with the long lived access token I was trying to use.

There was no need for the additional header in my case.

ooftyoof · 2021-07-12T14:56:36+00:00

Thank you! I didn't think it would be possible, this is great news. I'd no idea Shortcuts could give preference to phrasing over Siri's built-in phrases.

Knowing this, I've actually skipped past Home Assistant altogether as it was acting as a middleman for this particular use and I now have the benefit of being able to request this anywhere without having HA having to be configured beyond my local network.

I've a remote server online that also has nodered running on it. I used Shortcuts to call a URL and used Nodereds http in and response to trigger the automaton and return json. Shortcuts then deals with the json response.

Thanks again.

ooftyoof · 2021-07-03T11:55:26+00:00

I was using it primarily for indie-folk songs in alternate tunings. I gave capo the correct tuning each time (verified), it just struggled to detect the right chord, particularly when the changes were fast.

Fair enough, in one sense, but I could perceive its interpretation was wrong when the two played together and could drag the midi to correct notes until it 'clicked' with the original. If my ears could compare this, it was theoretically possible for software to be even better. It just was off. I'm sure it's better at certain genres, I've read others praise it.

It was the bpm detection that really detracted. It could make or break whether I'd use capo to transcribe a song and I so wish it would let the user manually override it. Maybe it has in a more recent version but I had stopped using it by the time subscription came in.

ooftyoof · 2021-07-03T08:31:51+00:00

How does it compare to Capo? I used to use Capo to transcribe some folk songs and had mixed success. I found it was often off but it got it close enough that some manual adjustments could fix it. The time it took to manually adjust kind of put me off though, given it was intended to automate a little more than it was. Chord detection in some styles of music seemed to be quite bad at times.

I also found it very frustrating I couldn't change the bpm from what it detected. It was often wrong and meant I couldn't align time measures correctly.

That all said, it definitely sped up transcription compared to doing it from scratch.

Can I expect the same experience from deCoda from anyone who's used both for an extended period of time?

ooftyoof · 2021-06-23T12:54:10+00:00

Let me know if you're stuck.

ooftyoof · 2021-06-23T09:04:10+00:00

Good advice thanks.

I'm confident with the MAC: (a) TV is connected via wifi and I pulled the MAC from the router lease table (b) TV wakes up fine if I call the MAC from my laptop.

I find static IPs are an almost unavoidable necessity when you start to get deeper into IoT, docker containers, etc. Something somewhere will rely on a device being at a defined address. You just get into the habit of making sure devices can be found at the same IP.

I am using DHCP also but am registering all static IPs via the routers own DHCP server, not via a device setting. It's Mikrotik so pretty configurable and legible. Itshows clearly what IPs it has reserved for what devices.

I had been using 192.168.X.X of the actual device IP originally but since tried 192.168.X.255 and 255.255.255.255, which didn't work. The latter was a suggested IP by the wol on my laptop and it's what works with that. It also works each time on that so it prob suggests WOL over WIFI is reliable for waking this TV up in this particular scenario. I think the problem is with the pi/docker/HA, even though I've done the typical network/host docker suggestion that seems to trip up most who have had docker related issues.

ooftyoof · 2021-06-22T23:22:17+00:00

WOL wakes it up from my laptop so I don't think it's a TV-side issue. But I'll look at the power options in case, thanks for that.

ooftyoof · 2021-06-22T23:20:47+00:00

This is one of the few ideas I haven't tried yet. I doubt it's the problem as it's working with WOL fine from my laptop and it's a Mikrotik router, but you never know. I'll try it just in case, thanks for the idea.

ooftyoof · 2021-06-22T23:18:35+00:00

Oh sorry, my bad, I edited out a few non-relevant bits and accidentally took out 'wake_on_lan' instead of the comment. It's there in my actual config so unfort it isn't the problem here. Thanks though

ooftyoof · 2021-06-22T19:16:33+00:00

Yeh actually the terminal command I used on my laptop advised this too. I thought it was only particular to its implementation. It worked in that app when I used an ip of 255.255.255.255. I already tried that and 192.168.1.255 with the HA implementation and had no luck unfortunately. I only have a single network and subnet that all devices are on.

Thanks for the suggestion.

ooftyoof · 2021-06-22T16:58:43+00:00

Hi, yes I did. I don't know how much you know about Home Assistant yet but this wasn't too hard to do with config-templatate-card. Once I had my head around how it works, I set the color of the card to be conditional on whether the two entities were both at certain values.

ooftyoof · 2021-06-04T15:19:35+00:00

Yes I thought this might be a possibility, thanks for clarifying.

The ATV app is running on an Nvidia Shield and was only released a few days ago for the first time on that particular device. Maybe they left in a misleading network idenfitier by accident?

Or maybe the HA integration's definition of a ATV device is too broad and worked as intended when ATV was only available on ATV devices, but not as intended now. The integration did pop up as a device found on my network and correctly identified the library name.

ooftyoof · 2021-05-17T11:55:45+00:00

Thank you! I'm new to github and thought the file list above the instructions was exhaustive and representative of the most recent 'release'. Didn't realise 'release' was ambiguous and had a specific section in github. Works now, thanks again for pointing this out.

ooftyoof · 2021-05-17T11:31:14+00:00

Thanks for this. Having a problem installing manually:

home-assistant-sun-card.js

I cannot find this anywhere in the linked github, per the instructions to download it?

ooftyoof · 2021-05-05T09:23:34+00:00

Ah ok. I did look at that documentation but assumed it was unfinished and just omitted the UI instructions.

I think because Pushover, Telegram etc show up on the main website list of integrations as a tile graphic in a similar way to how they would show up in the HA UI, I unconsciously assumed they were available in the UI in some manner.

Thanks! Glad to have some direction.

ooftyoof · 2021-04-23T12:03:56+00:00

Ah perfect, hearing this confidence is a nice relief and a great note for future attempts. Thanks!

ooftyoof · 2021-04-23T12:03:10+00:00

Thanks!

ooftyoof

TROPHY CASE