Month: February 2017

Docker for ProxyLCD

We have our base container with Python3, PyQt5, CharLCD and iot_message: bkosciow/rpi-qtpython.
Today we will learn how to get files from GitHub and put them into image.


Little tweaks in ProxyLCD

I found one annoying issue – when sending only number it crashes.

Crash was easy to fix but unexpected. While converting int to json, Python just convert it to number. I’m not sure if this is a bug or not. But I added additional check.

Lets make an app a little more talkative. When started it prints some useful info:

Config loaded. Starting app
TCP port:  5054
Broadcast IP:
Broadcast port:  5053
Name       | Node name  | Size    | Stream | Type
Debug      | node-40x4  | 40,4    | +      | charlcd
Info       | rpi1       | 20,4    | +      | charlcd
damaged    | node-2     | 16,2    | -      | charlcd

Docker for ARM, Python3 and PyQt5

Docker, Docker everywhere… you open the fridge and.. docker with butter and cheese, Docker may save the day but it may also make it horrible… But it doesn’t matter if you like it or not. Docker is here, its containers are everywhere. So lets join the flow 🙂

We will dockerize ProxyLCD in CLI mode. No more running the app manually:) Laziness !

Symfony ProxyLCD bundle

Finally 3rd phase of project – integration with Symfony 🙂 But I’m afraid it is not the last part 🙂

What is the goal of this Symfony bundle? It will hook to dump() command and send content to ProxyLCD application. It will transform any array or object to string representation.
Source on GitHub
Install via composer, package name: kosci/proxy-lcd-bundle


Proxy LCD – desktop application

In first part we saw a summary (hardware and software) of remote LCD. Such remote LCD works on NodeMCU and can be accessed via network. It was first stage of bigger project.
Now is time for second part, a desktop application. Its main task is to manage remote LCDs and provide a way to send content from computer to display.
One may add/remove node and set a stream option. What is stream option?
App works in two ways (one for now :P, second option in 3rd phase) if it receive content and it is not a proper packet it iterates over all added lcds and streams data to them. Difference between display and stream is that stream as name says is just a data stream and it send chars one after another. When it reaches end of available space on display it starts over.
In case of packet it will send formatted content to node.

Get from GitHub

Part 1 – remote LCD

CLI on Raspberry Pi