Thought I’d post here as I opened a similar thread here:
I also have a Samsung TV and moved from a Vero to Vero2 recently. Everything worked OK with the Vero but the Vero2 doesn’t seem to register as an Anynet+ device. CEC doesn’t work, the Vero2 doesn’t appear in the TV list of Anynet+ devices and while the Vero2 is running, CEC on the other devices appears to have some issues. e.g. I can’t get any sound from my tv through to my home theatre system while the Vero2 is connected.
Sam I sent you a message with a url to a log file upload as requested on the other thread.
yes, I’ve had to power down and disconnect my vero when I’m not using it. It seems that all Anynet devices share the same HDMI signal path and if one device misbehaves they all get a bit confused.
I’m sure there’ll be a Sam along with good news shortly.
I’m really don’t know what happend over night, when TV was off. But absolutely the same problem appears to me again. TV off / Source changing and CEC Controls are gone and must reconnect manually again.
In the same way I tested again with device_type 1,2,3 and 4, but with no positive results.
The only interesting change on device_type 4 was that after an reboot of the pi3 the cec/anynet magically was connected with my samsung tv, but source changing or TV turn off/on leads to immediately disconnection of Anynet and needs again manual interaction.
It’s really a tricky problem. But I feel that the solution isn’t so far… the question is, what variable/trigger is to change in the right way, to get the former comfort with automatic Anynet connection.
I have Vero2 and Samsung TV.
When I power-cycle the TV, then I need to select source for the Vero2 again.
Also the button for the context-menu on my TV remote doesn’t work with Vero2.
(it worked fine with Rasp Pi with OSMC on the same TV).
Otherwise, everything fine with Vero2 and my Samsung TV.