SBFspot Bluetooth homeassistant addon

HasQT · March 17, 2024, 8:48pm

Hi,
Sorry I’m abit confused here, can you explain your setup again.

You have a raspberry zero working with sbfspot installed directly? This is in range of your inverter.

You also have a HA server setup and want to run sbfspot on that to connect to your inverter? At a further distance I presume.

The addon isn’t designed to extend the range on a pi Zero. If the piZero is sending out MQTT data, you can receive the MQTT data in your Homeassistant server (without the sbfspot addon) you just need to make mqtt sensors available.

hilmar65 · March 18, 2024, 5:27pm

Hello HasQT,

thanks for your answer. Sorry for my description, but I am a beginner in HA.

Perhaps the following topology helps you, to understand my installation.

In the mqtt-explorer in HA I can‘t find the SBFspot-topics. When I try to connect HA via the addon SBFspot, I get no connection.

Can you help me and give me any tips.

Thank you for your feedback.

Hilmar

HasQT · March 18, 2024, 8:17pm

That is clearer, thanks.

So…

To be clear here.
You can’t link the piZero to the pi4 with sbfspot… It’s not designed like that.

The piZero, pi4, and MQTT-explorer need to be using the same server settings. Assuming you have that sorted and you are able to find the SBFspot MQTT data from the piZero.

Then:

What you want to do is have the pi4(homeassistant) receive the MQTT data from the piZero sbfspot. To do that the pi4(HA) needs to have some MQTT sensors created.

There are multiple ways to create MQTT sensors.

You can write them manually into your config.yaml (there are old examples on the addon github in the images directory). They need to match the MQTT data the piZero is producing.
You can write them for auto discovery by the MQTT integration in homeassistant. This is achievable, but quite the learning curve.
You can use this addon to create the sensors via discovery. This is possible if you can get a connection to the inverter(as in move your pi4 in range of the inverter). You really only need to do it once in your scenario to create the sensors, you could then delete the addon and have the piZero send out the MATCHING MQTT data.
You could also try to fool the addon into believing it has a connection to the inverter by creating a file in the addon with the inverter details. It should then be able to create the sensors as it would with a connection like option 3. If you want to try this method I can write you a detailed method.

For options 3 and 4 the piZero sbfspot needs to send the specific MQTT data that matches the sensor set ups.

hilmar65 · March 19, 2024, 6:26pm

Thanks for your answer,

I think, I’ll try it on next weekend.

After this, I will sent the result.

Greets

Hilmar

hilmar65 · March 24, 2024, 5:21pm

Hello HasQT,
today I get the PV-yield in HA (see following picture) by using configuration.yaml.

Thanks and greets

Hilmar

heli01 · July 17, 2024, 1:49pm

Hi, I’m quite new to HA and I have a few problems with this plugin. Perhaps somebody could help me a little bit…
I’m using HAOS in a virtual machine under proxmox, everything works fine so far.
On my PV I have to WR, one SMA Sunnyboy TL5000 with build in bluetooth a one SMA SunnyBoy TL2500 on which I put an bluetooth add-on card to communicate with.
Both SunnyBoy work on the same netID, t think it’s “2”.
When I set the MIS=0 I get this error:

[15:41:39] INFO: 
[15:41:39] INFO:  Linux 6.6.33-haos #1 SMP PREEMPT_DYNAMIC Tue Jun 18 13:51:59 UTC 2024 x86_64
[15:41:39] INFO: 
|   SKIPPING MQTT SENSOR CREATION   |
s6-rc: info: service legacy-services successfully started
[15:41:40] INFO: 
[15:41:40] INFO: 
[15:41:40] INFO:  [Host Bluetooth MAC Address] Controller B8:9A:2A:D7:E2:A8 homeassistant [default]
[15:41:40] INFO: 
[15:41:40] INFO: 
[15:41:40] INFO:  ||    Generating Bluetooth Configs    ||
[15:41:40] INFO:  ||    /usr/bin/sbfspot/SBFspot.cfg    ||
[15:41:40] INFO:  || /usr/bin/sbfspot/SBFspotUpload.cfg ||
[15:41:40] INFO: 
[15:41:40] INFO:  [Starting SBFspotUpload]
[15:41:40] INFO: [Starting cron in foreground]
SBFspot V3.9.11
Yet another tool to read power production of SMA solar inverters
(c) 2012-2024, SBF (https://github.com/SBFspot/SBFspot)
Compiled for Linux (LE) 64 bit with MySQL support
Commandline Args: -v -ad0 -am0 -mqtt -finq
Reading config '/usr/bin/sbfspot/SBFspot.cfg'
Wed Jul 17 15:42:10 2024: INFO: Starting...
sunrise: 05:28
sunset : 21:33
Connecting to 00:80:25:1C:2E:C1 (1/10)
Connecting to 00:80:25:1C:2E:C1 (2/10)
Connecting to 00:80:25:1C:2E:C1 (3/10)
Connecting to 00:80:25:1C:2E:C1 (4/10)
Connecting to 00:80:25:1C:2E:C1 (5/10)
Connecting to 00:80:25:1C:2E:C1 (6/10)
Connecting to 00:80:25:1C:2E:C1 (7/10)
Connecting to 00:80:25:1C:2E:C1 (8/10)
Connecting to 00:80:25:1C:2E:C1 (9/10)
Connecting to 00:80:25:1C:2E:C1 (10/10)
Wed Jul 17 15:42:19 2024: CRITICAL: bthConnect() returned -1
Wed Jul 17 15:42:19 2024: INFO: Done.
Configuration Error: Syntax error on line 34 [/usr/bin/sbfspot/SBFspotUpload.cfg]

When I set MIS=1 the error is a little bit different:

SBFspot V3.9.11
Yet another tool to read power production of SMA solar inverters
(c) 2012-2024, SBF (https://github.com/SBFspot/SBFspot)
Compiled for Linux (LE) 64 bit with MySQL support
Commandline Args: -v -ad1 -am0 -ae0 -mqtt
Reading config '/usr/bin/sbfspot/SBFspot.cfg'
Wed Jul 17 15:40:00 2024: INFO: Starting...
sunrise: 05:28
sunset : 21:33
Connecting to 00:80:25:1C:2E:C1 (1/10)
Connecting to 00:80:25:1C:2E:C1 (2/10)
Connecting to 00:80:25:1C:2E:C1 (3/10)
Connecting to 00:80:25:1C:2E:C1 (4/10)
Connecting to 00:80:25:1C:2E:C1 (5/10)
Connecting to 00:80:25:1C:2E:C1 (6/10)
Connecting to 00:80:25:1C:2E:C1 (7/10)
Connecting to 00:80:25:1C:2E:C1 (8/10)
Connecting to 00:80:25:1C:2E:C1 (9/10)
Connecting to 00:80:25:1C:2E:C1 (10/10)
Wed Jul 17 15:40:09 2024: CRITICAL: bthConnect() returned -1
Wed Jul 17 15:40:09 2024: INFO: Done.

The MQTT Sensors have been created, but I don’t get any data from both SunnyBoys.
Has anyone an idea where my problem is?
Sorry for my bad english…

HasQT · July 18, 2024, 12:37am

Your main issue is you are not getting a Bluetooth connection to your inverter.

This is usually due to the distance between your BT dongle/HA server and inverter. Although it is very much complicated by virtual machines, proxmox and hardware pass through.

You previously had this working? Your post from Feb 3 seems to indicate that. What has changed since then?

Line 34 in the Upload.cfg is usually PVoutput SID there may be a typo there or perhaps how the MIS=0 is being input.

MIS_Enabled: 0

heli01 · July 20, 2024, 9:07am

thanks for your answer!

I nearly had to change everything because of a hardware crash
The strange thing is that the mqtt sensors have been created for both inverters without any problems. Because of this I think the bluetooth connection has to be ok. The inverters a the proxmox host are located in a very short distance, under 1m.

HasQT · July 20, 2024, 10:30am

If you restored a previous version that had already connected via Bluetooth and made the sensors, then those sensors will exist.

The Bluetooth connection is not working in either of those logs you have provided above.

The sensor creation will generally do something even without a Bluetooth connection. It won’t necessarily create working sensors.

It might also be worth checking this page. Although I think most of these requirements are automatically installed thses days…

I haven’t ever played around with proxmox.
You might be able to spin up a Linux container to install the official SBFspot install and check if that is working with your Bluetooth dongle and hardware pass through.

heli01 · July 21, 2024, 7:50am

Thank you so far, I think you‘re right because I just have seen that the Bluetooth Mac adress which you can see in the logs above, ist the Mac of my intern Bluetooth device and not the one of the Bluetooth usb dongle which it should be…so I have to test something different to get it work.

mjude · December 2, 2024, 2:38pm

Hello HasQT,

I got a 1280 error code on SBFspot log:

Client null sending CONNECT
Connection error: Connection Refused: not authorised.
Client null received CONNACK (5)
Error: The connection was refused.
MQTT: Failed to execute '/usr/bin/mosquitto_pub' mosquitto client installed?
Error 1280 while publishing to MQTT Broker

I only found @tropfen with the same error code, but sadly the solution that solved his problem don’t seems to solve mine. I hope you’ll be able to easily read the problem and willing to help me

SBFspot complete log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun sbfspot (no readiness notification)
s6-rc: info: service legacy-services successfully started
[15:12:01] INFO: 
[15:12:01] INFO:  Linux 6.6.31-haos-raspi #1 SMP PREEMPT Tue Oct 15 12:43:14 UTC 2024 aarch64
[15:12:01] INFO: 
|   INITIALISE MQTT SENSOR CREATION   |
SunnyBoyBT
core-mosquitto
mqtt_mqtt
homeassistant/sbfspot_{plantname}/sbfspot_{serial}
PrgVersion,Plantname,Timestamp,SunRise,SunSet,InvSerial,InvName,InvTime,InvStatus,InvSwVer,InvClass,InvType,InvTemperature,InvGridRelay,EToday,ETotal,GridFreq,PACTot,PAC1,UAC1,IAC1,OperTm,FeedTm,PDCTot,UDC1,UDC2,IDC1,IDC2,PDC1,PDC2,BTSignal,InvWakeupTm,InvSleepTm
[15:12:02] INFO: Using Existing Device info
PrgVersion Plantname Timestamp SunRise SunSet InvSerial InvName InvTime InvStatus InvSwVer InvClass InvType InvTemperature InvGridRelay EToday ETotal GridFreq PACTot PAC1 UAC1 IAC1 OperTm FeedTm PDCTot UDC1 UDC2 IDC1 IDC2 PDC1 PDC2 BTSignal InvWakeupTm InvSleepTm
[15:12:02] INFO: Setting Up PrgVersion
[15:12:02] INFO: Setting Up Plantname
[15:12:02] INFO: Setting Up InvName
[15:12:02] INFO: Setting Up Timestamp
[15:12:02] INFO: Setting Up InvTime
[15:12:02] INFO: Setting Up SunRise
[15:12:02] INFO: Setting Up SunSet
[15:12:02] INFO: Setting Up InvSerial
[15:12:02] INFO: Setting Up InvClass
[15:12:02] INFO: Setting Up InvType
[15:12:02] INFO: Setting Up InvSwVer
[15:12:02] INFO: Setting Up InvStatus
[15:12:02] INFO: Setting Up InvTemperature
[15:12:02] INFO: Setting Up InvGridRelay
[15:12:02] INFO: Setting Up EToday
[15:12:02] INFO: Setting Up ETotal
[15:12:02] INFO: Setting Up PACTot
[15:12:02] INFO: Setting Up PAC1
Skipping PAC2
Skipping PAC3
[15:12:02] INFO: Setting Up UAC1
Skipping UAC2
Skipping UAC3
[15:12:02] INFO: Setting Up IAC1
Skipping IAC2
Skipping IAC3
[15:12:02] INFO: Setting Up OperTm
[15:12:02] INFO: Setting Up FeedTm
[15:12:02] INFO: Setting Up PDCTot
[15:12:02] INFO: Setting Up PDC1
[15:12:02] INFO: Setting Up PDC2
Skipping PDC
[15:12:02] INFO: Setting Up UDC1
[15:12:02] INFO: Setting Up UDC2
Skipping UDC
[15:12:02] INFO: Setting Up IDC1
[15:12:02] INFO: Setting Up IDC2
Skipping IDC
[15:12:02] INFO: Setting Up GridFreq
[15:12:02] INFO: Setting Up BTSignal
Skipping BatTmpVal
Skipping BatVol
Skipping BatAmp
Skipping BatChaStt
[15:12:02] INFO: Setting Up InvWakeupTm
[15:12:03] INFO: Setting Up InvSleepTm
Skipping MeteringWOut
Skipping MeteringWIn
Skipping MeteringWTot
[15:12:04] INFO: 
[15:12:04] INFO: 
[15:12:04] INFO:  [Host Bluetooth MAC Address] Controller DC:A6:32:EE:3C:DD homeassistant [default]
[15:12:04] INFO: 
[15:12:04] INFO: 
[15:12:04] INFO:  ||    Generating Bluetooth Configs    ||
[15:12:04] INFO:  ||    /usr/bin/sbfspot/SBFspot.cfg    ||
[15:12:04] INFO:  || /usr/bin/sbfspot/SBFspotUpload.cfg ||
[15:12:04] INFO: 
[15:12:04] INFO:  [Starting SBFspotUpload]
[15:12:04] INFO: [Starting cron in foreground]
SBFspot V3.9.11
Yet another tool to read power production of SMA solar inverters
(c) 2012-2024, SBF (https://github.com/SBFspot/SBFspot)
Compiled for Linux (LE) 64 bit with MySQL support
Commandline Args: -v -ad0 -am0 -mqtt -finq
Reading config '/usr/bin/sbfspot/SBFspot.cfg'
Mon Dec  2 15:12:34 2024: INFO: Starting...
INFO: SBFspotUploadDaemon Version 3.0.4
DEBUG: Retrieving new datapoints from DB...
sunrise: 07:55
sunset : 17:03
Connecting to 00:80:25:xx:xx:xx (1/10)
Initialising...
SUSyID: 125 - SessionID: 935616741
SMA netID=01
Serial Nr: 7D2F4587 (2100249991)
BT Signal=73.3%
Logon OK
SUSyID: 113 - SN: 2100249991
Device Name:      SN: 2100249991
Device Class:     Solar Inverters
Device Type:      SB 3000TL-20
Software Version: 02.08.01.R
Packet status: 21
SUSyID: 113 - SN: 2100249991
Device Status:      Ok
SUSyID: 113 - SN: 2100249991
Device Temperature: 42.1°C
SUSyID: 113 - SN: 2100249991
GridRelay Status:      Closed
SUSyID: 113 - SN: 2100249991
Energy Production:
	EToday: 5.086kWh
	ETotal: 55013.757kWh
	Operation Time: 57198.59h
	Feed-In Time  : 55536.87h
SUSyID: 113 - SN: 2100249991
DC Spot Data:
	MPPT 1 Pdc:   0.588kW - Udc: 278.29V - Idc:  2.116A
	MPPT 2 Pdc:   0.000kW - Udc:   0.00V - Idc:  0.000A
	Calculated Total Pdc:   0.588kW
AC Spot Data:
	Phase 1 Pac :   0.573kW - Uac: 227.49V - Iac:  2.522A
	Phase 2 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
	Phase 3 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
	Total Pac   :   0.573kW - Calculated Pac:   0.573kW
	Efficiency  :   97.45%
SUSyID: 113 - SN: 2100249991
Grid Freq. : 50.00Hz
SUSyID: 113 - SN: 2100249991
Current Inverter Time: 2014-11-16T07:14:57+0100
Inverter Wake-Up Time: 2014-11-16T00:04:35+0100
Inverter Sleep Time  : 2014-11-16T07:14:57+0100
MQTT: Publishing (homeassistant/sbfspot_{plantname}/sbfspot_{serial}),"PrgVersion": "3.9.11","Plantname": "SunnyBoyBT","Timestamp": "2024-12-02T15:13:06+0100","SunRise": "2024-12-02T07:55:00+0100","SunSet": "2024-12-02T17:03:00+0100","InvSerial": 2100249991,"InvName": "SN: 2100249991","InvTime": "2014-11-16T07:14:57+0100","InvStatus": "Ok","InvSwVer": "02.08.01.R","InvClass": "Solar Inverters","InvType": "SB 3000TL-20","InvTemperature": 42.090,"InvGridRelay": "Closed","EToday": 5.086,"ETotal": 55013.757,"GridFreq": 50.000,"PACTot": 573.000,"PAC1": 573.000,"UAC1": 227.490,"IAC1": 2.522,"OperTm": 57198.591,"FeedTm": 55536.872,"PDCTot": 588.000,"UDC1": 278.290,"UDC2": 0.000,"IDC1": 2.116,"IDC2": 0.000,"PDC1": 588.000,"PDC2": 0.000,"BTSignal": 73.333,"InvWakeupTm": "2014-11-16T00:04:35+0100","InvSleepTm": "2014-11-16T07:14:57+0100"
Client null sending CONNECT
Connection error: Connection Refused: not authorised.
Error: The connection was refused.
Client null received CONNACK (5)
MQTT: Failed to execute '/usr/bin/mosquitto_pub' mosquitto client installed?
Error 1280 while publishing to MQTT Broker
Reading events: 2024-Dec-01
Mon Dec  2 15:13:06 2024: INFO: Done.
SBFspot V3.9.11
Yet another tool to read power production of SMA solar inverters
(c) 2012-2024, SBF (https://github.com/SBFspot/SBFspot)
Compiled for Linux (LE) 64 bit with MySQL support
Commandline Args: -v -ad1 -am0 -ae0 -mqtt
Reading config '/usr/bin/sbfspot/SBFspot.cfg'
Mon Dec  2 15:15:00 2024: INFO: Starting...
DEBUG: Retrieving new datapoints from DB...
sunrise: 07:55
sunset : 17:03
Connecting to 00:80:25:xx:xx:xx (1/10)
Initialising...
SUSyID: 125 - SessionID: 968838168
SMA netID=01
Serial Nr: 7D2F4587 (2100249991)
BT Signal=73.3%
Logon OK
SUSyID: 113 - SN: 2100249991
Device Name:      SN: 2100249991
Device Class:     Solar Inverters
Device Type:      SB 3000TL-20
Software Version: 02.08.01.R
Packet status: 21
SUSyID: 113 - SN: 2100249991
Device Status:      Ok
SUSyID: 113 - SN: 2100249991
Device Temperature: 42.1°C
SUSyID: 113 - SN: 2100249991
GridRelay Status:      Closed
SUSyID: 113 - SN: 2100249991
Energy Production:
	EToday: 5.106kWh
	ETotal: 55013.777kWh
	Operation Time: 57198.63h
	Feed-In Time  : 55536.91h
SUSyID: 113 - SN: 2100249991
DC Spot Data:
	MPPT 1 Pdc:   0.460kW - Udc: 278.22V - Idc:  1.658A
	MPPT 2 Pdc:   0.000kW - Udc:   0.00V - Idc:  0.000A
	Calculated Total Pdc:   0.460kW
AC Spot Data:
	Phase 1 Pac :   0.451kW - Uac: 228.34V - Iac:  1.977A
	Phase 2 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
	Phase 3 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
	Total Pac   :   0.451kW - Calculated Pac:   0.451kW
	Efficiency  :   98.04%
SUSyID: 113 - SN: 2100249991
Grid Freq. : 50.01Hz
SUSyID: 113 - SN: 2100249991
Current Inverter Time: 2014-11-16T07:17:22+0100
Inverter Wake-Up Time: 2014-11-16T00:04:35+0100
Inverter Sleep Time  : 2014-11-16T07:17:23+0100
MQTT: Publishing (homeassistant/sbfspot_{plantname}/sbfspot_{serial}),"PrgVersion": "3.9.11","Plantname": "SunnyBoyBT","Timestamp": "2024-12-02T15:15:32+0100","SunRise": "2024-12-02T07:55:00+0100","SunSet": "2024-12-02T17:03:00+0100","InvSerial": 2100249991,"InvName": "SN: 2100249991","InvTime": "2014-11-16T07:17:22+0100","InvStatus": "Ok","InvSwVer": "02.08.01.R","InvClass": "Solar Inverters","InvType": "SB 3000TL-20","InvTemperature": 42.140,"InvGridRelay": "Closed","EToday": 5.106,"ETotal": 55013.777,"GridFreq": 50.010,"PACTot": 451.000,"PAC1": 451.000,"UAC1": 228.340,"IAC1": 1.977,"OperTm": 57198.632,"FeedTm": 55536.913,"PDCTot": 460.000,"UDC1": 278.220,"UDC2": 0.000,"IDC1": 1.658,"IDC2": 0.000,"PDC1": 460.000,"PDC2": 0.000,"BTSignal": 73.333,"InvWakeupTm": "2014-11-16T00:04:35+0100","InvSleepTm": "2014-11-16T07:17:23+0100"
Client null sending CONNECT
Connection error: Connection Refused: not authorised.
Client null received CONNACK (5)
Error: The connection was refused.
MQTT: Failed to execute '/usr/bin/mosquitto_pub' mosquitto client installed?
Error 1280 while publishing to MQTT Broker
********************
* ArchiveDayData() *
********************
startTime: 02/12/2024 00:00:00
Mon Dec  2 15:15:32 2024: INFO: Done.
[15:15:45] INFO: [SBFspot Upload Log Latest]

I’m absolutely unsure about what I’m reading. to me it seems everything is fine when getting BT data from the SunnyBoy, but error happens when trying to publish data to MQTT Broker.

MQTT Broker log:

2024-12-02 15:12:02: New connection from 172.30.x.x:38406 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38406 as auto-E4232AA7-79E2-5DFF-21BA-1C255070095A (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-E4232AA7-79E2-5DFF-21BA-1C255070095A disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38412 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38412 as auto-D8BB9254-84BA-14BA-6E8A-C32C19CCACFD (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-D8BB9254-84BA-14BA-6E8A-C32C19CCACFD disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38424 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38424 as auto-FA8D161D-462D-CC00-CCDD-E0FF21093B62 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-FA8D161D-462D-CC00-CCDD-E0FF21093B62 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38440 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38440 as auto-320346BF-6399-525A-CC28-5F68D8B1B06E (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-320346BF-6399-525A-CC28-5F68D8B1B06E disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38454 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38454 as auto-57211E11-73E3-430D-6785-9AC151D86482 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-57211E11-73E3-430D-6785-9AC151D86482 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38462 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38462 as auto-084D9F6D-9AB6-EA51-CCB2-2B5628F9651A (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-084D9F6D-9AB6-EA51-CCB2-2B5628F9651A disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38476 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38476 as auto-F3E8A487-658B-3AAB-8263-C7EA09A1413B (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-F3E8A487-658B-3AAB-8263-C7EA09A1413B disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38482 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38482 as auto-C18F03F4-FC4A-A701-4A3A-CEF1CAFD56BC (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-C18F03F4-FC4A-A701-4A3A-CEF1CAFD56BC disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38492 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38492 as auto-7199A4EA-9855-7609-8A99-5EB482A5FDFD (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-7199A4EA-9855-7609-8A99-5EB482A5FDFD disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38496 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38496 as auto-98C32398-ED5B-AF95-7CFF-8B1200955BD0 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-98C32398-ED5B-AF95-7CFF-8B1200955BD0 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38502 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38502 as auto-8F6C7C23-E071-F01B-5AF2-DD9D7F9ADC32 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-8F6C7C23-E071-F01B-5AF2-DD9D7F9ADC32 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38506 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38506 as auto-A735ABFE-AA0B-6795-191F-B3517E125D85 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-A735ABFE-AA0B-6795-191F-B3517E125D85 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38510 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38510 as auto-4D39DFBD-9050-4B27-2C19-F805BF4E3E0B (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-4D39DFBD-9050-4B27-2C19-F805BF4E3E0B disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38526 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38526 as auto-DF8C7796-8DE5-37B0-BFDC-E3A5A8C29280 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-DF8C7796-8DE5-37B0-BFDC-E3A5A8C29280 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38540 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38540 as auto-B6B87853-7096-A55D-EDB2-F6AF1BD7B39E (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-B6B87853-7096-A55D-EDB2-F6AF1BD7B39E disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38556 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38556 as auto-CABEC730-BBCC-FCD7-2630-AD7E217B71D9 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-CABEC730-BBCC-FCD7-2630-AD7E217B71D9 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38572 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38572 as auto-B05D0353-6CB6-F34B-5ED0-957009E56AEA (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-B05D0353-6CB6-F34B-5ED0-957009E56AEA disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38580 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38580 as auto-21E4F8BE-40C8-C1EF-993E-B474F80FFCEB (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-21E4F8BE-40C8-C1EF-993E-B474F80FFCEB disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38590 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38590 as auto-A9BEB2AE-C303-8C82-CF3F-96F3493EB19A (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-A9BEB2AE-C303-8C82-CF3F-96F3493EB19A disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38594 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38594 as auto-2D21E0E6-FFFF-03C1-0BF9-82E770195F30 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-2D21E0E6-FFFF-03C1-0BF9-82E770195F30 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38610 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38610 as auto-9250E044-84F1-13E8-30F0-557B208A35BA (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-9250E044-84F1-13E8-30F0-557B208A35BA disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38618 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38618 as auto-D1E573E1-F57A-44FA-285C-D9574E59D578 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-D1E573E1-F57A-44FA-285C-D9574E59D578 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38624 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38624 as auto-04169935-A588-488B-88C9-4C3328D328E3 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-04169935-A588-488B-88C9-4C3328D328E3 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38628 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38628 as auto-3537B222-4460-61D5-D20E-E3E6ADCE1A2D (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-3537B222-4460-61D5-D20E-E3E6ADCE1A2D disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38642 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38642 as auto-3335A5AC-1639-81D7-66F6-AB1DD6777CE4 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-3335A5AC-1639-81D7-66F6-AB1DD6777CE4 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38644 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38644 as auto-CE8D8B37-C28F-8F2F-D948-8396D0A3D724 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-CE8D8B37-C28F-8F2F-D948-8396D0A3D724 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38656 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38656 as auto-C57723C9-81E8-A47A-71A6-E7A2FBCA7380 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-C57723C9-81E8-A47A-71A6-E7A2FBCA7380 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38660 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38660 as auto-C9C7625C-C4E1-6246-3C52-38A9FE4CD219 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-C9C7625C-C4E1-6246-3C52-38A9FE4CD219 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38668 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38668 as auto-E999DC6F-F5D5-3646-0EFC-96E99D1A8F51 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-E999DC6F-F5D5-3646-0EFC-96E99D1A8F51 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38678 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38678 as auto-1C5D2504-DE65-730C-C707-F574266DA756 (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-1C5D2504-DE65-730C-C707-F574266DA756 disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38694 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38694 as auto-1EEB723A-0D6D-E628-5E2D-BED9403DE09D (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-1EEB723A-0D6D-E628-5E2D-BED9403DE09D disconnected.
2024-12-02 15:12:02: New connection from 172.30.x.x:38706 on port 1883.
2024-12-02 15:12:02: New client connected from 172.30.x.x:38706 as auto-F9DECDF3-EA8B-101F-0B3F-B956BAE5790F (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:02: Client auto-F9DECDF3-EA8B-101F-0B3F-B956BAE5790F disconnected.
2024-12-02 15:12:03: New connection from 172.30.x.x:38710 on port 1883.
2024-12-02 15:12:03: New client connected from 172.30.x.x:38710 as auto-E0FACC6A-8E10-1B57-2C5D-B6C1E689C7BC (p2, c1, k60, u'mqtt_mqtt').
2024-12-02 15:12:03: Client auto-E0FACC6A-8E10-1B57-2C5D-B6C1E689C7BC disconnected.
2024-12-02 15:13:06: New connection from 172.30.x.x:43574 on port 1883.
2024-12-02 15:13:06: Client auto-85C26BC8-34BB-C37B-C944-BDAA3067A12C disconnected, not authorised.
2024-12-02 15:13:26: New connection from 172.30.32.2:47444 on port 1883.
2024-12-02 15:13:26: Client <unknown> closed its connection.
2024-12-02 15:15:26: New connection from 172.30.32.2:44954 on port 1883.
2024-12-02 15:15:26: Client <unknown> closed its connection.
2024-12-02 15:15:32: New connection from 172.30.x.x:49734 on port 1883.
2024-12-02 15:15:32: Client auto-B5CD91AC-846B-D278-0FB0-CE37DBD1276C disconnected, not authorised.

Also here is my config for HAOS-SBFspot:

Connection_Type: Bluetooth
Sensors_HA: Create
BTAddress: 00:80:25:xx:xx:xx
Password: "0000"
LocalBTAddress: DC:A6:32:xx:xx:xx
IP_Address: 55.255.255.255
Plantname: SunnyBoyBT
Latitude: "x.45"
Longitude: "x.00"
Timezone: Europe/Paris
DateTimeFormat: "'%H:%M:%S %d-%m-%y'"
SQL_Password: xxxxxxxxxxx
MQTT_User: mqtt_mqtt
MQTT_Pass: xxxxxxxxxx
MQTT_Topic: homeassistant/sbfspot_{plantname}/sbfspot_{serial}
MQTT_Data: >-
  PrgVersion,Plantname,Timestamp,SunRise,SunSet,InvSerial,InvName,InvTime,InvStatus,InvSwVer,InvClass,InvType,InvTemperature,InvGridRelay,EToday,ETotal,GridFreq,PACTot,PAC1,UAC1,IAC1,OperTm,FeedTm,PDCTot,UDC1,UDC2,IDC1,IDC2,PDC1,PDC2,BTSignal,InvWakeupTm,InvSleepTm
PVoutput_SID: "0123456789:12345"
PVoutput_Key: fake9364fake4545afke834fake
LogLevel: debug

It’s also a possibility that the reason why nothing works is obvious, I’m ready to hear that

Hope you can help me

HasQT · December 2, 2024, 9:34pm

@mjude

Hi there,

Bluetooth setup looks like it is working correctly, so that’s good.

The mqtt error relates to username and password. The username and password in the SBFspot settings is being rejected because it doesn’t exist. You need to setup the user and password in either the mqtt addon or as a user in homeassistant settings.

You haven’t, but don’t use, “homeassistant” as the user either, as that is specific to homeassistant. It needs to be a separately named user.

If you have already setup a user in one of those spots, then you should double check your SBFspot addon settings for any errors.

mjude · December 3, 2024, 1:36pm

Hi @HasQT , thanks for your reply.

I assumed it was a user error, but I still don’t understand properly: On the log I provided above, I tried to use the same user as the one used by z2m to communicate with MQTTBroker but no luck (it works between z2m and the broker though). I thought maybe it can’t be the same user. So I tried to create another user in HA users. This time I the user to mqtt_sunnyboy, but I still end with the same error:

MQTT: Publishing (homeassistant/sbfspot_{plantname}/sbfspot_{serial}),"PrgVersion": "3.9.11","Plantname": "SunnyBoyBT","Timestamp": "2024-12-03T14:31:45+0100","SunRise": "2024-12-03T07:57:00+0100","SunSet": "2024-12-03T17:02:00+0100","InvSerial": 2100249991,"InvName": "SN: 2100249991","InvTime": "2014-11-17T06:33:36+0100","InvStatus": "Ok","InvSwVer": "02.08.01.R","InvClass": "Solar Inverters","InvType": "SB 3000TL-20","InvTemperature": 42.640,"InvGridRelay": "Closed","EToday": 3.798,"ETotal": 55017.764,"GridFreq": 49.980,"PACTot": 304.000,"PAC1": 304.000,"UAC1": 230.980,"IAC1": 1.319,"OperTm": 57206.589,"FeedTm": 55544.437,"PDCTot": 309.000,"UDC1": 285.380,"UDC2": 0.000,"IDC1": 1.084,"IDC2": 0.000,"PDC1": 309.000,"PDC2": 0.000,"BTSignal": 72.941,"InvWakeupTm": "2014-11-17T00:07:45+0100","InvSleepTm": "2014-11-17T06:33:36+0100"
Client null sending CONNECT
Client null received CONNACK (5)
Connection error: Connection Refused: not authorised.
Error: The connection was refused.
MQTT: Failed to execute '/usr/bin/mosquitto_pub' mosquitto client installed?
Error 1280 while publishing to MQTT Broker
Reading events: 2024-Dec-01
Tue Dec  3 14:31:45 2024: INFO: Done.

Is it possible that password can’t use specific symbols in sbfspot?
Or maybe I’m forgetting something else? Just creating user through HA users isn’t enough?

HasQT · December 3, 2024, 8:46pm

Yes complex passwords can be a problem, although that usually relates to characters causing a split in the word, which then breaks the config. Try a fairly plain user and password with no dash or other special characters. Try adding the user in the mqtt broker too.

mjude · December 3, 2024, 8:55pm

After some tests its seems users through Home Asssitant weren’t recognized. I created a user under mqtt broker config, but it didn’t worked either. However I finaly had it working by removing any special symbol in the password:

Client null sending CONNECT
Client null received CONNACK (0)
Client null sending PUBLISH (d0, q0, r0, m1, 'homeassistant/sbfspot_SunnyBoyBT/sbfspot_2100249991', ... (776 bytes))
Client null sending DISCONNECT
Reading events: 2024-Dec-01
Tue Dec  3 21:47:12 2024: INFO: Done.

Still, entities only report “Unknown” states, but maybe its because it’s night time.

Again, thanks for your time

mjude · December 4, 2024, 12:20pm

Hi @HasQT, sorry to bother you again (and for double posting). Sadly even at day time (12h30 right now), entities created through MQTTBroker keep returning “Unknown” state, and this time I absolutely don’t see any reason why this happens. Maybe you’ll have an idea.

The SBFSpot log seems perfect I think:

SBFspot V3.9.11
Yet another tool to read power production of SMA solar inverters
(c) 2012-2024, SBF (https://github.com/SBFspot/SBFspot)
Compiled for Linux (LE) 64 bit with MySQL support
Commandline Args: -v -ad1 -am0 -ae0 -mqtt
Reading config '/usr/bin/sbfspot/SBFspot.cfg'
Wed Dec  4 12:25:00 2024: INFO: Starting...
DEBUG: Retrieving new datapoints from DB...
sunrise: 07:58
sunset : 17:02
Connecting to 00:80:25:xx:xx:xx (1/10)
Initialising...
SUSyID: 125 - SessionID: 956303024
SMA netID=01
Serial Nr: 7D2F4587 (2100249991)
BT Signal=73.3%
Logon OK
SUSyID: 113 - SN: 2100249991
Device Name:      SN: 2100249991
Device Class:     Solar Inverters
Device Type:      SB 3000TL-20
Software Version: 02.08.01.R
Packet status: 21
SUSyID: 113 - SN: 2100249991
Device Status:      Ok
SUSyID: 113 - SN: 2100249991
Device Temperature: 44.0°C
SUSyID: 113 - SN: 2100249991
GridRelay Status:      Closed
SUSyID: 113 - SN: 2100249991
Energy Production:
	EToday: 2.958kWh
	ETotal: 55021.168kWh
	Operation Time: 57212.92h
	Feed-In Time  : 55550.37h
SUSyID: 113 - SN: 2100249991
DC Spot Data:
	MPPT 1 Pdc:   1.521kW - Udc: 293.85V - Idc:  5.179A
	MPPT 2 Pdc:   0.000kW - Udc:   0.00V - Idc:  0.000A
	Calculated Total Pdc:   1.521kW
AC Spot Data:
	Phase 1 Pac :   1.473kW - Uac: 231.77V - Iac:  6.359A
	Phase 2 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
	Phase 3 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
	Total Pac   :   1.473kW - Calculated Pac:   1.473kW
	Efficiency  :   96.84%
SUSyID: 113 - SN: 2100249991
Grid Freq. : 49.98Hz
SUSyID: 113 - SN: 2100249991
Current Inverter Time: 2014-11-18T04:27:18+0100
Inverter Wake-Up Time: 2014-11-18T00:16:15+0100
Inverter Sleep Time  : 2014-11-18T04:27:22+0100
MQTT: Publishing (homeassistant/sbfspot_{plantname}/sbfspot_{serial}),"PrgVersion": "3.9.11","Plantname": "SunnyBoyBT","Timestamp": "2024-12-04T12:25:32+0100","SunRise": "2024-12-04T07:58:00+0100","SunSet": "2024-12-04T17:02:00+0100","InvSerial": 2100249991,"InvName": "SN: 2100249991","InvTime": "2014-11-18T04:27:18+0100","InvStatus": "Ok","InvSwVer": "02.08.01.R","InvClass": "Solar Inverters","InvType": "SB 3000TL-20","InvTemperature": 43.960,"InvGridRelay": "Closed","EToday": 2.958,"ETotal": 55021.168,"GridFreq": 49.980,"PACTot": 1473.000,"PAC1": 1473.000,"UAC1": 231.770,"IAC1": 6.359,"OperTm": 57212.915,"FeedTm": 55550.366,"PDCTot": 1521.000,"UDC1": 293.850,"UDC2": 0.000,"IDC1": 5.179,"IDC2": 0.000,"PDC1": 1521.000,"PDC2": 0.000,"BTSignal": 73.333,"InvWakeupTm": "2014-11-18T00:16:15+0100","InvSleepTm": "2014-11-18T04:27:22+0100"
Client null sending CONNECT
Client null received CONNACK (0)
Client null sending PUBLISH (d0, q0, r0, m1, 'homeassistant/sbfspot_SunnyBoyBT/sbfspot_2100249991', ... (775 bytes))
Client null sending DISCONNECT
********************
* ArchiveDayData() *
********************
startTime: 04/12/2024 00:00:00
Wed Dec  4 12:25:32 2024: INFO: Done.
[12:25:45] INFO: [SBFspot Upload Log Latest]

And the MQTT Broker log don’t seems to return any error:

2024-12-04 12:25:32: New connection from 172.30.xx.xx:50228 on port 1883.
2024-12-04 12:25:32: New client connected from 172.30.xx:xx:50228 as auto-6AD68BB6-DD6C-F12E-5485-EEE2BC3A8D67 (p2, c1, k60, u'mqtt_sunnyboy').
2024-12-04 12:25:32: Client auto-6AD68BB6-DD6C-F12E-5485-EEE2BC3A8D67 disconnected.

Yet, every entities still return “Unknown” (in french sorry, “Inconnu” = “Unknown”):

I feel so close to the goal it’s so annoying. Have you any idea about what I am doing wrong?

HasQT · December 4, 2024, 12:24pm

@mjude

Try deleting the sensors and recreate them. It’s probably created the first sensors incorrectly due to the password problem.

You can check that the topics match if you click on “mqtt info” on that mqtt page, and compare to your SBFspot log(which indeed does look correct)

Edit: you can also check with MQTT explorer (on windows or the addon)
mqtt-explorer

mjude · December 4, 2024, 1:42pm

@HasQT

Still no luck. Tried to Purge from SBFspot, tried to delete whole topic homeassistant/sensor/sbfspot_SunnyBoyBT from MQTT Explorer, then chose Create from SBFspot. Entities came back as expected, but still returning “Unknown”.

However I looked on MQTT Info as you suggested, and I think you were right, there is a mismatch between the topic shown here and the one shown on SBFspot log:

MQTT Info:

SBFSpot log:

MQTT: Publishing (homeassistant/sbfspot_{plantname}/sbfspot_{serial}),"PrgVersion": "3.9.11","Plantname": "SunnyBoyBT","Timestamp": "2024-12-04T14:35:33+0100","SunRise": "2024-12-04T07:58:00+0100","SunSet": "2024-12-04T17:02:00+0100","InvSerial": 2100249991,"InvName": "SN: 2100249991","InvTime": "2014-11-18T06:37:20+0100","InvStatus": "Ok","InvSwVer": "02.08.01.R","InvClass": "Solar Inverters","InvType": "SB 3000TL-20","InvTemperature": 46.350,"InvGridRelay": "Closed","EToday": 5.990,"ETotal": 55024.199,"GridFreq": 49.990,"PACTot": 1196.000,"PAC1": 1196.000,"UAC1": 230.910,"IAC1": 5.178,"OperTm": 57215.082,"FeedTm": 55552.533,"PDCTot": 1231.000,"UDC1": 289.550,"UDC2": 0.000,"IDC1": 4.253,"IDC2": 0.000,"PDC1": 1231.000,"PDC2": 0.000,"BTSignal": 72.941,"InvWakeupTm": "2014-11-18T00:16:15+0100","InvSleepTm": "2014-11-18T06:37:25+0100"
Client null sending CONNECT
Client null received CONNACK (0)
Client null sending PUBLISH (d0, q0, r0, m1, 'homeassistant/sbfspot_SunnyBoyBT/sbfspot_2100249991', ... (775 bytes))
Client null sending DISCONNECT

If i’m reading correctly, the topic from MQTTBroker is:
/homeassistant/sensor/sbfspot_SunnyBoyBT/
while SBFspot try to publish under
homeassistant/sbfspot_SunnyBoyBT/

I’ll try to modify MQTT topic from SBFspot config

HasQT · December 4, 2024, 2:01pm

The mqtt info state_topic is showing /sbfspot_
It is missing the serial number.

Copy your SBFspot options, so you can copy and past them back in. Delete the the addon. Delete the sensors from mqtt. Reinstall the addon, paste your config back in. Recreate the sensors.

Looks like a stuck file(fairly common) in the addon that gets created to read the serial number from your inverter. I should have said that in the last post. I should put a warning in the readme to not create the sensors until the mqtt setup is working.

Edit: the

homeassistant/*sensor*/sbfspot_SunnyBoyBT

Topic is for the discovery topic. The actual sensors topic doesn’t use the /sensor/ part

mjude · December 4, 2024, 3:10pm

Oh, ok got it. I misunderstood the topic thing.
So I did what you said, copied my sbfspot config, uninstalled completely the addon, made sure MQTTBroker wasn’t showing SBFspot entities anymore (double checked inside MQTTExplorer), rebooted the host, pasted my SBFspot config then recreated sensors… But still no luck, entites kept reporting “Unknown”.
BUT. I did noticed a difference in behavior: MQTTBroker was reporting a correct serial number this time, both in MQTT info and in MQTTBroker Devices list. Everything looked strong this time.
Then I remembered earlier today when I thought it was a good idea to add /sensor/ in the MQTT Topic through SBFSpot config. I removed sensors again, corrected MQTT Topic path as it was earlier, recreated sensors, and BOOOOOM

Thanks again for your time and your patience, you’re a king