Alex Martens

> Hi, sorry for my delay, but covid shot me. No worries, hope you are doing well now! > monitorcontrol -vvvv --get-luminance > DEBUG monitorcontrol.vcp.vcp_linux header=b'\x08\x08' > DEBUG monitorcontrol.vcp.vcp_linux payload=b'\x08\x08\x08\x08\x08\x08\x08\x08\x08'...

I got access to a failing monitor (thanks @jiri-one !) a while ago. I think I found the root cause of this issue in the way the DDC packets were...

Similar issue: https://github.com/newAM/monitorcontrol/issues/46 The same comment applies here: > At the moment there is no way to identify unique monitors, this would be a good feature to have though. >...

> I'd love to, if fact I looked into doing that while working on this, but was not clear how to proceed, so I did not. I suppose the way...

Can you let me know this information? ```text * Monitor manufacturer and model number: * Input source (HDMI, VGA, display port, ect.): * Output device (video card, discrete graphics, ect.):...

> Is there any way to get monitor brightness without DDC-CI support you mentioned? Depends what your monitor implements, there are other ways to control displays such as HDMI CEC...

I was experiencing the same thing and I did some measurements. The H7 issue suggested this was due to repeat clock initialization, so I setup an experiment: * 2x STM32WLE5...

@ALABSTM can you share any updates on this issue?

I did some more digging on my issue, turns out the LSE frequency is really far off (32.775 kHz, 232 ppm) on the seeed LoRa-E5 modules I am using.

 Tested the broker + client in loopback, and tested the client with my existing TLSv1.3-PSK proxy. Works as expected in both cases.