I must say that if these extensions are bundled in with generic Modbus binding, that surprises me too. Sounds like bloatware
Addressing that as it stands now is just a case of adding explanatory words to the doc pages.
I must say that if these extensions are bundled in with generic Modbus binding, that surprises me too. Sounds like bloatware
Addressing that as it stands now is just a case of adding explanatory words to the doc pages.
Yeah I think the maintainers have opted to follow the same approach even though it might not make sense here.
Original discussion was with sunspec https://github.com/openhab/openhab-addons/pull/6331#discussion_r410307406
I actually do agree, I argue that most people have at most one type of modbus device, not more. It would be therefore reasonable to install them one by one. The ui would not be bloated of different type of modbus devices that you would not work with.
You could raise this up in the github issue I referred to, perhaps it can be adjusted for oh3
This does seem like the opportune time to properly consider this, and implement if needed. Iâll have a think about raising a more generic Github issue.
Yes, I think a more generic issue is the better way. The Issue @ssalonen raised is already solved in a Pull Request
@rossko57 Will you raise one? If not Iâll raise the github issue.
Pull request from @bern77 was closed actually (due to target wrong branch) so the immediate problem remains still.
I am not quite sure now the situation with openhab 2.x vs 3.0⊠Will there be new 2.x addon releases?
I think we might be on the last 2.5.x version already
As you can see the installation is broken. Honestly I donât know if there will be a fix release for 2.5.9. I can only offer to place the latest Release Candiadte into the openhab2-addons folder.
This was a first stab at a fix but my understanding out of this was also that 2.5.9 should be the last release in the 2.x version.
I understand that https://github.com/openhab/openhab-addons/pull/8575 does the same for the main
branch now, so there the problem should be fixed.
Iâm really not sure if thereâs a way to offer the extensions other then providing download links to the JARsâŠ
Did that, without any visible change. Afterwards iâve added modbus-e3dc
to /etc/openhab2/services/addons.cfg
, but this didnât worked well:
2020-09-28 09:34:03.813 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-modbus-e3dc'
Any suggestions?
I donât think addons.cfg needs to be adapted. I just dropped my bundle in the addons folder - thatâs it! So after copying the bundle into addons folder youâre still not able to see E3DC devices in PaperUI via Modbus Binding?
Correct, iâve just dropped the jar bundle and even restarted openHAB without success.
[19:30:54] openhabian@openHABianPi:~$ ls -lah /usr/share/openhab2/addons/
total 92K
drwxrwxr-x+ 2 openhab openhab 4.0K Sep 28 09:21 .
drwxrwxr-x+ 4 openhab openhab 4.0K Sep 21 09:51 ..
-rw-rw-r-- 1 openhab openhab 77K Sep 28 09:21 org.openhab.binding.modbus.e3dc-2.5.8-SNAPSHOT.jar
-rw-r--r-- 1 openhab openhab 70 Sep 20 19:12 README
Hi Timo,
in my case it worked just like Bernd described.
However: I see in your directory list âlsâ that your âjarâ is 77K in size, whereas in my case it is 47K.
Are you sure you have downloaded a correct file?
-rw-râr-- 1 openhabian openhabian 47K Oct 4 22:22 org.openhab.binding.modbus.e3dc-2.5.8-SNAPSHOT.jar
When you copy the jar file to addons folder, you should take a look in the log viewer - there openhab is telling what is going on during installation of the binding.
Good luck, Vjeko
Thank you, that filesize stuff was the right hint. Iâve re-downloaded the file and now everything seems working.
Hi all,
I encoutered the same problem with my E3DC system, but with some strange behavior:
My E3DC is appearing in the Thing inbox as a FSInternetradio thing.
Any idea?
Bernd
Hi,
is this Thing automatically added into your Inbox? Seems that the Internet Radio Binding discovers the E3DC device as radio station. Thatâs weird!
The E3DC Binding doesnât provide automatic discovery service. You have to setup it manually.
Hi Bernd,
yes, it is discovered automatically.
Including all the undocumented features: Power on/off, Volume, Current titleâŠjust kidding
Anyway, I tried manual setup, still struggling with thisâŠ
Bernd
Please tell me where youâre struggeling. Maybe I can improve the setup description!
Hi Bernd
Thanks for the offer.
Maybe just a typo.
My things file:
Bridge modbus:tcp:device âE3DC Modbus TCPâ [ host=â192.168.178.53â, port=502, id=1 ] {
Bridge e3dc powerplant âE3DC PV-Batterieâ @ âHausâ [ refresh=2500 ]
}
My items file:
String E3DC_ModbusId âE3DC Modbus IDâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:info#modbus-idâ }
String E3DC_ModbusFirmware âE3DC Modbus Firmwareâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:info#modbus-firmwareâ }
Number E3DC_SupportedRegisters âE3DC UnterstĂŒtze Registerâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:info#supported-registersâ }
String E3DC_Manufacturer âE3DC Herstellerâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:info#manufacturer-nameâ }
String E3DC_ModelName âE3DC Modellâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:info#model-nameâ }
String E3DC_Firmware âE3DC Modbus Firmware IDâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:info#firmware-releaseâ }
String E3DC_SerialNumber âE3DC Modbus IDâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:info#serial-numberâ }
Number E3DC_PVPower âE3DC PV-Leistungâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:power#pv-power-supplyâ }
Number E3DC_BatteryDischarge âE3DC Batterie Entladenâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:power#battery-power-supplyâ }
Number E3DC_BatteryCharge âE3DC Batterie Ladenâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:power#battery-power-consumptionâ }
Number E3DC_Household âE3DC Hausverbrauchâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:power#household-power-consumptionâ }
Number E3DC_GridConsumption âE3DC Netzeinspeisungâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:power#grid-power-consumptionâ }
Number E3DC_GridSupply âE3DC Netzbezugâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:power#grid-power-supplyâ }
Number E3DC_AutarkyLevel âE3DC Autarkie [%]â (e3dc) { channel=âmodbus:e3dc:device:powerplant:power#autarkyâ }
Number E3DC_SelfConsumptionLevel âE3DC Eigenverbrauch [%]â (e3dc) { channel=âmodbus:e3dc:device:powerplant:power#self-consumptionâ }
Number E3DC_BatterySOC âE3DC Batterie Ladestandâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:power#battery-socâ }
Number E3DC_String1V âE3DC String 1 Voltâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:strings#string1-dc-voltageâ }
Number E3DC_String2V âE3DC String 2 Voltâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:strings#string2-dc-voltageâ }
Number E3DC_String1A âE3DC String 1 Ampereâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:strings#string1-dc-currentâ }
Number E3DC_String2A âE3DC String 2 Ampereâ (e3dc) { channel=âmodbus:e3dc:device:powerplant:strings#string2-dc-currentâ }
Number E3DC_String1W âE3DC String 1 Wattâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:strings#string1-dc-outputâ }
Number E3DC_String2W âE3DC String 2 Wattâ (e3dc,persist) { channel=âmodbus:e3dc:device:powerplant:strings#string2-dc-outputâ }
Thanks
Bernd