-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi Version - Direct serial interface #131
Comments
@cakuhn can you try these options?
|
I had the exact same issue after migrating to the new release. I am glad I came across this thread as, touch wood, Direct Serial + pymodbus seemed to have resolved it. I am using a RS485 to usb converter direct to my HA server. There was a thread on powerforum with a user with the same issue, I will link them here for resolution. Update: See you already responded there. PS. thanks for your work on this addon! |
Same failure on my side since upgrading to HassOS 10.1. I've tried all 3 methods above to no avail.
Any help would be appreciated. Thnx |
This is good. You either have no sensors in the addon config, or no auto-discovery enabled in HA |
Thnx for responding. I definitely haven't turned off auto-discovery in HA and my addon config lists the following sensors:
I'm not a complete newb, but I must admit, this has had me pulling my hair out the last week! Any help would be appreciated. Thnx |
Thanks so much, This one worked for me "pymodbus - Using the device selected in DEBUG_DEVICE (at the bottom of the settings)". All time out errors experienced on the original version is also gone now. Using the NOW sensors, it also updates almost instantly by the second. AWESOMENESS |
Best to open your own issue, as the driver seems to only be one of your problems. Please include all detail there including your mqtt server info |
Thnx guys. After much struggling, the problem was the connection to the MQTT server! Prior to HassOS 10.1, connecting to HA internal MQTT server on 127.0.0.1 was working fine, but fails for some reason in 10.1. |
in most cases core-mosquitto (the default) should work fine. 127.0.0.1 is not expected to work in standard Docker, as this points to the addon container itself
👍🏼 |
I have a similar issue as reported at the opening of the issue. All pymodbus options give me the following error:
The umodbus options gives me the same error: The cable should work as I have tested it with a SolarAssitant setup, however, that was on a Deye 5kw inverter. I'm trying to install this add-on on a Sunsynk 8kW,
@kellerza Any ideas? |
Try the faul finding guide & make sure you plug it into the correct port - see the adaptors & wiring page. Maybe this is a newer model with a shared port? |
I've tried both ports to test whether it is a combined port. I've also checked everything on the fault finding page. As stated previously the cable wiring is definitely correct as it work on a previous SolarAssistant setup. Is there a way to check the port on the Inverter, i.e. that it is actually working. |
Try from your laptop with modbuspoll/modbus CLI If still not working ~R100 will get you a different RS485 adaptor & run a short wire while standing next to the inverter. Personally, I would just redo the wire since you changed the Inverter |
Ok I preserved ( 11hrs solid lol ) . Then after broker install 09:10:08 INFO MQTT: Connection successful |
@Leecavturbo nice! The docs will show you that If power flow card shows nothing you probably have incorrect entity names. Check these under devices/dev tools- state |
Thanks any / all help pointers appreciated for a novice 👍 |
You can use total PV energy sensor for the flow chart . |
Does that give Pv1+Pv2 power ? Not Kwh |
Yes kWh but the HA flow chart only use kWh or you talking about other flow
chart?
Le dim. 3 sept. 2023 à 17:23, Leecavturbo ***@***.***> a
écrit :
… You can use total PV energy sensor for the flow chart .
System do the calcul automatically and show only the day prod .
Does that give Pv1+Pv2 power ? Not Kwh
—
Reply to this email directly, view it on GitHub
<#131 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYDJ6M3QMDU5QIIKLKFYWQ3XYSOHLANCNFSM6AAAAAAXGM3XVI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Pv1 power shows the instantaneous KW of that mppt ( string ). pv2 and the combined is what I’m after in kw |
|
Wouldn’t even know where to start and I’ve never seen pv2 (187) as a sensor so suspect more work before your math sensor 👍 |
I've been wondering if I should not simply add an
|
Nice solution. If you use the power flow card you can also visualize two separate sensors and see the total in the UI - |
got samba working and established i can create the .py from windows as notepad save as > in the share/hass-addon . but the code from 'here' link doesn't give your example. just add text below to the code ? |
to update pv1 +pv2 sum is now working with SS add-on. Sensor = pv lowercase. |
Anyone know what the sensor for UPS load is ? load_2 or output_2 eg ? |
If you meant backup power output I guess you should read issues about all that sensors ("essentials" is a load on backup output): |
Hallo good people. With Direct Serial interface, how can I get two inverters to detect? Any ideas what I can do? |
HI
On the latest version, installed this morning (Sunsynk Inverter Add-on (multi): Current version: 2023.04.20b-0.3.2 (Changelog)) I get the below errors as reported in the log. The application then crash. Any ideas on a possible fix and the reason for these?
Thanks
2023-04-21 07:32:39,121 ERROR Read Error: <class 'Exception'>: (1,59,1) 'Serial' object has no attribute 'host'
2023-04-21 07:32:52,742 ERROR Read Error: <class 'Exception'>: (1,268,6) 'Serial' object has no attribute 'host'
2023-04-21 07:33:03,835 ERROR Read Error: <class 'Exception'>: (1,59,1) 'Serial' object has no attribute 'host'
2023-04-21 07:33:18,948 ERROR Read Error: <class 'Exception'>: (1,59,1) 'Serial' object has no attribute 'host'
2023-04-21 07:34:38,121 ERROR Read Error: <class 'Exception'>: (1,78,1) 'Serial' object has no attribute 'host'
The text was updated successfully, but these errors were encountered: