I would i) in configuration.yaml set shuffle: False so it always runs in the same order from start and don't send any command by MQTT, HA etc. Here are some thoughts off the top of my head:Ī) It's possible to get a list of systemd caught output by typing journalctl at the command prompt - but I'm not sure you will learn anything extra by running picframe as a service rather than from clī) It would be nice to isolate the problem a bit more. I'm going to be out again today but might get a chance to look at it later. This may be because in the log file, it appears that picframe recognized that the root directory name should be converted to a blank string: But in my testing, this did not immediately cause the "no-pictures behavior" problem (as I would expect). ![]() It appears to me that this "no-pictures behavior" is somehow related to switching subdirectories in Home Assistant, but it does not occur immediately after a switch.Īs to the issue setting the subdirectory using Home Assistant: it's true that I was using the root directory name as a subdirectory option. (Whether a black screen or the no-pictures image, Home Assistant is showing that the current image is the no-pictures image.) Once this has happened, picframe is no longer responsive to mqtt commands to switch to another subdirectory to resume the slideshow, the process must be terminated from the command line (with CTRL - C) and restarted. No, I think there's one primary issue: picframe gets 'confused' and shows either the no-pictures image or a black screen - without any immediate interaction from me. Is is possible that picframe is getting confused and trying to find image files at /home/pi/Pictures/Pictures? (That directory does exist and contains lower resolutions of the same files found in /home/pi/4kpix/Pictures. One other odd thing I noticed: Although I have pic_dir set to /home/pi/4kpix in my configuration.yaml file, the sqlite db also has entries for files located in /home/pi/Pictures. I'm still testing, but it may be that the problem occurs sometime after I switch image directories in Home Assistant using the directory select helper entity input_select.picframe_directory. In case it matters, I have integrated picframe with the latest version of Home Assistant as described in. ![]() I've also attached my configuration.yaml file and the pictureframe.db3 file. See line 116752 for the first occurrence of no_pictures.jpg. After this happened several times, I ran picframe in DEBUG mode and captured all the output to a log file (attached). After running successfully for many hours, picframe will abruptly "forget" where the image files are located and show only the no_pictures.jpg image.
0 Comments
Leave a Reply. |