IRTrans Warning Error sending Remote: xxxx, Command: xxxx: Timeout

[michaeldecharon]

I've recently switched from an PC to a Synology NAS with VMM Windows 10 for Homeseer 3.

Because my NAS isn't near my TV, i had to replace my IRTrans USB for an IRTrans Ethernet.

I've multiple IRTrans Ethernet modules which work well.

But now i recieve the following error:

IRTrans Warning

Error sending Remote: versterker-woonkamer, Command: off: Timeout

I've set the Inter-Send Delay to 50 milliseconds.

Any idea how i can fix this problem?

[YoYo]

Hi Michael,
Can you verify that everything works well using the supplied IRTrans software, leaving HS3 out of the mix for troubleshooting purposes?

If it doesn't work via the IRTrans software, that might be an indication of a connectivity issue between the IRTrans server software and the ethernet module.
You might also try pinging the ethernet module at the address shown in the IRTrans server diagnostics window as well.
Also, double-check that the IRTrans server diagnostics window is actually showing separate IP addresses for each module.

The Inter-Send delay only comes into play when sending multiple IR commands at the same time. Some IR controlled devices need to see a minimum "quiet" time between pulses to recognize the signal as a separate command.

Please let us know what you find out...

[michaeldecharon]

Hi YoYo,

Thank you for you're reply.

I've pinged my three IRTrans Ethernet modules and also checked the IRTrans server diagnostics window as well. Everything looks good to me.

Ping

C:\Users\admdecharon>ping 192.168.2.37

Pinging 192.168.2.37 with 32 bytes of data:
Reply from 192.168.2.37: bytes=32 time=1ms TTL=64
Reply from 192.168.2.37: bytes=32 time=1ms TTL=64
Reply from 192.168.2.37: bytes=32 time<1ms TTL=64
Reply from 192.168.2.37: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.2.37:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\admdecharon>ping 192.168.2.44

Pinging 192.168.2.44 with 32 bytes of data:
Reply from 192.168.2.44: bytes=32 time=1ms TTL=100
Reply from 192.168.2.44: bytes=32 time=1ms TTL=100
Reply from 192.168.2.44: bytes=32 time=1ms TTL=100
Reply from 192.168.2.44: bytes=32 time=1ms TTL=100

Ping statistics for 192.168.2.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\Users\admdecharon>ping 192.168.2.104

Pinging 192.168.2.104 with 32 bytes of data:
Reply from 192.168.2.104: bytes=32 time=7ms TTL=64
Reply from 192.168.2.104: bytes=32 time=2ms TTL=64
Reply from 192.168.2.104: bytes=32 time=2ms TTL=64
Reply from 192.168.2.104: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.2.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 7ms, Average = 3ms

IRTrans server diagnostics window

IRServer64 Version 6.10.23
[ 0]: IRTrans LAN : IR VER: E6.10.10 ETH VER: L2.06.44 SN: 202607
MAC:00-22-3e-0f-25-9c IP Addr: 192.168.2.37
[ 1]: IRTrans LAN : IR VER: E6.08.42 ETH VER: L1.11.06 SN: 72434
MAC:00-22-3e-07-03-b2 IP Addr: 192.168.2.44
[ 2]: IRTrans LAN : IR VER: E6.10.10 ETH VER: L2.06.36 SN: 85752
MAC:00-22-3e-0f-0e-b0 IP Addr: 192.168.2.104

Testing only with IRTrans software

When i send an IR-signal from the IRTrans software i get the following error on all the three IRTrans Ethernet modules:

irtrans error result [4 - 3] Timeout

But it sends the IR-signal

For your information, i don't always get a error message in Homeseer

[YoYo]

Hmmm, that's interesting...
OK, so it's probably not the IRTrans plug-in; but instead something between the IRTrans server software and the devices themselves. Strange that the signal is still sent...
You may need to check with the IRTrans company for additional help, but let me check what version of the software I have here, and I will setup a test environment with the same versions as you're using if not; and see if I run into the same issue.

[michaeldecharon]

Hmmm, that's interesting...
OK, so it's probably not the IRTrans plug-in; but instead something between the IRTrans server software and the devices themselves. Strange that the signal is still sent...
You may need to check with the IRTrans company for additional help, but let me check what version of the software I have here, and I will setup a test environment with the same versions as you're using if not; and see if I run into the same issue.

Ok YoYo,

I'll will contact the IRTrans company and let you know the results.

I'm looking forward to hear about your testings.

[michaeldecharon]

Hi YoYo,

I've restarted my Windows, before i contacted the IRTrans company.

And for now everythings works well.

If this changes i will post the answer from the IRTrans company.

Thanks for your support!

[michaeldecharon]

YoYo,

The problem did occur again. In the logfile from the IR Trans Software i get this error multiple times:

Get Devicedata hs6_signals-0
IR Error: Specified Remote Control [hs6_signals] not found
Send Status 272 - 272 [1]

When i disable your plugin, this error doesn't show up anymore. So it must be a connection issue between the ir transsoftware and your plugin?

This is the answer of the IRTrans company:

It looks like the HS plugin is doing some strange things in the background all the time. It is looking for a command "0" for the remote control "hs6_signals". That is repeated all over again. This might keep the server busy so that clients run into timeouts.

[YoYo]

This is normal and expected behavior of the plugin.
In order to determine the status of the IRTrans server, the plugin issues a status command periodically for a remote that does not exist. If the plugin does not get any answer back, it can infer the IRTrans server software is no longer running, record an error message in the HS log, and try to reconnect whenever the server would restart.

[michaeldecharon]

Ok i will post your answer to the IRTrans company in the hope they got a solution.