ISYhbsh01

@michel-kohanim Will Polisy support nodeservers for more than one ISY?

That post you responded to seems to have been a spam post.

Someone correct me if I am wrong. Scene commands are sent only once & no acknowledgments from the devices are received. The ISY just updates their status on the assumption that the scene command was properly received. With a direct command it is repeated 3 times until the device sends an acknowledgment. If your device has less than optimal communication this will explain why a scene command doesn't always work while you doing it from the console does work. You might want to consider having the program send direct commands instead of using a scene. Or you might send a direct command to that device only in addition to the scene.

I received my order 2-3 days ago.

For some people more than others.

I agree.

I remember that thread. In that specific case the lamp was controlled by an old switchlinc that always reverted to on after a power loss. That lamp was actually off when the scarf was thrown on it. It was only much later when they were away on vacation that the house had a power loss and turned on the lamp with the scarf on it.

And for a tenth of the price.

It would still take at a minimum several seconds of having the lights on at full brightness in the middle of your sleep until the ISY gets to send the command to turn it off on startup. What I have also noticed sometimes with those real short power outages for milli seconds, that's it's enough to reset my alarm clock and effect some electronics but not others. In such cases the ISY would not lose power either and wouldn't even know that there was a power outage. So in such cases I wouldn't even be able to rely on the ISY to run programs at startup.

The issue is not just that it doesn't remember the color. It doesn't remember the power state either. There are many posts on many forums from people complaining that every time they have the occasional 1 second power outage in the middle of the night, they wake up to having all their hue lights on at full brightness glaring in their face.

I don't have a WeMo myself but I know that IFTTT supports WeMo. There are a couple of threads about how to have the ISY send commands to IFTTT using network resources.

I don't know specifically about the iMeterSolo and I don't have Zwave. But for Insteon in general there is no "normal polling" involved. The Insteon devices instantly report any change in their status to the PLM/ISY. (With some exceptions on a few older devices) So unless there are communication problems, the ISY should have the correct status of all devices without any polling. Of course you could setup an ISY program to query devices if you want to. As for battery devices, those can't be polled since those devices go to sleep.

On an Android tablet I would use the Tasker app to do this.

They do have a version for the Pi. I posted the question on their forum if the pi version supports all the REST commands that the Windows version supports. This is the response I got so far: Hi, Does JRiver for the Raspberry Pi support all the same MCWS commands that the Windows version supports? Thanks I'm not sure about "all," but the ones that I've tested and script with work the same. Additionally the remote apps (Gizmo, JRemote) rely on MCWS functioning correctly and I've had no issues using the remote apps with a Pi client FWIW. So I'd be willing to wager support is 95%, if not identical. Link here: http://yabb.jriver.com/interact/index.php?topic=102874.0 ' class='bbc_url' title='External link' rel='nofollow external'> http://yabb.jriver.com/interact/index.php?topic=102874.0

In Jriver you can do almost anything with simple REST commands, no scripts needed. They call it MCWS commands.

If you keep an eye on the slickdeals website you can get every now & then good android prepaid phones for real cheap. I got a couple of Moto G's and Moto E's, which are rock solid Android phones, for $10 a piece at various times. I don't activate them with the carrier I just use wifi.

This project has unofficialy been on hold for a while due to lack of time... But it is high on my todo list. I know they recently made a linux version of Jriver, but I am not sure if it can run on a pi. Also since it is a stripped down version I am not sure if it accepts REST commands like the Windows version does. Also see my edited post above about using Tasker & AutoRemote on an Android.

At home I have an Asus Vivo mini PC running Jriver connected to my -work in progress- whole house audio system. Jriver is a very powerful media player software which accepts REST commands for almost any function you can think of. I am still in the very early stages of making all this work the way I want. But I currently already use the ISY network resource to send REST commands to Jriver to play pre-recorded mp3 files to specific zones in the house. EDIT: Another option, instead of a PC running Windows & Jriver, one can use a cheap android phone with tasker & autoremote and plug it in to an existing whole house audio system.

Using Tasker & AutoRemote my android phone is making various voice announcements upon receiving network resource calls from the ISY.

The Phillips Hue and GE Link smart bulbs also turn full on after a power outage regardless of their previous state. I remember reading on a forum someone saying that all Zigbee devices behave this way but I am not sure if that's true. I have read people complaining how they woke up in the middle of the night to full brightness of their hue lights because of a half a second power outage. So to be fair it's not just Smarthome who did it this way ten years ago. The bigwigs like Phillips & GE do this today with their latest & greatest line of products. I do totally agree though that this is not an ideal implementation.

FYI: IP cameras can have a lag of a couple of seconds even when logged in directly to the camera, on a low resolution sub-stream, and with the seconds of the current time rolling. This is especially true when on a mobile connection. A lot of things can happen in a few seconds.

Secondary KPL buton LED's cannot be directly controlled even from the Admin Console. This is an Insteon protocol limitation. The only way to control secondary KPL LED's is by including the button in a scene & then you can turn the scene on/off. Once you create such a scene you can obviously control the scene via REST.

And of course, do not do any direct linking between devices. Everything should be done in the ISY.

Teken, A better option in my opinion, and which has been on my own to-do list for a long time, is to get yourself a cheap (but good) android phone. Have it always plugged in & connected to your Wi-Fi. Install Tasker which is a very powerful app that lets you do a million things including sending REST commands based on conditions (called contexts in Tasker) that you set up. There are several ways that you can get email data into Tasker. Two of them that comes to my mind is by either using the K-9 email app which has a plugin for Tasker, or by using Notify My Android which is a push notification service which also assigns you an email address and has a Tasker plugin as well. There is a learning curve to Tasker but once you have this set up & you get the hang of it, the sky is the limit for what you can do with it. The only possible downside for you is that once you will realize what you can do with Tasker you might never want to look at your iPhone ever again… If you keep an eye out on the Slickdeals.net website, you should be able to get every now & then a good prepaid Android phone for as low as $10 sometimes. You don’t have to activate it, you can just use it on Wi-Fi. I got a couple of Moto G’s & Moto E’s for $10 at various times which are relatively rock solid phones with solid specs for these kind of purposes. I wouldn’t get a junk Android phone though which might lock up at times and thus wouldn’t be 100% reliable for home automation purposes.

Thanks