This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Official SDK2
Comments
I use Openelec.. You don't need the UDP port, but the tcp one (version 1.1 and higher) . The default portnumber is 9090 (also suggested when you add a new device).
When you use the app store version you can just use the details of your webserver on Openelec.. Default port there is 8080, but you'd need to enable the webserver first (see the instructions when adding a new device)
@Fire69 and @MartijnDeRhoter : Could you report your test findings here? I want to push 1.1 to the app store, but need some test feedback first .
Made a flow: When <a movie has started>, Then <turn off light><say something: starting <title>>
This is working very good!
Do you want me to test something else?
Setup was quite straightforward, once I figured out that an offline RP3 won't respond on any port
I'll do some more testing tonight.
Some remarks about the json-file:
- You have a double trigger (first and last): "en": ["play latest episode of", "play the latest episode of", "play latest episode", "play latest episode of"],
- Could you add 'start' to "nl" : ["speel film", "speel de film"] (maybe for series too)? Seems more natural to me. Maybe it's a Belgian thing
- "nl": ["speel muziek"]: can you add something here? Artist, album, genre?
- Ouch, that last one should be 'play the latest episode'. Nicely found!
- Good suggestion, I'll add 'start film' as well
- Not necessary to add artist or album here.. This is just for the trigger. So a function 'playMusic' gets triggered by 'speel muziek', then I can check whether the user wants to search for an artist (speel muziek van artiest) or genre (speel muziek van genre) by looking at the total transcript (=what the user said).
@All: Any requests regarding new features? I am already working on multi device support, but that's it for now. The way Homey parses numbers needs to be improved before I can add specific series play back (play series xxx season 1 episode 2). Homey now parses numbers as text when included in a sentence (24 = twenty four).
So apparently you already implemented it the way I'd like it to be
For music you could maybe add the party mode, so Kodi starts playing random songs.
http://www.makermusings.com/2015/08/22/home-automation-with-amazon-echo-apps-part-2/
thanks for all the great work so far.
i tried to add a kodi device to homey but it doesn't proceed nor does it give an error.
the port is 8080, with or without password.
I tried to misspell the ip and I get an error.
So could this be a ui error or do I have to do more tests?
i haven't tested it from another client, so I'll test that first
thx for the suggestions
Similar problem?
I don't think so. As far as I know the iKettle app automatically searches for connected iKettle's on the network. Since you manually need to configure your Kodi details, this shouldn't be an issue.
Could you explain (in detail please) what you tried? Also, what is the IP of your Kodi and Homey device? The following should work:
- Enable webserver on Kodi
- Add a Kodi device on Homey and enter the details (IP / port / username / password)
If not this does not work, try browsing to the IP address (192.168.x.x):port (default 8080) on a PC that is connected to the same network (e.g. with Chrome or IE), then enter the username / password. If that works, then there's something wrong with the app, if that doesn't work, then there's something wrong with your (network?) configuration..
Thx for the reply.
i've tested the kodi web server on 2 different computers without password: the web server works! Homey does not find the kodi web server, there is no feedback from the ui.
after that I've changed the subnet to 192.168.1.x
2 computers can connect to kodi web server with kodi/kodi as credentials
but the reply from homey changed!
now the ui replies: "could not connect to your Kodi! Please verify your details"
This is different than before.
it looks like the local network config, seems to be correct.
2 out of 3 clients can connect to the web server
Kodi gives me a reply, with the 192.168.88.x that didn't happen.
now I'm thinking about another way to get it to work
I'd wait until v1.1 gets approved. I use a different connection method as of v1.1. This should result in a better, more stable connection. Or, if you feel really adventurous, grab v1.1 from Github . There are instructions on how to do this in this topic.
OK, once again, you're doing great work on the app and the support!
The problem got resolved by wiping all data on Homey and start all over again.
(the lifx bulbs are working now also)
Next time I'll do a complete wipe before I start asking questions
If you are ever curious about investigating, right now I have it working via a HTTP call to Kodi's JSON, something along the lines of:
{"jsonrpc": "2.0", "method": "Player.Open", "params": {"media":"plugin://plugin.xxxxx"}, "id": 1}
If I'm home and I can check what I exactly have, I will update this post.