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.
I already replaced the power supply, to rule out that factor.
Wow - mine also bricked itself today - I'm having trouble finding the ap51-flash-gui.exe program as the link in the no-ip method doesn't work. Would you be able to share the file please? Sorry I have no clues to help your problem though. Thanks Ian vk2him at gmail . com
I recall reading in an old forum posting that Bart said if the reflash didn't work, then there isn't much else you can do. If you're not getting the heartbeat after the flash, then I think there's nothing else you could do.
When I reflashed mine just now, it takes about 40 seconds to flash, then a few lights go off , it then takes about a minute and the lights come back on with the heartbeat. I hen had to reset the network by holding the button for about 20 seconds and I could then go to 192.168.255.1 ...
I'd really like to buy a new one - did Bart reply to your emails? Thanks
for me the lights after the full (successfull) flash never go off, it seems the reset is never executed.
Bart didn't reply yet.
10 years of uninterrupted service is a thing... So, one root cause may also be that the flash memory itself is corrupt, what also may happen as these chips age, too. Same applies to old SolarLog hardware on which the internal flash memory just dies. Then there is a reflow necessary or a replacement of the complete unit. R.I.P. (as the clamps mostly don't perish, there is the option to build a replacement using a simple ESP8266/NodeMCU and some open source software for integration in e.g., HomeAssistant) These days Smart Home is just some clicks away and rather cheap.
I agree but the usability/stabilty of a home build vs a pre-build solution is often quite different. And trust me, I'm a happy user of HomeAssistant, with ESPhome and tasmota nodes for ESP8266 relay controllers, ebusd adapter with Wemos D1 as comm module and also 40+ Zigbee devices).
The Flukso box always served me well. The web stats/graphs were very usefull and the integration towards HA using MQTT was powerfull voor automations.
I don't want to spend the time hacking a (just as good) solution together again, with InfluxDB + grafana for visualisations, based on again 3 custom nodes, only for less or (maximum) comparable insight.
I did it before with other sensors, it worked nicely. I did spent too much time at it but it's overkill for what I need it to be.
I'm up to my ears in personal (and new job) projects already and time is limited :(
And I have no problem (de/re)soldering SMD components, I have my microscope for microsoldering, to have a working solution again with not too much trouble.
If you think it's the flash chip(s) acting up, I saw some winbond flash chips under the sensor module on the board, I can order 2 and replace them.
This evening I'll have a look for the exact types and order a few from Ali or a local distributor if I can combine with another order
Maybe first try an onboard memory consistency and health check provided by the onboard OS (actually the FLM itself "should" perform such health checking already, so check the logs)...
If people need to replace their flash chip, it's a Winbond W25Q64CVFIG type.
So it's a 64Mbit SPI flash in a SOIC-16 package. Bigger size (in Mbits) should be fine, as long as it's the same voltage and package type.
My replacement is somewhere in Chinese warehouse, on it's way to Belgium.
If it ever gets here, after replacing, I'll update the result (good or bad) after reflashing.
I am able to reflash my flukso, but after it reboots i can't connect to it.
It's connected to my computer using the same cable to flash it, but when i try to connect using 192.168.255.1 i get an error page.
When i check my network adapter page i see it has a windows default IP 169.254...
Anyone has an idea if my flukso chip will also be dead?
But why would i then be able to flash it with success?
@Hero - I assume you have ethernet reporting enabled as this disables DHCP - if so try setting a static IP - I use 192.168.255.11 - When it's in wifi reporting mode, DHCP is enabled.
@VK2HIM, i will try that.
I tried to use the mode switch but that doesn't seem to work.
Not tested yet to apply a static IP to it.