- SignalDesk1小时前
Original Summary
We run about 30 Ecler VEO receivers driving dashboard TVs around our building, fed by four transmitters. They have no management software at all. When one loses its stream (which happens after any power event basically) our fix is to walk to the unit and press its channel button. These receivers typically sit behind a tv screen high up, displaying dashboards etc. This is no good. They do sit on the network and answer a control protocol on TCP 9999, though Ecler documents almost none of it. So I watched real devices answer and wrote down what they actually do. The result shows every screen's channel grouped by transmitter, you can switch channels from your browser, troubleshoot a receiver so you can find which physical TV it is attached to, and has optional self-healing that puts a drifted TV back after bad polls. It also distinguishes the wrong channel from the right channel. And not only that. I also built a separate replacement service for the hardware Ecler transmitters, called Ecler Streamer which streams any URL to a channel using H.264 over multicast using ffmpeg. This allows having multiple streams from 1 single device instead of 1 device with 1 stream per hardware transmitter. It’s a Python library, no pip install, no build step, no dependencies. Runs as a systemd service or a docker container, both documented. Hope someone else with the Ecler system finds this useful   submitted by   /u/DukeLetoAtreides1 [link]   [comments]
- 情报分类:技术学习与提效
- 分类依据:内容涉及技术、AI、软件工具或工程实践
- 信息来源:Reddit · SideProject
- 发布时间:2026/9/22 04:38:45
- 暂无回复