jca001

@pmarcos It may be labeled / listed as Z-Wave Plus, but could have been manufactured before the patent expired that allowed all manufactures to provide instant status update. The work around the patent was to have the device send a hail when the status changed and then the controller could query the device to get the current status. So you have to create a program where the IF checks for the hail and when triggered, the THEN should do a query of the device. The status of the device in ISY will be delayed by a small amount.

@Michel Kohanim I installed zabbix5-agentd-5.0.6 and it seems to be working fine. It found CPU information, File System information and other things and there are no errors logged on Polisy or my Zabbix Server. So this may be fine for my needs.

@Michel Kohanim I had done "pkg search zab" before and nothing showed up. But I just did it now and see zabbix-agent-5.0.6. I am running Zabbix 5.2.2, any chance the agent for 5.2 could be provided? I am going to install the 5.0.6 agent on my Polisy and see if my Zabbix Server can use it. Thanks for all the help you have provided.

@Michel Kohanim I was able to get SNMP configured on Polisy and Zabbix Server is getting lots, really too much, information. I will continue to make changes to /etc/snmpd.config.

@Michel Kohanim I just checked Zabbix Download page and selected FreeBSD and it shows support only up to 11.2 of the OS for Zabbix 5.2 that I am running. So this may be why it is not listed in the UDI's repository. Unless you can find an Agent in the UDI repository, I will just try setting up SNMP. I just want to monitor that Polisy is on my network and running and I think Generic SNMP will provide some System information, such as CPU utilization, Memory utilization, etc that would indicate Polisy is running. I checked Polisy I can find /etc/snmpd.config, but not the snmpd program itself. Maybe FreeBSD implemented it using a different name for the daemon. Running sudo pkg -v version, indicates there are 3 SNMP related packages installed and up to date. I will loook at /etc/snmpd.config and see if I can figure out how to configure SNMP. I may need a little help with this.

@Michel Kohanim There is still something wrong. sudo pkg search zab, does not show anything. Just to make sure the command does match something I did, sudo pkg search dev, and it showed many packages that contained "dev" somewhere in the package name. I think even if the package was in the repository your example would have failed because I think you meant to type "zabbix5-agent", 2bs.

@Michel Kohanim I was hoping that was a missed step and everything would be fine after that, but it is not. [admin@polisy ~]$ uname -a FreeBSD polisy 12.2-RELEASE-p2 FreeBSD 12.2-RELEASE-p2 r368666 POLISY amd64 sudo pkg update, says there is nothing to update. sudo pkg upgrade, says everything is up to date. sudo pkg install zabbix-client, still says the package is not matched. I am running zabbix 5.X, so maybe a version needs to be specified? Something like zabbix-client5. I tried to find an option for pkg (man pkg) to list all the available packages, but could not identify one.

@Michel Kohanim thanks for the quick reply. I am missing something or there are more command that I need to run. Before doing the following I rebooted Polisy. [admin@polisy ~]$ uname -a FreeBSD polisy 12.1-RELEASE-p5 FreeBSD 12.1-RELEASE-p5 r361000 POLISY amd64 [admin@polisy ~]$ sudo pkg update Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. [admin@polisy ~]$ sudo pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy ~]$ sudo pkg install zabbix-client Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'zabbix-client' have been found in the repositories

@Michel Kohanim Thanks. As always one answer leads to more questions. Just for clarification, do you mean the Zabbix Client or SNMP in general? Is there a Time Line, version update when it will be available? Will the inclusion be automatic or will I have to do some special steps?

I have a Zabbix Server running on a RPI 4 that is monitoring my PCs, other RPIs, Network Equipment, etc. I know ISY994 does not support any kind of SNMP so Zabbix just checks it is up by doing a ping. I have a Polisy and I know it is running BSD and Zabbix has a BSD Agent. So my question is can the Zabbix BSD Agent be install on Polisy? Or does Polisy support some Generic SNMP that I can configure Zabbix to use?

Good information. When I go to the URL and click on any of the vendor links or manual links it does not take me to them. It opens a window like I did a search on GitHub stating nothing found. Note: I do not have a GitHub account and therefore I am not signed in.

Because 5.3.0 is now an official release should it show available on Help or somewhere else on the Admin Console if you are running one of the 5.X releases? Or is it still going to require a manual upgrade?

I also have (ISY Portal variable pseudo MS) and several weeks ago they just stopped working. I waited a week to see if they would fix them self (Amazon identify something in general and fix it). But that did not happen and I contacted Amazon Support and have done so each week since. I get the same thing from them (be assured our technical staff is working on your problem and we will contact you when they have a fix). All that really happens is they say my MS must not be working correctly. Then I explain again that looking on the iPhone Amazon Alexa App it shows motion detected for the MS, but the routine still does not run. So that indicates to me that the ISY Portal and Amazon are communicating with each other. I can also manually cause the routine to play from the iPhone Amazon Alexa App and it does what it is supposed to. So that indicates to me there is nothing wrong with the routine. So I will be contacting them again tomorrow to get an update, which I am sure it will be the same.

@TexMike I did a lot of Googling and came across several post about this type of problem and some had (Amazon Personal) stating it was reported to development and then later stating it was resolved, but nothing about what the real problem and solution was. And follow up post stating the OP was still having the problem, and then nothing. Most were last year or earlier this year, but nothing for the last week or so. Your solution was to use a different account, so that sounds like it may be something specific to an account and not an over all problem affecting everybody. So I wonder if it related to an option that accidentally got changed or defaulted after some update and need to be changed, some count of something being done, etc? Did you get any response from others in the other forum stating they were having the same type of problem? Since this was back in July, have you tried setting up things in your account again to see if something changed?

Mine is setup for (Detect:1) because when the ISY is reboot the variable will default to 0 unless you have an init value defined.

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.