Maybe this is part of the issue? Perhaps this commit was meant to be tagged 0.17.1? It's what I intended, but it seems the version number is off.
It all works great now on latest appletv:test, though I'm also getting Version: 0.16.1.
What will be the upgrade path if and when pyatv 0.18 is released? (admin said this will happen soon)
Thanks!
Let me know when that happens, and I'll build a new container.
Sure.
Built as bnhf/ah4c.appletv.test2. I set this up to install whatever version is considered current by pip3 -- which should be 0.18. If you could confirm that the container functions, along with it containing this most recent version, I'd appreciate it.
If everything looks good I'll build this again as :appletv
Looks good so far.
Container has 0.18 and tuning with no errors on my end!
1 Like
I just started this up and seems to be working good so far...
root@atvtuner:/opt# atvremote --version
atvremote 0.18.0
root@atvtuner:/opt#
No issues for last few hours...
On another note, I think I had mentioned in an earlier msg that suddenly the ATVs were turning on captioning everytime now. I figured out what was happening for me. For a long time I sent commands that would actually completely shut down the spectrum app when exiting. Apparently with one of the lastest Spectrum versions it looks like they don't remember your captioning settings if you close the app completely out on the ATVs.
Tested with just using "home" for stopping and it remembers your last state. But it goes right back to captions if you loose power or shut the app completely off. 
1 Like
This is done. New bnhf/ah4c:appletv built this morning -- so, I'll be deleting :appletv.test and :appletv.test2 shortly.
Now that :appletv is using a Dockerfile that's very close to :latest, I'm leaning towards merging these two. They will always need different start scripts though, which we'll handle with an env var like PYATV=true with a default of false.
1 Like
Can you explain this further? Do you mean that deployment will look at the PYATV tag to build the container, Or do you mean we will need to adjust our tuning scripts?
The idea is no changes for you -- other than needing to set an env var. That env var will determine which start script the container uses. This is not any of your scripts, this is the script the container uses when it starts. My thinking is, a single ah4c container that works with both ADB and ATV targets, will be easier to maintain. For the :appletv crowd, this should mean more up-to-date builds.
This is what I thought, it sounds great, and makes sense for maintainability.
Happy to deploy ah4c:latest in a test container using the new environment variable to test the merged code. Just say the word....
As usual - thanks for all you do!