You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have this working well on a raspberry pi zero w.
When the pi is connected to the HDMI port before being powered up, everything works well.
However, if HDMI is plugged in afterward the Pi has booted, the cec never initalises.
If I scan the bus using:
echo scan | cec-client -s -d 1
The adapter opens, and all works as expected.
So I tried adding the scan line to my supervisord script. When it restarts (with no HDMI plugged in) the adapter opens, and initalises MQTT. But if you plug in HDMI cable, it nevers finds a new device on the bus unless rebooted or scanned again.
Is this an issue with cec-mqtt-bridge or raspberry pi?
Thank you
The text was updated successfully, but these errors were encountered:
I have this working well on a raspberry pi zero w.
When the pi is connected to the HDMI port before being powered up, everything works well.
However, if HDMI is plugged in afterward the Pi has booted, the cec never initalises.
If I scan the bus using:
echo scan | cec-client -s -d 1
The adapter opens, and all works as expected.
So I tried adding the scan line to my supervisord script. When it restarts (with no HDMI plugged in) the adapter opens, and initalises MQTT. But if you plug in HDMI cable, it nevers finds a new device on the bus unless rebooted or scanned again.
Is this an issue with cec-mqtt-bridge or raspberry pi?
Thank you
The text was updated successfully, but these errors were encountered: