Interesting. I didn't know they were going to offer service that far south this year. I know some folks who are on the beta in the boondocks of north-central Washington state. They're ecstatic since they only had dial-up previously.
Great! Thanks!
That would be my thought. I can't tell from the product description how much space is allowed for connections. You could also buy the PoE hat for the PI. That's how I power my PI server. The PoE Ethernet switch is on the UPS, so the PI is automatically backed up in the event of a power fail.
@dest Interesting. How do you plan to power this?
Piling on here---I also found this confusing. My assumptions: "Save" does just what it says. Hitting "Exit" will then exit with no prompt. Hitting "Exit" alone will prompt for "Save and Exit?" or "Don't save and exit" or something similar.
I've seen the light! Thanks!
No spinner, but after a hard refresh dark mode is gone (back to light mode) and there's doesn't seem to be a way to get it back. Did I miss something?
I assume you mean that Vera is not seeing the "untrip" event from the motion detector, a sadly common problem in recent firmwares. I 've solved it by adding the "AutoUntrip' variable to the device with a \ time-out delay to untrip the sensor. 60 seconds is a good value, but you can choose any number you want.
@DesT Thanks for the quick response!
Something has changed. The spinner now spins for a fraction of a second during the update only, which is the desired behavior.
Same here. The spinner is constant, and I'm on wireline at 150 Mb/s.
LUUP on Vera is a Linux executable written in C/C++ that provides the operational functions of Vera, a Lua environment for running Lua scripts, HTTP, serial device support and the UPnP control model. The problem as I see it is that many of these functions should not be part of single executable, but in fact should be provided by the OS since that's why it's there. The basic architecture of LUUP is therefore fragile, and can become unstable under a variety of internal and external conditions. For example, HTTP request to external sites (e.g. a cloud-based whatever) can crash LUUP if the external site takes too long or responds in a way that LUUP can't process. LUUP either crashes on its own, or makes the decision to "self-crash" and reload to attempt to get itself back to a sane operating state. These are my assumptions based on what I've been able to observe. Anything that causes a delay will almost certainly crash LUUP. I know we have folks here who have delved much more deeply into LUUP, or at least as deep as you can by observing its external behavior and who will have far more insight than I.
I have done embedded Linux systems since the early 2000's. We used as many OS functions as possible, since that's why you have an OS. We wrote our own Linux device drivers for our special I/O devices, and confined the executable to the actual control and computations required by our application. We also used shell scripts, as does Vera, for various OS functions. Our systems did not use Lua, and did not have any mechanism for user-written code. This made it much easier to have stable systems. It comes down to architectural decisions and IMHO Vera chose poorly.
Forgot this: https://www.lua.org/
Lua: https://en.wikipedia.org/wiki/Lua_(programming_language)
Interesting backstory.
@Black-Cat As I understand it, dark mode is a forum-wide setting, hence the informal voting to turn it on today.
Thanks for having us!
Yay dark mode! Many thanks!
Hi everyone! I'd like a dark my also.
