Switches connected to Telldus Live through TelldusCenter do not work #1
Comments
|
I've seen this issue before but never been able reproduce it myself since I don't have any of those devices. However I've tried my best to reproduce it and make it as simple as possible for you to solve. There is a branch called "unknown-model-support" which I would like you to try. It will be used for updates until it works. Please follow these instructions to remove the old version and install the branch:
Hopefully you should see something like this:
Next step is to start homebridge (should result in the same issue that you saw earlier)
Now to the solution that might work. I've added support for a field called
Supported modelsThis should be more flexible, but haven't had time to implement it so that it would be easy to define services with out having to use code.
Please try this and come back to me if it works or not :)! (If it does not work please add the logs). |
|
Following your instructions below does indeed make it work! The devices appear in the HomeKit app I use, and I can control them as expected. Cheers!
|
|
Great! I'll try to make a better version of this later. It would be awesome if you could test it when it is ready. |
|
Sure, just let me know when to do it!
|
|
This works fine for me, it only worked with the dimmer unit on the main branch, but with this all units worked. |
|
Now I have updated my setup with a Telldus Znet Lite, and the two units I have added to that one is not working: [Telldus Liv!e] Device "Motorvärmare2" could not be mapped to homebridge-telldus. Device information:
{"device":{"id":"1050875","name":"Motorvärmare2","state":"2","statevalue":null,"methods":"3","type":"device","client":"184080","protocol":null,"model":null,"online":"1","editable":1,"parameter":[],"status":"off"},"name":"Motorvärmare2","id":"1050875","model":"unknown","manufacturer":"unknown"}
[Telldus Liv!e] Device "Lysrör garage" could not be mapped to homebridge-telldus. Device information:
{"device":{"id":"1051218","name":"Lysrör garage","state":"2","statevalue":null,"methods":"3","type":"device","client":"184080","protocol":null,"model":null,"online":"1","editable":1,"parameter":[],"status":"off"},"name":"Lysrör garage","id":"1051218","model":"unknown","manufacturer":"unknown"}It would be great if the power consumption could be taken care of from that switch. It is reported as a power value under sensors, and also together with the switch in the telldus live page now. |
|
When is this issue going to be resolved "for real" or is this workaround the final solution? |
|
As of now it will be in a separate branch since I haven't figured out a better solution and I'm not very happy with the current one. I will give this project some time end of September/beginning of October and if I can't figure out a better solution, then I will merge this solution. Unfortunately I think it is hard to make it more dynamic. |
|
Does this mean that The unknown-model-support approach is The only Way to get this to work at The moment? |
|
Yes |
|
Ive tried the above but all devices registers but they are all marked as "no answer" in homekit. Nothing else happens. |
|
I installed eve on my phone and via eve everything seems to work. If I try to change anything like switching a dimmer on via Home (even if it says no response) I get "[Dimmer] Updated state int : 1". But if I try sending a on command via Eve I get: And it works. So does this mean that the fault is within how home handles recive and transive commands? |
|
@SpareHook I have the exact same issue with the "Home"-app. It works with siri and other homeKit apps.. Very Annoying! |
|
Removing the characteristic "get" handler solved it for me, but it was based more on trial and error than anything. A more solid solution would be better. My fork repository (master branch) also have commits fixing some issues I had with dimming through the Home app. The code now works well with scenarios, but switching on a dimmer through the home app does not work. It had to be disabled in order to make the dimming work. Well, this works for me, as I'm just using Scenarios, and not turning lights on or off manually. However, I was reluctant to create a pull request from my "experiments", as it still contains bugs. |
|
Big pull request #11 has been merged now, so in master everything should be working now. I'm using this code with unknown dimmers and switches and its working fine. npm install -g git+https://github.com/jchnlemon/homebridge-telldus.git |
|
Hi! I use this unsupported branch and it's been working great except getting "no answer" in the Home app (everything else including Siri works). I have my config configured as instructed above with the ID and type of unknown device. Love to get this going if possible. Updating to the new master, I get the following error: |
|
Hi. And then start homebridge with this environment variable like so: |
|
If I remember correct, you need to change your config file. |
|
That's correct @gustafnilklint. However I don't think using the wrong model names should cause that error. |
|
So I ran with your fork mifi and now everything works fine. The home app is also showing the different lights. I'm attaching the complete log. Is there any difference in running your fork vs the master one?
|
|
Yes. In my fork, in addition to adding optional debug output, I added a fix for model=null from the telldus api, which is the problem in your case. In my case model field from telldus api shows "n/a", dunno why it's different. So now it will no longer crash with model=null. |
|
Wow great support! Thanks! I'll run with your fork in the meanwhile. |
|
Your fork works great without "unknown_accessories" except for Oregon Scientific temperature/humidity sensor THGN132N. It reports being a '1A2D' This is my result: [Veranda] Your device (model 1A2D, id xxxxxxx) is not auto detected from telldus live ... I understand that 1A2D is not of the "valid models" so I'm just asking if you know if it is possible to set it up properly? |
|
Have you tried added your accessory to unknown_accessories with model: "temperaturehumidity" ? |
|
This in config.json: Still gets (I had this before your fork. Didn't work then either ...) : [Veranda] Your device (model 1A2D, id 4878760) is not auto detected from telldus live. Please add the following to your config, under telldus platform (replace MODEL with a valid type, and optionally set manufacturer): |
|
I have the same problem. Sensors not working.
And I havre this in config.json:
Latest node.js, 0.0.4 homebridge-telldus, 0.4.5 homebridge. UPDATE: It works with: npm install -g git+https://github.com/jchnlemon/homebridge-telldus.git Update 2: It works without any config in config.json !! |
For EA4C (guess that's fineoffset protocol), all works for me too with the mifi fork. 1A2D, Oregon protocol does not. Not with mifi, nor with jchnlemon. Unfortunately. |
|
Please post telldus api response (see comment above about DEBUG env variable) |
|
DEBUG file attached. I now have everything working except the '1A2D' Oregon sensors with your 'mifi' fork. Did try a workaround found on Telldus (http://forum.telldus.com/viewtopic.php?f=1&t=6129&start=30#p34172) but my index.js looks different from the one referenced, so I'm keeping my hopes on you ;-) |
|
I added the definition for the 1A2D sensor in the code on my fork now, so it should work now if you do a reinstall. As for why it's not working when you were defining the 1A2D sensors as temperaturehumidity in unknown_devices, that I cannot explain. Did you add ALL the unknown 1A2D's like this? "unknown_accessories": [ |
|
Yes, I had all of them in the "unknown_accessories" when I started looking into this (at least with an older version of homebridge-telldus). But anyway, with your latest update all '1A2D' sensors works like a charm in homebridge! Many thanks! Just bring your updated code into the master, and I guess more users will enjoy having Oregon sensors '1A2D' working. |
|
Great. I have a pending pull request which now also includes the 1A2D, but someone needs to merge it. Maybe someone could give me admin access to this project. I'd be happy to maintain it. If not I could instead publish my fork to npm under another name. |
|
Perfect. Now we only need a way to implement Telldus Live->homebridge-telldus with multiple homes. I have a summer house and but those sensors and switches appears where I run the server, i.e. at home. They appear (see sensors and switches with a dot before the name in my DEBUG above), but I would like to sort them under another home in HomeKit). If you also find a solution to that, I'll buy you a coffee ;-) |
|
@mifi I've added you as an admin to this project. Awesome if you could help out since I don't have that much time. |
|
Thanks, will you also add me to npm (user mifi) so I can publish new versions or do you want to have responsibility for that? |
Don't know either, but in Telldus Live they are defined as "places" in the web interface. In homebridge-telldus, all devices in all places comes in one list ("predefined room"?) instead of sorted by place. I'll search the Telldus Wiki for information and let you know. I can't see that setting up another bridge would solve the problem either, the only way would be to create another Tells Live account and move one place to that account, loosing any Pro functionality. [Maybe this discussion should be in a new development thread instead of the (non related) issue we are writing in now] |
|
Indeed, feel free to make a new issue. I'm closing this. |
I have a couple of self-learning Nexa switches that I connect to Telldus live using a Tellstick Duo. The switches appear all right in Telldus Live. When starting homebridge, I get the log message
'Device "Fönsterlampa" is defined with unsupported model type "unknown", please contact developer or add it yourself and make a pull request.'
Using TelldusCenter 2.1.2 on Mac OS X Yosemite.
The text was updated successfully, but these errors were encountered: