Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Michael Schwingen <news-1513678000@discworld.dascon.de>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: tapping into Vaillant Ebus data
Date: 12 Feb 2025 20:48:38 GMT
Lines: 15
Message-ID: <slrnvqq296.sal.news-1513678000@a-tuin.ms.intern>
References: <vn5k3m$3manf$2@dont-email.me> <vnlp9t$7kav$1@dont-email.me>
 <vnrc5t$1f9qg$2@dont-email.me> <voi7r8$2ba43$1@dont-email.me>
X-Trace: individual.net SQlaGq22Vqd86phJCC/QAw4aNiLC4WuLIbVCTYafVC3khKvCEM
Cancel-Lock: sha1:91HDbVA7uXeU5cPLHb+3SpIWxdA= sha256:SFaFDyDsngk+Ea/giPnlcT0Ki/if5N8qWWohTs1YC/k=
User-Agent: slrn/1.0.3 (Linux)
Bytes: 1365

On 2025-02-12, Harry Bloomfield Esq <harry.m1byt@outlook.com> wrote:
> Both are working. What I didn't understand, about HDMI, was that the 
> display need to be on before the Rpi. Rpi 'talks' to the display, whilst 
> setting up, to enquire what the display resolutions it supports. If it 
> doesn't get the replay, the Rpi doesn't activate the HDMI output - or at 
> least that seems the way it is..

The DDC EEPROM in the monitor *should* be powered by the pi via the HDMI
cable, so having the monitor plugged in should be enough - it does not
have to be powered on.

cu
Michael
-- 
Some people have no respect of age unless it is bottled.