jca001

Are you using the ISY Portal and have the variable there defined as a Motion Sensor? As I said I can see the Motion Sensor status change on the smartphone App, maybe in 1 - 2 seconds, but the routine does not seem to run. I wish there was more status information about the routine, like it is running (in case you have a wait), the last time it ran if it is not currently active, the number of time it has run.

The above was in my original post. And I did it again while talking to them on Chat. I have even done it again since then and still have the problem. I really think the problem is on their end and is why I was asking if other have had the same problem so they can report the problem too. Thinking the more that report it the more likely somebody will take a closer look at something that is common and not just with my account. As I said looking at the smartphone App I can see when the virtual motion sensor indicate there is motion, but the routine does not run.

I have Insteon Motion Sensors at my front and side doors. When motion is detected an ISY program runs and sets a state variable and waits for 15 minutes. The state variable is set in the ISY Portal so Alexa sees it as a Motion Sensor. When set to 1, Alexa announces there has been motion at the front and/or side door on several echos. This has been working for many months, until last Saturday. The wife really likes this, especially when she is in the basement and may not hear the door bell. If I access the Alexa App on my smart phone it shows the motion sensor device as active, but the Alexa Routine does not run, no announcement. I even tried just making it only turn on a light in case there was a problem with making announcements. The light did not turn on, again like the routine did not run at all. I reported this to Alexa Support and naturally they had me cycle (unplug and plug in) each of the echos, delete the Alexa Routines and create them again. All of which I had already done before contacting them. They have escalated the problem to development, that was 2 days ago, but it still has not been fixed. So is anybody else using Alexa Routines and are they having problems? Note: I have another Alexa Routine that is voice activated and it works. It seems to only be the one that are activated by motion sensors. I also have several lights and fans controlled by voice that works, so I know Alexa is able to communicate through the ISY Portal to my ISY.

You select the Low Battery node and then query. It does not really try to query the MS, it just updates the status to OFF.

@mapeter I don't know which version it was added, but I know in 5.0.14 you can set Z-Wave Parameters in a program. Select "Your Device" and then select a Z-Wave Device and then the selection on the right where you select "On, Off, etc" has "Set Configuration". Then you can select the parameter number, size and value.

Correct. In the FD MS Low Battery Check program the IF is evaluating 2 variables, one is a State Variable and the other is an Integer Variable. The IF will be evaluated when the State Variable changes value, but it takes both variables being greater than 0 to make the IF true and run the THEN. Yes, Event driven programming takes some getting use to if you have done top down programming.

Let me try to clarify some things for LarryM since he is new to ISY. Assume the programs I provided are in place and the ISY Variables are defined. The MS sends the Low Battery Control message and the variable gets incremented. This will only happens once. Then twice a day a programs runs and checks the variable and sends a notification because the variable is greater than 0. It is Tuesday and you do not have time to replace the MS battery until Saturday because it requires you getting the big latter to reach MS. You will continue getting 2 notifications each day reminding you the MS battery is low. On Thursday you have a power failure and the ISY reboots. Because the variable has an init value of 1 or greater, you still get the notifications. On Saturday you change the MS battery, this resets the Low Battery indication in the MS itself, but does not change the On status of the Low Battery node for the MS in ISY because the MS does not send a Battery OK message. If the ISY did not reboot then you have to select that node in the device tree and then click query at the bottom which does not really query the MS, it just changes the status from On to Off. It does not matter if the ISY rebooted or not, you have to go the variable tab and zero the init and current values for the variable and click save at the bottom. I chose to be notified twice a day, but you could change it to be just once a day. You could also change it to check multiple times on Saturday and Sunday or some other day when you know you are at home. When the Low Battery message is first received it does not mean the battery is almost dead. I have put off changing a MS battery for weeks because I was out of town and it continued to work normally. I just got the notification twice a day. When I change the battery, I use a Volt Meter to check the voltage and write it and the date on the battery. You can search the forum and there are several threads about the battery life of the MS. Some people have tracked, recorded how often the battery needed to be changed, the brand they used and the voltage before as I do, and when changed to try to determine what the Low Battery threshold is. There are some recommendation for specific brands.

The old MS sends the Low Battery Control Event only once. The program is using the Control Event, not checking the status of the Low Battery node. Again if the ISY reboots for whatever reason, that node will be incorrect because the MS does not send the Battery status with each motion detection on and off. So that was my reason to write the program to set a variable and its init value, then check the variable twice a day. If you do not want to replace the battery until the MS does not work any more, then you could check the status of the Dusk-Dawn to see if it is on when you know it is dark where ever the MS is located. Like mine at the Front Door, I could check it at 11PM every night. But there have been some reports that when the Battery gets real low, the MS sends the Control On Event over and over. The mileage on the Battery is going to depend on how often the MS detects motion and has to transmit a message.

You have to go the the Variable Tab and manually change the init and current value to 0. and then click save at the bottom.

LarryM: That sets the initial value of the variable. By default all variables are initialized to 0 when the ISY is rebooted. If you look at the variable tab you will see a column "Init" and it will be 0 for each variable unless you manually change the value or do it in a program like I did. The statement is setting the variable's init value to its current value. Therefore if the ISY reboots for whatever reason, the variable will still indicate the MS has a low battery and I will still get a notification 2 times a day.

gfrancis0: There is a program like this for each MS. When this program runs because the MS sent the Low Battery Event, it increments a variable and then initializes it so if the ISY is rebooted, maybe because of a Power Failure the Low Battery status will not be lost. FD MS Low Battery On - [ID 0024][Parent 0060] If 'Front Door / Front Door-Sensor / Front Door-Low Bat' is switched On Then $Int_FD_MS_Battery_Low += 1 $Int_FD_MS_Battery_Low Init To $Int_FD_MS_Battery_Low Else - No Actions - (To add one, press 'Action') ======================================================= There is a program like this for each MS. When the State variable is changes by the program below this one and the Low Battery variable for the MS is non-zero it will send a notification. FD MS Low Battery Check - [ID 0026][Parent 0060] If $State_Check_MS_Low_Battery > 0 And $Int_FD_MS_Battery_Low > 0 Then Wait 10 seconds (Random) Send Notification to 'Home and Work' content 'FD MS Low Battery' Else - No Actions - (To add one, press 'Action') ======================================================= When this program runs it will cause the above program to run the then if the MS has caused the MS_Battery_Low to be non-zero. Check MS Low Battery - [ID 0023][Parent 0001] If Time is 7:15:00AM Or Time is 7:15:00PM Then $State_Check_MS_Low_Battery = 1 Wait 30 seconds $State_Check_MS_Low_Battery = 0 Else - No Actions - (To add one, press 'Action') ======================================================= Let me know if you have any questions about the above programs.

Michel I am running 5.0.14 already.

I have a program for each MS that sets a variable to 1 when the Low Battery Control happens. Then I have another program that runs twice a day and if the variable is not 0, then it sends me a notification. I use this method because if a notification is only sent once, it may not get delivered for what ever reason, and I keep getting reminded twice a day until I replace the battery and then zero the variable.

I know this thread is about the Z-Wave 500 Series Beta and it is closed. I think the questions I am going to ask, may have been asked in another thread, but I cannot find it. Orchestrated Home has a 500 Series Z-Wave radio, Gen 3 listed, which I assume is this Z-Wave board. Is it a later version (gen) than the Beta version? Is it OK to purchase and use now?

This question comes up now and then and sometimes there are new icons with an update and wiki is not updated. Therefore, why not have a selection under "Help" that shows the tree of devices and each icon with a brief description and for the program tab for folders and programs? This way it will always be up to date for the version being used.

Michel: I tried again later in the day and it worked. So I have renewed for 2 more years.

I received and email today stating my ISY Portal Subscription expired on 11/11/17 and I must renew by 06/30/17. So I clicked on the link provided which took me to the ISY Portal and License Renewal. I selected PayPal and that took me to PayPal, which I had sign in, but when I click OK to Pay I received a PayPal API Error. Also refresh our memory on ISY Portal License Subscription and already having a paid Network Resource Module. I did not search the forum for this because I figured it would return lots of posts I would have to read through.

I had basically the same problem and determined the ISY would only try to connect to the email Server 1 time and if it failed for whatever reason (DNS, email Server not responding ...) it did not queue the request to try again later. This was with a Comcast and GoDaddy accounts. So I searched for an email Relay Service and found ultrasmtp.com. It seems to be very reliable as far as accepting a connection and then queuing the email to be delivered to wherever. If the final email Server does not respond for whatever reason it queues the email and keeps trying every few minutes. Once it is able to deliver the email it send me an email there was a delay in delivering the email, which is an option. There are reports you can review to see how often that happens. Since making all my email notifications go through ultrasmtp.com I have only missed a few email notifications and I suspect that was because my internet was having problem in general and ISY could not get to ultrasmtp.com.

Predevice: "back" Postdevice: "overhead" A little off topic and maybe it has been covered somewhere else, but it would be nice if we could ask Alexa to list the devices. "Alexa tell issy to list devices"

What about Jeeves for Jeeves the valet, Jeeves the butler, who's first name is Reginald and other valets call him Reggie.

I have a program that increments a variable when the low battery control message is received. Then there is another program that checks if the variable is greater than 0 each morning and sends me an email if it is. Then when I change the battery I just query the MD to clear the status and manually set the variable to 0. I did it this way because sometimes emails don't get sent from ISY for some other unknown reasons. This also reminds me each day and the variable indicates how many days I put off changing the battery. There is still the problem of the MD either not sending the low battery message or it just being missed for what every reason, noise, ISY happen to be off because I was doing something, power outage, etc. So it would be nice to be able to query it, but because it is a RF device only that sleeps, that is probably not going to happen. My MDs do things that I would notice when they are not working, lights not coming on when we enter the front door, but I have been thinking of adding some more programs to check the last run time of the programs they trigger and if it has been over 24 or 48 hours, then sending me an email. But I would have to take into consideration of times we may be gone for the weekend and they would not be triggered.

Michel: Client Address (the address the ISY is using) Server Address (the address of the DHCP server, helps in case there is more than one DHCP on a network, home router, PC, maybe other devices that have DHCP server service enabled the user did not realize was enabled) Gateway Address NetMask Lease date and time (to be able to see the lease is getting renewed if it has lease timeout) Domain name provided by the DHCP server (this may not be in the main DHCP reply, the ISY may have to ask for this during DHCP communications) Domain Name Server Address (generally will be the address of the home router, but could be different if configured on the DHCP server) Any other information the developers can think of that may help trouble shoot network related problems, link speed and duplex. It would be good to be able to see all this information from the ssh connection to help with problems with the Admin Console is not working.

Michel: Thanks for the quick reply. It would be nice if in the Configuration/System screen showed this in the Network Settings, just grayed out if Automatic (DHCP) is checked. And maybe some other information that was provided by the DHCP Server. This would help with trouble shooting some network related problems, such as what I have run into. Please put it on the wish list.

Is there a way to show the Network Information the ISY is using? I know the IP Address because I can connect to it via the Admin Console and ssh. But I need to know the other things such as netmask, domain name, nameserver addresses, gateway address, etc that was provided by DHCP. I recently upgraded from V 3.2.6 to 3.3.5 and had some network resources that use the simple name to access them instead of the FQDN. Example: caiwc1 instead of caiwc1.allenhouse.network My router is running DD-WRT and has dnsmasq enabled to handle DHCP and local DNS with the LAN domain set to allenhouse.network The ISY is setup to use DHCP and gets assigned the same IP Address from the router based on the MAX Address. It should also get the other information stated above. From my other computers I can do "nslookup caiwc1" and get the correct IP Address returned. But there does not seem to be any way to make the same test from the ISY. I connected via ssh and did not find a command to show the current Network Information, only being able to change it.

Check out the new forum group (CAI Web Control to ISY Integration) in the Third Party Products for the solution I came up with.