This thread is getting very long. Should I start one for my issues?
Anywaystill the same error after a couple of clean rebuilds No module named “paho”
I am really stuck after fiddling around all last night and today 
I rekon my brain tumor is growing back 
Anyone got it working on a rpi 400 (4)
I wish I knew why it worked initially for a day?
This might be the answer;?? Waiting to see what happens.
sudo pip3 install paho-mqtt
In lieu of: pip install paho-mqtt
Nice work.
Can you document what steps you required that were different to the readme to get everything working so I can post them in the script page for other users of a pi4 with bookworm. or if you need to get it going again some other time…
im not sure if your playing around with it or the readings are playing up?
Like a roller Coaster at the moment. I had to swap the sensor codes around again in the script.
https://pvoutput.org/intraday.jsp?id=1335&sid=4380
Not me, every 10mins . Only been running for about 25mins so far.
Might be something to do with the 5minute call?
I will try to see what I did. A lot of forum reading and script lines in there BUT I believe its the step in post above …sudo pip3 install paho-mqtt
The sudo and pip3 changes.
what version did you end up using?
do you have any rules set by any chance?
zip off this page…whats a “Rule” ha ha
thats the same version you ran before and it seemed to work fine.
not sure whats happening.
Edit:
Seems to be working fine now
1 Like
Clue I think was in this thread, last post.
https://forums.raspberrypi.com/viewtopic.php?t=176131
Plus the Answer on this page
just noticed my script somehow stopped uploading at at 1am this morning.
just done a stop and start and its working again… it has been up for about 7 days without issue.
sudo systemctl stop flukso2pvoutput_mqtt.servicesudo systemctl start flukso2pvoutput_mqtt.service
I should have tried
sudo systemctl status flukso2pvoutput_mqtt.service and seen what the script was saying…
debug log didnt show anything other than. just stopping after writing the adjusted values but never got to send to pvouput.
2024-06-17 01:00:00 - Initial payload: {‘d’: ‘20240617’, ‘t’: ‘01:00’, ‘v1’: 0, ‘v2’: 0, ‘v3’: 0, ‘v4’: 193, ‘v5’: 0, ‘v6’: 0, ‘v7’: 0, ‘v8’: 0, ‘v9’: 0, ‘v10’: 0, ‘v11’: 0, ‘v12’: 0}
2024-06-17 01:00:00 - Adjusted payload: {‘d’: ‘20240617’, ‘t’: ‘01:00’, ‘v1’: 0, ‘v2’: 0, ‘v3’: 0, ‘v4’: 193, ‘v5’: 0, ‘v6’: 0, ‘v7’: 0, ‘v8’: 0, ‘v9’: 0, ‘v10’: 0, ‘v11’: 0, ‘v12’: 0}
2024-06-17 01:00:02 - Sent data to PVOutput: 200 OK 200: Added Status
2024-06-17 01:00:02 - Payload: {‘d’: ‘20240617’, ‘t’: ‘01:00’, ‘v4’: 193, ‘v7’: 0, ‘v8’: 0}
2024-06-17 01:05:00 - Initial payload: {‘d’: ‘20240617’, ‘t’: ‘01:05’, ‘v1’: 0, ‘v2’: 0, ‘v3’: 0, ‘v4’: 267, ‘v5’: 0, ‘v6’: 0, ‘v7’: 0, ‘v8’: 0, ‘v9’: 0, ‘v10’: 0, ‘v11’: 0, ‘v12’: 0}
2024-06-17 01:05:00 - Adjusted payload: {‘d’: ‘20240617’, ‘t’: ‘01:05’, ‘v1’: 0, ‘v2’: 0, ‘v3’: 0, ‘v4’: 267, ‘v5’: 0, ‘v6’: 0, ‘v7’: 0, ‘v8’: 0, ‘v9’: 0, ‘v10’: 0, ‘v11’: 0, ‘v12’: 0}
Bugger…
Welcome to the Party
Im sure you will find the issue quicker than me .
v1 has been running stable sending my hot water since before this script was available on github.
v3 is the one that crashed after 7 days. that is doing counters for water and just sending power values for the fun of it.
I have updated it to 3.2 and its working fine atm. I don’t need rules or net metering on it so no real gain.
will see how long this one goes for…
anyone that’s competent in python see any reason it would crash? only possible thought is it having to ‘remember’ too much data ? but its meant to clear the readings ever loop too so …
1 Like
Mine seems to be steady now with this script settings.
Solar input and Consumption plus temp now working from pvoutput settings.
But why sensor 2 and sensor 4 and not sensor 1 and 2?
@ciarly
I did wonder that myself.
At a guess maybe that’s where they are in the flukso?
It doesn’t matter where they go so not a big issue
@ciarly I am using the Pulse inputs NOT currents clamps on the Flukso if that was your question.
But I dont think it was.
I believe I was instructed to use 2 and 4 earlier in this conversation?
BUT it seems to work. 
1 Like
@bazzle
That was to use v2 and v4 as the pvoutput “v” values
Sensors can go anywhere.
I assume everyone would just use 1 to 5 in that order.
It’s working so don’t mess with it 
2 Likes
I also recommend setting up an idle system alert so if the script stops for some reason you can stop/start the service again…
edit your system and enable this
Good idea. Done.
Hi All, I have just finished setting up and testing a PVOutput system using a Flukso Version 3 with it’s current clamps not setup in the normal positions to export (v2) generation and (v4) consumption. In this case the clamps had been placed on the inverter output (v2) generation and the connect going to the grid. As a result the Custom Rules was setup to use the bi-direction function of the Flukso V3 to calcuate the house consumption (v4) so the script exported Generation (v2) and Consumption (v4) to pvoutput in the normal manner. It’s important to reference the Rules_HowTo_F2PVO contained at GitHub - B-Mqn/FluksoToPvoutput at B-Mqn-patch-1.
The document attached gives some examples of Flukso V2 and V3 being used in diferent setups and using the Customer Rules. Pages 6 and 7 show the setup discribed above.
I hope this helps someone, but please reference “Rules_HowTo_F2PVO” for the details how to construct the custom rules.
2 Likes