Guy Lavoie

Sounds like the blinds come with their own zwave hub. You can't really have two controlling hubs. So unless there is some kind of published or open spec for controlling them externally, this might prove difficult. Option B might be to exclude one from their hub and then add it to your eisy. You'd have to see what functionality you'd lose or gain that way. If they came with remotes, those might no longer work, etc.

Yes, the word for open vs turn on may or may not work. Try opening a light and see what happens. Here at home we're all set up in French with Alexa and "ouvre/ferme" works both ways.

You might try doing a zwave exclude and then adding it back.

Did you try the default "admin" as a password? The local userid and password are both "admin".

Set zwave to yes, and zigbee to no. Did you do the procedure to disable zmatter? If that's done, you should see an option in the configuration screen to "migrate to zmatter", which you don't want to do, because you're using the Zooz dongle.

I'd start implementing it at the admin console, on your PC. Yes, I'd follow the instructions with the link to deactivate zmatter, which sets the controller back to expecting the Zooz dongle. Once that is done (not sure if it involves a controller reboot) then you should be able to go into the zwave menu at the top and add devices. You might need to do an "exclude" on them first, which will then allow them to be added.

Ok. So leave it there for now. If/when you get several notifications when it rains, test it again.

I'd try testing the notification separately. Create a separate program that just looks for a state variable being set to 1, then send that same notification. If s_test_variable = 1 Then send notification Then s_test_variable = 0 Then just go into the variables tab and set it to 1. You should get one notification, and variable gets reset to 0. Test it a few times. If that looks ok, then leave the program there and if the multiple notifications ever happen again, redo this test.

Mine is very simple, with Alexa defining it as an on/off device, setting a variable. Program logic then handles all the details such allowing by time of day, alarm status, etc.

Great! This will make others happy, the question of a user assigned IP address comes up every now and then. Remember though: that added line in your /etc/rc.conf file can get removed by a version upgrade, so be ready to add it back if that happens.

The eisy has 4 usb ports so there is no problem.

Software problems rarely just "go away". What type of notification is sent? Email? Plugin driven?

If you only need zwave and not zigbee, then you can alternatively get a Zooz zwave dongle (700 or 800 series). The ZMatter price shown on the UDI website isn't the usual price. Seems they put a temporary price like that when it's out of stock. Usual price is $152. Not sure if/when it might be available again. They might be looking for an alternate solution.

I don't know if this could cause it. I'm just giving something to check which could be related. Or not. Let us know if it changes the behavior. A reboot restarts the whole controller (Unix, etc) while IoX restart only restarts the task that runs your programs.

Mine is working, but it's often slower to respond. Sometimes she'll say that the controller is not responding, but the command ends up working anyway, after a delay that can be 10 seconds or more. Another thing I've noticed is that it appears to sometimes be sending a command twice. I haven't yet made a connection with those "non responding" controller messages (like maybe it retries?). You don't noice it with lights, but I did see it happen with opening the garage door, because if it sends another command to trigger the iolinc, the second command will stop the opening door, leaving the door half open. I have a similar issue with a toggle type command that turns on/off a video fireplace. I ask it to turn it off which it does, then it does it again, which leaves it on at the main menu. I'd have to add lockout timer code to avoid this.

On your main Configuration -> System screen, do you have the setting "Catch up on schedules at Restart" checked?

Well let's back up a bit. Does the sump pump programming itself work ok? If it does, then there might be a problem with notifications itself.

Another thing: Send Notification is using a plugin, right? Are you able to send notifications ok and only once in other programs?

Interesting. Well what is in the Gen Sump2 program, and why is it run as a separate program? I have not really used Run statements like that so It might be a bit foggy as to what would happen, but I cannot see why you'd get those notifications if the "if" statement never triggered. You could also try putting the notification statement before the Run line.

As I like to say: there are two groups of computer users, those who have lost data, and those who will.

Looks right. Let me know how it goes!

Was the backup that you used for the restore recent? If it predates much of your scene creation, or worse: if it's a backup from a previous PLM, then there isn't much you can do. There is no "restore scene" utility.

It's been working fine here. Thanks again!

Ah ok yes, it's State. My booboo.

For the purpose here, you need to use a status variable. Go into variables, click on Status at the top. Then add a variable, editing the name to what you want, then click on Save. I like to prefix the name with a "s" for atatus, such as s_rain_flag. You should then be able to select the variable when programming, such as a If variable statement. Let me know if that works.