[asprunt]

I started a new topic to document my experiences trying to run read-only.

[asprunt]

Dan,

When I tried to re-create the issue tonight, I couldn’t. I don’t know whether it was ever really there or if it was a chair to keyboard interface error! Thanks for your offer of help and my apologies for the distraction.

Best,
Alex

[asprunt]

I think I am seeing the same issue. I can run the program manually (“now”) and it will start automatically if I change it to be “interval” rather than “weekly.” The “preview” on the home screen also doesn’t seem to work when the program is weekly, as opposed to interval. I’m on version 2.2.32 / 07b71aa.

Were you ever able to resolve this issue?

Thanks,
Alex

[asprunt]

A closer reading of the i2cdetect manpage and this stackoverflow answer makes me think the “UU” at 68 is not a problem, in that it’s just indicating that there’s likely a chip (the RTC) at that address, which is already in use by a driver (presumably the one I installed).  So does anyone know if the device found at “48” is indicative of a problem?

[asprunt]

I am experiencing the same issue as Brendan Coupe. Very high CPU utilization by python (as shown by sudo top from the command line). With OSPi stopped, CPU utilization is negligible. The web UI and even interaction via SSH are so laggy as to be hardly useable.

The installation was done cleanly from github. My repository is at 8d12fac. I configured the RTC using the instructions here. The only anomaly is 

pi@ospi ~ $ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: — — — — — — — — — — — — —
10: — — — — — — — — — — — — — — — —
20: — — — — — — — — — — — — — — — —
30: — — — — — — — — — — — — — — — —
40: — — — — — — — — 48 — — — — — — —
50: — — — — — — — — — — — — — — — —
60: — — — — — — — — UU — — — — — — —
70: — — — — — — — —

Which I’m afraid I don’t understand at all. Yesterday, “UU” was 68, but the “48” has been there the whole time.

I’d appreciate any suggestions. Otherwise, my next step will probably be to start the whole process again from a clean raspbian image.

Thanks

[asprunt]

In preparation for my OSPi, I’m trying to figure out how to do the mechanical installation. I’d like to mount it outside, have a well shaded spot selected, and was planning to use an Orbit 57095 or similar waterproof enclosure. I’m not too concerned with the Pi overheating, because it rarely reaches 90F here, and doesn’t stay that hot for long when it does.

There’s an “exterior” AC outlet nearby, but having the cord from the OSPi “permanently” holding the outlet cover’s door open seems like a bad idea, even though the spot is relatively sheltered. I know this isn’t really an OSPi question, but can anyone tell me what the appropriate solution is? Should I cut an outlet shaped hole in the back of the waterproof enclosure, install it over the outlet, and seal the resulting joint with silicone? Should I replace the existing outlet cover with something else?

Thanks.

[Author]

Posts