New troubles

Just a q about rebooting the Flukso v2b: is it normal that removing power and reconnecting the power (after a minute or so) takes 2 to 10 retries (power ups) before it finally gets the wifi working?
I am beginning to doubt if this device is, or has ever been, stabile. And since it is only a week old...

More people having troubles rebooting this device and get a stabile wifi connection within a few minutes? Or any suggestions on how troubleshoot this kind of problem? Connecting thru cable is possible but a lot of trouble since the device is fitted near the fusebox.
(Answers in english or dutch are fine)

adamcowin's picture

No not normal that it takes 2-10 retries to power up and connect to the wifi...

I'd suggest some basic troubleshooting - this will be a bit general since im not sure of your setup:

1. try plugging the flukso into the network via the cat 5 cable. Once its plugged in, turn it on and see if it connects (check the lights ontop of the flukso etc)
2. If it connects via cat 5 cable, try to simulate the issue you were having - IE remove power and then reconnect and see what happens.
3. If it fails to connect this way as well (which rules out wifi) then look at how it is connecting to the network/internet - IE is it able to get an IP address? Is it able to get out to the internet or being blocked via firewalls etc?

Side note: If it does not work when plugged into the LAN cable, try to connect to the device via your pc/laptop and check the syslog tab for errors - feel free to post syslog errors here as they will help us to help you :)

If you are able to get it to work each time via cat 5 cable, then the next step is troubleshooting the wifi.

I noticed that you said the device is connected near the fuse box and via wifi. If you have a laptop, take it out to where the flukso is and try to connect to your wifi. if you are able to connect, check the signal strength of the connection. If it is very low, then this may well be the cause of it - i am unsure which would have a better aerial, a laptop or the flukso with its external antenna.

Good luck and let us know how you go

cheers
adam

bazzle's picture

In the setup page you can see the wifi signal strength. What are the numbers ie 30/70 etc

adamcowin's picture

I cant get to my flukso device at present (away for work) so i was writing the above troubleshooting going on memory of the flukso interface.

But +1 for Baz's suggestion above first. - This is the best starting point.

Check the wifi signal strength and let us know what the signal strength is - if needed, then can do some troubleshooting as per my previous comment :)

Cheers
Adam

gentleheart's picture

On cable the device works fine even when a failed WiFi boot occurs.

Signal Quality 53/70

Only ONE of many wifi devices have connection problems here (an IP-cam that has been switched off for several months) All other devices function well on Wifi, (this is typed on a laptop connected thru wifi)

Gonna reboot the Flukso device now...
Ok, 5 minutes passed, still no wifi! Only Power and Heart leds are on.
Cable connect then... LAN led comes on. Laptop gets ip 192.168.255.153
In a browser to the static DHCP ip (192.168.178.122) of the Flukso gives an index with folders?! And WIFI is STIL OFF?! How the @&*#??:
../ modified: Thu, 01 Jan 1970 00:02:06 GMT directory - 0.00 kbyte
cgi-bin/ modified: Wed, 16 Oct 2013 14:49:19 GMT directory - 0.03 kbyte
components/ modified: Wed, 16 Oct 2013 14:49:17 GMT directory - 0.05 kbyte
img/ modified: Wed, 16 Oct 2013 14:49:17 GMT directory - 0.04 kbyte
luci-static/ modified: Wed, 16 Oct 2013 14:49:19 GMT directory - 0.03 kbyte
scripts/ modified: Wed, 16 Oct 2013 14:49:17 GMT directory - 0.05 kbyte
sensor/ modified: Tue, 20 May 2014 02:39:17 GMT directory - 0.00 kbyte
styles/ modified: Wed, 16 Oct 2013 14:49:17 GMT directory - 0.05 kbyte
views/ modified: Wed, 16 Oct 2013 14:49:17 GMT directory - 0.12 kbyte
----
Ok now to the syslog thru ip 192.168.255.1:
Gives the same directory listing!
Clicking these folder links I get empty folders!
So not possible to get to syslog.

Checking router DHCP:
Mac: a8##41####c6
ip: 192.168.178.122
mask: 255.255.255.000
Lease time: D:01 H:00 M:00 S:00
Lease expires: Sat May 24 02:55:45 2014

Wifi access control - Connected Clients:
MAC Address: A8:##:41:##:##:C6
Age(s): 3
RSSI(dBm): -47
IP Addr: 192.168.178.122
Host Name:
Mode: g
Speed (kbps): 54000

Q: Why doesn't the flukso register a HOSTNAME? (another great argument for FIXED IP!)
Note that WiFi LED on the Flukso is still OFF.
---
Going to reboot AGAIN, this time with the cable plugged in...
Globe Led is ON this time AND wifi (ALL leds are on)
Device is now responding normally on BOTH wifi and LAN cable ip's.

Status:
System
Serial: FL0300####
Model: FLM02B
Hostname: flukso-7a**** <- again this hostname is NOT passed to the router!
Firmware version: 232
Time: 23-5-2014 04:25:22
Uptime: 0days 0h 3min 39s

Network
Reporting mode: wifi
SSID: MySSID
Link quality: 55/70
Gateway IP address: 192.168.178.1 (corect ip for my router)
Flukso.net ping test: successful

Sensor config synchronisation
Last: 20-5-2014 04:39:04
Status: successful

---
Syslog (anonimized):
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.190000] TCP reno registered
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.190000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.190000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.190000] NET: Registered protocol family 1
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 0.190000] PCI: CLS 0 bytes, default 16
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.200000] Radio config found at offset 0xf8(0x1f8)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.240000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.240000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.250000] msgmni has been set to 57
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.250000] io scheduler noop registered
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.250000] io scheduler deadline registered (default)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.250000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.270000] serial8250: ttyS0 at MMIO 0xb1100003 (irq = 37) is a 16550A
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.280000] gpiodev: gpio device registered with major 254
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.290000] Searching for RedBoot partition table in spiflash at offset 0x7d0000
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.670000] 6 RedBoot partitions found on MTD device spiflash
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.670000] Creating 6 MTD partitions on "spiflash":
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.670000] 0x000000000000-0x000000030000 : "RedBoot"
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.680000] 0x000000030000-0x000000110000 : "vmlinux.bin.l7"
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.690000] 0x000000110000-0x0000007d0000 : "rootfs"
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.700000] mtd: partition "rootfs" set to be root filesystem
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.700000] mtd: partition "rootfs_data" created automatically, ofs=3B0000, len=420000
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.700000] 0x0000003b0000-0x0000007d0000 : "rootfs_data"
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.710000] 0x0000007d0000-0x0000007df000 : "FIS directory"
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.720000] 0x0000007df000-0x0000007e0000 : "RedBoot config"
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 0.730000] 0x0000007e0000-0x000000800000 : "boardconfig"
Jan 1 00:00:24 flukso-7a**** kern.warn kernel: [ 0.810000] eth0: Atheros AR231x: ##:##:41:00:##:c7, irq 4
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.880000] ar231x_eth_mii: probed
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.880000] eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01)
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 0.890000] Registered led device: wlan
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 0.890000] Registered led device: globe
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.900000] TCP cubic registered
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.900000] NET: Registered protocol family 17
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.900000] 8021q: 802.1Q VLAN Support v1.8
Jan 1 00:00:24 flukso-7a**** kern.warn kernel: [ 0.900000] Please be patient, while OpenWrt loads ...
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.940000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 0.940000] Freeing unused kernel memory: 164k freed
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 2.380000] eth0: Configuring MAC for full duplex
Jan 1 00:00:24 flukso-7a**** kern.notice kernel: [ 13.390000] JFFS2 notice: (291) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 14 of xref (0 dead, 10 orphan) found.
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 16.590000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 16.590000] Backport generated by backports.git backports-20130617-4-ge3220f5
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 16.690000] cfg80211: Calling CRDA to update world regulatory domain
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 16.690000] cfg80211: World regulatory domain updated:
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 16.690000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 16.690000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 16.690000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 16.690000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 18.910000] ath: EEPROM regdomain: 0x0
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 18.910000] ath: EEPROM indicates default country code should be used
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 18.910000] ath: doing EEPROM country->regdmn map search
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 18.910000] ath: country maps to regdmn code: 0x3a
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 18.910000] ath: Country alpha2 being used: US
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 18.910000] ath: Regpair used: 0x3a
Jan 1 00:00:24 flukso-7a**** kern.debug kernel: [ 18.910000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 18.920000] ath5k: phy0: Atheros AR2317 chip found (MAC: 0x90, PHY: 0x48)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 18.920000] cfg80211: Calling CRDA for country: US
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 18.920000] cfg80211: Regulatory domain changed to country: US
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 18.920000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 18.920000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 18.920000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 18.920000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 18.920000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 19.850000] PPP generic driver version 2.4.2
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 20.300000] ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 20.830000] NET: Registered protocol family 24
Jan 1 00:00:24 flukso-7a**** kern.info kernel: [ 20.890000] nf_conntrack version 0.5.0 (460 buckets, 1840 max)
Jan 1 00:00:33 flukso-7a**** kern.info kernel: [ 33.410000] device eth0 entered promiscuous mode
Jan 1 00:00:33 flukso-7a**** kern.info kernel: [ 33.410000] br-lan: port 1(eth0) entered forwarding state
Jan 1 00:00:33 flukso-7a**** kern.info kernel: [ 33.410000] br-lan: port 1(eth0) entered forwarding state
Jan 1 00:00:33 flukso-7a**** daemon.notice netifd: Interface 'lan' is now up
Jan 1 00:00:33 flukso-7a**** daemon.notice netifd: Interface 'loopback' is now up
Jan 1 00:00:34 flukso-7a**** user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Jan 1 00:00:35 flukso-7a**** kern.info kernel: [ 35.410000] br-lan: port 1(eth0) entered forwarding state
Jan 1 00:00:38 flukso-7a**** kern.info kernel: [ 38.660000] cfg80211: Calling CRDA for country: BE
Jan 1 00:00:38 flukso-7a**** kern.info kernel: [ 38.660000] cfg80211: Regulatory domain changed to country: BE
Jan 1 00:00:38 flukso-7a**** kern.info kernel: [ 38.660000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 1 00:00:38 flukso-7a**** kern.info kernel: [ 38.660000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 1 00:00:38 flukso-7a**** kern.info kernel: [ 38.660000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 1 00:00:38 flukso-7a**** kern.info kernel: [ 38.660000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 1 00:00:38 flukso-7a**** kern.info kernel: [ 38.660000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Jan 1 00:00:46 flukso-7a**** kern.info kernel: [ 46.030000] wlan0: authenticate with a4:##:31:##:##:ee
Jan 1 00:00:46 flukso-7a**** kern.info kernel: [ 46.040000] wlan0: send auth to a4:##:31:##:##:ee (try 1/3)
Jan 1 00:00:46 flukso-7a**** kern.info kernel: [ 46.040000] wlan0: authenticated
Jan 1 00:00:46 flukso-7a**** kern.info kernel: [ 46.080000] wlan0: associate with a4:##:31:##:##:ee (try 1/3)
Jan 1 00:00:46 flukso-7a**** kern.info kernel: [ 46.080000] wlan0: RX AssocResp from a4:##:31:##:##:ee (capab=0x411 status=0 aid=3)
Jan 1 00:00:46 flukso-7a**** kern.info kernel: [ 46.090000] wlan0: associated
Jan 1 00:00:48 flukso-7a**** cron.info crond[667]: crond: crond (busybox 1.19.4) started, log level 1
Jan 1 00:00:49 flukso-7a**** daemon.notice netifd: wan (675): udhcpc (v1.19.4) started
Jan 1 00:00:50 flukso-7a**** daemon.notice netifd: wan (675): Sending discover...
Jan 1 00:00:50 flukso-7a**** daemon.notice netifd: wan (675): Sending select for 192.168.178.122...
Jan 1 00:00:51 flukso-7a**** daemon.notice netifd: wan (675): Lease of 192.168.178.122 obtained, lease time 86400
Jan 1 00:00:52 flukso-7a**** daemon.notice netifd: Interface 'wan' is now up
Jan 1 00:00:54 flukso-7a**** user.notice firewall: Reloading firewall due to ifup of wan (wlan0)
Jan 1 00:00:54 flukso-7a**** authpriv.info dropbear[714]: Running in background
Jan 1 00:01:02 flukso-7a**** user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Jan 1 00:01:02 flukso-7a**** user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq[762]: started, version 2.66 cachesize 150
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq[762]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq-dhcp[762]: DHCP, IP range 192.168.255.100 -- 192.168.255.249, lease time 12h
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq[762]: using local addresses only for domain lan
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq[762]: reading /tmp/resolv.conf.auto
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq[762]: using nameserver 212.54.44.54#53
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq[762]: using nameserver 212.54.40.25#53
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq[762]: using local addresses only for domain lan
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq[762]: read /etc/hosts - 1 addresses
Jan 1 00:01:06 flukso-7a**** daemon.info dnsmasq-dhcp[762]: read /etc/ethers - 0 addresses
Jan 1 00:01:07 flukso-7a**** daemon.info dnsmasq-dhcp[762]: DHCPINFORM(br-lan) 192.168.255.153 ##:0e:a1:##:##:4f
Jan 1 00:01:07 flukso-7a**** daemon.info dnsmasq-dhcp[762]: DHCPACK(br-lan) 192.168.255.153 ##:0e:a1:##:##:4f SORAYA
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534).
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Successfully dropped root privileges.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: avahi-daemon 0.6.31 starting up.
Jan 1 00:01:08 flukso-7a**** daemon.warn avahi-daemon[768]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Loading service file /etc/avahi/services/flukso.service.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Loading service file /etc/avahi/services/http.service.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Loading service file /etc/avahi/services/mqtt.service.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Loading service file /etc/avahi/services/ssh.service.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.122.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: New relevant interface wlan0.IPv4 for mDNS.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.255.1.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: New relevant interface br-lan.IPv4 for mDNS.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Network interface enumeration completed.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Registering new address record for 192.168.178.122 on wlan0.IPv4.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Registering new address record for 192.168.255.1 on br-lan.IPv4.
Jan 1 00:01:08 flukso-7a**** daemon.info avahi-daemon[768]: Registering HINFO record with values 'MIPS'/'LINUX'.
Jan 1 00:01:11 flukso-7a**** user.info sysinit: setting up led wlan
Jan 1 00:01:11 flukso-7a**** daemon.info avahi-daemon[768]: Server startup complete. Host name is flukso-7a****.local. Local service cookie is 913707133.
Jan 1 00:01:13 flukso-7a**** user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:13 flukso-7a**** daemon.info supd[786]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Jan 1 00:01:13 flukso-7a**** user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:13 flukso-7a**** daemon.info spid[789]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Jan 1 00:01:14 flukso-7a**** user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:14 flukso-7a**** daemon.info fluksod[792]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Jan 1 00:01:15 flukso-7a**** user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:15 flukso-7a**** daemon.info parsed[797]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Jan 1 00:01:16 flukso-7a**** daemon.info avahi-daemon[768]: Service "Secure Shell on flukso-7a****" (/etc/avahi/services/ssh.service) successfully established.
Jan 1 00:01:16 flukso-7a**** daemon.info avahi-daemon[768]: Service "MQTT Broker on flukso-7a****" (/etc/avahi/services/mqtt.service) successfully established.
Jan 1 00:01:16 flukso-7a**** daemon.info avahi-daemon[768]: Service "Web Server on flukso-7a****" (/etc/avahi/services/http.service) successfully established.
Jan 1 00:01:16 flukso-7a**** daemon.info avahi-daemon[768]: Service "Flukso RESTful API on flukso-7a****" (/etc/avahi/services/flukso.service) successfully established.
Jan 1 00:01:24 flukso-7a**** user.info heartbeat[800]: POST https://api.flukso.net/device/7a##e69d247c2******4bd598ba3**8c: 200
Jan 1 00:01:25 flukso-7a**** daemon.info supd[786]: Received event START for ntp
May 23 02:23:45 flukso-7a**** cron.err crond[667]: time disparity of 23346862 minutes detected
May 23 02:23:54 flukso-7a**** daemon.info fluksod[792]: processed pulse 18ee***...***0429:1400811834:17170
May 23 02:23:56 flukso-7a**** daemon.info fluksod[792]: POST https://api.flukso.net/sensor/18ee***...***0429: 200
----------------------------------------------------------------------------
So when I boot WITH cable BOTH wifi and lan work, disconnecting the cable now will keep wifi up... Check
How about connecting a loopback connector to the Flukso...
Cant seem to find one right now. :(

So concluding: It WILL boot and connect to WiFi when the cable is connected as well, but device hangs in boot most of the time when no cable is connected?

Now what? Time to send it back? This thing is becoming a very time consuming gadget. I don't mind a little work on this, but this has been many many many hours and the ONLY thing WORKING so far is the power sensor. Beginning to get disappointed by this gadget...

bazzle's picture

Prob not the right answer but have you tried cycling the wifi/lan by pressing the button as per the manual?

gentleheart's picture

Bazzle!!!
You are my hero. Seems I have read all over it and still missed that one... schaamrood op mijn lippen... feeling so sily.... Dank je! Thank you!

gentleheart's picture

Another strange new bug: now I cannot logon to the flukso thru wan ip anymore. The address I reserved was 192.168.178.122 and because I hacked the firewall settings I could connect thru wifi to the device. Suddenly the device now only responds to 192.168.178.122:8080 but then I cannot login???
I says wrong password or username. Please try again. But whatever I try: I can NOT log on. Suggestions anyone?

Fred.'s picture

Jou probably did something wrong then.
Just ssh into the device and put back the default wan settings?

vi /overlay/etc/config/network

  1. config interface 'wan'
  2.         option proto 'dhcp'
  3.         option ifname ‘eth0'

gentleheart's picture

I reapplied the firewall fix and that seems to have fixed the problem.