Just installed the Vera Plug in!.. Pretty cool.
Added, Advanced tab, TTS for some scenes when fired off.
NICE!!!
Did not know such a plugin even existed. Thanks for sharing!
Hmmm, will have to check this out.
@ Thibault
Great stuff this plugin!!!
One suggestion; is it possible to add a scene command that wakes up the screen?
Such command would enable cool stuff; scene trigger is “doorbel is activated”, scene commands; “tablet wakes up”… “change to page x to view front door camera”
Thanks,
Is there any documentation for the add-in? I installed it but I just get an error. I think it’s looking for an IP address but I’m not sure what IP address it’s looking for.
Thanks for sharing ! MCV validated the plugin very fast 
The official doc is available at the location provided by jimpapa in his previous post : https://imperihome.zendesk.com/hc/en-us/articles/201397057
Hmm the “change dashboard page” api call should also wake up the tablet, isn’t it the case ?
Best,
[quote=“ImperiHome, post:7, topic:179155”]Hmm the “change dashboard page” api call should also wake up the tablet, isn’t it the case ?
Best,[/quote]
IF this is true, that is amazing!!! What if it is not the app that is currently in focus? will it being the app in focus?
Edit: it does not wake my screen if it is off (it might if I was using the “camera wake” feature built in, but that just blackens out the screen). It also does not bring the app to focus, which is ok. It just would have been awesome if it did that.
Hmm the "change dashboard page" api call should also wake up the tablet, isn't it the case ?
Is it possible that the wake up does not work because I am not using the Imperihome wake up functionality, but instead use the Alternative front camera wake-up method?
[quote=“Jackpost, post:9, topic:179155”]
Hmm the “change dashboard page” api call should also wake up the tablet, isn’t it the case ?
Is it possible that the wake up does not work because I am not using the Imperihome wake up functionality, but instead use the Alternative front camera wake-up method?[/quote]
I believe that is the case. The imperihome method doesn’t actually turn the screen off, it just sets it too all black. I’m hoping that they give the option to actually turn it off instead of making it black (with the understanding that the touch to wake won’t work).
I cannot get the TTS to work on a nexus 7 gen 1 via the Plugin nor the local webserver. It however works on a Nexus 7 gen 2.
Does any one know why? The other two API functions seem to work correctly.
The TTS works fine on both my Nexus 7s (1 2012, 2 2013). Does it work through other apps (VeraAlerts for instance)?
Just implemented an improvement in the Control API in which a GoToPage API call really wakes up the device from standby (not only the ImperiHome half-standby) AND brings the dashboard to front if running in the background.
Will be part of the next upgrade in some days.
Best,
That would be awesome! I have tasker doing it now but it was a bit of a. pain to get it going. Thanks for the quick addition!
Sent from my Nexus 7 using Tapatalk
Got it working just got to put the IP in down the bottom section of the imperi home device and enable the HTTP part on the android app too easy.
Had a play with voice recognition on my Samsung tablet, picks my voice up well from about 2 meters.
If like what the others are suggesting and you can “wake” the tablet properly I can see some very cool things I can do with this soon.
Thanks for the hard work dev.
Version 2.0.11 does wake the tablet up when using the Alternative front camera wake-up method.
Great stuff…Imperihome offers functionality that no other app can…
[quote=“Javelin, post:15, topic:179155”]Got it working just got to put the IP in down the bottom section of the imperi home device and enable the HTTP part on the android app too easy.
Had a play with voice recognition on my Samsung tablet, picks my voice up well from about 2 meters.
If like what the others are suggesting and you can “wake” the tablet properly I can see some very cool things I can do with this soon.
Thanks for the hard work dev.[/quote]
The new version actually does wake the device (from screen off), but there is a bug where it actually opens the most recent app to the forefront. If I’m in Hulu and send the command it does nothing (except turn on the screen), if I click home, turn off the screen (or not), it will turn on the screen (if off) and open Hulu (not Imperihome). I will only seem to open ImperiHome if it was the last app that had focus (and yo uare currently on the home screen).
That is at least how it works for me. It’s also an all or nothing. It turns on the screen no matter what (might be nice if there was a setting, but it doesn’t affect me as all the devices I will have this one, will need this specific functionality.
Feature Request for the plugin:
Since I will be running between 5 and 10 tablets, is there a way to have 1 Vera device that handles multiple tablets (Like VeraAlerts handles it?). It seems like there will be a lot of overhead. Either that or allow the creation of children devices and only have 1 parent device (as children devices don’t have as much overhead from what I understand).
Hi,
This has just been fixed in our development environment : will be released in the next upgrade.
[quote=“SirMeili, post:17, topic:179155”]Feature Request for the plugin:
Since I will be running between 5 and 10 tablets, is there a way to have 1 Vera device that handles multiple tablets (Like VeraAlerts handles it?). It seems like there will be a lot of overhead. Either that or allow the creation of children devices and only have 1 parent device (as children devices don’t have as much overhead from what I understand).[/quote]
Hmm I agree that this would probably be better to have one device to handle all tablets. However I’m afraid that we won’t work on this quite soon as I think this would require quite some time to adapt :s
Best,
[quote=“ImperiHome, post:18, topic:179155”]Hmm I agree that this would probably be better to have one device to handle all tablets. However I’m afraid that we won’t work on this quite soon as I think this would require quite some time to adapt :s
Best,[/quote]
I understand. It’s just a “memory” issue. I do believe the plugin in general would use less memory if it either handled multiple tablet’s per device, or used child devices. I’m not sure the latter uses less memory, but I believe it does.
Child Devices use less memory than individual devices.
That’s why Z-Wave devices are cheap in memory compared to Plugins.
Z-Wave devices share the same controlling device.