Over the last few months I’ve noticed that a WiFi outage (as simple as an access point rebooting from a firmware update) will cause the spark (3) to fail to reconnect and even once it reconnects the spark service requires a manual restart. This didn’t used to happen it I believe I did a Brewblox update a few months back. I updated again but no luck.
Can we get this fixed?
Just to clarify, you’re connecting from the Brewblox server to the spark over the network, yes?
That is correct, Brewblox server is a VM running on Proxmox for the last few years and the Spark is on wifi.
I have my setup configured the exact same way. How have you managed the IP addressing or hostname config from the server to find the Spark?
I have my Spark setup with a static IP and I have included that in my config file. I’m happy to share that with you if you want it.
The Spark has a fixed DHCP address. Interested in how to add it to the config file.
It makes things much easier if you can assign it a static lease via DHCP.
Here is my config:
vim ~/brewblox/docker-compose.yml
You should have an existing file by this name with some of this config pre-populated and likely more beyond this.
services:
ferm-spark:
image: ghcr.io/brewblox/brewblox-devcon-spark:${BREWBLOX_RELEASE}
privileged: true
restart: unless-stopped
environment:
- BREWBLOX_SPARK_DEVICE_HOST=XXX.XXX.XXX.XXX
- BREWBLOX_SPARK_DEVICE_ID=XXXXXXXXXXXXXXXXXXXXX
- BREWBLOX_SPARK_DISCOVERY=mdns
volumes:
- type: bind
source: /etc/localtime
target: /etc/localtime
read_only: true
- type: bind
source: ./spark/backup
target: /app/backup
Replace all Xs with your specific values. The BREWBLOX_SPARK_DEVICE_ID can be found under your Brewblox Spark service section in the System Info block.
Thanks, I added that but along the way discovered that somehow the Spark is connecting to an old SSID. At least a year ago I split my network into several VLANs. At that time I moved the Spark to my IOT VLAN which required changing the SSID. Apparently its stored the old one as well and has started reconnecting. Very odd. With a reboot, the Spark connects to the desired SSID but I did have to restart the brewblox (did not try just the service) to connect so I’m not sure this fixed my issue.
I did reflash the firmware to the Spark just now, but I believe its been flashed twice sine the issue started before today. I also re-entered the WIFI credentials.
I also have a similar issue with the multiple SSIDs. I haven’t found the fix for that yet and just reboot/reconnect the Spark when it’s connected to the wrong network and roll the dice that it reconnects to the proper network.
On a Spark 3, you can hold the setup button for 10 seconds to clear wifi credentials.
Then brewblox-ctl wifi again to configure wifi. It can remember multiple SSIDs if I remember correctly. Clearing and setting up just one could help.
- BREWBLOX_SPARK_DEVICE_HOST=XXX.XXX.XXX.XXX
- BREWBLOX_SPARK_DISCOVERY=mdns
if you specify a device host, the discovery setting does nothing. It will just use the host without any discovery.
That requires a USB connection, correct?
For now I’ve denied it access to the network it shouldn’t be connecting to in Unifi.
These changes fixed the Spark side of the issue but the service still isn’t reconnecting automatically all the time. It seems to be when its disconnected for several plus seconds–example, we had a power outage earlier this week so during the time where my generator started and transferred the Spark was down. Wifi and Brewblox were up since all my IT infrastructure is on a UPS.
I’m having a (possibly) similar sort of issue.
My spark2 wifi connected brewblox setup has been working fine in a Proxmox LXC for many months. In the last 8 weeks or so i find that the spark controller loses connection with the brewblox service and won’t reconnect again until i power off then power on the spark. After that it works for about 48 hours before the same issue arises and i have to power off/on the controller again.
Whilst the spark is disconnected, it is however online and contactable by http on the ip address and hostname producing the usual line of text e.g. !BREWBLOX,7a42c2d etc etc and the IP address shows on the controller display.
I am updated to latest spark firmware and brewblox version. I have the controller ID and host IP in my docker-compose.yml. It doesn’t help to reboot brewblox.
Does this sound like your issue matt or is it different?
Sounds similar. It happened last week and I did have to power cycle the spark. It’s in a cabinet so I didn’t see the screen but will check next time it happens. I’ll check if it’s on the network too.