tmorse305

Hi @markv58, I have one switch associated with ISY variable ID 47 that does not show up in the AC. I've tried a reboot of the NS and restarts on the AC but no luck. So I thought I would try to delete it then add it back. When I press the delete key next to the switch 47 entry, it deletes but than about 3 seconds later it reappears. Any suggestions? Thanks for your help.

Hi @markv58, I was trying out the virtual switch tonight for the first time (BTW the temp is working great!). I added it to a scene. I could only add it as a responder not sure why. It tracks the scene status unless I brighten from off using one of the physical switches. See attached, I brighten from off using one of the switches but you can see it is still off. Thanks for your insight.

We all owe you a beer or 2!

I am still running v1.0.15, I have 12 nodes ( all value=temperature). It has been up and running for 12 hours. Maybe the crash is related to temperaturec? I'm not using that.

v1.0.14 solved the issue. Its been running correctly for a few hours. Thank you.

Hi, Today when I checked my temps I noticed that the Since Last Update was stuck at 2 minutes. I checked the log and it looks like an error occurred, see below. A restart of the node server and Polyglot did not help. Thanks for your help. 2020-07-22 13:25:55,704 Controller polyinterface ERROR polyinterface:write: Exception in thread Controller: 2020-07-22 13:25:55,704 Controller polyinterface ERROR polyinterface:write: Exception in thread Controller: Traceback (most recent call last): Traceback (most recent call last): File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner self.run() self.run() File "/usr/lib/python3.7/threading.py", line 865, in run File "/usr/lib/python3.7/threading.py", line 865, in run self._target(*self._args, **self._kwargs) self._target(*self._args, **self._kwargs) File "/home/pi/.local/lib/python3.7/site-packages/polyinterface/polyinterface.py", line 846, in _parseInput File "/home/pi/.local/lib/python3.7/site-packages/polyinterface/polyinterface.py", line 846, in _parseInput self.longPoll() self.longPoll() File "./Virtual.py", line 56, in longPoll File "./Virtual.py", line 56, in longPoll self.nodes[node].getDataFromID() self.nodes[node].getDataFromID() File "./Virtual.py", line 387, in getDataFromID File "./Virtual.py", line 387, in getDataFromID self.pullFromID(_type, self.action1id) self.pullFromID(_type, self.action1id) File "./Virtual.py", line 401, in pullFromID File "./Virtual.py", line 401, in pullFromID LOGGER.info('Init = %s Prec = %s Value = %s',_value[1], _value[2], _value[3]) LOGGER.info('Init = %s Prec = %s Value = %s',_value[1], _value[2], _value[3]) IndexError: list index out of range IndexError: list index out of range

Things are looking good on my end, thank you!

@markv58, I installed v1.0.12 but the settings for Action 1, Action 1 Var Type, and Action 1 Var ID do not survive an AC restart. However it appears to be working, in my case variable 46 is updating the node display at the long poll interval.

Thanks @Teken, I had no clue that was a button thought it was just a label! I pressed them and ISY went busy for a moment so it seemed to save. However when I restarted the AC they were gone. Curiously it did load the correct value from variable 46 in the current field. @markv58, I did restart the Node server, no obvious errors in the log that I can see. Will send it to you.

Thanks @markv58, my node display is now correct. Sorry, I missed your comment about temperaturec only in v1.0.10. The potential bug you just described may be happening to me. I think I have it configured correctly but the Time Since Last update just continues to increase with no updates. Just so I'm clear about the changes you have made, the number used to configure the node in the Polyglot configuration (46 in my case) no longer associates it with variable 46? To do that I have to make the connection as I did below. Safe Travels. @Teken, what did you mean by this: "The key thing is to press on the side button so that selection is saved"

I upgraded to v1.0.9 but encountered the same problem I had with an earlier rev. The display on the ISY side still looks like the earlier revision. Here's what I tried: Update to v1.0.9 Restarted nodeserver confirmed it is running v1.0.9 Brought up the AC, did a Profile Update, closed AC Restarted the AC, still shows the earlier version of the temp node, closed AC Restarted Polyglot(RPI) Brought up the AC, did a Profile Update, closed AC Restarted the AC, still shows the earlier version of the temp node Rebooted ISY Brought up the AC, did a Profile Update, closed AC Restarted the AC, still shows the earlier version of the temp node What else can I try? Thanks for your help. (same result with v1.0.10)

You're welcome and thanks to @bmercier for continuing to enhance the Alexa interface.

Here's what the programming would look like if you use a variable with "Device with Open/Close syntax. In my case I choose Open=2 and Close=1 for the variable($sLeft_Control) assignment. This eliminates the need for the helper program and also eliminates the Routines on the Alexa side. I use a resource for the door control not an I/OLink but the idea is the same.

From https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#Programs Programs Turn On: “Alexa, turn on the kitchen light” - runs Then Turn Off: “Alexa, turn off the kitchen light” - runs Else You can't run the IF directly from Alexa. Instead of having your Alexa routine run programs you could have it set a variable instead. Then on the ISY side your IF could include the variable as a condition. Or you can eliminate the Alexa routine all together and expose the variable as "Device with Open/Close syntax in the Portal. Then when you say "Alexa, open the <variable name> the variable will be set to the on value and vice versa.

Sorry markv58, I didn't see your post when I replied to Teken. The update to v1.0.8 solved the problem. Thank you and Teken for your help.

Set precision to 1 on the temp state variable, rebooted RPI, Updated Profile again, restarted AC, but no luck. Interesting that when the Polyglot restarted all of the nodeservers came up running except VIrtual. I had to restart it manually. Not sure if that offers anyone a clue.

Thanks Teken, I had already tried everything in your first paragraph before reaching out for help. I rebooted Polyglot first, then ISY. Tried another Profile Update and AC restart but still no joy.

Is there something else I need to do to see the additional fields? I'm running 1.0.7, I updated the profile and restarted the AC, ran the 'then' part of the program twice but I still see this. Thanks for all the work you have done on this nodeserver!

If you have an Alexa within earshot you could have it say "Shed door opened" when the breach occurs.

Is the door sensor Insteon as well? Is the door sensor available in your ISY or is the email being sent to you some other way? If you have outside spot lights that hit the shed, then you could set those off when the door is opened. Tell us a little more about your setup.

I use this program to keep track of the battery level in the MS. I can't take credit for it, I found it in a thread here years ago. It uses the light/dark sensor to confirm that the motion sensor is still alive. If the light/dark sensor doesn't toggle in less than 26 hours I get a message to check the battery. DW Motion Battery Check Copy - [ID 0076][Parent 0001] If 'Outside / Driveway-Sensor / Driveway-Dusk.Dawn' is switched On And 'Outside / Driveway-Sensor / Driveway-Low Bat' Status is Off Then Wait 26 hours Send Notification to 'Text-Tim' content 'Battery Check' Set 'Outside / Driveway-Sensor' Write Changes Run Program 'DW Motion Battery Check Copy' (If) Else Wait 5 minutes Send Notification to 'Text-Tim' content 'Battery Check' Set 'Outside / Driveway-Sensor' Write Changes

I'm glad you figured it out, I was getting ready to suggest a support ticket, you seemed to be doing everything correctly.

Alexa is treating it as a light, that's why it displays the on/off controls. A light will never show up it the trigger list. Could you try deleting it from Alexa and then rediscovering it? Don't touch anything in the portal, it seems ok from there but it is not coming through correctly. In your last picture the type is "other", that's not correct, the description doesn't make sense either. Compare to mine. Is the state variable 'Motion' the first one you defined? That's what the (1) would suggest. Just checking.

You're right it should show up under the 'Smart Home' listing. The reason it's not showing up for you is that Alexa thinks it's a light. Try deleting 'cottage motion' from Alexa and rediscovering it. It should show up as a motion sensor not a light.

Based on screen #2, you have defined the Alexa Category as a light not a motion sensor. That's why it's not showing up in the routine choices. Go back to the portal and double check the Alexa Category. It should say Motion sensor, see screen shot. The only ISY devices that show up in Alexa as those defined in the portal, if they're in Alexa you must have create the link in the portal. For the August lock to show up you must have enabled the August skill for Alexa, or through the portal.