While viewing the Karaf console locally (the Pi is plugged into a TV currently), after trying to display certain characters, character-map seems to be a mess. See the pictures, they explain better than me
Any ideas why and how to fix it?
Not overclocked, power works fine on my other pi. Iāve since changed the SD card and a new install.
It only seems to happen once itās tried to display a āstrangeā character. I donāt have an identical model pi else I would swap SD card. edit I swapped power supply but itās exactly the same
Strange things will happen when you emmit ANSI control character to the console. Since karaf shell behaves like real shell it reacts on such things (ie to color some lines, bold some text and so on). If you would be so kind to tell us what this strange character is so we can isolate issue and check with Karaf shell. List of characters karaf may react is here:
Where can I find the actual log file which is displayed when log:tail is used? As in, where is it located in the directory structure?
That way I can find the offending character.
So whatās happening then? I can understand Raspbian being incapable of displaying anything but the basic of characters; but then to get itself into a state where it jumbles the display like thisā¦
Surely this sort of problem should have been fixed years ago?
Iāve no idea what that even is. Perhaps related to trying to create a switch item for my busch-jaeger zigbee switch (which doesnāt seem to be supported by the Hue binding - another issue)
Hmm
@Benjy reply simply clear all control characters. It is a escape character which should cause terminal reset (clearing all control characters/switches being used).
But this is not yet caused by that - source of troubles sits in some of your configuration files. Try to find āMac OS Xā string which occurs in log: find /etc/openhab2 -type f -exec grep "Mac OS X" {} \;. You most likely have malformed configuration.
You have somehow malformed file. By default openhab.cfg should be text file but for some reason it become a binary file. Iām not even sure if itās necessary for OH2. Remove these two matched files and problem will dissapear.