That would be awesome.
Thanks.
having major issues with 3.0 and this binding.
The first 5 channels sync accross fine. the 6th doesn’t want to sync. i have 4 boards running with 21 channels in total.
Please help
@Christopher_Hemmings i will need to compile a new version for 3.0 i will do that this weekend. Sorry for the delay
Thanks heaps. It says version 3.0 and it works mostly but there are some issues. For now I’m using openhab remote binding to link to my 2.5 setup but eventually want to move over to 3
Has anyone managed to get the konnected 3.0 binding to work?
I added the binding and it auto discovered the device and configured the 2 default channels. As soon as I do that it caused the konnected Pro to panic and continue to do so repeatedly. The only way to stop is to reflash the device.
Any pointers on debug welcome.
@wr18962 Here is a link for a 3.0 version try this one and see if it works
When i was compiling this i noticed a bug that probably didn’t get fixed in the automatic transfer of the binding from 2.5.x to 3.0. This fixes that and adds support for the pro module.
Please uninstall the binding that ships with openhab3.0 and install this binding manually.
As an update submitting for approval of these changes into the official binding in 3.0.x. Feel free to follow along there with progress.
Hi Zachary,
Once I install the UPNP Control binding the Konnected binding loads ok.
I have not tested exhaustively but the binding no longer causes the device to panic and I am able to control the 3 default output channels that are created (Alarm1, Alarm2, Output1).
When I try to create a read-only switch channel on one of the input channels it creates the following error:
2021-01-11 17:49:28.568 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:614) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:770) ~[?:?]
at org.openhab.binding.konnected.internal.handler.KonnectedHandler.lambda$6(KonnectedHandler.java:338) ~[?:?]
at java.util.ArrayList.forEach(ArrayList.java:1541) ~[?:?]
at java.util.Collections$UnmodifiableCollection.forEach(Collections.java:1085) ~[?:?]
at org.openhab.binding.konnected.internal.handler.KonnectedHandler.constructSettingsPayload(KonnectedHandler.java:331) ~[?:?]
at org.openhab.binding.konnected.internal.handler.KonnectedHandler.updateKonnectedModule(KonnectedHandler.java:406) ~[?:?]
at org.openhab.binding.konnected.internal.handler.KonnectedHandler.lambda$5(KonnectedHandler.java:296) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Let me know if you need any further information.
Regards
-Lawrence
@lawrence, Thanks for the above can you upload the complete log file.
Thanks
Hi Zachary,
Hopefully this is what you need. I could not get any of the input channels (1 - 6 on the Konnected Pro) to work no matter how they were configured (Read-only Switch, Sensor etc)
There is no unusual output on the Lua console on the Konnected Pro
Let me know if you would like me to try something else to get different debug output
openhab.log (267.8 KB)
@wrtaff thanks for that. This is the file I need to look at. Can you first set the logging level of the konnected binding to debug by executing the command
log:set DEBUG org.openhab.binding.konnected
Then once that is done restart openhab and wait a minute or two for everything to try and start and then upload the log file. My suspicion is that something is not starting up right and is crashing the binding when it tries to start, thus its not properly running. But i can’t tell what it is trying to do because debug logging is not enabled.
@wr18962 I also mean to add that the panic from the pro is due to a incorrect config file being sent to the device. There is a newer version of the pro firmware that was just released in december that is supposed to stop this behavior. That’s another reason i need to have debug logging turned on so i can see what json payload the binding is actually trying to send to configure the device.
Hi Zachary,
here is the log with debug turned on.
I did remove some of the obsolete OH2 bindings.
The binding now reading the state of the zones ok.
openhab.log (31.2 KB)
Hello,
Hoping someone can help.
I’ve got a new Konnected Pro board and a new install of 3.0 Openhabian on a Pi. I’ve got the 3.0 jar file for the binding in the addons directory and with upnp active, the binding discovers the konnected board. When I add it, I get three things by default. After that, I can’t get anything added for the zone things no matter what I’m trying.
Accessing the /status url on the konnected board yields a response that matches up with what I see in the debug logs. Looking at the /konnected url on the openhab server port yields a 500 error for a null pointer exception which matches what I see in the debug logs as well.
If I try to add a channel via the OH3 web UI, it adds for a minute, but never logs anything in the debug logs and it disappears from the web channel listing within about a minute after adding it.
I’m clearly doing something wrong, but I’m really quite unclear on what it is. I’m new to OH and 3.0 is my first install, so having most of the docs (for OH in general) apply to versions I’ve never seen is making things really hard.
I should note that I’ve updated the Konnected board to the latest firmware version.
Logs attached.
log-output.txt (15.5 KB)
Thanks for any help you can provide!
A little more info - I did a pcap capture on the IP traffic between the Openhab server and the konnected pro board during a restart of the openhab service and it looks like the initial communication is fine: the JSON push to the konnected board is sane (valid JSON and matches the default three configured channels) and the konnected board responds with a 200. Then, the konnected board opens a new TCP session and sends a “GET /konnected/device/ea40f5207585?zone=alarm1 HTTP/1.1\r\n” to the OpenHab server on port 8080 to which the OH3 server responds with a 500 error.
Also, when trying to add a new channel, I’m not seeing any communication between the konnected board and the OH3 server.
Thanks!
@gb1227 Thanks for this you may have identified a bug. It looks like there is no JSON payload being sent with this first get request and my code doesn’t properly handle this and thus errors out
Firmware is v0.1.2-c6ad60 - which is the latest they seem to have available.
@volfan6415 That would explain the errors. Thanks! FWIW, I do have it mostly working now as follows: each zone is added to the Konnected thing as a channel with a channel ID of only the numeric value of the channel - i.e.: “1”, “2”, etc. Also, I cannot add zone “4”, or the whole things fails. So long as I name the channels that way and do not create a channel “4”, it all seems to work, though it does throw some exceptions.
Really appreciate all your work on this