MASLOW 4.1 (vertical) initial setup and calibration, a few questions:
Joining Home Wifi.
If anyone has a link they can share on what settings and where they are configured (for the latest firmware release), that would be magic.
I have set SSID, Password (dhcp and fixed IP), subnet and fixed IP, all good as is gateway settings- is there something I am missing? (settings? - Fast Scan? )
How can I tell 1. if it’s connected (from the maslow), I assume the static IP is one way
What you have here appears correct, If the Maslow can find a signal it flashes the Blue LED with the IP address. If it can’t then it provides a network “maslow” and no blue flashing LED.
If all is connected you should be able to find the Maslow with
maslow.local
in the address line of your browser. Some browsers don’t like connecting to a device with no internet access and some timeout (although you can generally set this not to happen)
I am now having this problem as well. I’m getting a blue flashing light but I can’t find it or connect to it no matter which browser or settings I try on mobile or laptop.
I am now having this problem as well. I’m getting a blue flashing light but I
can’t find it or connect to it no matter which browser or settings I try on
mobile or laptop.
the blue flashing light is blinking out the digits of the IP address.
you should also be able to look at your access point to see what dhcp addresses
it has handed out.
The maslow attempts to register/advertise itself as maslow.local, but not all
networks support that.
The default of sta->ap tells it to attempt to connect to the configured network,
but if you can’t, fire up your own network as an AP. so you can move it away
from the network you configured it as and get into it that way to change
settings.
Maybe you’ll have some insight into why now I’m in an infinite calibration loop? I’m not touching anything and it just keeps calibrating…
you are currently on v1.16, which is rather old.
but you are getting a lot of messages:
[MSG:ERR: Calibration data not acknowledged by computer, resending]
that will cause this sort of problem. What’s causing it is a harder question,
but until you get the firmware and index.thml up to the current version, it’s
not going to be worth spending time to try and figure out a bug in an old
version.
the UI (aka index.html.gz) which you load through the file button
or you upgrade both via the USB upgrade mechanism
It is always possible I misread something in the logs, so go to settings → test
and check both version numbers that get shown in the logs at the top of the
output it produces