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.
InfraRed CommunityApp SDK2
Comments
The Neeo smartphone app is a bit extensive so I have to fiddle around with it some more. I want to be able to control my Somfy screens through Homey and that works, but I still have to find a way to make it easier to use (I now have buttons "Balkon omhoog", "Balkon omlaag", "Zijkant omhoog", "Zijkant omlaag" and those texts are too long to show on the remote control....)
I have seen that it is possible to "Show controls" of a device but I was unable to make a device "Balkon" with up and down buttons so far. But maybe I overlooked the option and maybe I just made the virtual device of the wrong type.
Any tips are welcome
There are multiple way's you could do this and mostly comes down to the device type you are using. depending on the capabilities of the Somfy driver you could use a slider to set a specific value. but buttons are okay to. if a slider works then i would chose a device type ligt for instance. or Assesory. an Assesory device doesn't have a custom page in neeo but you can add all components like any other device as shortcuts.
The device type and the button names are what the remote will use to map physical buttons and to add widgets.
You could for instance add a gameconsole devicetype and set shutter up and down to the direction key's of channel up/down key's. there is an option to change the icon in the SDK but that isn't in my code yet.
when just two buttons are all you need then i would sugest an assesory device per somfy with the name "Balkon", the other "Zijkant" in both virtual devices add a buttons named "Up", "Down" when adding the as a shortcut you will get something like:
Up
Balkon
or
Down
Balkon
The device name is mentioned in the shortcut when adding it as a shortcut.
Hope this helps.
Also Jorden, Know that you can also link your Onkyo driver with NEEO.
This recording is made with my NEEO app and your Onkyo App :-D
Thanks for the tips, I'm going to fiddle around with it this weekend!
The way i do it is working well but doesn't look super clean as there is not a widget that i could use for a thermostat at this point. You need to add the capabilities as shortcuts.
So your thermostat has more or less the same capabilities as mine has.
You can create a new virtual device using the NEEO settings.
Choose the CLIMA device type and add the following capabilities
Now you will need the following flows:
One to inform the remote when you set a different temperature in your thermostat directly:
The first neeo card updates the value of the textfield. so it displayed the target temperature.the second neeo card informs the slided on what the current value is. so if you change the temperature directly on your thermostat then you will see the slider move to the position representing the correct temperature.
One to inform the remote about the currently measured temperature:
So if the temperature is different then the textlabel gets changed to the actual measured temperature.Ignore the logging, you wont need it but i personally like to log activities.
One to set the temperature:
The first neeo card is to update the textlabel so you can see what you have specifically set with the slider.
the second card sends the requested temperature to your thermostat. Use the value TAG. The decimal Tag is a percentage between 0 and 1 and is not usefull here.
I will try this next week. I am sure i can work that out. Simply log installed and indeed gives me information. Have to figure that one out.
For now I am going to install my Neo minix x 8-h plus. Fully updated. Hopefully this time Kodi will work better as before. Did not use it forca year. Neeo should be able to work in a better way as my harmony did before.
For now many thanks. Will let you know when it is working.
Marcel
I did not find a Clima device name. Is this missing?
Marcel
I’m about to update my 0.50.x release and I added the clima as an option so soon you’ll be able to. If you can’t wait then choose any other device type and later go to homey, settings, neeo, configuration. Mage a backup first by using the download button. Edit the configuration and change the device type to CLIMA.
there are some other useful features in the coming version. Like setting the minimum value of a slider. Especially handy with a temperature slider so you can limit it to normal values like 19/23.
in a couple of minutes I will push the code. It will then be available depending on how fast atom will approve the update.
- Added slider minimum value.
- Added function while adding a new txtlabel, checkbox to hide/show label name.
- Added new device type "CLIMA"
- Added feature to select a custom icon while adding a new device.
## Version 0.50.1 - Fixed a bug in the favourite feature.
- Added new device type "MUSICPLAYER"
- Removed predefined TUNER capabilities from MEDIAPLAYER. can still be added manually. Existing drivers will be untouched.
- Removed predefined VOLUME capabilities from MEDIAPLAYER. can still be added manually. Existing drivers will be untouched.
## Version 0.49.5
- removed depricated buttons 'SKIP BACKWARD' and 'SKIP FORWARD' for new virtual devices.
## Version 0.49.4
- Favorite edit tool. (Settings-> NEEO-> Configuration -> Brain, Favorites ->)
- Included "specificname" SDK feature. New virtual devices won't be added as MEDIA or GAME but with their specific name.
- Bug fixes.
the neeo - Homey integration lets you control every aspect of the remote. Commanding every button, switch, slider and recipe you have on NEEO. Besides that you can build your own virtual devices using the homey UI, this way you can use the NEEO remote to control every device connected to your homey including your homey itself.
A good example; If you use a homey AVR app for instance, you can create a AVR virtual device in the NEEO app that include a slider. With flows you can link the slider to the AVR volume. This way you can slide the volume using your neeo remote. Another flow can update the slider state when for instance you use the volume knob on the AVR. For that you’ll use the AVR app “volume changed” card (or equivalent) and add a NEEO card to update the state of the slider.
the virtual devices offer buttons, switches, sliders, images, text fields you can all use in flows.
All events generated by a NEEO remote are sent to homey. So homey knows exactly what recipe is active and when buttons are pressed etcetra. So all in all everything I could think off i have exposed to the users.
does this help?
But how do you catch events from Kodi by the way (e.g. when a movie starts)? Does the NEEO remote send an event to Homey? Or does Homey track kodi events (with the Kodi app for example)?
The way I see it is that Homey should listen to events of devices, regardless of whether they were controlled by NEEO. NEEO should be a controller only (e.g. do this or turn this light on).
Maybe I should rephrase my question. Do NEEO recipes replace Homey flows? Or are NEEO recipes just a 'chain' of commands? (turn tv on, turn playstation on, switch tv to HDMI1). I would purchase NEEO if it is a really advanced controller, rather than a partial replacement of homey.
the KODI driver has no relation with homey and is native to NEEO. I do capture now playing events. And will present it on the remote. First code steps where written a couple of days back and will be made available soon™️