I've tried changing the values. No luck.
The switches and dimmers are all from NEXA. They worked great before, and I thought that a new TellStick DUO would fix the problem. Could low battery make any issues? I can see that the Tellstick receives the signal from the switch.
Switchking has high load / very high load when I click the switches. I only have three switches and three lights. And two temperature sensors.
Problem using switches.
-
- Administrator
- Posts: 2655
- Joined: Tue 09 Nov 2010, 20:25
Re: Problem using switches.
Do you have any information in your logs that can help us tracking down the load issue?
A faulty USB can give high load since Switch King forces Telldus to retry transmissions.
A faulty USB can give high load since Switch King forces Telldus to retry transmissions.
Martin | Switch King
-
- 1 star
- Posts: 9
- Joined: Thu 06 Dec 2012, 10:36
Re: Problem using switches.
I just switched the livingroom lights on and off a couple of times. From I click and see the blue lights on the tellstick, until I see the red light and the lights turns on. I takes 6-8 seconds. Same when turning them off.
This is from the log:
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Device with id 10, name stue, native id 10 and code 2:3 has a nonmatching state.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Device with id 10, name stue, native id 10 and code 2:3 is in semi auto mode that is targetted for cancellation.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Device with id 10, name stue, native id 10 and code 2:3 is being dimmed to level 100. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Telldus API Dim responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Device with id 10, name stue, native id 10 and code 2:3 is being dimmed to level 100. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:21 -- Telldus API Dim responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:31 -- Device with id 10, name stue, native id 10 and code 2:3 has a nonmatching state.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:32 -- Device with id 10, name stue, native id 10 and code 2:3 is being turned off. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:32 -- Telldus API TurnOff responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:32 -- Device with id 10, name stue, native id 10 and code 2:3 is being turned off. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:32 -- Telldus API TurnOff responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:52 -- Device with id 10, name stue, native id 10 and code 2:3 has a nonmatching state.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:52 -- Device with id 10, name stue, native id 10 and code 2:3 is being dimmed to level 100. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:52 -- Telldus API Dim responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:52 -- Device with id 10, name stue, native id 10 and code 2:3 is being dimmed to level 100. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:53 -- Telldus API Dim responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:04 -- Device with id 10, name stue, native id 10 and code 2:3 has a nonmatching state.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:04 -- Device with id 10, name stue, native id 10 and code 2:3 is being turned off. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:04 -- Telldus API TurnOff responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:04 -- Device with id 10, name stue, native id 10 and code 2:3 is being turned off. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:05 -- Telldus API TurnOff responded with: 0
This is from the log:
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Device with id 10, name stue, native id 10 and code 2:3 has a nonmatching state.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Device with id 10, name stue, native id 10 and code 2:3 is in semi auto mode that is targetted for cancellation.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Device with id 10, name stue, native id 10 and code 2:3 is being dimmed to level 100. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Telldus API Dim responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:20 -- Device with id 10, name stue, native id 10 and code 2:3 is being dimmed to level 100. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:21 -- Telldus API Dim responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:31 -- Device with id 10, name stue, native id 10 and code 2:3 has a nonmatching state.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:32 -- Device with id 10, name stue, native id 10 and code 2:3 is being turned off. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:32 -- Telldus API TurnOff responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:32 -- Device with id 10, name stue, native id 10 and code 2:3 is being turned off. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:32 -- Telldus API TurnOff responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:52 -- Device with id 10, name stue, native id 10 and code 2:3 has a nonmatching state.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:52 -- Device with id 10, name stue, native id 10 and code 2:3 is being dimmed to level 100. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:52 -- Telldus API Dim responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:52 -- Device with id 10, name stue, native id 10 and code 2:3 is being dimmed to level 100. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:40:53 -- Telldus API Dim responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:04 -- Device with id 10, name stue, native id 10 and code 2:3 has a nonmatching state.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:04 -- Device with id 10, name stue, native id 10 and code 2:3 is being turned off. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:04 -- Telldus API TurnOff responded with: 0
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:04 -- Device with id 10, name stue, native id 10 and code 2:3 is being turned off. Method used is TellStickWrapper.
{BusinessAccess - Invocation} --<Status> -- 2014-07-28 23:41:05 -- Telldus API TurnOff responded with: 0
-
- Administrator
- Posts: 2655
- Joined: Tue 09 Nov 2010, 20:25
Re: Problem using switches.
Have you changed the "Send count", the "Send interval" and the "Receive delay"?
Try to lower "Send interval" and "Receive interval".
Try to lower "Send interval" and "Receive interval".
Martin | Switch King
Who is online
Users browsing this forum: No registered users and 2 guests