forum.excito.org

Hi

I did the Telldus-core installation via repository on my B3, no problems. Got the new v2.1.0. Had some minor problems with comm-error and tellstick not found but that were solved. When everything was working fine with tdtool, I installed HA 2.0.2 which was no problem at all. Everything is working perfect except groups and schedules with several units. It´s always only the first one that activates, not the rest. I still have one problem left with tdtool, the comm-error. As described in http://www.telldus.se/forum/viewtopic.php?f=15&t=1479
Since tdtool sends the command but does not get confirmation, will HA then cancel the rest of the commands? The log indicates that they were all activated. Is tdtool cancelling the rest of the commands?

Do anyone have a solution to the comm-error?

Regards

Jocke

I also upgraded to 2.1.0 once and struggled to get it working. The only solution for me was to downgrade to 2.0.4, which is working flawlessly.

What ha does when a group or schedule contains more devices is sending them in one call to tdtool (like "tdtool --on 5 --on 6"). Check if a call like that works from command line. If it doesn't, I'd suggest downgrading telldus-core.

/Daniel

Ok, thanks, I tried. Not as I expected. It tries both but only the first works. Must have something to do with the lack of confirmation from the stick.

~$ tdtool --on 6 --on 2
Turning on device 6, - An error occurred while communicating with TellStick
Turning on device 2, - An error occurred while communicating with TellStick

I read some about it on the Telldus forum. Apparently this concerns old Tellstick batches and some new(?!). Since I have batch no 13 I must be unlucky or the problem is only related to the new Telldus-core version.

Is it a lot of job to do the removal? Read something about a lot of leftovers. Is the old version available from the repository for B3? A lot of questions but again, thanks.

/Jocke