Memory leak with Nikobus in 1.7.1?

I checked your log file and noticed something odd. It appears that every time the feedback starts failing, this occurs immediately after button N478032 was pressed. I’m wondering if that button may be broken and is sending invalid data on the bus.

Can you increase the log level to trace, restart openhab and press that button? This will show all the traffic on the nikobus. If the button is sending something odd, it should show up. If my theory is right, the feedback should also start failing right after the button press.
To activate the trace, you need to update the log config to the following:

<logger name="org.openhab.binding.nikobus" level="TRACE" />

Alternatively, you could try to not use that button for a while and see if the feedback keeps working.

Thank you, I will try it.

Davy,

Thank you for the support.
I found a error in my items file for that button. There was a wrong adress of the module for reading back the status, an adress that didn’t exist.
Now it keep on working after pressing that button.:grinning:
Tomorrow, I will see that everything is still working.

Great!

Already one day working without problem.
I think the problem is solved, because before it didn’t work that long!!

:grinning::grinning::grinning:

Great!!

So I can conclude that there is no bug, and I can safely purchase my module?

Sorry for raising a false issue Davy!
Thanks for your support!

Until now, everything keep on working. Now more than one day

Yep. It’s working fine. I got my pc-link module on a second hand website. Sometimes there are people that buy one just to configure their system and then sell it again.
Alternatively, if you are a maker, I can get you in touch with some people who have designed a compatible PCB board. I’m not sure how complex it would be to build as that is out of my comfort zone…

That is great news, I’m currently using Nikons with Irule and SimpleControl but SimpleControl doesn’t support custom feedback and iRule has a bug so the Nikons feedback is not working.

Wanted to use Openhab but was worried when I saw this topic, glad it seems to be working.

One quick question, how did you connect the Pi to the serial port? did you use one of those MAX3232 modules or are you using a serial server and serial over IP (like the Tibbo DS203 http://tibbo.com/products/controllers/ds203.html or likes).

Any suggestions or recommendations what works best?

I’am using a standard USB to Serial converter.
I was worry that I had to install some drivers, but I didn’t had to do anything.
I just plugged it into the PI and it worked.
In the openhab config file I just added
nikobus:serial.port=/dev/ttyUSB0and it worked

Marc,

which one did you buy or where did you buy it ? Then I’ll just buy the same, when googling I see a lot of topics around this and the fact yours works without any driver installation sounds extremely appealing :slight_smile:

Rohnny

Rohnny,

I bought it a couple of years ago (more then 5years ago). I used it for programming my Nikobus system on my Windows PC. Now I use it for Openhab with my PI.
I don’t know the type. There is nothing written on it :neutral_face:
I will see if can find something about it.

I use this one
http://www.conrad.be/ce/nl/product/971791/Serieel-USB-20-Aansluitkabel-1x-USB-20-stekker-A-1x-D-sub-stekker-9-polig-100-m-Zwart-Vergulde-steekcontacten

But every converter with the ftdi chipset should work out of the box

Hi

Fairly new with OpenHAB, some experience with nikobus. I added all codes to my Harmony, for the WAF. I added an IP2IR inverter, read all the codes in with IPTach Learner, so I can now use my smartphone with iRule to command my nikobus too. Problem with that is that i have no feedback so no statusses of channels, reason why I’m switching to openhab. Rules aren’t that important to me, I would like to know the status of my lighting, my roller shutters and my dimmers.

Thought I’d share what I’ve found out for other noobs with linux and openhab :slightly_smiling:

  1. Serial
    I got permission denieds, solved it with
    tried it first with
    sudo chown openhab /dev/tttyUSB0
    sudo chown root /dev/tttyUSB0
    still permission denied
    sudo adduser openhab dialout
    sudo adduser root dialout
    sudo adduser pi dialout
    and then it worked.

  2. question about the binding
    on https://github.com/openhab/openhab/wiki/Nikobus-Binding Davy states

… CommandReceiver[:177] - Received NikobusCommand [command=$186C9400100167FF78607E, repeats=1] …
The 4 characters following $18 are the switch module address. In the example above, that’s C964. With this address, you can now define the different channels in your item configuration, …

Shouldn’t C964 be 6C94?

Just got my channels read out, so still have to check.

  1. Could someone post his sitemap? This would be very handy to use as sitemap.

  2. I have a module 05-000-02 with 12 channels
    I suppose I can go from 1 to 12 and not from 1:1-6 and from 2:1-6?

1=$18B74F00100155FF76C01A
Switch light_office {nikobus=“B74F:1”}
Switch light_hallway {nikobus=“B74F:2”}
Switch light_living {nikobus=“B74F:3”}
Switch light_kitchen {nikobus=“B74F:4”}
Switch light_diningroom {nikobus=“B74F:5”}
Switch light_toilet {nikobus=“B74F:6”}
Switch light_office {nikobus=“B74F:7”}
Switch light_hallway {nikobus=“B74F:8”}
Switch light_living {nikobus=“B74F:9”}
Switch light_kitchen {nikobus=“B74F:10”}
Switch light_diningroom {nikobus=“B74F:11”}
Switch light_toilet {nikobus=“B74F:12”}

Thanks for all the good advice :wink:

Yes. The typo is fixed now.

For new questions, please start a new topic rather than hijacking an existing one.

Thx. I didn’t want to hijack. As part of my reply was about the issues I had with serial thought I’d share in a thread where there were questions about serial, so. And since I had other questions where after four hours of trial and error I couldn’t find an answer to, I added them.

I’ll start a new one.

Davy,

I’m using OpenHab 2.0 and I don’t have any logback_debug.xml file.

So where do I put the DEBUG config line? I tried putting it in the logging.cfg file in the conf folder but that didn’t work.

Kind regards,

At the openhab> prompt, enter

log:set DEBUG org.openhab.binding.nikobus

Also, see this topic:

Thanks, that worked, I now have detailed logs but the problem is still there:-)

Problem is the status of my lights are not updating and the log file looks ok. All lights remain off, even after scheduled status update.

Below my items and log file

Items:

testnikobusaan {nikobus="#NBA03CF[09B9-1,09B9-2]"}
Switch testnikobusuit {nikobus="#NFA03CF[09B9-1,09B9-2]"}
Switch NB_S1_O1_lichtWC "WC" <light> {nikobus="09B9:1"}
Switch NB_S1_O2_lichtbadkamer "Badkamer" <light> {nikobus="09B9:2"}
Switch NB_S1_O3_lichtkeuken "Keuken" <light> {nikobus="09B9:3"}
Switch NB_S1_O4_raamtransparant {nikobus="09B9:4"}
Switch NB_S1_O5_ {nikobus="09B9:5"}
Switch NB_S1_O6_lampjesdressoirbovenuit {nikobus="09B9:6"}
Switch NB_S1_O7_lichtgarage "Garage" <light> {nikobus="09B9:7"}
Switch NB_S1_O8_lichttraphal "Traphal" <light> {nikobus="09B9:8"}
Switch NB_S1_O9_lichtfitnesscentraal "Fitness" <light> {nikobus="09B9:9"}
Switch NB_S1_O10_lichtbureau "Bureau" <light> {nikobus="09B9:10"}
Switch NB_S1_O11_lichteetplaats "Eetplaats" <light> {nikobus="09B9:11"}
Switch NB_S1_O12_kastkinesis "Kast Kinesis" <light> {nikobus="09B9:12"}
Switch ClimaVentOn {nikobus="#N3103CF"}
Switch ClimaVentOff {nikobus="#NB103CF"}

and my logfile:
2016-10-24 22:41:35.925 [NikobusBinding ] - Requesting scheduled status update for 09B9
2016-10-24 22:41:35.927 [NikobusBinding ] - Sending command with ack $101709B98605FA
2016-10-24 22:41:35.929 [NikobusCommandSender ] - Sending command $101709B98605FA
2016-10-24 22:41:35.930 [NikobusInterface ] - Sending : $101709B98605FA
2016-10-24 22:41:35.952 [NikobusInterface ] - Received: $
2016-10-24 22:41:35.976 [NikobusInterface ] - Received: 0517
2016-10-24 22:41:35.976 [NikobusCommandReceiver ] - Received NikobusCommand [command=$0517, repeats=1]
2016-10-24 22:41:35.978 [NikobusAckMonitor ] - Processing nikobus command $0517
2016-10-24 22:41:36.330 [NikobusInterface ] - Received: $1
2016-10-24 22:41:36.355 [NikobusInterface ] - Received: C09B90000FF0000FF0061AA
2016-10-24 22:41:36.379 [NikobusInterface ] - Received: 86
2016-10-24 22:41:36.379 [NikobusCommandReceiver ] - Received NikobusCommand [command=$1C09B90000FF0000FF0061AA86, repeats=1]
2016-10-24 22:41:36.382 [NikobusAckMonitor ] - Processing nikobus command $1C09B90000FF0000FF0061AA86
2016-10-24 22:41:36.385 [NikobusAckMonitor ] - Received expected ack '$1C09B90000FF0000FF0061AA86’
2016-10-24 22:43:35.925 [NikobusBinding ] - Requesting scheduled status update for 09B9
2016-10-24 22:43:35.926 [NikobusBinding ] - Sending command with ack $101209B96DF5D9
2016-10-24 22:43:35.928 [NikobusCommandSender ] - Sending command $101209B96DF5D9
2016-10-24 22:43:35.930 [NikobusInterface ] - Sending : $101209B96DF5D9
2016-10-24 22:43:35.952 [NikobusInterface ] - Received: $0
2016-10-24 22:43:35.976 [NikobusCommandReceiver ] - Received NikobusCommand [command=$0512, repeats=1]
2016-10-24 22:43:35.976 [NikobusInterface ] - Received: 512
2016-10-24 22:43:35.978 [NikobusAckMonitor ] - Processing nikobus command $0512
2016-10-24 22:43:36.331 [NikobusInterface ] - Received: $
2016-10-24 22:43:36.356 [NikobusInterface ] - Received: 1C09B9000000FF000000735
2016-10-24 22:43:36.380 [NikobusInterface ] - Received: 928
2016-10-24 22:43:36.380 [NikobusCommandReceiver ] - Received NikobusCommand [command=$1C09B9000000FF000000735928, repeats=1]
2016-10-24 22:43:36.382 [NikobusAckMonitor ] - Processing nikobus command $1C09B9000000FF000000735928
2016-10-24 22:43:36.384 [NikobusAckMonitor ] - Received expected ack ‘$1C09B9000000FF000000735928’

So clearly the status of some items needs to change

Think I found part of the issue, the binding seems to be picky on the module. I have a 05-200 and a 05-201 and for my other connects (GlobalCache) I can mix them so you can connect 2 external systems to the Nikobus, for the OpenHab binding you need to select the right one