Replies: 9 comments 3 replies
-
Additional information: |
Beta Was this translation helpful? Give feedback.
-
Looks like a problem with how you setup your MQTT entities.
The ESP does not sent all values in every message so what you see in MQTT
explorer is normal, it can only send what it has received and decoded from
the RS485 and I have to assume that the inverter does not send all data
every time.
There is code for HA in the repository, I would suggest creating sensors
with that code and testing again. Once you have the first valid message the
value of the sensor will persist in HA until the next MQTT message arrives
with a new value for that variable.
…On Tue, Oct 31, 2023 at 10:50 PM kiwibhoy ***@***.***> wrote:
Additional information:
I have now realised that I can add the mqtt "explorer" (sorry I was
calling it "express") as an addon to HA which I have done and some time
after that I had explorer showing all values. In my excitment I forgot to
do a screenshot and when I went to the Sofar dashboard which showed all the
values and then back to the mqtt page all the values had disappeared. Just
thought it might be a clue to what is happening.
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOGAXEFVJD6PJD6EUOTXHHTYCF6BZAVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINBQGMZTM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
[cid:4b1a9661-d050-4a5d-95bc-d36b0e0f2086]
I took this photo today and noticed that "sofar" below Sofar2mqtt looks like another "Topic". Its not in the explorer. Is this normal?
Regards
Mike
________________________________
From: cliffdude ***@***.***>
Sent: Thursday, 2 November 2023 12:39 am
To: cmcgerty/Sofar2mqtt ***@***.***>
Cc: kiwibhoy ***@***.***>; Author ***@***.***>
Subject: Re: [cmcgerty/Sofar2mqtt] Sofar dxoverdy dashboard occassionally shows values (Discussion #71)
Looks like a problem with how you setup your MQTT entities.
The ESP does not sent all values in every message so what you see in MQTT
explorer is normal, it can only send what it has received and decoded from
the RS485 and I have to assume that the inverter does not send all data
every time.
There is code for HA in the repository, I would suggest creating sensors
with that code and testing again. Once you have the first valid message the
value of the sensor will persist in HA until the next MQTT message arrives
with a new value for that variable.
On Tue, Oct 31, 2023 at 10:50 PM kiwibhoy ***@***.***> wrote:
Additional information:
I have now realised that I can add the mqtt "explorer" (sorry I was
calling it "express") as an addon to HA which I have done and some time
after that I had explorer showing all values. In my excitment I forgot to
do a screenshot and when I went to the Sofar dashboard which showed all the
values and then back to the mqtt page all the values had disappeared. Just
thought it might be a clue to what is happening.
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOGAXEFVJD6PJD6EUOTXHHTYCF6BZAVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINBQGMZTM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
—
Reply to this email directly, view it on GitHub<#71 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APVHUIH2VIDDVRVTTDYHZWDYCIYF3AVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINBUG44TO>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
The only thing I see there, as you already mentioned is that you are using
2 topics in your config file sofar2mqtt/# to set the modes and the sofar/#
to get the readings.
In MQTT explorer you also show "sofar2mqtt/solarPV1" with data?
I am not using the latest version as I created my own fork and removed some
of the values I don't find relevant.
The 2 topics may be normal now but you may want to reflash your ESP with a
clean copy of the code.
I have the HYD-4000-ES by the way, it is identical to yours less 1kw output
on the AC.
A quinta, 2/11/2023, 06:39, kiwibhoy ***@***.***> escreveu:
… [cid:4b1a9661-d050-4a5d-95bc-d36b0e0f2086]
I took this photo today and noticed that "sofar" below Sofar2mqtt looks
like another "Topic". Its not in the explorer. Is this normal?
Regards
Mike
________________________________
From: cliffdude ***@***.***>
Sent: Thursday, 2 November 2023 12:39 am
To: cmcgerty/Sofar2mqtt ***@***.***>
Cc: kiwibhoy ***@***.***>; Author ***@***.***>
Subject: Re: [cmcgerty/Sofar2mqtt] Sofar dxoverdy dashboard occassionally
shows values (Discussion #71)
Looks like a problem with how you setup your MQTT entities.
The ESP does not sent all values in every message so what you see in MQTT
explorer is normal, it can only send what it has received and decoded from
the RS485 and I have to assume that the inverter does not send all data
every time.
There is code for HA in the repository, I would suggest creating sensors
with that code and testing again. Once you have the first valid message
the
value of the sensor will persist in HA until the next MQTT message arrives
with a new value for that variable.
On Tue, Oct 31, 2023 at 10:50 PM kiwibhoy ***@***.***> wrote:
> Additional information:
> I have now realised that I can add the mqtt "explorer" (sorry I was
> calling it "express") as an addon to HA which I have done and some time
> after that I had explorer showing all values. In my excitment I forgot
to
> do a screenshot and when I went to the Sofar dashboard which showed all
the
> values and then back to the mqtt page all the values had disappeared.
Just
> thought it might be a clue to what is happening.
>
> —
> Reply to this email directly, view it on GitHub
> <
#71 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AOGAXEFVJD6PJD6EUOTXHHTYCF6BZAVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINBQGMZTM>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub<
#71 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/APVHUIH2VIDDVRVTTDYHZWDYCIYF3AVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINBUG44TO>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOGAXEDK3E7YEXPXFXBHYX3YCM53HAVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINJTGAYTI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hi,
I reflashed the esp and still have the same problem, your comment re sofar/#, I must of somehow did this when I was cleaning out topics in the App when changing over to HA version of explorer.
But it is interesting that it picked up as a topic when the only place it was put as a topic is in the explorer app.
when Sofar did appear it produced a list and the dashboard had values, they didn't update mind you.
I am using the dxoverdy Hybrid inverter YMAL file and also the dashboard YMAL file from the same source.
The photo below shows that the RS485 data is streaming through and is showing over 400 messages, those messages I think, should be coming out in the form of a list and the list should update the dashboard values every 10 seconds if the value has changed since the last update.
Do you agree?
Refer also to the mqtt add on log you will see the following IP address:
172.30.32.2:46758 on port 1883 appears continually.
Is this normal?
What system are you using to collect the RS485 data?
FYI and nothing to do with the issue:
I've included a photo of my system which you will see has two inverters the Hybrid and a grid tied inverter and two batteries.
The data coming out of the Hybrid is not total power, but the import and export data are total.
I want to be able to make best use of the power generated and reduce the export power if I can put it to use.
Thanks for taking the time to try to help me get this going, is there anything that I can send you that would help make your task easier and make sure I dont waste your time.
Regards
Mike
Regards
Mike
________________________________
From: cliffdude ***@***.***>
Sent: Thursday, 2 November 2023 8:29 pm
To: cmcgerty/Sofar2mqtt ***@***.***>
Cc: kiwibhoy ***@***.***>; Author ***@***.***>
Subject: Re: [cmcgerty/Sofar2mqtt] Sofar dxoverdy dashboard occassionally shows values (Discussion #71)
The only thing I see there, as you already mentioned is that you are using
2 topics in your config file sofar2mqtt/# to set the modes and the sofar/#
to get the readings.
In MQTT explorer you also show "sofar2mqtt/solarPV1" with data?
I am not using the latest version as I created my own fork and removed some
of the values I don't find relevant.
The 2 topics may be normal now but you may want to reflash your ESP with a
clean copy of the code.
I have the HYD-4000-ES by the way, it is identical to yours less 1kw output
on the AC.
A quinta, 2/11/2023, 06:39, kiwibhoy ***@***.***> escreveu:
[cid:4b1a9661-d050-4a5d-95bc-d36b0e0f2086]
I took this photo today and noticed that "sofar" below Sofar2mqtt looks
like another "Topic". Its not in the explorer. Is this normal?
Regards
Mike
________________________________
From: cliffdude ***@***.***>
Sent: Thursday, 2 November 2023 12:39 am
To: cmcgerty/Sofar2mqtt ***@***.***>
Cc: kiwibhoy ***@***.***>; Author ***@***.***>
Subject: Re: [cmcgerty/Sofar2mqtt] Sofar dxoverdy dashboard occassionally
shows values (Discussion #71)
Looks like a problem with how you setup your MQTT entities.
The ESP does not sent all values in every message so what you see in MQTT
explorer is normal, it can only send what it has received and decoded from
the RS485 and I have to assume that the inverter does not send all data
every time.
There is code for HA in the repository, I would suggest creating sensors
with that code and testing again. Once you have the first valid message
the
value of the sensor will persist in HA until the next MQTT message arrives
with a new value for that variable.
On Tue, Oct 31, 2023 at 10:50 PM kiwibhoy ***@***.***> wrote:
> Additional information:
> I have now realised that I can add the mqtt "explorer" (sorry I was
> calling it "express") as an addon to HA which I have done and some time
> after that I had explorer showing all values. In my excitment I forgot
to
> do a screenshot and when I went to the Sofar dashboard which showed all
the
> values and then back to the mqtt page all the values had disappeared.
Just
> thought it might be a clue to what is happening.
>
> —
> Reply to this email directly, view it on GitHub
> <
#71 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AOGAXEFVJD6PJD6EUOTXHHTYCF6BZAVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINBQGMZTM>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub<
#71 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/APVHUIH2VIDDVRVTTDYHZWDYCIYF3AVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINBUG44TO>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOGAXEDK3E7YEXPXFXBHYX3YCM53HAVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINJTGAYTI>
.
You are receiving this because you commented.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub<#71 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APVHUIALCWUZXR7E6OJC2ZLYCNDT3AVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINJTGM2DK>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
2023-11-07 11:07:13: New connection from 172.30.32.2:53558 on port 1883.
2023-11-07 11:07:13: Client <unknown> closed its connection.
2023-11-07 11:09:13: New connection from 172.30.32.2:57444 on port 1883.
2023-11-07 11:09:13: Client <unknown> closed its connection.
2023-11-07 11:11:13: New connection from 172.30.32.2:55060 on port 1883.
2023-11-07 11:11:13: Client <unknown> closed its connection.
2023-11-07 11:13:13: New connection from 172.30.32.2:46598 on port 1883.
2023-11-07 11:13:13: Client <unknown> closed its connection.
2023-11-07 11:15:13: New connection from 172.30.32.2:35414 on port 1883.
2023-11-07 11:15:13: Client <unknown> closed its connection.
2023-11-07 11:17:13: New connection from 172.30.32.2:42026 on port 1883.
2023-11-07 11:17:13: Client <unknown> closed its connection.
2023-11-07 11:18:11: Client 6zouckqcfPIW1DGWiivXSG closed its connection.
2023-11-07 11:19:13: New connection from 172.30.32.2:37058 on port 1883.
2023-11-07 11:19:13: Client <unknown> closed its connection.
2023-11-07 11:19:14: New connection from 172.30.32.1:48093 on port 1883.
time="2023-11-07T11:19:19+13:00" level=error msg="POST error: Post \"http://127.0.0.1:80/authentication\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
time="2023-11-07T11:19:19+13:00" level=error msg="Post \"http://127.0.0.1:80/authentication\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
2023-11-07 11:19:14: Bad socket read/write on client 40FqVzqBfEEF95Prh0hKWm: Unknown error.
2023-11-07 11:19:27: New connection from 172.30.32.1:52613 on port 1883.
2023-11-07 11:19:27: New client connected from 172.30.32.1:52613 as 40FqVzqBfEEF95Prh0hKWm (p2, c1, k60, u'battery').
2023-11-07 11:21:13: New connection from 172.30.32.2:45912 on port 1883.
2023-11-07 11:21:13: Client <unknown> closed its connection.
2023-11-07 11:22:50: Client mqtt-explorer-38018e50 disconnected.
2023-11-07 11:22:50: New connection from 172.30.32.1:35676 on port 1883.
2023-11-07 11:22:50: New client connected from 172.30.32.1:35676 as mqtt-explorer-38018e50 (p2, c1, k60, u'battery').
2023-11-07 11:23:13: New connection from 172.30.32.2:44646 on port 1883.
2023-11-07 11:23:13: Client <unknown> closed its connection.
2023-11-07 11:25:13: New connection from 172.30.32.2:49968 on port 1883.
2023-11-07 11:25:13: Client <unknown> closed its connection.
2023-11-07 11:27:13: New connection from 172.30.32.2:56422 on port 1883.
2023-11-07 11:27:13: Client <unknown> closed its connection.
2023-11-07 11:29:13: New connection from 172.30.32.2:46002 on port 1883.
2023-11-07 11:29:13: Client <unknown> closed its connection.
2023-11-07 11:31:13: New connection from 172.30.32.2:60922 on port 1883.
2023-11-07 11:31:13: Client <unknown> closed its connection.
2023-11-07 11:33:13: New connection from 172.30.32.2:45502 on port 1883.
2023-11-07 11:33:13: Client <unknown> closed its connection.
2023-11-07 11:35:13: New connection from 172.30.32.2:50302 on port 1883.
2023-11-07 11:35:13: Client <unknown> closed its connection.
2023-11-07 11:36:50: Saving in-memory database to /data//mosquitto.db.
2023-11-07 11:37:13: New connection from 172.30.32.2:59022 on port 1883.
2023-11-07 11:37:13: Client <unknown> closed its connection.
2023-11-07 11:39:13: New connection from 172.30.32.2:35408 on port 1883.
2023-11-07 11:39:13: Client <unknown> closed its connection.
2023-11-07 11:41:13: New connection from 172.30.32.2:55352 on port 1883.
2023-11-07 11:41:13: Client <unknown> closed its connection.
2023-11-07 11:43:13: New connection from 172.30.32.2:48982 on port 1883.
2023-11-07 11:43:13: Client <unknown> closed its connection.
2023-11-07 11:45:13: New connection from 172.30.32.2:60648 on port 1883.
2023-11-07 11:45:13: Client <unknown> closed its connection.
2023-11-07 11:47:13: New connection from 172.30.32.2:39916 on port 1883.
2023-11-07 11:47:13: Client <unknown> closed its connection.
2023-11-07 11:49:13: New connection from 172.30.32.2:56434 on port 1883.
2023-11-07 11:49:13: Client <unknown> closed its connection.
2023-11-07 11:51:13: New connection from 172.30.32.2:53644 on port 1883.
2023-11-07 11:51:13: Client <unknown> closed its connection.
2023-11-07 11:53:13: New connection from 172.30.32.2:40248 on port 1883.
2023-11-07 11:53:13: Client <unknown> closed its connection.
2023-11-07 11:55:13: New connection from 172.30.32.2:52790 on port 1883.
2023-11-07 11:55:13: Client <unknown> closed its connection.
2023-11-07 11:57:13: New connection from 172.30.32.2:33298 on port 1883.
2023-11-07 11:57:13: Client <unknown> closed its connection.
2023-11-07 11:59:13: New connection from 172.30.32.2:50688 on port 1883.
2023-11-07 11:59:13: Client <unknown> closed its connection.
2023-11-07 12:01:13: New connection from 172.30.32.2:56602 on port 1883.
2023-11-07 12:01:13: Client <unknown> closed its connection.
2023-11-07 12:03:13: New connection from 172.30.32.2:56566 on port 1883.
2023-11-07 12:03:13: Client <unknown> closed its connection.
2023-11-07 12:04:33: Client HAClient disconnected.
2023-11-07 12:04:33: New connection from 172.30.32.1:56792 on port 1883.
2023-11-07 12:04:33: New client connected from 172.30.32.1:56792 as HAClient (p2, c1, k60, u'battery').
2023-11-07 12:05:13: New connection from 172.30.32.2:56456 on port 1883.
2023-11-07 12:05:13: Client <unknown> closed its connection.
2023-11-07 12:06:51: Saving in-memory database to /data//mosquitto.db.
2023-11-07 12:07:13: New connection from 172.30.32.2:42958 on port 1883.
2023-11-07 12:07:13: Client <unknown> closed its connection.
2023-11-07 12:09:13: New connection from 172.30.32.2:35506 on port 1883.
2023-11-07 12:09:13: Client <unknown> closed its connection.
2023-11-07 12:11:13: New connection from 172.30.32.2:49742 on port 1883.
2023-11-07 12:11:13: Client <unknown> closed its connection.
2023-11-07 12:13:13: New connection from 172.30.32.2:41432 on port 1883.
2023-11-07 12:13:13: Client <unknown> closed its connection.
2023-11-07 12:15:13: New connection from 172.30.32.2:40964 on port 1883.
2023-11-07 12:15:13: Client <unknown> closed its connection.
2023-11-07 12:17:13: New connection from 172.30.32.2:46796 on port 1883.
2023-11-07 12:17:13: Client <unknown> closed its connection.
2023-11-07 12:19:13: New connection from 172.30.32.2:38908 on port 1883.
2023-11-07 12:19:13: Client <unknown> closed its connection.
2023-11-07 12:21:13: New connection from 172.30.32.2:33446 on port 1883.
2023-11-07 12:21:13: Client <unknown> closed its connection.
2023-11-07 12:21:46: New connection from 192.168.1.7:54696 on port 1883.
2023-11-07 12:21:46: Client Sofar2mqtt already connected, closing old connection.
2023-11-07 12:21:46: New client connected from 192.168.1.7:54696 as Sofar2mqtt (p2, c1, k15, u'battery').
2023-11-07 12:23:13: New connection from 172.30.32.2:57832 on port 1883.
2023-11-07 12:23:13: Client <unknown> closed its connection.
2023-11-07 12:25:13: New connection from 172.30.32.2:60054 on port 1883.
2023-11-07 12:25:13: Client <unknown> closed its connection.
2023-11-07 12:27:13: New connection from 172.30.32.2:33474 on port 1883.
2023-11-07 12:27:13: Client <unknown> closed its connection.
|
Beta Was this translation helpful? Give feedback.
-
I think you are over complicating this. `Message 1 received on Sofar2mqtt/state at 8:10 AM: { My mqtt JSON does not have all the values as I have modified Colin's code to only send me what I need. This strings will keep coming in every 10 seconds or so with the updated values. If this works correctly and the values are coming in, not every value must be sent every time, the ESP is doing it's job as intended. In that case the problem is the YAML files in HA. |
Beta Was this translation helpful? Give feedback.
-
This is what I get from listening to sofar2mqtt it is not in a list form like yours, although I did have a list once during this exercise with about 10 items in it and I could see that it was displayed in my dashboard but not updating. The results are similar to using mqtt explorer.
I compared my .ino file with the mcgerty one and it is the same.
Also refer the Config YMAL file I am using from dxoverdy.
Does your mqtt log display similar patterns to the one I sent the other day with regard to
172.30.32.2:46758 on port 1883 appears continually.
Is this normal?
[https://res.cdn.office.net/assets/mail/file-icon/png/txt_16x16.png]Config YMAL.rtf<https://1drv.ms/u/s!AssGCVRNcaOTgugl4a0t6N4FLtMoZg>
I am trying hard not to complicate things but this is quite complicated stuff for a 81 year old, ha ha
Regards
Mike
…________________________________
From: cliffdude ***@***.***>
Sent: Tuesday, 7 November 2023 9:17 pm
To: cmcgerty/Sofar2mqtt ***@***.***>
Cc: kiwibhoy ***@***.***>; Author ***@***.***>
Subject: Re: [cmcgerty/Sofar2mqtt] Sofar dxoverdy dashboard occassionally shows values (Discussion #71)
I think you are over complicating this.
The problem is either the ESP no sending info to HA or HA not interpreting the info correctly and thus not updating sensors etc...
Forget mqtt explorer and all the rest of it and in HA go to Settings -> Devices and services -> mqtt -> configure.
Under "listen to a topic" put 'Sofar2mqtt/#' or whatever you set in the ESP arduino .ino file as the device name then press start listening and wait. After a few seconds you should see a JSON string like this:
PS: If you can't see anything just put a # in the topic to see all MQTT messages, I don't know if you have other devices.
`Message 1 received on Sofar2mqtt/state at 8:10 AM:
{
"running_state": 2,
"grid_voltage": 2407,
"grid_current": 297,
"grid_freq": 5001,
"grid_power": 0,
"battery_power": 53,
"battery_voltage": 489,
"battery_current": 1045,
"systemIO_power": 20,
"batterySOC": 19,
"battery_temp": 19,
"battery_cycles": 170,
"consumption": 18,
"solarPV": 71,
"solarPVAmps": 0,
"today_generation": 24,
"today_exported": 0,
"today_purchase": 433,
"Solarpv1": 63,
"Solarpv2": 9,
"today_consumption": 451,
"inverter_temp": 32,
"inverter_HStemp": 20
}`
My mqtt JSON does not have all the values as I have modified Colin's code to only send me what I need. This strings will keep coming in every 10 seconds or so with the updated values. If this works correctly and the values are coming in, not every value must be sent every time, the ESP is doing it's job as intended. In that case the problem is the YAML files in HA.
—
Reply to this email directly, view it on GitHub<#71 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APVHUIBWQD7MDIDDYIO343LYDHVB7AVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TIOJWGAYTK>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hi Listening to |
Beta Was this translation helpful? Give feedback.
-
Ok in that case it could be a comunication error on the rs485. Try a
different power adapter fo the Esp, I had an issue like that once as well.
Also use some twisted pair like cat5 or cat6 to connect he esp to the
inverter rs485.
A domingo, 19/11/2023, 01:39, kiwibhoy ***@***.***> escreveu:
… Hi
I got this list today about 4 or 5 intervals one after the other and then
it reverted back to just a couple of sensors each interval. I am not
changing anything or touching any equipment and I am beginning to wonder if
the format of the Inverter RS485 output is changing. Sounds silly I know.
Listening to
Sofar2mqtt/#
Message 4178 received on Sofar2mqtt/state at 1:24 PM:
"running_state": 2,
"grid_voltage": 2357,
"grid_current": 725,
"grid_freq": 4995,
"grid_power": 111,
"battery_power": 286,
"battery_voltage": 543,
"battery_current": 5353,
"systemIO_power": 165,
"batterySOC": 87,
"battery_temp": 25,
"consumption": 67,
"solarPV": 521,
"solarPVAmps": 0,
"today_generation": 672,
"Solarpv1": 191,
"today_consumption": 575,
"inverter_HStemp": 59
Qos
STOP LISTENING
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOGAXEFQ2J7NNCMLXP6NREDYFFPLVAVCNFSM6AAAAAA6W2EZ6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMBZGAZDA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This is a difficult issue to explain I have been trying for ages to get the Sofar dashboard to show values and occassionally it has shown values but never updated them, the files below give you a snapshot of what I mean.
Sofardashboard with values– Home Assistant PDF.pdf
Sofar – Home Assistant dashboard shows no values PDF.pdf
It would appear that the mqtt express app shows values coming through from the inverter all the time.
I have checked all connections even going to the bother of making up a vero board and soldering all connections and getting the same result.
The fact that mqtt express is showing values at all times is making me think I had issues in the way I loaded the sofar dashboard so I put on another instance of HA and installed the sofar dashboard again and got the same result I then added the BME280 stuff and displayed the BME280 values on the NodeRed dashboard successfully.
I have used both a D1 Mini and a NodeMCU esp8266 connected to a RS485 to TTL board, with the same results.
I have checked the integrety of the network, although the fact that mqtt express always shows values coming through would point to the network being OK.
As I said I found this a difficult issue to explain I just hope someone point me in the right direction to making this work.
Beta Was this translation helpful? Give feedback.
All reactions