RFLink Gateway via Synology with Domoticz

[drenergy]

Hi all,

Yesterday i installed the new spk package of domoticz for Synology. Everything is working great except the RFLink communication.

First attemp i received a few signals from my weatherstation (only WIND 4 times), after that the RFLink got initialized again, and again, and again...

http://jadahl.dscloud.me/sspks/index.php?fulllist=true

There you can find the SPK packages.

Are there any members here that use RFlink combined with a Synology? Is there another place to check for log files for more information?

EDIT:

Code: Select all

2015-09-02 22:55:12.452 Hardware Monitor: Fetching data (System sensors)
2015-09-02 22:55:13.552 Error: RFLink: Not received anything for more then 15 seconds, restarting...
2015-09-02 22:55:16.504 RFLink: Using serial port: /dev/ttyACM0
2015-09-02 22:55:16.512 RFLink: 20;00;Nodo RadioFrequencyLink V1.1;
2015-09-02 22:55:16.512 RFLink: Controller Initialized!...
2015-09-02 22:55:34.561 Error: RFLink: Not received anything for more then 15 seconds, restarting...
2015-09-02 22:55:37.513 RFLink: Using serial port: /dev/ttyACM0
2015-09-02 22:55:38.432 RFLink: 20;00;Nodo RadioFrequencyLink V1.1;
2015-09-02 22:55:38.432 RFLink: Controller Initialized!...
2015-09-02 22:55:42.781 Hardware Monitor: Fetching data (System sensors)
2015-09-02 22:55:55.571 Error: RFLink: Not received anything for more then 15 seconds, restarting...
2015-09-02 22:55:58.523 RFLink: Using serial port: /dev/ttyACM0
2015-09-02 22:55:59.441 RFLink: 20;00;Nodo RadioFrequencyLink V1.1;
2015-09-02 22:55:59.441 RFLink: Controller Initialized!...
2015-09-02 22:56:13.111 Hardware Monitor: Fetching data (System sensors)
2015-09-02 22:56:16.581 Error: RFLink: Not received anything for more then 15 seconds, restarting...
2015-09-02 22:56:19.532 RFLink: Using serial port: /dev/ttyACM0
2015-09-02 22:56:20.461 RFLink: 20;00;Nodo RadioFrequencyLink V1.1;
2015-09-02 22:56:20.461 RFLink: Controller Initialized!...
2015-09-02 22:56:20.611 RFLink: 20;01;Alecto V1;ID=000f;RAIN=04a4;
2015-09-02 22:56:20.611 (RFLink Gateway USB) Rain (Rain)
2015-09-02 22:56:37.590 Error: RFLink: Not received anything for more then 15 seconds, restarting...
2015-09-02 22:56:40.542 RFLink: Using serial port: /dev/ttyACM0
2015-09-02 22:56:41.470 RFLink: 20;00;Nodo RadioFrequencyLink V1.1;
2015-09-02 22:56:41.471 RFLink: Controller Initialized!...
2015-09-02 22:56:43.440 Hardware Monitor: Fetching data (System sensors)
2015-09-02 22:56:44.460 RFLink: 20;01;Alecto V1;ID=0024;TEMP=0080;HUM=86;BAT=OK;
2015-09-02 22:56:44.461 (RFLink Gateway USB) Temp + Humidity (Unknown)

Thanks in advance

[datzmazzie]

Same question here.

I am planning to buy RFLink and was hoping it will work with my Synology.

[Stuntteam]

Some changes have been done to the timeout handling...
It might be the solution to this as well.

[drenergy]

Some changes have been done to the timeout handling...
It might be the solution to this as well.

Hi Stuntteam,

I will try the new release R30 today, will let you know how this works out!

Thanks you for this great piece of software!

[datzmazzie]

Just received the RFLink today.
I'm on R30 but same problems as the topic starter.

2015-09-10 20:28:45.114 Error: RFLink: Not received anything for more then 15 seconds, restarting...
2015-09-10 20:28:47.975 RFLink: Using serial port: /dev/ttyACM0
2015-09-10 20:28:48.891 RFLink: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R30;
2015-09-10 20:28:48.891 RFLink: Controller Initialized!...
2015-09-10 20:29:03.601 Hardware Monitor: Fetching data (System sensors)
2015-09-10 20:29:05.517 Error: RFLink: Not received anything for more then 15 seconds, restarting...
2015-09-10 20:29:08.374 RFLink: Using serial port: /dev/ttyACM0
2015-09-10 20:29:09.289 RFLink: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R30;
2015-09-10 20:29:09.289 RFLink: Controller Initialized!...

[Stuntteam]

The timeout handling on the Domoticz side has been modified for this.. what Domoticz version are you using?

[datzmazzie]

2.2619. Where can I find the version number of the current version on Github?

Crap. Have a new synology and dit not add jadahl.dscloud.me/sspks/

Update to 2994 is working for me.
Only thing left is that it is not able to send a signal

015-09-10 22:55:30.111 RFLink Sending: 10;NewKaku;6cbc3a;1;ON
2015-09-10 22:55:35.002 Error: RFLink: TX time out..

[datzmazzie]

The problem must be in the USB drivers for synology. I installed the serial drivers from http://jadahl.dscloud.me/sspks/index.php?fulllist=true

Sometimes the rflink is receiving the input from my KAKU remote. But most of the time there is nothing.

With a terminal session on my computer i can send 10;NewKaku;6cbc3a;1;ON and the rflink is working.

any suggestion?

[Stuntteam]

Obviously all works fine on WIN/Pi systems.. so the issue is in combination with the Synology.

There are 2 timeout's being used.. one is a heartbeat that checks if there is data coming in.. this one has been updated to perform better..
The other one is available on the hardware settings page. You can select "not active/x minutes/x hours" If it is not disabled, disable that one.. (set to not active)

Domoticz is not available via the Synology package center.. when I have time I might take a closer look on how to install it..

[datzmazzie]

You can add http://jadahl.dscloud.me/sspks/ to your synology sources to install domoticz.

The timeout on the hardware page is not enabled. I will also look into te code dor a solution

[jumbotroll]

I am struggling with the same problem on my DS-712+
I am testing RFLink Arduino Mega R30 Firmware and I think there is a USB driver problem.
The cdc-acm.ko is loaded but, but RFLink: Controller Initializing all the time.
Working ok on my linux mint machine.

This is my dmesg:
[306432.014815] cdc_acm 4-2:1.0: ttyACM0: USB ACM device
[306432.022264] usbcore: registered new interface driver cdc_acm
[306432.028065] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

And this is my Domoticz log:

2015-09-11 13:35:50.631 Incoming connection from: 192.168.0.140
2015-09-11 13:35:50.838 RFLink: Using serial port: /dev/ttyACM0
2015-09-11 13:35:51.757 RFLink: Controller Initialized!...
2015-09-11 13:35:57.131 Hardware Monitor: Fetching data (System sensors)
2015-09-11 13:36:03.120 RFLink: Controller Initialized!...
2015-09-11 13:36:25.478 RFLink: Controller Initialized!...
2015-09-11 13:36:27.189 Hardware Monitor: Fetching data (System sensors)
2015-09-11 13:36:47.840 RFLink: Controller Initialized!...
2015-09-11 13:36:57.252 Hardware Monitor: Fetching data (System sensors)
2015-09-11 13:36:59.986 RFLink: Controller Initialized!...
2015-09-11 13:37:10.198 RFLink: Controller Initialized!...

Regards
Jumbotroll

[datzmazzie]

Indeed Jumbotoll. I got the same messages. Didn't know if the initializing was normal.

Can I still download the R29 somewhere?

[jumbotroll]

Indeed Jumbotoll. I got the same messages. Didn't know if the initializing was normal.

Can I still download the R29 somewhere?

I have tested R29, but have the same problem.
If you want R29, you can download it from my server: http://jadahl.com/RFLink_v1.zip

Regards
Jumbotroll

[datzmazzie]

Thnx!
Also not working indeed.

It's "crashing" almost immediately. After the initializing i press a button on the KAKU remote and It only register the first 1-2 times.
Must be an USB driver problem.
Here is the log from ttyACM0:

20;00;Nodo RadioFrequencyLink V1.1;
20;01;NewKaku;ID=006cbc3a;SWITCH=1;CMD=ON;
20;00;Nodo RadioFrequencyLink V1.1;
20;01;NewKaku;ID=006cbc3a;SWITCH=1;CMD=OFF;
20;00;Nodo RadioFrequencyLink V1.1;
20;01;NewKaku;ID=006cbc3a;SWITCH=1;CMD=ON;
20;00;Nodo RadioFrequencyLink V1.1;
20;00;Nodo RadioFrequencyLink V1.1;
20;00;Nodo RadioFrequencyLink V1.1;

[datzmazzie]

@Jumbotroll
Do you know if the CDC-ACM driver is standard on the Synology or did it come with the domoticz installation.

And is it also possible to asign an other driver to the RFLink?
I'm to mutch a linux noob to fix this I guess.

[jumbotroll]

@Jumbotroll
Do you know if the CDC-ACM driver is standard on the Synology or did it come with the domoticz installation.

And is it also possible to asign an other driver to the RFLink?
I'm to mutch a linux noob to fix this I guess.

The cdc-acm.ko comes default in synology kernel.
I am not a developer and have looked at different solutions, but not solved it yet

Regards
Jumbotroll

[datzmazzie]

Maybe there is a solution in the auto-reset function of the arduino 2560::


The Arduino/Genuino Mega 2560 has a resettable polyfuse that protects your computer's USB ports from shorts and overcurrent. Although most computers provide their own internal protection, the fuse provides an extra layer of protection. If more than 500 mA is applied to the USB port, the fuse will automatically break the connection until the short or overload is removed

Or

The Arduino/Genuino Mega 2560 board contains a trace that can be cut to disable the auto-reset. The pads on either side of the trace can be soldered together to re-enable it. It's labeled "RESET-EN". You may also be able to disable the auto-reset by connecting a 110 ohm resistor from 5V to the reset line;

[datzmazzie]

The cdc-acm.ko comes default in synology kernel.
I am not a developer and have looked at different solutions, but not solved it yet

The problem is in the Auto reset. I cut of the "wire" between the two plates where stands the text RESET-EN and now the RFLink is working on the Synology DS214play.

[jumbotroll]

The cdc-acm.ko comes default in synology kernel.
I am not a developer and have looked at different solutions, but not solved it yet

The problem is in the Auto reset. I cut of the "wire" between the two plates where stands the text RESET-EN and now the RFLink is working on the Synology DS214play.

Great News!
Tested here and it's working on DS712+

Regards
Jumbotroll

[datzmazzie]

I guess this means that we have to click on the reset button if we need to update the arduino firmware
Or just put a peace of iron between the plates... Would be better if there was a jumper for RESET-EM instead of a 'wire'.

I have the arduino connected with the USB 2.0 port. Will test the 3.0 port tomorrow.