But I doubt the Rpi 3B+ is that much faster than the Rpi 3B in this matter. I have an Odroid C2 on its way, when it arrives it will take over from my Rpi 3B+ running openhab server. Since 1920 x 1080 is the resolution I´m planning to use om my 22" monitor I probably have to live with this delay untill I get a faster Rpi/SBC. So this is unfortunatly a matter of size (resolution) and computer power. When I forced the resolution of the Rpi to 1920 x 1080, the delay came down to something like 3-4 seconds. Opening the same habpanel dashboard on my workstation, (Quad core Intel I7 CPU with 32GB RAM and SSD drive, using the same 27" 2K monitor) there is no delay at all. When I have my floorplan running in habpanel showing in Chromium, there´s about 10sec from an item change to the change show on the floorplan, which in my opinion is way too much. Raspbian seems to use a high resolution by default, (I cant tell how much, since I cant find any utility to show. While setting up this little project, I´m using my 27" 2K monitor. So thats my next hurdle in this little project…Īnd as usual - Any ideas is most welcome, thanks…Īn important note about the habpanel speed i Chromium. So now I´m in a splitted situation… Somehow I need to turn off the screensaver when I want to look at the monitor, without using keyboard/mouse… I wont accept not having a screensaver, but it makes no sense, if I cant turn it off… And having a 22" monitor turned on showing a floorplan 24/7 is fare for a great idea. I cant get out of the screensaver, ofcouse (stupid thinking )… Then I came to think about the screensaver and the idea I had of not having a keyboard/mouse connected… In short - Using screensaver while having no keyboard and mouse, thats NOT such a great idea anyway. (It is slow as hell though, but thats probably the Rpi). Got the Rpi up running and it starts chromium from boot in kiosk mode showing the dashboard from habpanel. Keep that in mind… I just hammered on my keyboard for several minutes trying to exit kiosk mode with F11, ESC etc… It wont work, and probably not at all, if you continue to hammer your keyboard like I did Important note - When running Chromium in fullscreen kiosk mode, its only possible to exit using ALT-F4.
0 Comments
Leave a Reply. |