__group__,ticket,summary,component,version,milestone,type,owner,status,created,_changetime,_description,_reporter Active Tickets,114,Use a TellStick Net from TelldusCenter,telldus-core,2.1.0,Some future release / Patches welcome,enhancement,micke prag ,new,2011-10-25T12:32:04+02:00,2013-03-14T09:35:18+01:00,"If TellStick Net has an interface for local control, without Telldus Live! it will be possible to use the device as a TellStick Duo.",micke prag Active Tickets,246,td-calls after tdClose() and tdInit() gives access violation,telldus-core,2.1.1,,defect,,new,2012-09-27T17:13:11+02:00,2012-09-27T17:13:11+02:00,"Note: On Beta of driver 2.1.2. After implementation of ticket #188, succeeding ""td-calls"" might fail with access violation after tdInit(), tdClose() and then tdInit() again. This might occur if multiple calls to Telldus Core has been made between the first tdInit() and tdClose() - such as tdGetProtocol, tdGetName, tdGetNumberOfDevices and registration of callback listeners. The second tdInit() succeeds, but tdSetName call after that fails. td-calls after tdClose() and tdInit() gives access violation.",Martin Videfors Active Tickets,215,TelldusCenter segfault in Linux,TelldusCenter,2.1.1,2.1.2,defect,micke prag ,assigned,2012-06-04T13:05:13+02:00,2012-06-18T14:19:39+02:00,Latest developer version of TelldusCenter segfaults on (at least) Kubuntu 12.04. ,stefan persson Active Tickets,225,Optimize reception of Elro-remotes in TellStick Duo,telldus-core,2.1.1,2.1.2,defect,,new,2012-06-27T15:02:36+02:00,2012-06-27T15:02:36+02:00,"TellStick Duo seems to have problem with some Elro branded remotes. In comparison with TellStick Net, it reacts to less signals.",stefan persson Active Tickets,256,Telldus Live! web browser compatibility,Telldus Live!,,2.1.2,defect,,new,2012-10-11T10:19:13+02:00,2013-03-25T16:36:45+01:00,"- Devices not listed in IE10 on Windows 8 - Google service login not working in Chrome",stefan persson Active Tickets,106,Support for efergy energy monitors,other,,2.1.2,enhancement,micke prag ,new,2011-10-07T13:52:53+02:00,2013-03-27T11:22:24+01:00,"More info:[[BR]] http://electrohome.pbworks.com/w/page/34379858/Efergy-Elite-Wireless-Meter-Hack [[BR]] http://www.ukha-archive.com/ml/ukhad/2007-jan/msg00653.html [[BR]] http://jdesbonnet.blogspot.com/2010/09/smart-electricity-meter-based-on-efergy.html [[BR]] http://jdesbonnet.blogspot.com/2011/04/smart-electricity-meter-based-on-efergy.html ",http://login.telldus.com/id?i=1&h=02e40fbda1971adadd5f99ad50f2ec08e91f57f9 Active Tickets,140,Add scheduler to TelldusCenter,TelldusCenter,,2.1.2,enhancement,,new,2011-12-07T10:10:20+01:00,2012-02-10T14:46:08+01:00,"The scheduler is almost done, but need graphic touch up and some more testing on different platforms.",stefan persson Active Tickets,154,Using TelldusCenter on headless linux system,TelldusCenter,2.1.0,2.1.2,enhancement,micke prag ,assigned,2012-01-03T20:42:44+01:00,2013-04-19T13:06:16+02:00,"Request a feature to use TelldusCenter on a standalone headless linux server. There is a common use case to have a tellstick that is connected to an linux server that doesn't have X installed due to minimized hw/sw setup. It would be a great advantage to be able to run TelldusCenter on this setup as well. With it the customer can benfit from the Telldus Live! service for remote internet control of devices as well as simplified device management. ---- Idea 1 TelldusCenter for headless linux servers could be controlled via a web interface, prerequsite to have i.e. apache web server installed with xx modules. ---- Idea 2 Add basic functionallity for communication between a TelldusCenter service and Telldus Live!, open API's. All setup and configuration could be done via conf files with descriptive log messages in the service deamon. API function for TellStick Duo so that i.e. temperature or sensor data can be used to program own control of devices. ",roger lindquist Active Tickets,155,Support for newer generations of Roxcore projector screens,telldus-core,2.1.0,2.1.2,enhancement,,new,2012-01-04T12:11:00+01:00,2012-02-10T14:49:35+01:00,Support only for the first generation at the moment.,thomas@… Active Tickets,181,Sensors in TelldusCenter in Ubuntu package,other,,2.1.2,task,,new,2012-01-31T16:45:10+01:00,2012-01-31T16:45:10+01:00,"Add as own package, since its dependencies cannot be met in Debian.",stefan persson Active Tickets,198,Upgrade ftdi driver,installer,2.1.1,2.1.2,task,fjacobsson,new,2012-03-12T16:34:39+01:00,2012-08-21T09:36:51+02:00,"Include latest version av ftdi driver. Preferably the one after WHQL 2.08.14, seems to be many good changes there. Among other things, better handling of hibernation mode.",stefan persson Active Tickets,157,Tdtool takes long time to exit in Linux/Mac,telldus-core,2.1.0,2.1.3,defect,,new,2012-01-11T10:15:41+01:00,2013-02-12T15:19:20+01:00,"Interrupt ""std::wstring clientMessage = d->eventSocket.read(5000);"" when stopping Client thread. That's why for example tdtool now takes up to 5 seconds to finish in Linux (tdClose). See if Windows is affected.",stefan persson Active Tickets,87,Received event -> New action-connection,Telldus Live!,,2.1.3,enhancement,stefan persson ,new,2011-09-12T12:27:52+02:00,2013-05-03T09:24:41+02:00,"Possible to act on a received signal. New type of ""receiving device"" which can be connected, via a method (e.g. on/off/dim), to another device or device group.",http://login.telldus.com/id?i=10&h=174530911a9afc527ca9880c9e6c75cca0d32fe2 Active Tickets,186,Show sensor data from TelldusCenter in Telldus Live!,TelldusCenter,2.1.1,2.1.3,enhancement,,new,2012-02-16T12:03:09+01:00,2012-07-27T23:38:02+02:00,Only TellStick Net sensors are displayed at the moment.,stefan persson Active Tickets,145,Only 24 sensor values can be polled,other,,Cannot reproduce,defect,telldus technologies ,new,2011-12-22T15:42:51+01:00,2012-01-24T17:37:12+01:00,"Investigating where and why. Cannot reproduce, can receive > 30 values, both in Windows and Linux, and list them with tdtool (could not do that earlier, prior to 2.1.1_beta1). If the error still exists for someone, it must be in another part.",stefan persson Active Tickets,97,Commit EventGhost plugin upstream,other,,Some future release / Patches welcome,defect,micke prag ,assigned,2011-09-30T17:11:12+02:00,2011-11-28T16:15:20+01:00,"Old version is using TellUsbD101.dll, which is not included in TelldusCenter 2.1.0.",http://login.telldus.com/id?i=10&h=174530911a9afc527ca9880c9e6c75cca0d32fe2 Active Tickets,70,Support for pronto HEX-codes,telldus-core,2.0,Some future release / Patches welcome,enhancement,stefan persson ,new,2009-10-02T12:04:12+02:00,2011-10-07T17:13:59+02:00,telldus-core should support Pronto HEX-codes as an alternative to raw codes.,mprag Active Tickets,124,Implement absolute dimming for X10,telldus-core,2.1.0,Some future release / Patches welcome,enhancement,telldus technologies ,new,2011-11-07T13:36:46+01:00,2011-11-28T16:12:48+01:00,Please see attached document.,micke prag Active Tickets,136,Support for EV1527,telldus-core,2.1.0,Some future release / Patches welcome,enhancement,,new,2011-11-29T14:33:42+01:00,2013-02-12T15:01:33+01:00,"Add support for receiving signals from EV1527 chips such as projector screens, smoke alarms and such.",micke prag Active Tickets,205,Compilation/Installation guide of TelldusCenter on Linux,TelldusCenter,,Some future release / Patches welcome,task,,new,2012-03-15T09:45:43+01:00,2012-03-15T09:45:43+01:00,,stefan persson Active Tickets,300,Saving a device does not end remote scanning,Telldus Live!,2.1.1,2.1.2,defect,stefan persson ,new,2013-04-15T14:54:22+02:00,2013-04-15T14:54:22+02:00,,stefan persson Active Tickets,63,The width of the state-column is to small,TelldusCenter,2.0,2.1.2,enhancement,micke prag ,new,2009-09-22T20:13:08+02:00,2011-10-07T17:15:53+02:00,"The width of the state-column is to small when a device has been dimmed, the width should be dynamic or static but wider.",fjacobsson Active Tickets,86,TellStickFlasher requires manual stopping of service,other,2.1.0,2.1.2,enhancement,micke prag ,assigned,2011-09-12T12:23:28+02:00,2012-06-21T12:50:13+02:00,This should be done automatically.,http://login.telldus.com/id?i=10&h=174530911a9afc527ca9880c9e6c75cca0d32fe2 Active Tickets,107,Add support for sensor events in TelldusNetWrapper,other,,2.1.2,enhancement,stefan persson ,new,2011-10-07T13:54:24+02:00,2011-10-07T17:16:58+02:00,See summary,http://login.telldus.com/id?i=10&h=174530911a9afc527ca9880c9e6c75cca0d32fe2 Active Tickets,161,Support for Velleman K8056,telldus-core,2.1.0,2.1.2,enhancement,,new,2012-01-13T10:23:46+01:00,2012-01-13T10:23:46+01:00,Attached is a demo-implementation in .Net.,David Näslund Active Tickets,162,Support for Draper projector screens,telldus-core,2.1.0,2.1.2,enhancement,,new,2012-01-17T10:17:44+01:00,2012-01-17T10:17:44+01:00,,Martin Mellerhav Active Tickets,229,Support TelldusCenter for arm,TelldusCenter,2.1.1,2.1.2,enhancement,,new,2012-07-13T10:40:36+02:00,2012-12-06T14:25:42+01:00,Build our debian packages for debian arm as well. This would allow for easy isntallation on Raspberry pie.,micke prag Active Tickets,217,FAQ for Telldus Live!,Telldus Live!,2.1.1,2.1.2,task,,new,2012-06-05T09:20:10+02:00,2012-06-05T09:20:10+02:00,"FAQ with common questions, for example: condition for an old sensor to be removed (7 days without signals + no name or not in view-list), max number of sensors, how many signals before a sensor is visible, ""ghost""-readings",stefan persson Active Tickets,35,Possibility to add a text for information how to configure a device,telldus-gui,2.0,2.1.3,enhancement,fjacobsson,new,2009-08-18T10:25:40+02:00,2012-02-10T15:10:08+01:00,"The window for adding and editing a device should have a textbox where a guide on how to configure the certain device could be inserted. The textbox should be able to handle html.",fjacobsson Active Tickets,82,Scene support,telldus-core,2.0,2.1.3,enhancement,stefan persson ,new,2010-11-10T11:53:36+01:00,2012-02-10T15:10:29+01:00,Provide support for devices of type 'Scene'. On device that controls several others and different states for them. ,http://login.telldus.com/id?i=4&h=46e8df2a59b065848aff4127f5d54383d20b1e93 Active Tickets,83,Request for new timestamp methods in API,telldus-core,2.0,2.1.3,enhancement,micke prag ,new,2010-11-24T09:57:01+01:00,2012-02-10T15:10:45+01:00,"I would like a new method that returns a timestamp for a given device, the time when a command/value was last sent. Requested (java syntax): public long tdTimestampLastSent(int intDeviceId); Existing (java syntax): public int tdLastSentCommand(int intDeviceId, int methodsSupported); public String tdLastSentValue(int intDeviceId); The timestamp could be number of milliseconds since Jan 1, 1970.",nexahome@… Active Tickets,91,Let one device react to several codes,other,,2.1.3,enhancement,stefan persson ,new,2011-09-26T12:22:57+02:00,2013-02-12T14:55:45+01:00,"Some way to update status of a device with several different remote codes. A single device may react to many signals, for example group/single. This is not reflected in TelldusCenter. Perhaps implement with pseudo-devices.",http://login.telldus.com/id?i=10&h=174530911a9afc527ca9880c9e6c75cca0d32fe2 Active Tickets,113,Backup/Restore devices from TelldusCenter,TelldusCenter,2.1.0,2.1.3,enhancement,mprag,new,2011-10-17T10:13:37+02:00,2012-02-10T15:11:04+01:00,"Easy, user friendly way to export/import devices.",stefan persson Active Tickets,211,Sorting in Telldus Live!,Telldus Live!,2.1.1,2.1.3,enhancement,,new,2012-05-29T09:52:13+02:00,2012-05-30T10:07:09+02:00,"It should be possible to order sensors by date too, and preferably also by type, location etc in edit mode.",christiancorell@… Active Tickets,2,Provide functions to control non predefined devices,driver,1.2,Some future release / Patches welcome,enhancement,micke prag ,new,2008-03-04T22:55:01+01:00,2011-10-07T17:19:35+02:00,"The API should be exposing function for controlling devices which is not setup using TelldusSetup. For some software TelldusSetup is not a good solution and must be provided with ""raw"" access to TellStick. Both sending raw-strings and wrapper functions such as {{{devNexaTurnOn(char house, char unit)}}} should be in the public API. This also makes software depending on {{{rfcmd}}} able to use the API directly and not use ugly wrappers to {{{rfcmd}}}. {{{rfcmd}}} could also rely on the API and not calculate the data itself and then support all the devices the main API supports.",mprag Active Tickets,72,Add support for more Nexa door bells,telldus-core,2.0,Some future release / Patches welcome,enhancement,micke prag ,new,2009-11-24T20:51:44+01:00,2011-12-21T11:47:30+01:00,"Add support for more Nexa door bells, such as: 18600, 18601, 18602, 18603, 18604, 18605. ",fjacobsson Active Tickets,73,Add support for more Clas Ohlson door bells,telldus-core,2.0,Some future release / Patches welcome,enhancement,micke prag ,new,2009-11-24T20:53:41+01:00,2011-12-21T11:47:56+01:00,"Add support for more Clas Ohlson door bells, such as: 36-3371, 36-2382, 32-7478, 36-3372, 36-3384, 36-3383 ",fjacobsson Active Tickets,74,Add support for more Kjell & Company door bells,telldus-core,2.0,Some future release / Patches welcome,enhancement,fredrik jacobsson ,new,2009-11-24T20:54:34+01:00,2011-12-21T11:48:13+01:00,"Add support for more Kjell & Compant door bells, such as: 50-106, 50-115, 50-116, 50-254",fjacobsson Active Tickets,90,Allow TellStick Duo to receive new protocols,other,,Some future release / Patches welcome,enhancement,micke prag ,new,2011-09-22T17:11:22+02:00,2013-01-08T18:27:25+01:00,"Possibility to, via software, set TellStick Duo in ""promiscuous"" mode, where it just filters out garbage, but all that could be valid signals are sent on to the computer. This would allow TellStick Duo owners to participate in adding support for more protocols.",http://login.telldus.com/id?i=10&h=174530911a9afc527ca9880c9e6c75cca0d32fe2 Active Tickets,99,Setting for turning off LEDs in TellStick Duo,other,,Some future release / Patches welcome,enhancement,micke prag ,new,2011-10-04T11:48:02+02:00,2011-12-21T11:49:29+01:00,"In some enviroments, the LEDs can be disturbing. Ability to turn these off.",http://login.telldus.com/id?i=10&h=174530911a9afc527ca9880c9e6c75cca0d32fe2 Active Tickets,109,Support for more Oregon Scientific devices,other,,Some future release / Patches welcome,enhancement,mprag,new,2011-10-13T10:50:16+02:00,2012-11-16T10:26:08+01:00,"Complete protocol: http://wmrx00.sourceforge.net/Arduino/OregonScientific-RF-Protocols.pdf",stefan persson Active Tickets,134,Allow TellStick Net to be configures using a static ip,Telldus Live!,,Some future release / Patches welcome,enhancement,,new,2011-11-28T11:35:24+01:00,2012-06-21T12:54:18+02:00,Right now a DHCP server is required. Some brands seems to have problems leasing ip addresses to TellStick Net.,micke prag Active Tickets,138,Raw-command files,telldus-core,2.1.0,Some future release / Patches welcome,enhancement,telldus technologies ,new,2011-12-02T10:08:14+01:00,2011-12-02T10:08:14+01:00,"Possibility to add new protocols as files with raw-commands. These can be used for pre-releases (easily distributable), incomplete protocols, or if someone wants to control some unique device.",stefan persson Active Tickets,185,Support for a virtual COM-port allowing other Homeautomation software use a TellStick Net,telldus-core,2.1.0,Some future release / Patches welcome,enhancement,,new,2012-02-10T16:50:34+01:00,2012-12-29T03:25:02+01:00,"I would suggest to develop a specific driver that could: - From one side, emulate a viruel USB/COM port so it could be used by the several existing home automation softwares (homeseer,...) - At the other side, convert the instruction sent to virtual COM port into TCP requests for the Telldus Net. That could be implemented in SOAP or RAW TCP or UDP depending what the telldusnet device is supporting easyly. Check that GPL project: http://com0com.sourceforge.net/doc/UsingCom0com.pdf Part of this master project based on virtual com port pairing: http://sourceforge.net/projects/com0com/ Problems: - Windows based software - Need to be adapted because we don't want to connect like This PC.A--virtualCOM------tcp------virtualCOM--PC.B but PC.A--virtualCOM------tcp (or UDP??)------TelldusNet",stephane dierick Active Tickets,187,Add possibility to log in with any OpenID provider,other,2.1.1,Some future release / Patches welcome,enhancement,,new,2012-02-17T10:46:32+01:00,2012-02-17T10:46:32+01:00,"Instead of just ours, google and yahoo.",stefan persson Active Tickets,234,Olov Hilding,telldus-core,2.1.1,Some future release / Patches welcome,enhancement,,new,2012-08-09T11:37:12+02:00,2013-02-12T16:43:42+01:00,"I am using sensors from Hideki weatherstation also sold as Cresta, Honeywell, Irox, Medus and RST. It would be very nice if the tellstick.net/live could support this . There has been work done with the Arduinoboard and the protocol has been hacked se this https://bitbucket.org/fuzzillogic/433mhzforarduino/wiki/Home and the paper Crestaprotocol.pdf. I cannot write C myself but i have tested the Arduino and the 433mhz reciever and it works very well. Sigolhi",Olov Hilding Active Tickets,278,Support for new blinds manufacturer,other,2.1.1,Some future release / Patches welcome,enhancement,,new,2013-01-08T10:25:19+01:00,2013-01-08T10:25:19+01:00,"Hi, Telldus-Team it's possible to integrate these shutters into the tellstick-system ??? http://www.rohrmotor24.eu/Elektronischer-Rollladenmotor-10-Nm-RME-10-15-SW60-Rolladenmotor These shutters a from a german company, produced in china presumably, with 433,92 Mhz WITHOUT a rolling code. The internal code is cracked by a user from the mikrocontroller-forum. http://www.mikrocontroller.net/topic/242784 I have the complete code! ",Raik Active Tickets,249,Diming a group will change status even of undimmable devices to dimmed,Telldus Live!,,2.1.3,defect,,new,2012-10-03T14:37:54+02:00,2012-10-03T14:37:54+02:00,"If a device in a group does not support dimming, this device will still have the status icon of a dimmed device in Telldus Live! if the group is dimmed. ",stefan persson Active Tickets,178,"Diff in Trac ""Description modified"" does not work",other,2.1.0,Some future release / Patches welcome,defect,,new,2012-01-30T10:01:35+01:00,2012-02-10T15:07:22+01:00,"Clicking ""Diff"" in Trac ""Description modified"" leads to error: Trac detected an internal error: KeyError: 'fields'",stefan persson Active Tickets,257,segfault in release 2.1.1,telldus-core,2.1.1,,defect,,new,2012-10-20T17:13:12+02:00,2013-02-06T00:05:23+01:00,"After a short period the telldus library segfaults. It would seem to be a threading/timing issue as the segfault happens at different times. This happens with both {{{tdtool.py -t}}} and a program of my own. The program registers a listener for raw events and prints these to stdout. * Telldus HW: Duo * Batch: #3 * SNo: 354 * Telldus SDK version: 2.1.1 (the tarball download) * OS: Ubuntu 12.04. * Uname: {{{ 3.0.0-26-generic #43-Ubuntu SMP Tue Sep 25 17:19:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux }}} Backtrace at time of segfault: {{{ Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffed627700 (LWP 11622)] 0x00007ffff75e87fa in pthread_cond_signal@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 (gdb) bt #0 0x00007ffff75e87fa in pthread_cond_signal@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007ffff7bcb45e in EventHandler::signal (this=0x7ffff6e39c80, event=0x603a30) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/EventHandler_unix.cpp:58 #2 0x00007ffff7bce0e6 in Event::sendSignal (this=0x603a30) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Event_unix.cpp:24 #3 0x00007ffff7bcd204 in EventBase::signal (this=0x603a30, eventData=0x6071b0) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Event.cpp:61 #4 0x00007ffff7bcd172 in EventBase::signal (this=0x603a30) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Event.cpp:53 #5 0x00007ffff7bcac4f in TelldusCore::Thread::exec (ptr=0x607170) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Thread.cpp:82 #6 0x00007ffff75e3efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x00007ffff78ddf4d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x0000000000000000 in ?? () (gdb) thr apply all bt Thread 307 (Thread 0x7fffed627700 (LWP 11622)): #0 0x00007ffff75e87fa in pthread_cond_signal@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007ffff7bcb45e in EventHandler::signal (this=0x7ffff6e39c80, event=0x603a30) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/EventHandler_unix.cpp:58 #2 0x00007ffff7bce0e6 in Event::sendSignal (this=0x603a30) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Event_unix.cpp:24 #3 0x00007ffff7bcd204 in EventBase::signal (this=0x603a30, eventData=0x6071b0) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Event.cpp:61 #4 0x00007ffff7bcd172 in EventBase::signal (this=0x603a30) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Event.cpp:53 #5 0x00007ffff7bcac4f in TelldusCore::Thread::exec (ptr=0x607170) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Thread.cpp:82 #6 0x00007ffff75e3efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x00007ffff78ddf4d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x0000000000000000 in ?? () Thread 2 (Thread 0x7ffff6e3a700 (LWP 11293)): #0 0x00007ffff782d99b in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff78241d4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007ffff7824667 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x00007ffff781c422 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x00007ffff781ad22 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x00007ffff781a902 in iconv_open () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x00007ffff7bca372 in TelldusCore::wideToString (input=...) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Strings.cpp:200 #7 0x00007ffff7bbff19 in TelldusCore::Client::callbackRawEvent (this=0x603010, command=..., controllerId=-2) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/client/Client.cpp:98 #8 0x00007ffff7bc0a1e in TelldusCore::Client::run (this=0x603010) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/client/Client.cpp:207 #9 0x00007ffff7bcac66 in TelldusCore::Thread::exec (ptr=0x603010) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/common/Thread.cpp:84 #10 0x00007ffff75e3efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x00007ffff78ddf4d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #12 0x0000000000000000 in ?? () Thread 1 (Thread 0x7ffff7fe2740 (LWP 11292)): #0 0x00007ffff78a9bcd in nanosleep () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff78d7804 in usleep () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00000000004010f0 in msleep (msec=10000000) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/gjoekeredet/../common/common.h:27 #3 0x0000000000401081 in listen () at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/gjoekeredet/main.cpp:84 #4 0x00000000004010ad in main0 () at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/gjoekeredet/main.cpp:94 #5 0x00000000004010c8 in main (argc=1, argv=0x7fffffffe638) at /home/eriklovlie/Dropbox/telldus/telldus-core-2.1.1/gjoekeredet/main.cpp:100 }}} ",erik løvlie Active Tickets,288,Poorly implemented UrlDecode,Telldus Live!,,,defect,,reopened,2013-02-08T00:30:01+01:00,2013-02-20T10:33:27+01:00,"Hi, I'm programming in C# and have encountered a problem with the Live API. I have been spending a few hours on trying to get the extras parameter to work when calling clients/list (clients/list?extras=coordinate,timezone,tzoffset). The reason why I didn't get it to work turns out to be a poorly implemented UrlDecode on the server end. See this link for an explanation. http://stackoverflow.com/questions/918019/net-urlencode-lowercase-problem Best regards, Göran Karlsson",göran karlsson Active Tickets,295,Tellstick Net DHCP client fails if DHCP server takes more than 2s to respond,other,,,defect,,new,2013-02-23T22:51:55+01:00,2013-02-23T22:51:55+01:00,"The Tellstick Net (Tested on v4) sends its DHCPREQUEST as expected, but exactly two seconds later, if it hasn't received any DHCPACK, it sends a new DHCPDISCOVER and ignores the coming DHCPACK. So if the DHCP server takes more than two seconds to respond, the Tellstick will never get any address. More than two seconds is not unusual, I think, because the server may ask (ARP request) on the network if there is any other node using that IP. My Win7 PC takes more than three seconds, for example, and I have heard others talk about five seconds. My conclusion is that the timeout is far too short. ",andreas bergvall Active Tickets,296,Tellstic Net DHCP client does not give up requesting a desired IP adress,other,,,defect,,new,2013-02-23T23:02:36+01:00,2013-02-25T21:49:56+01:00,"The Tellstick Net (v4 tested) includes a desired IP address in the DHCPDISCOVER message, which is fine. But if the server doesn't approove that address it may (according to wikipedia) silently drop the DISCOVER message and not respond. The client should then (again according to wikipedia) timeout and send a new DISCOVER without any desired IP adress. The Tellstick, however, keeps sending the same identical DISCOVER message over and over, possibly never getting any OFFER. I'm not sure whether this is a serious problem but I have tried one bridged setup where the router never responded to the DISCOVER message and this could perhaps be the cause. In another bridged setup the router responded after about 10 seconds - a behavior I have no theory about.",andreas bergvall Active Tickets,299,telldus-core-2.1.1 not closing filedescriptors/sockets properly on ARM/Raspberry Pi?,other,2.1.1,,defect,,new,2013-03-18T23:16:55+01:00,2013-03-18T23:16:55+01:00,"During investigations on why telldusd becomes unresponsive after a day or two, I found that filedescriptors were kept open. Not sure if this is the cause of the problem but it seems logical. After each invocation of tdtool i have as many more open files as i have devices (six of them) by a new thread-id. Not sure if this has anything to do with #216 or #271, it does compile on my Raspberry Pi but the fix from 488ab8 does not help with the bug. {{{ lsof | grep /tmp/Telldus | wc -l && tdtool --list > /dev/null && lsof | grep /tmp/Telldus | wc -l 24 30 lsof | grep /tmp/Telldus | wc -l && tdtool --list > /dev/null && lsof | grep /tmp/Telldus | wc -l 30 36 lsof | grep /tmp/Telldus | wc -l && tdtool --list > /dev/null && lsof | grep /tmp/Telldus | wc -l 36 42 }}} The file /tmp/TelldusEvents is the one that is opened multiple times: {{{ COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME telldusd 21141 nobody 1u unix 0xcbaa6200 0t0 3387972 /tmp/TelldusEvents telldusd 21141 nobody 4u unix 0xca7dec80 0t0 3390846 /tmp/TelldusEvents telldusd 21141 nobody 5u unix 0xca421900 0t0 3388417 /tmp/TelldusEvents telldusd 21141 nobody 6u unix 0xcbb09200 0t0 3388894 /tmp/TelldusEvents telldusd 21141 nobody 8u unix 0xca7dee40 0t0 3391133 /tmp/TelldusEvents telldusd 21141 nobody 9u unix 0xcbaa6c80 0t0 3391332 /tmp/TelldusEvents telldusd 21141 21142 nobody 1u unix 0xcbaa6200 0t0 3387972 /tmp/TelldusEvents telldusd 21141 21142 nobody 4u unix 0xca7dec80 0t0 3390846 /tmp/TelldusEvents telldusd 21141 21142 nobody 5u unix 0xca421900 0t0 3388417 /tmp/TelldusEvents telldusd 21141 21142 nobody 6u unix 0xcbb09200 0t0 3388894 /tmp/TelldusEvents telldusd 21141 21142 nobody 8u unix 0xca7dee40 0t0 3391133 /tmp/TelldusEvents telldusd 21141 21142 nobody 9u unix 0xcbaa6c80 0t0 3391332 /tmp/TelldusEvents telldusd 21141 21143 nobody 1u unix 0xcbaa6200 0t0 3387972 /tmp/TelldusEvents telldusd 21141 21143 nobody 4u unix 0xca7dec80 0t0 3390846 /tmp/TelldusEvents telldusd 21141 21143 nobody 5u unix 0xca421900 0t0 3388417 /tmp/TelldusEvents telldusd 21141 21143 nobody 6u unix 0xcbb09200 0t0 3388894 /tmp/TelldusEvents telldusd 21141 21143 nobody 8u unix 0xca7dee40 0t0 3391133 /tmp/TelldusEvents telldusd 21141 21143 nobody 9u unix 0xcbaa6c80 0t0 3391332 /tmp/TelldusEvents telldusd 21141 21144 nobody 1u unix 0xcbaa6200 0t0 3387972 /tmp/TelldusEvents telldusd 21141 21144 nobody 4u unix 0xca7dec80 0t0 3390846 /tmp/TelldusEvents telldusd 21141 21144 nobody 5u unix 0xca421900 0t0 3388417 /tmp/TelldusEvents telldusd 21141 21144 nobody 6u unix 0xcbb09200 0t0 3388894 /tmp/TelldusEvents telldusd 21141 21144 nobody 8u unix 0xca7dee40 0t0 3391133 /tmp/TelldusEvents telldusd 21141 21144 nobody 9u unix 0xcbaa6c80 0t0 3391332 /tmp/TelldusEvents telldusd 21141 21145 nobody 1u unix 0xcbaa6200 0t0 3387972 /tmp/TelldusEvents telldusd 21141 21145 nobody 4u unix 0xca7dec80 0t0 3390846 /tmp/TelldusEvents telldusd 21141 21145 nobody 5u unix 0xca421900 0t0 3388417 /tmp/TelldusEvents telldusd 21141 21145 nobody 6u unix 0xcbb09200 0t0 3388894 /tmp/TelldusEvents telldusd 21141 21145 nobody 8u unix 0xca7dee40 0t0 3391133 /tmp/TelldusEvents telldusd 21141 21145 nobody 9u unix 0xcbaa6c80 0t0 3391332 /tmp/TelldusEvents telldusd 21141 21146 nobody 1u unix 0xcbaa6200 0t0 3387972 /tmp/TelldusEvents telldusd 21141 21146 nobody 4u unix 0xca7dec80 0t0 3390846 /tmp/TelldusEvents telldusd 21141 21146 nobody 5u unix 0xca421900 0t0 3388417 /tmp/TelldusEvents telldusd 21141 21146 nobody 6u unix 0xcbb09200 0t0 3388894 /tmp/TelldusEvents telldusd 21141 21146 nobody 8u unix 0xca7dee40 0t0 3391133 /tmp/TelldusEvents telldusd 21141 21146 nobody 9u unix 0xcbaa6c80 0t0 3391332 /tmp/TelldusEvents }}} ",peter af geijerstam Active Tickets,293,Adding control of domestic central heating systems via Tellstick Net,Telldus Live!,2.1.1,,enhancement,,new,2013-02-21T11:06:37+01:00,2013-02-21T11:06:37+01:00,"We have just started using your product and like it very much because it is not tied to just one type of home automation. We do however feel that at the moment the focus is largely on controlling electrical appliances and that there is a lot of duplication between the supported devices. We would very much like to see support for central heating controls. Since in the average home approximately 60% of the energy used is in heating the house and hot water, this would make a very attractive addition and make you much more competitive with other products such as: the Conrad FS20 system, HomeMatic, and the LightwaveRF system (JSJS heating controls to be released next month). Please see: http://www.conrad-uk.com/ce/en/product/646478/HomeMatic-Black-Central-HM-Cen-3-1-B-Station http://www.conrad-uk.com/ce/en/category/SHOP_AREA_17199/Conrad-FS20-Wireless-Control-Systems http://www.lightwaverf.com/ and http://www.jsjsdesigns.com/ We recommend that you look at integration with some of the mainstream heating controls from Honeywell, Danfoss, etc. as a number of their wireless controls already operate on 433 MHz - for example: Danfoss tp5000-rf si or tp5000-rf so and rx-2 or rx-2c This would need to be two way communication i.e. being able to see the status of the heating and temperatures in the house remotely as well as being able to turn the heating on and off remotely is critical to the application working well. This would also allow users to control their heating from an iPhone or Android device or even a browser. Please also see your main support Ticket: 4628. Thank you for your consideration of this matter, Best regards Julian",julian alder Active Tickets,298,List and revoke third party access,Telldus Live!,,,enhancement,,new,2013-03-12T13:35:22+01:00,2013-03-25T17:03:02+01:00,"As a user of third party apps I would like the possibility to, within live.telldus.com, list any valid authentication tokens third parties might have and be able to invalidate/revoke them so that the third party app cannot access my account anymore.",patrik åkerfeldt Active Tickets,304,Add error code in error response,Telldus Live!,,,enhancement,,new,2013-04-28T16:28:23+02:00,2013-04-28T16:36:43+02:00,"It would be really useful if we could have a response code to every error response. For instance, a code to associate the following error with: {""error"":""The sensor with id ""299540"" does not exist""} This makes it much easier for third party apps to do something useful when particular errors occur. ",patrik åkerfeldt Active Tickets,306,Teknikmagasinet Viking Väderstation,telldus-gui,,,task,,new,2013-05-09T10:31:40+02:00,2013-05-09T10:31:40+02:00,"Hej. == Se tidigare korrespondans nedan. == Först vill jag framföra att jag är mycket nöjd med denna produkt (Telldus Net). Det som jag saknar är att den skall kunna ta emot data från min nyinköpta väderstation från Teknikmagasinet (http://www.teknikmagasinet.se/db.pl?tf=product.html&;artnr=340664) Den tar in temperatur samt fukt, enda problemet är att den visar temperaturen 40grader högre, dvs. är det 5.4 grader ute så står det i Telldus 45.4 grader. Är detta något som ni tror att ni kommer att lägga resurser på för att kunna lösa? Jag tror att denna väderstation är ganska ny så det finns risk att det kommer fler förfrågningar angående detta. Med vänlig hälsning Tomas. == Erat svar. == Hej! Det verkar ju som att den använder ett protokoll som vi redan har stöd för, men antingen med en liten modifikation eller att vi i vår protokollavkodning har missat en del som inte används i de tidigare versioner som vi har tittat på. Ska se om vi kan införskaffa en likadan enhet och försöka ändra vår kod så att den tar emot denna också korrekt. Det bästa är om du kan lägga in ett utvecklingsärende om detta själv på developer.telldus.com (logga in med OpenId uppe till höger). http://www.teknikmagasinet.se/db.pl?tf=product.html&artnr=340664",tomas larsson Active Tickets,208,Client does not receive events after that the daemon has been restarted,telldus-core,2.1.1,2.1.2,defect,,new,2012-03-16T16:28:42+01:00,2013-02-12T15:59:46+01:00,"Steps to reproduce: 1. Start telldusd 2. Start client that listens to events 3. Trigger an event -> client notices this 4. Restart telldusd 5. Trigger an event -> client does NOT notice this Don't know if this is supposed to work or not.",erik johansson Active Tickets,259,Telldus center preventing reboot,TelldusCenter,2.1.1,2.1.2,defect,,new,2012-10-22T20:41:56+02:00,2013-02-12T16:55:13+01:00,"When selecting reboot(starta om) osx, computer will not reboot unless telldus center is shut down manually. OSX 10.7.5 macbook mid 2007 Tellstick batch 16",p-a enarsson Active Tickets,271,Debian package fails to build from source,telldus-core,2.1.1,2.1.2,defect,,new,2012-12-06T14:32:01+01:00,2013-05-10T10:32:36+02:00,"I tried getting the Debian/Ubuntu source package and building it, but it is missing build dependencies specified in control file (""Build-Depends:""). I changed to: Build-Depends: debhelper (>= 7), libftdi-dev, libconfuse-dev but it still fails to compile: telldus-core-2.1.1/common/Socket_unix.cpp: In destructor ‘virtual TelldusCore::Socket::~Socket()’: telldus-core-2.1.1/common/Socket_unix.cpp:44:18: error: ‘close’ was not declared in this scope ",marius kotsbak Active Tickets,290,"Value ""timezoneoffset"" missing when querying /sensors/list",Telldus Live!,,2.1.2,defect,,new,2013-02-09T10:53:36+01:00,2013-02-12T16:42:19+01:00,"When querying sensors/info the sensors contains the value lastUpdated and timezoneoffset, however when querying sensors/list only the value lastUpdated is returned for each sensor. /sensors/info: {***, ""name""=>""Sensor 2"", ""lastUpdated""=>1360403284, ""ignored""=>0, ***, ""timezoneoffset""=>3600} /sensors/list [***, ""name""=>""Sensor 2"", ""lastUpdated""=>1360403089, ""ignored""=>0, ***, ""online""=>""1"", ""editable""=>1}] I've cut some of the data from the responses, but the timezoneoffset is clearly missing. Clients would be forced to query each sensor individually to be able to check if the values have been updated since last query. Instead, it would be better to have this value in the sensors/list and be able to query only once for all sensors.",leonard broman Active Tickets,179,Delete schedule after execution,Telldus Live!,2.1.1,2.1.2,enhancement,,new,2012-01-30T12:53:16+01:00,2012-03-30T11:00:39+02:00,"Allow the user to configure ""one-time schedules"" in the scheduler. Whenever a schedule has been executed, it should be removed. This would allow developers to build ""timers"" in their applications, webservices etc, ""Turn off light in 15 minutes"". A schedule is set for time + 15 minutes, and deleted after execution.",sebastian långström Active Tickets,267,Support Nexa Pro devices,TelldusCenter,,2.1.2,enhancement,,new,2012-11-27T21:47:58+01:00,2013-02-12T16:21:57+01:00,"Nexa has recently re-released their Nexa Pro (433 MHz) serie. From reports in the forum it looks like these doesn't work with Tellstick yet. http://www.nexa.se/Mottagare-fast-installation-3.htm Especially WRR-1 and WDR-1",patrik åkerfeldt Active Tickets,285,Filter devices per client,Telldus Live!,,2.1.2,enhancement,,new,2013-02-04T10:27:33+01:00,2013-02-12T16:33:21+01:00,"It would be nice if clients/list had an additional client filter parameter where one could put one or more client ids. The resulting device set would only include devices belonging to any of the specified client ids. Why? There seems to be a need for not including all clients all the time (like Sommarstugan).",patrik åkerfeldt Active Tickets,212,Flags in Live,Telldus Live!,,2.1.3,enhancement,,new,2012-06-01T13:23:38+02:00,2013-02-12T16:06:47+01:00,"It would be a great feature if there could be a possibility to add flags in the Live environment that could be set by external apps. If these flags then could be used to trigger different schemes to be active or inactive would that give the possibility to get a more controllable way of using the Live environment. The easiest way would be to have a limited number of flags 5 to 10 and that you could enable them to control each scheme. You could have a tick box per flag and one tick box to either use AND or OR in order to have a proper logic. '''Example: Home or out''' If two flags ""Fredrik-home"" and ""Anna-home"" could be set so that when one or more of them is set to ON so is the ""Home-scheme"" enabled and when both is set to OFF so is the ""out-scheme"" enabled. Then could the flags be controlled by for instance Tasker in Fredrik’s and Anna’s mobiles so when they are close to home is the flag enabled and when they are out is the flag disabled. So when anyone is home you have lighting that is suitable and when all are out is the lighting limited. ",fredrik töörn Active Tickets,241,Display IP-number on My devices,Telldus Live!,,2.1.3,enhancement,,new,2012-09-05T21:10:51+02:00,2013-02-12T16:13:38+01:00,"Add IP-number from where the Telldus unit is reporting from on ""My devices"" page. Could be a simple Title/tooltip hoovering the status. This will help me find the current IP-number from where my server/net is connected. Good when DynDNS is out of service or for any other reason you would like to trace where my unit is connected.",johannes hansson Active Tickets,270,Poll multiple sensors in Live! API,Telldus Live!,,2.1.3,enhancement,,new,2012-12-04T10:05:47+01:00,2013-02-12T16:24:04+01:00,"New method suggested '''sensors/poll''' which gives sensor values and lastUpdated for each ID specified. For example: sensors/poll?ids=12345,12346 might return: [ { ""id"": ""12345"", ""lastUpdated"": 1354259383, ""data"": [ { ""name"": ""temp"", ""value"": ""2.7"" }, { ""name"": ""humidity"", ""value"": ""65"" } ] }, { ""id"": ""12346"", ""lastUpdated"": 1354259401, ""data"": [ { ""name"": ""temp"", ""value"": ""19.7"" }, { ""name"": ""humidity"", ""value"": ""75"" } ] } ] Suggested parameters: ids => comma separated list of sensor Ids (the global id) to include in the result set This request would include every id specified, even though it might refer to an ignored sensor.",patrik åkerfeldt Active Tickets,272,Support for device push notification from Telldus Live!,Telldus Live!,,2.1.3,enhancement,,new,2012-12-17T19:19:19+01:00,2013-03-24T16:31:02+01:00,"It would be nice with push notifications from Telldus Live! on certain events. Like when devices change states or when a sensor reaches a certain threshold value. I am particularly interested in support for Google Cloud Messaging (GCM). Needed: registerDevice(type, identifier) where type is either APN or GCM (more?) and identifier is the device identifier for the type. unregisterDevice(...) And then some methods for what events to get push notifications for.",patrik åkerfeldt Active Tickets,284,Oregon Scientific 3.0 protocol (e.g. Oregon THGR810),other,2.1.1,2.1.3,enhancement,,new,2013-01-29T21:25:24+01:00,2013-02-12T16:32:18+01:00,"According to http://telldus.com/forum/viewtopic.php?f=12&t=3004#p18855 Oregon THGR810 uses version 3.0 of the Oregon Scientific protocol, which is currently not supported by tellstick duo/net. This protocol is documented here: http://jeelabs.org/2010/04/15/oregon-sensors and here: http://wmrx00.sourceforge.net/Arduino/OregonScientific-RF-Protocols.pdf Hopefully this will help you implement support for this sensor (and other sensors from Oregon).",per andersson Active Tickets,184,"Telldus Net: Oregon THR128 SENSOR dispayed, updated but Temp is 0°C",Telldus Live!,,Some future release / Patches welcome,defect,,new,2012-02-07T20:35:51+01:00,2013-02-12T15:51:46+01:00,"Telldus Net v3 recognize Oregon Temperature Sensor THR128, show it up in sensor list on Telldus Live, Last updated time is up to date each minute but temp is always 0°C. 3 different chanel of the sensor have been tried",stephane dierick Active Tickets,149,New functionalities in Telldus Live! Scheduler,other,,Some future release / Patches welcome,enhancement,,new,2011-12-28T10:35:15+01:00,2013-02-12T15:39:35+01:00,"2 - ""Calender"": A view in Live! where you can see all scheduled events in cronological time per weekday and per week. 3 - Not run scheduled event EVERY week: Availability to chose if an event should be executed ""Sunday, 6pm"" every Sunday or every 2nd, 3rd or 4th Sunday. 4 - Randomizer: Per device and within a predefined time slot (ex. 5pm - 11pm) will the transmitter randomly send On and Off signals with a predefined minimum and maximum time between every signal. Example: Receiver X shall between 5pm and 11pm (or around clock every Tuesday or 24x7) get on and off randomly with a minimum of 45 minutes and a maximum of 3 hours between avery command. Additions from support ticket 3151, evaluate the suggestions and translate: 6. Vill gärna kunna se i schemaläggaren symboler för soluppgång/solnergång samt att angiven offset visas. 7. Förbättra schemasidan för utskrift, så att man kan få en tydlig lista över samtliga schemaläggningar. (därav symbol för solnedgång/soluppgång, i annat fall är listan inaktuell redan efter ett dygn). 8. Tidpunkt för soluppgång/nergång vid utskriftstillfället får gärna visas på ett ställe i sidhuvudet. 9. Önskar även möjlighet för ”gångtid” dvs att man anger ”till” vid solnedgång och ”från” efter tex 2 timmar. Additions from support ticket 3152, evaluate the suggestion: 10. Is it possible to add a SLEEP option meaning turn the device ON now and OFF again in about a hour (or a configurable time with a random option)? ''Comment by Telldus: Perhaps by adding the one-shot schedule that has been discussed?'' Addition from scheduler logging ticket: 11. Perhaps in the future let members see their failed/successful jobs.",johan bäckvall Active Tickets,182,Add support for thermometer Prologue YT6981,other,2.1.1,Some future release / Patches welcome,enhancement,,new,2012-01-31T20:41:13+01:00,2013-02-12T15:50:16+01:00,"I have a Tellstick Net v3, and I am already reading the temperature off of an Oregon Scientific Term88 (can't find link, sorry. Bought at Clas Ohlson a couple of years ago). It has the ID 193 and type ""oregon"". Works like a charm. I bought three new sensors, but they don't work. Product 36-4744 here: http://www.clasohlson.no/Product/Product.aspx?id=167262846 Pictures: PCB: http://dl.dropbox.com/u/1012820/New%20folder/IMAG0181.jpg Specs: http://dl.dropbox.com/u/1012820/New%20folder/IMAG0187.jpg More links: - http://www.clasohlson.co.uk/Siteseeker/Search_o.aspx?q=yt6981&resid=1121608488&defst=True&uaid=74B9A9A5BF500B367B2B48AB58BC2A4B%3a37372E34302E3133382E323433%3a5246321595411859154 - http://www.youtonggroup.com/yt/details.asp?catid=258&id=1129&typeid=2",kevin haffner Active Tickets,213,Eventlog in Telldus Live for magnetic switches (or other devices and sensors),Telldus Live!,,Some future release / Patches welcome,enhancement,,new,2012-06-03T22:36:26+02:00,2013-02-12T16:07:43+01:00," I have bought a Tellstick Net and 2 Nexa magnetic switches and I would like to see when the switches goes on and off in Telldus Live. It would have been nice to be able to have a log to see when doors/windows/postbox/garage/whatever has been opened or closed. To see when the cleaning staff come and go or just to check when a door was used last. A time stamp next to the device when it was last changed would also be useful.",tomas kulle Active Tickets,214,Support for Oregon Scientific WMR88 Pro,Telldus Live!,,Some future release / Patches welcome,enhancement,,new,2012-06-04T10:52:46+02:00,2013-02-12T16:09:14+01:00,"I just bought WMR88 and was really hoping that it would be supported by my Tellstick Live, but it wasnt. I would really love to get Rain sensor, wind sensor and temperatur via Tellstick Live to my phone and PC. If we can get such information, it would be rather easy to make a weather statistic app. If it would help, I could lend you mine WMR88 pro for a while (I live in the Lund area).",eric strömgren Active Tickets,281,Firmware: Sending of sensor readings from Tellstick,other,,Some future release / Patches welcome,enhancement,,new,2013-01-09T22:12:05+01:00,2013-02-12T16:30:46+01:00,"A request for virtual sensors at http://www.telldus.se/forum/viewtopic.php?f=11&t=3136&sid=afeee5197f50e1e11dd3f1f56c3ac50c gave an idea: Make it possible to send sensor readings from Tellstick. With this capability, inexpensive commodity thermometers / thermo/hygrometers could be used as displays for various things. With suitable software, a thermometer could be used to show temperature from the net, e.g. from a summer house. Or displays could be used to tell detected movement from a movement sensor, also audibly when the receiver device has an alarm for a specific temperature / humidity value. With some support from a computer (or maybe with additions to firmware, though might be too complicated), this would also allow for use of a single-channel thermometer receiver as a multiplexed display for multiple sensors. ",jyrki kuoppala Active Tickets,282,Nexa WRR-1,Telldus Live!,,Some future release / Patches welcome,enhancement,,new,2013-01-10T10:08:20+01:00,2013-02-12T16:31:46+01:00,"Will there be any function specific to the receiver Nexa WRR-1 ? What i´m looking for is the ability to follow the receivers state depending on the off-timer built in to the receiver, if it could be done by reading the receivers current stat or with a timer function in the button (that you manually match with the timer in the receiver. I would also like to see a button that can be used when controlling a impulse relay, to control the relay i set the receivers off-timer to 1 sek. Basically i want a button that only sends an on-signal but alternates between on and off //Christian ",christian hedin Active Tickets,286,"Send control messages to Home Easy Heating Control, HE105.",telldus-core,2.1.1,Some future release / Patches welcome,enhancement,,new,2013-02-05T21:50:01+01:00,2013-02-12T16:35:08+01:00,"It would be great, as you add new sensors and controls, that you have a look at the Home Easy Heating control, HE105. It uses a different protocol from the other Home Easy equipment. It was discussed here >> http://www.telldus.com/forum/viewtopic.php?f=11&t=1145&p=7033&hilit=he105#p7033 and here > http://www.telldus.com/forum/viewtopic.php?f=12&t=1155&p=7034&hilit=he105#p7034 and here > http://www.telldus.com/forum/viewtopic.php?f=12&t=1360&p=8985&hilit=he105#p8985 and here > http://www.telldus.com/forum/viewtopic.php?f=12&t=1545&p=9495&hilit=he105#p9495 Many thanks even if we only have channel 5 it would be great. ",simon chorley Active Tickets,287,Get Tellstick Net to submit unknown messages as events with unknown protocol,other,,Some future release / Patches welcome,enhancement,,new,2013-02-05T22:24:10+01:00,2013-02-12T16:40:12+01:00,"I had a look at the source in http://git.telldus.com/telldus-common.git, trying to figure out how to get my Tellstick Net to report the information needed to implement support for my sensors, and decided to look at how the firmware could be extended to submit event / information also for the unparsed messages. The attached patch is a first draft, untested (as I failed to find a working compiler - the latest version was said to not work), but hope it can be a start and get you to tell me if I am heading in the right direction or not. Is there a reason the firmware isn't doing this already? Is there a reason not to report events also for unknown messages?",someone somewhere Active Tickets,265,Tellstick Duo: Add compability for Oregon Scientific THN128,telldus-core,,Some future release / Patches welcome,task,,new,2012-11-22T14:45:53+01:00,2013-02-12T16:20:57+01:00,"Tellstick Duo gets signals from Oregon Scientific THN128, but they shows 0c and 0% humidity.",mattias andersson Active Tickets,189,Enumeration of supported protocols,telldus-core,2.1.1,2.1.3,enhancement,,new,2012-02-21T14:29:51+01:00,2012-02-21T15:55:20+01:00,"It would be useful to be able to enumerate the protocols supported by telldusd using the telldus-core library. This would probably require a bit of work since there doesn't seem to be any code present for this in the daemon at the moment.",torbjörn lönnemark Active Tickets,190,Enumeration of parameters per protocol,telldus-core,2.1.1,2.1.3,enhancement,,new,2012-02-21T14:36:32+01:00,2012-02-21T15:56:12+01:00,"It's currently possible to set and get parameter values, but there is no way to retrieve available parameters using only telldus-core. Implementing this shouldn't be that much work, since the enumeration code is already present in the daemon (Device::getParametersForProtocol).",torbjörn lönnemark Active Tickets,191,Save sensor data longer time,Telldus Live!,,2.1.3,enhancement,,new,2012-02-22T14:47:02+01:00,2013-02-12T16:42:52+01:00,"Right now, it's only possible to get the latest value from a sensor. I suggest a new feature in the API that allows developers to retrieve historical sensor data. This would allow both developers and the official ""Telldus Live""-page to display graphs over temperature and, maybe, humidity. Sensor data could be saved up to a month or more.",sebastian långström Active Tickets,233,Tellstick driver in Android,telldus-core,1.2,Some future release / Patches welcome,enhancement,,new,2012-08-08T23:38:47+02:00,2012-08-10T14:27:15+02:00,"Make it possible to use an old Android cellphone to physical connect a Tellstick with USB to use it as a Telldus Center. Tellstick Live should be great also to use to prevent changing IP or behind a firewall. /Mats",mats ekström Active Tickets,204,Add function to get the library version,telldus-core,2.1.1,Some future release / Patches welcome,enhancement,,new,2012-03-14T11:43:23+01:00,2012-06-21T12:55:52+02:00,"When writing a wrapper for telldus core it might be valuable to be able to get the library version to know if a specific feature is supported or not. The branch td-version on git://github.com/erijo/telldus.git contains a basic implementation of a tdVersion() function.",erik johansson