Guy Lavoie

I have a zwave watercop valve. Zwave is generally quite reliable. A hardwired valve would need to be controlled by a contact closure, which would necessarily involve some communications (wired or wireless) between the eisy and a contact closure device.

I don't think anyone will get rich "selling" plugins. But it can be a rewarding experience to expand the controller's capabilities, and share that with other users. A bit of financial reward can't hurt either, if it can help in justifying the time and effort put into it. I've signed up for plugin develoment, and got a few simple plugins to work. It really gives an insight to some of the inner workings of the controller. Documentation is sparse, so you'll likely learn by examining other plugins. If I can get around to polishing my own plugins to the point of offering them to others, they will be free. It's a great way to pay back @sjenkins and others who are doing the same thing.

I think you're referring to the thread below. The odd thing (as my final post in that thread indicates) is that I'm running 6.0.5 in both a Polisy and a eisy, each with ZMatter dongles, and zigbee is working fine. Yet rolling back to 6.0.4 fixed the original poster's issue. We might never know what that was about.

From your pc dos prompt: ssh admin@eisy.local Or.. ssh admin@<ip address> Then enter your admin password. The first time it will ask if you want to add the fingerprint, answer yes. If you suspect that a calculation program is causing issues, add a statement to wait a couple of seconds, to have it wait a bit between recalculations.

It starts to become sluggish in admin console. You try to edit a variable and nothing seems to happen. You can view cpu activity by accessing it with ssh and run the "top" command.

One thing to watch out for are programs that aren't triggered by external events, such as recalculating a variable value based on it's initial value. That can cause a tight loop.

Do you know it's IP address? If not, look for it in your router's device table. Then try launching IoX finder, click on the "Add" button, and add a line like this: eg: IP address of 192.168.0.123 https://192.168.0.123:8443/desc See if that works.

Cloud dependant devices (and any related plugins) are always at the mercy of the manufacturer's whim. You gotta accept that from the start.

If I'm not mistaken, green means that the program is running. You could try something simple, like disabling that program (right click, disable) and see if that makes a difference. If it does, then that program would need to be examined.

Adding any new devices normally requires a sync in UD Mobile. Think of it as an integral part of the process.

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.