Closed ArBleizBZH closed 1 year ago
Is the daemon not running?
I'm getting a Daemon log so I've been assuming that it is. Is there a foolproof way to check? (cuz I'm a fool who knows nothing of Mycodo, very little of Raspberry Pi and even less of Linux :D ).
Also, I noticed that when I add a widget, it always adds two of the same instead of one. The reason I wonder if this is related is because I just tried to delete one widget, and I got two status messages: Success: Delete widget with ID: 5eec230d-a8be-48d7-90c3-30382512665d × Error: Delete Widget: 'NoneType' object has no attribute 'widget_remove'
I had already deleted the duplicate, hence the error. But it got me wondering whether those extra widgets are related to the issues I have while saving. Could the widget IDs get mixed up when it's creating extraneous ones?
Found this in the Daemon log also: 2022-06-15 06:50:19,005 - INFO - mycodo.daemon - Mycodo daemon v8.13.10 starting 2022-06-15 06:50:20,202 - INFO - mycodo.outputs.on_off_kasa_kp303_0_4_2_946252eb - Starting asyncio RPC server...
In case it's related, I did notice that the only sensor I have hooked up (BME280) was no longer reporting measurements after a system restart (issued from Mycodo). I tried to get it going again for a while in vain, but what eventually did the trick was to deactivate it and then reactivate it.
I believe this issue has been fixed in one of the recent fixes. You can upgrade to the master branch (see the github wiki) to test prior to the next release.
Mycodo 8.15.0 was just released. Please upgrade and let me know if the issue persists (reopen this issue).
Hello Kyle! I've been enjoying/admiring your videos for some time, but only just made the plunge a couple days ago, with getting a Pi and setting it up with Mycodo. My indoor garden is already going, so all the infrastructure is in place, it's mostly a question of adding inputs and outputs to get everything automated.
Anyways, the Pi and the Mycodo builds are brand new as of yesterday (debug data follows).
BUG SUMMARY: Attempting to configure an existing widget results in a 500 server error.
REPRO STEPS: These are the steps, but I'm not sure you'll be able to repro; since it's such an obvious, un-missable issue I'm guessing the cause is with my environment config.
RESULT: The browser displays a 500 Server Error with the message "AttributeError: 'NoneType' object has no attribute 'widget_add_refresh'" (full details below)
NOTES: Even though saving causes a 500, the changes are sometimes persisted nonetheless. Though I did notice that was not true for increasing the number of color stops, when I do this, the number of stops does not change in the widget, and the new stops do not get added for configuration in the config page, Though I'm thinking this is likely a separate issue.
Thanks for the help, debug data follows, let me know if you need anything more. And also, I apologize in advance as this smells like some sort of user config error or some such; I did try to track it down but couldn't. Merci Kyle!!!
FULL ERROR DUMP:
DEBUG INFORMATION:
uptime 06:40:34 up 9:56, 2 users, load average: 0.30, 0.13, 0.12 Kernel Information: uname -a Linux raspberrypi 5.15.32-v7l+ #1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux
Processes (frontend and threads): top -b -H -n 1 -p 521 top - 06:40:35 up 9:56, 2 users, load average: 0.30, 0.13, 0.12 Threads: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 922.0 total, 67.9 free, 478.4 used, 375.6 buff/cache MiB Swap: 512.0 total, 350.4 free, 161.6 used. 248.3 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 521 root 20 0 25272 3208 2224 S 0.0 0.3 0:08.42 python
Disk Usage: df -h Filesystem Size Used Avail Use% Mounted on /dev/root 115G 11G 99G 10% / devtmpfs 332M 0 332M 0% /dev tmpfs 461M 17M 445M 4% /dev/shm tmpfs 185M 1.3M 184M 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p6 253M 50M 203M 20% /boot tmpfs 93M 24K 93M 1% /run/user/1000
Diagnostic Messages: dmesg | tail -n 20 [30828.893014] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.893024] MAI: soc_pcm_open() failed (-19) [30828.900439] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.900456] MAI: soc_pcm_open() failed (-19) [30828.900797] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.900812] MAI: soc_pcm_open() failed (-19) [30828.901058] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.901068] MAI: soc_pcm_open() failed (-19) [30828.935413] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.935439] MAI: soc_pcm_open() failed (-19) [30828.935982] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.935998] MAI: soc_pcm_open() failed (-19) [30828.936496] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.936513] MAI: soc_pcm_open() failed (-19) [30828.943007] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.943034] MAI: soc_pcm_open() failed (-19) [30828.943457] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.943480] MAI: soc_pcm_open() failed (-19) [30828.943776] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19 [30828.943793] MAI: soc_pcm_open() failed (-19)