Yes i checked that several times… It`s the new one. But it looks like the same error. For me, it looks that the Name “SKSC1/2” is the problem. More precisely the “/” is the problem. Or is that another mistake?
yes for sure that is the problem. The used resol-vbus library outputs the name of you controller with the / - which is not allowed for the thing name in openhab. It is hard for me to reproduce, as I don’t have your controller, but if you look at the commit it is clear, that the call to createThing happens in line 223 only for the old version…
Maybe it is worth to double check the file - is it really named org.openhab.binding.resol-2.3.0-SNAPSHOT-2018-03-11.jar and you do not have the old version in parallel? Maybe you delete the old one, check, that it is really removed and the Resol binding is not visible in openhab anymore and then copy the new one.
i reinstalled openhab again. And now, IT´s working! Thank you so much!!!
yes! i will do that. I think at the funktion of calculating the mass of Thermal energy. In my case, I have the channel, but no vallue. So we probably could calculate that nearly maybe that is a cool funktion to see the mass of energy, coming from the solar panels
ah great. Good to hear. Please also give feedback in case you are interested of additional features or have further issues.
Hey there! I’m running the vbus binding since some time now. At current versions some temperature channels are pretty long after the decimal point. Can you cut them off after the first position?
Thanks for the feedback. I have seen this also from time to time (I think not even limited to the latest version) and at other times it is good again. The formatting is in the defined in the channeltype and currently defined as “1 digit after the decimal point” for all numbers, and for the Temperatures the unit should be “°C”. Somehow this link to the channel type is missing in your situation. Can you maybe try to add another item for the channel:
maybe the exisiting items from the old version keep their channel type (where it should also have been a number, but still, who knows.) Also please give me a note (or create a ticket in my github project) in case you see more trouble or when you have ideas when it happens or how it gets fixed. Currently I am out of ideas…
Hi,
I have successfully got the binding working with a DL3, which in turn is connected to a SKSC3HE from which I can read all values as expected.
I also have a couple of sensors connected directly to the DL3, but i can’t find these in the Paper UI, i tried adding the DL3 as a device, but no luck there.
(Also posted it on github, but not sure that was the correct place for it https://github.com/ramack/openhab2-addons/issues/16)
Thanks for the report. Putting that as ticket in my github repo is perfect. I propose to discuss the details there.
BTW @all: I now connected two controllers with two separate VBUS-LAN interfaces to the binding (which shows two bridges and the corresponding devices). The openhab architecture is perfect for that, because this feature was there completely without additional effort.
hi.
sorry for my maybe stupid question, followed this threat but not 100% clear what to do to make this work. Having DL2 with MX in combination. donwloaded the JAR file and put into /share folder. seems to be found as a new binding is available.
But now it starts to get tricky…whats next. i tried to add two items (vbus,…) but some things are unclear like a serial port? is this virtually as i’m going LAN…
please please, can someone provide few lines explaining what else is required to make RESOL happen on my opnehab 2.3 instance. Cheers
Hello,
I plan to provide such a step-by-step tutorial in the readme, but you know how it goes… Just too much other “real life” priorities right now.
Normally you should just need to add one Resol-Vbus thing manually. Which is the “VBUS LAN Bridge”. Then go to the settings and add the password of the DL2 data connection and your inbox should be populated with some new things…
I hope that helps,
Rapha
Hi,
thanks for this great Resol binding!
I’m running OpenHAB 2.2.0 on Ubuntu 16.04.4 LTS.
Two VBUS devices (DeltaSol_BX and DeltaTherm_FK) are connected to two VBus/LAN adapters. Both bridges and VBUS devices have been successfully discovered (status “online”).
I created some items for the temperature sensor channels. The item values are correctly updated on restart of the OpenHAB2 service but they don’t receive any further updates.
My item definition:
Number DeltaSol_BX_S1 "Kollektor [%.1f °C]" <temperature> (g_RESOL) {channel="resol:device:VBusLAN_20:DeltaSol_BX:Temperature_sensor_1"}
When I manually perform a refesh within cli, the items are updated but an exception occurs.
bundle:list 229
START LEVEL 100 , List Threshold: 50
ID │ State │ Lvl │ Version │ Name
────┼────────┼─────┼────────────────────┼────────────────────────────────────────────────────────────────────────────────────────
229 │ Active │ 80 │ 2.3.0.201803102330 │ Resol Binding
openhab> bundle:refresh 229
openhab> Exception in thread "Thread-101" java.lang.NullPointerException
at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:598)
at de.resol.vbus.Specification.createUtcDateFormat(Specification.java:77)
at de.resol.vbus.Specification.access$0(Specification.java:76)
at de.resol.vbus.Specification$Formatter$2.formatTextValue(Specification.java:145)
at de.resol.vbus.Specification.formatTextValueFromRawValueInternal(Specification.java:723)
at de.resol.vbus.Specification.formatTextValueFromRawValue(Specification.java:738)
at de.resol.vbus.Specification.formatTextValueFromRawValue(Specification.java:754)
at de.resol.vbus.Specification$PacketFieldValue.formatTextValue(Specification.java:485)
at org.openhab.binding.resol.handler.ResolBridgeHandler$1$1.packetReceived(ResolBridgeHandler.java:354)
at de.resol.vbus.Connection.emitHeaderReceived(Connection.java:160)
at de.resol.vbus.TcpConnection.runInBackground(TcpConnection.java:134)
at de.resol.vbus.TcpConnection.access$0(TcpConnection.java:124)
at de.resol.vbus.TcpConnection$1.run(TcpConnection.java:99)
at java.lang.Thread.run(Thread.java:748)
Any ideas how to solve this problem?
@ramack hm…when I add the vbus thing it also requests a “AdapterSerial” otherwise it does not allow to save the manual thing. What does it require here…any virtual port that is not used yet?
I’m also having the same problem as Marcel
Hi Norbert,
the adapters provide a cgi-script to get the serial:
http://<device-ip>/cgi-bin/get_resol_device_information
The output looks like this:
vendor = "RESOL"
product = "VBus/LAN Adapter"
serial = "2714661"
version = "1.0.3"
build = "rc2-WL"
name = "VBus-Solar"
features = "vbus"
Mh. Can you try with only one vbuslan device active? Maybe we can find out whether it is related to the BX or the FK device.
Also it would be interesting to understand your language setup. - which locale do you have configured?
@norbert_jordan, @Anquietas86 as @Marcel_Duscher has pointed out, it is the serial number of the device. But to be honest, I wonder why you need to configure that yourself… I am quite new to openhab and have more experience in programming for it, than in using (my main use case is based on the Resol interface and therefore I had to implement the binding before being effectively able to use openhab ) I use the paper UI to add a thing, and when I select the resol binding the first time it auto-detects the VBUS-LAN bridge and also automagically fills the serial number etc.
So for me it would be great to understand your use cases. And also in case you have a suggestion to improve the wording feel free to propose. Should I maybe rename the “serial” to “serial number”? to make it more clear? - On the other side, I would believe, that this is not needed at all, because the real TCP connection is created only based on IP and live-data port…
Rapha
It’s not related to BX or FK device. When both devices are connected the exception occurs twice.
My locale settings:
marcel@vm34-openhab:~$ locale
LANG=de_DE.UTF-8
LANGUAGE=
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=
I am using a Vbus LAN adaptor & a DeltaSol BS/4 controller.
The AdaptorSerial was filled in automatically & is the same as shown in the adaptor.
The controller was picked up automatically & added via the Inbox.
It all used to work ok with the 2.0 version of the binding, but i decided to try with the 2.3 version for the easier configuration & bug fixes.