Hi,
my FLM2B has been serving me for years but last year it bricked itself, no heartbeat, no life.
I could reflash it using th no-IP method, I got it back up, reconfigured it, all ok again.
But some time ago this year it bricked itself again. No heatbeat and of course no updates anywhere anymore. Same old.

I reflashed it yesterday 2x, letting it (re)boot ... no heartbeat. today again a successfull reflash but no heartbeat. Is there something I can do further to troubleshoot? Any serial connection internally I can tap into to maybe get a shell and see what's (not) going on?

I know it's (just) a Dragino v1.0, HW produced in 2011, so maybe long past it's service life but since I could still happily flash the device, there's still life in it. Alternatives are buying a new one but they're not available for sale anymore. Or I have to look at a completely different solution.

Thanks.

Hello
Does anyone know of anywhere in australia that sells clamps? the postage from flukso is more than twice the price of the clamp.
regards
Stephen

(no, no basic question about how to set a client IP ;)

Had a bricked Flukso v2 with a broken power supply. The power supply is replaced, and the flukso boots again. However, it is not responding on IP.

Fully simular case as https://www.flukso.net/content/no-ip-connect:

1/ wifi off
2/ eth on
3/ globe on
4/ heartbeat on
5/ power on

Successfully flashed the flukso according to the procedure mentioned above. Flash succeeds (from windows, run as administrator, reboot flukso, finds the correct arp requests and can flash it completely). Last step is "rebooting the device". Waited 10 minutes after that.

After the 10 minutes, I cannot connect to 192.168.255.1 (pc has 192.168.255.100/24, direct connection). To make it more special, when capturing the network traffic on this NIC, and filtering on the wired mac of the Flukso, i notice it sends out arp request for itself, but no response.

Frame: Number = 1008, Captured Frame Length = 60, MediaType = ETHERNET
+ Ethernet: Etype = ARP,DestinationAddress:[FF-FF-FF-FF-FF-FF],SourceAddress:[A8-40-41-00-1F-49]
- Arp: Request, 192.168.255.1 asks for 192.168.255.1
HardwareType: Ethernet
ProtocolType: Internet IP (IPv4)
HardwareAddressLen: 6 (0x6)
ProtocolAddressLen: 4 (0x4)
OpCode: Request, 1(0x1)
SendersMacAddress: A8-40-41-00-1F-49 <- mac of the wired interface of the flukso
SendersIp4Address: 192.168.255.1
TargetMacAddress: 00-00-00-00-00-00
TargetIp4Address: 192.168.255.1

From what I see, I would say that the flukso can load network L2, but not layer3.

The reset in the manual (30-60 sec or 60-120 sec) is not working either, as this requires the globe led to flash.

Any hints how I can reanimate this device?

Hi
I had flukso working for a lot of years but now every 2-3 days I see MQTT stop reporting any data.
Killing demon and restarting it helps but in 2-3 days it's dead again .
Anyone could suggest on how to troubleshoot it ?
So far i didn't find any specific issues at all . Only strange thing i see is in Sensor config synchronisation section date is still 1970 even so system time is correct.
Any recommendations/suggestions ?
Regards

Hi,

I would like to store the mqtt messages sent by my FLM02 to an influxdb/Telegraf docker combo I have running.

I'm not so familiar with Telegraf and I'm having trouble letting it parse the messages my flukso sends out.

Has anyone tried this before?
Or is there a way to change the message format to JSON instead of the array style messages?

Best regards,
Jan