fixme-s on the /network page; the MAC addresses for
wireless are not available.
[Don’t-know] Use the WebApp, Device page,
Power and Reset to
SHUTDOWN the bot actually causes a
FarmBotOS.Platform.Target.SystemTasks.shutdown does the correct thing (power-off).
[FarmBotOS] The configured (advanced) optional NTP 1 and NTP 2 servers are ignored.
Thanks for the reports. We just fixed the reboot and ntp issues. Working on the mac address one next
using API at
Farmbot app: farmbot exited 0: :shutdown after many
This then causes endlessly repeating FarmBotOS re-boot. (period about 3 minutes)
Also (probably not related to v8.0.0)
The RPi serial console reports (every 2nd boot or so) early after Erlang VM starts :
(edit in actual msg :))
kmsg_tailer: (null): sendfile: Broken pipe
That’s very strange. Ill check this out. Thereay be a race condition that needs catching or maybe there was a momentary breakage in infrastructure like you said
I was testing
Release v8.0.0-rc29 today and had some trouble with taking pictures:
Is this supposed to work at the moment? I saw that
@connor recently made changes to the farmware interface so I am not sure if this still is work in progress.
Also after upgrading from 7.0.1, the first-party farmware was completely missing. I re-flashed the SD card and manually installed the camera farmware to have it at least show the error message.
Please see this post for what is and is not expected to work as of this time
Hello FarmBot community,
Today we have a big software update for you! Some things you may have seen already because they were deployed to the app several weeks ago, some things were just deployed today, and yet other features will only be available to you if you decide to try out the FBOS v8 beta. So let’s kick it off!
FarmBot OS v8 Beta
Today, after about 10 months of refactoring, feature development, and sweeping architectural changes, FarmBot OS v8 is ready to be beta tested. Big c…
Still have that repeating (3 minute) Farmbot app: crash followed shortly by OS Restart.
Will see what I can make of the Erlang stack traces. (Not sure it’s Infrastructure, but I am way over in Ausstrayliaah . . and previous poster seemed to have their bot up long enough to play with
Think I have a clue on this one . . I always just grab the from the GitHub Pre-Release artefacts, check its
sha256sum then burn it to a known good SDHC then go and Configurate it, etc…
Others probably use the
NervesHub to do an
OTA update !! I wonder if that’s it ??
I just booted a
built locally and it’s staying up.
@connor, in your copious spare time, could you grab a from Release and see whether it behaves badly for you too ?
hmm that’s a good question if an image file works. I had my doubts that beta images would work. I’ll try it out
I’ve opened an issue
#850 and hopefully fixed with #851. Still waiting on continuous integration to build it please test it out when it’s up.
I just tested and it seemed to work. Let me know if it works for you
Thanks . . but still not working on
my RPi in fact assets won’t even boot !?
and then tried
file . . in each case, the RPi just does 4 slow
Red blinks and 4 fast Red blinks, repeating, until I remove power. Nothing on the
You must be using a RPI 3b+. I just fixed this in the latest RC
Yes, RPi 3 B+ is the same machine I’ve used since before
won’t boot either.
< Oh, wait ! >
I just see
. . I’ll give that a spin.
Aaaaahhhhhhh . . the sweet sounds of machinery humming
Thanks ! (
Those User-specified NTP server names are still being ignored, however
AND this seems new on the Serial Console for this Pre-Release
Huh i thought i fixed this. I’ll reopen the ticket.
That is normal, unfortunately. It is
espeak opening the sound device. ALSA is just really noisy for some reason. I could probably add a config file of some sort with all the defaults to prevent it, but it’s not that big of a deal. To get serial logs, you should be able to do a
now but NTP server names config still not activated.
Maybe this one belongs with the
:nerves_time app. ?
May have another issue coming . . I just need to dig deeper / debug it some more.
I’m in AU (Australia) and the WiFi Configurator AP is painfully slow and unresponsive, even on my trusty Ubuntu laptop.
I usually end up using the serial console and
IEx to setup the basic network and credentials.
I noted that the AP is using
US reg.dom. WiFi channels . . I need to check whether this is a problem.
You are setting these values from configurator right? they aren’t checked after configuration time so if your device was already configured they probably wouldn’t be used.
Yes, these were set from the
/config_wired Configurator page, Advanced fields.
The persisted values I showed were sampled after at least one OS full reboot.
processes is enough ? (21 ?) Raspberry Pi 3 B+ on
( Only went looking because poor old RingLogger got duplicate after duplicate of the
dmesg message set
Oh, and also, why is
running on my
wired interface ??
< D’Oh, of course, it needs to
renew leases and all that jazz . . sorry >
Lol. Getting connected to NervesHub often requires restarting
:nerves_runtime which apparently doesn’t cleanup after itself. Really I only use that for development so maybe I’ll just disable it in production releases.
As for the udhcpc on eth0, I assume you are using static? That could cause problems if there is a DHCP server running. I’ll make a ticket for that one
@connor, pls. don’t bother with that on
I corrected my misteak with an edit which you may have missed.
DHCP wired works well, and, I haven’t bothered trying
_ because I didn’t know that
VintageNet supports it yet (?)