Hello,
since June 15 around 09:00 UTC my Flukso device stopped sending sensor data to flukso.net (and PVOutput).
Device status:
* sensors are working and pulses are correctly processed locally
* network and DNS are OK (api.flukso.net reachable)
* heartbeat requests succeed (HTTP 200)
Issue:
All sensor uploads fail consistently:
POST https://api.flukso.net/sensor/: -151
This affects both sensors. Restarting fluksod and clearing local queues does not resolve the issue.
Only /device heartbeat works; /sensor uploads fail immediately.
No changes were made on my side. The issue started suddenly.
It looks like a backend/API change or TLS compatibility issue affecting sensor uploads.
Could you please check if anything changed recently on the /sensor endpoint or TLS requirements for legacy Flukso devices?
Thank you.
I think the certificate on api.flukso.net has expired. Hopefully Bart will be able to renew it when he gets a chance :)
Thanks. Are you having the same problem?
Yeah same problem as you. Everything is working, but its not uploading data to pvoutput or flukso.net.
Once the certificate gets renewed it should all just start working again.
I just had a quick look and i've had my flukso for 12 years now, which is amazing! A testimate to Barts work and R&D that the hardware is still going strong 12 years later
Bart - If you read this, we'd love to hear from you. even just an update on how everythings going :)
My Flukso has also stopped reporting. Do we just have to wait until the certificate has been renewed?
Hi, it really looks as though we’ll have to wait. It’s a shame, because it’s probably something that’s easy to sort out.
Ok I got my flukso updating pvoutput again now. Found some instructions from Petur in a different thread (https://flukso.net/content/graph-my-flukso-stopped?page=2)
Essentially, you can follow their instructions from the page on github and download an updated file (fluksod.lua)
Or just do what I did (brief steps and more info under)
Download putty (if you dont have it already)
Connect to your flukso via putty (SSH)
Login with username of root and password you used (default is root)
Backup the fluksod.lua file
Edit the flukso.lua file - scroll down to line 262
Change line 262 from: options.tls_context_set_verify = 'peer'
Change to: options.tls_context_set_verify = 'none'
save the file
reboot
To backup flukso.lua file:
cp /usr/sbin/fluksod.lua /usr/bin/fluksod.lua.bak
To edit the flukso.lua file:
vi /usr/sbin/flukso.lua
Use arrow keys to scroll down to line 262 and then across to "peer" with the curser on the letter p
press x and delete the word peer (leave the ' )
press i and type in none
Hit escape
Type :wq
That will save the file and put you back to the command line
type in reboot and wait for the flukso to reboot
it will take 15-30 minutes for the pv output dashboard and flukso dashboard to update with the data
Hope this helps :)
Ahh thank you ADAMCOWAN, mine is now fixed.
I wish we could still buy these, incredibly reliable last 14 years..
Regds Fm Bne Australia
Indeed the certificate for api.flukso.net expired on June 14th.
Thanks for the advice, it worked right away.
You can skip the edition in vi by using sed instead. Make sure to create a backup with the cp command first !
sed -i "262s/'peer'/'none'/" /usr/sbin/fluksod.lua
Note that my fix only works for FLM2, not FLM3, have not figured out how that firmware connects as it's no longer a lua script but a binary (I think) and I don't find any sources
So my FLM2 is still working but the FLM3 is 'out' again
@ Petur
Hi, my Flukso's have the same problem.
I am currently using the script that VK2HIM created, and that works fine.
Yesterday (Windows update) my Home Assistant stopped working, which meant no data was being sent to PVoutput.
If I use your fix, no settings will be lost, nor will the sensor data and tokens change, VK2HIM's script depends on that.
If that works, would you check the commands, because I see another improvement thanks to NUDUPONT.
At 73, a clear line of commands is highly appreciated.
if you have an FLM02 you can use my patch, nothing of sensors or data is changed.
the method is available here:
https://github.com/peturdainn/flm02_patch
on Windows you need an SSH client (for example putty), and need to know the IP address of your flukso and the login (what you use on the FLM02 local webinterface)
Thanks for sharing Petur - FLM02 still going strong !
I have same prob. What is best resource for none techy
@petur Both Flukos are working again and displaying graphs in the Dash.
Thanks
ok, i will do again the steps, but first i will look at my backup of 2024 (if found) how i did it, it don't want to make mistakes. Tough almost lost my FLM02 a few times, like it was bricked of so.