SBFspot and 123solar Errors

mexjerry · April 30, 2022, 2:44pm

Thanks for the excellent instructions for getting this operational on something other than a pi.
I suffered a power outage recently, and decided to try and get this running on amd64 and debian, mostly running, see below for the issues I’m having.

using sbfspot_version 3.9.4 and 123solar 1.8.4.3, on bullseye 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux.
I have followed the wiki to compile and install SBFspot.
123solar outputs the graph, and is visible in the web gui, SBFspot is the communications.
Configured the pvout section with sysid and api.
Created the crontabs for uploads, daydata and monthdata.
Put 123solar in debug: 30/04/2022 09:26:38 Starting 123Solar debug (298565)

In 123solar, go to enhanced comm test and select comms test, this is received:
5 : Sat Apr 30 09:31:48 2022: CRITICAL: Failed to initialise Speedwire connection. ERROR !
6 : 20220430-09:31:49 120.720 7.251 1518.000 120.140 0.000 0.000 0.000 0.000 0.000 59.980 161.834 -21474836.000 0.000 14015.481 157.210 2.031 319.000 201.030 3.078 619.000 120.720 7.251 1518.000 >>>S123:OK 848.56 (ms)
7 : Sat Apr 30 09:31:51 2022: CRITICAL: Failed to initialise Speedwire connection. ERROR !

I am able to tail -f /home/jerry/smadata/2022/MySma-Spot-20220430.csv, and see data being sent to the csv file.

/usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv
SBFspot V3.9.4
Yet another tool to read power production of SMA solar inverters
© 2012-2022, SBF (https://github.com/SBFspot/SBFspot)
Compiled for Linux (LE) 64 bit with SQLite support
Commandline Args: -v -finq -nocsv
Reading config ‘/usr/local/bin/sbfspot.3/SBFspot.cfg’
Sat Apr 30 09:38:21 2022: INFO: Starting…
sunrise: 07:26
sunset : 20:13
Connecting to Local Network…
Initialising…
SUSyID: 125 - SessionID: 868673864
Device IP address: 10.0.0.33 from config
ERROR: Connection to inverter failed!
Is 10.0.0.33 a correct IP?
Sat Apr 30 09:38:23 2022: CRITICAL: Failed to initialise Speedwire connection.
Sat Apr 30 09:38:23 2022: INFO: Done.
The inverter is at 10.0.0.33 and password is correct.

So why am I able to see the data in 123solar and no upload to pvout?

mexjerry · April 30, 2022, 4:52pm

forgot a couple of things
systemctl status SBFspotUpload.service
● SBFspotUpload.service - SBFspot Upload Daemon
Loaded: loaded (/usr/local/bin/sbfspot.3/SBFspotUpload.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2022-04-30 08:57:12 CDT; 2h 52min ago
Main PID: 293471 (SBFspotUploadDa)
Tasks: 1 (limit: 14169)
Memory: 59.5M
CPU: 5min 39.832s
CGroup: /system.slice/SBFspotUpload.service
└─293471 /usr/local/bin/sbfspot.3/SBFspotUploadDaemon

Apr 30 08:57:12 thunder SBFspotUploadDaemon[293471]: SBFspotUploadDaemon Version 3.0.1
Apr 30 08:57:12 thunder SBFspotUploadDaemon[293471]: Loglevel=4
Apr 30 08:57:12 thunder SBFspotUploadDaemon[293471]: LogDir=/var/log/sbfspot.3/

Also sunnyportal and web connect to the inverter show as speedwire errors.
thanks

SBF · May 2, 2022, 8:59am

Try with IP_Address=0.0.0.0 in config for auto discovery

mexjerry · May 2, 2022, 11:17am

with 0.0.0.0 it replies:
/usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv
SBFspot V3.9.4
Yet another tool to read power production of SMA solar inverters
© 2012-2022, SBF (https://github.com/SBFspot/SBFspot)
Compiled for Linux (LE) 64 bit with SQLite support
Commandline Args: -v -finq -nocsv
Reading config ‘/usr/local/bin/sbfspot.3/SBFspot.cfg’
Mon May 2 06:01:24 2022: INFO: Starting…
sunrise: 07:25
sunset : 20:14
Connecting to Local Network…
Initialising…
SUSyID: 125 - SessionID: 922065137
Valid response from SMA device 10.0.0.33
Inverter replied: 10.0.0.33 → 413:xxxxx07
Logon OK
Have a look here:
Mexico Sun 3.892kW

The output to pvout was yesterday, the pic is yesterday as well, it acts like something is loosing comms.

SBF · May 3, 2022, 7:50am

Just wondering, is SBFspot running twice at the same time? Once for 123solar and once for pvoutput? If so, there might be a conflict.

mexjerry · May 3, 2022, 1:08pm

Commented out the cron for SBFspot, we’ll see how it goes.
I have no other crons related to upload.
I’m not sure how SBFspot hooks into 123solar, prior to the power outage, things were running fine, with no modifications.
Thanks
EDIT:
systemctl stop SBFspotUpload.service

ps ax | grep sbf
881951 ? S 0:00 sh -c timeout --kill-after=15s 10s /usr/local/bin/sbfspot.3/SBFspot -finq -q -123s=DATA -cfgSBFspot_1.cfg
881952 ? S 0:00 timeout --kill-after=15s 10s /usr/local/bin/sbfspot.3/SBFspot -finq -q -123s=DATA -cfgSBFspot_1.cfg
881953 ? S 0:00 /usr/local/bin/sbfspot.3/SBFspot -finq -q -123s=DATA -cfgSBFspot_1.cfg

This seems to suggest 123solar also calls sbfspot

If I tail -f, here is what I see:
03/05/2022 08:06:35,73.000,77.000,79.000,0.458,0.367,0.383,162.070,211.170,208.510,206.000,0.000,0.000,1.196,0.000,0.000,121.210,115.690,0.000,229.000,206.000,89.956,
0.053,14117.540,59.970,5838.855,5603.228,N/A,Ok,Closed,N/A
03/05/2022 08:06:36,74.000,78.000,79.000,0.452,0.376,0.387,165.360,207.870,205.230,206.000,0.000,0.000,1.196,0.000,0.000,121.210,115.690,0.000,231.000,206.000,89.177,
0.053,14117.540,59.970,5838.855,5603.228,N/A,Ok,Closed,N/A

SBF · May 4, 2022, 7:34am

You have the latest version of SBFspot now which may take some more time to complete than the previous installed one.

mexjerry · May 4, 2022, 10:24pm

An update, today May 4, 2022.
Seems to be functioning as it should, 123solar is tracking generation, SBFspot is uploading to pvoutput.
What I did.
Changed ethernet connection at the inverter, from A to B.
At the router, assigned a static IP, 10.0.0.251 to the inverter.
Changed SBFspot.cfg to reflect the changes.
Moved the SBFspot.db to orig.SBFspot.db
This is on a Raspberrypi, and was not sure on howto either, rebuild or repair the db, so I mv’d it, and initiated
curl -s https://raw.githubusercontent.com/sbfspot/sbfspot-config/master/sbfspot-config | sudo bash
this rebuilt the db, the following checks in the wiki worked.
Restarted 123solar, it started tracking the generation, a check of the pvoutput confirmed it was uploading.

I think the key to the problem, was moving the .db, 123solar was stuck on the 28 April, would not update, despite reboots, systemctl restarts, SBFspot did report successful communications, while not uploading to pvoutput, pvoutput never received any updates.
Thanks for the help.