macjeff

I think I had this issue and it was the password. I cant remember but it was either it wanted the envisilink password or the passcode. Disarm has a different code and thats probably why it works. Also make sure you can do it all with the EV4 aopo. If you can there then you know you are good and its a config issue. If thats not the issue, sorry but I thought I would see if I can help since I have an EV4 and honeywell.

UPDATE- Rebooted polisy (which I had done many times before running the sudo pkg upgrade -f) and now my polisy magically came back to 2.2.13 but when I just run sudo pkg upgrade it now tells me 0 candidates) All seems fine. Not sure what the 1 candidate was but its not coming up anymore, Polisy is back to 2.2.13 and everything seems to be working.

I ran the Check For Polisy Updates. Been a few weeks since updated. I usually have at least 1. Had none. Checked with another member and he said he checked a few days ago and had none and checked yesterday and had 1. So I manually did the check I noticed I had this when doing the sudo pkg upgrade it says 1 candidate. I could not get the 1 candidate to go away. and noticed it did download and process..... [admin@polisy ~]$ sudo pkg update && 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. 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 (1 candidates): 100% Processing candidates (1 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. I finally fixed it by running this. Notice it says my Polygot was newer. So I let this run.... [admin@polisy ~]$ sudo pkg upgrade -f Password: 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 (446 candidates): 100% Processing candidates (446 candidates): 100% The following 425 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: polyglot: 2.2.13 -> 2.2.11_3 [udi] Installed packages to be REINSTALLED: (DID NOT SEND LIST BECAUSE ITS HUGE) After it downgraded now I ran the same command and now zero candidates [admin@polisy ~]$ sudo pkg upgrade Password: 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 ~]$ So I should be good now? Anything else I should run or any idea why I had a newer version? I only do the updates it says to run. Jeff

I had someone else test with my system on their iOS device and had the same problem but I don’t have another ISY running that node server to test with. But I have access to an android device it will test that shortly so I can confirm it’s just an iOS issue.

Timedata Nodeserver looks fine on the ISY Admin Console. All nodeservers are fine in UD Mobile (new iOS release) except timedata (and I have about 20 nodeservers running) Here are some screenshots. Data is missing from timedata and no data in sun (part of timedata). BUT its all in the ISY admin console just fine and everything is working. SO...this is not a huge deal but would be willing to work with you if you want me to help test.

You need .net v5 installed first. It no longer works with 3.1. I ran it on a mac for a while and now on a pi. I would highly recommend fixing or replacing your Pi. But if you did not see it, you can download a short setup guide here http://automationshack.com/Files/NodeLink_Setup.pdf

KeenHome also works with Ecobee but they are having issues this week. Flair update for the same problem came out Dec 5. Still waiting for Keen update for the app. They totally changed some things on the Ecobee end. Surprised the UDI nodeserver is still working fine. I may end up going with Flair if that is not fixed.

sorry about that. I did a quick google and did not look. But yes its KeenHome

btw...forgot to say WHY i have keen vents. I live about 50 miles outside of DC and run servers for places in DC (mostly backup ones) for disaster recovery. I have a server room in my house that of course runs hot. Keen vents solved the problem. It cools every room to the same temp using their own (or Ecobee/nest) room sensors. It closes vents and opens them if needed.

I invested in KEEN SmartVents because they were first before Flair. I saw there is a flair nodeserver but not about to spend $2000 to replace all my vents with flair unless I have to. I would be willing to chip in for time and also beta test. Of course if its going to cost as much as the flair vents then I guess I will go that route. Not sure if UDI would assist at all. Here is their API https://keen.io/docs/api/?python# I h

I discovered something new. When the Check Updates and Install Updates wont give any feedback, it wont retrieve the configuration when asked under the settings menu. It just stays on retrieving configuration (as mentioned by another user in this post). The polisy reboot fixes this also but as with the check for updates I assume its a temporary fix,

yes but just did it again [admin@polisy ~]$ curl -s https://pkg.isy.io/script/update121.sh | sudo bash Password: Installing FreeBSD-base updates 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. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. All repositories are up to date. 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 'FreeBSD-*' have been found in the repositories lookig for .pkgnew files... Preserving files that are unique to Polisy lookig for any left over .pkgnew files... Upgrade complete, please reboot using: sudo shutdown -r now

yes and he said on the chat he has the same behavior as me "Maybe I declared victory too early.... I am actually seeing the same behavior as @macjeff. After a Polyglot restart, you get the green "No updates available..." bar BUT, one day later, the bar no longer appears. Past history has been for updates to be released at least every week. I plan to wait a few weeks and see if any updates are received and successfully installed. " and I have spoken to him just recently and it is still happening. If you reboot everything is fine. You say check for updates under the system menu. and you get a response in a green box Update Check complete. No updates available!" or Update Polisy under the System Menu and you get a green box saying "Update success! Check polisy logs for details." BUT if you wait a while. Sometimes 12 hours but for sure the next day. You check for updates or Update Polisy and you get no response. Again I confirmed that @gviliunas still has the same issue. jeff

any update on this. Now been a month and if I reboot polisy I can check for updates and get no response. I used to get a banner that says Success- No Updates Available or maybe 1-5 minor updates available. I even did an UPDATE polisy and no response there either. I used to get a response there too. Once I reboot it works and I can try again later and it works but the next day every time it wont work. And I have confirmed I am not the only one seeing this problem. So the workaround is just to reboot polisy. I can confirm NodeServer updates are working as they should.

I reported this issue a week ago to Michel. I have done testing since. If I check for updates now it works but every morning when I get up I dont get the green bar. But if I reboot polisy then I get the green NO UPDATES AVAILABLE bar. Try again later in the day or at night its fine, but the next morning same thing. No bar. This started after the last Polisy updates I ran about 1-2 weeks ago.

Not only did I reboot several times but I restored both my polisy and ISY from backup up to a few days ago. I restored back after all the tests (again) to my latest backup. everything is working fine but I CANT delete the nodeserver so I will just leave it until UDI can come up with a solution Worse case I lose a slot in the ISY because as I said I can delete from Polisy, delete all nodes from ISY (but leave the server in the nodeserver menu which wont delete) and then install the same nodeserver in another slot. It works fine in the other slot and it deletes. Its just my one slot that wont delete.

yes I have the 994 Pro with Z-Wave. I looked and it was FEB when I installed this. I have backups from just about every day and some more than one in a day. but going back that far would mean recreating a lot. I would have to manually backup the contents of all the emails. I can export programs.. But variable data, etc. So much would be lost. Thats why I do so many backups!!! I may end up having to install this node server in a different node slot and just leaving the old one unused. once I get rid of it in polisy it will allow me to reinstall it and polisy sees the other version as UNMANAGED

I tried that. Nodeservers menu Configure Go to node number and choose it Click DELETE Delete this configuration pops up Answer yes SOCKET TIMEOUT ERROR All other nodes working. All other nodes will delete just fine. Just the one at 19 in the ISY I restore everything again and started the delete out of Polisy. Real quick a message pops up something about over 200 out of reach. I will try and get it again so I can capture but its a lot of work to bring that back. I need a way to get into the ISY to delete that node and have a feeling UDI might have to screenshare in and do it.

I have had a node server in polisy installed for weeks. I had some issues with it and have to delete it. I went into Polisy and stopped the node server. I then hit delete and normally it would delete from the ISY. This time it deleted from polisy but stayed in the ISY. I can delete the nodes from the ISY but if I try to delete the actual node server I get SOCKET TIMEOUT ERROR Yes I can add it to another node slot but dont want to waste my slots. I restored both my ISY backup and the Polisy Backup both current and then tried to delete again from the Polisy the way I have done this a dozen times with other node servers and it wont work. I cant go back to a backup before this existed because it has been months. Suggestions?

that worked. I had to replace DRIVER with the actual filed ID which in this case is something like GV5. Thanks, Jeff

I installed the TimeData server. If gives you data like Day of the Week and Season. So lets say I want an email every day that says its DAY OF THE WEEK and its SEASON. How can I get the data into email? The only way I see is assign season and day of the week to variables but they are numbers. So season would be 1-4 for spring summer winter fall and day of the week would be 1-7. So I can write a bunch of programs I guess to figure out which email to send but is there not a better way to dump that info into an email? could i format this so it gets the data?? ${sys.node.#.name} If so could you send me info on how to configure it for example here are some Node server address- n014_timedata Name of data field for example- Month or Season thanks, Jeff

I use MacOS X and running Mono 6. So far no issues on my end with v 6.4. I would be glad to test if you are interested in a tester on MacOS X. Jeff

Sometimes the version change is hardware. However it could be an internal software thing. One negative on Insteon though is it’s not firmware upgradable. The average life on devices is about 7 years. Mine are dying constantly since I have had my main network 7 years now. soooo. No way to know what the difference is and I am sure it would be hard to get an answer from them. You do have a 30 day return on them so you could try for a newer version. I hope it fixes the battery port issue I mentioned in previous posts. I have about 9 sensors and about every 2-3 weeks one of them has no signal and I have to adjust the battery port. On average probably each sensor reports every 6 months since its not the same one over and over every 2-3 weeks.

The original leak sensor program still works for me. there is a flaw in the leak sensors themselves. The battery connector over a few months gets pushed in and the battery stops responding. the leak sensor program will send you an error 9 which is no response from sensor. 9 out of ten times the issue is the Battery connector. Gently pull them forward so the battery fits tight. Usually then I push and hold the set button until I get the blinking light. If that works sensor is ready to go. If not replace the battery. But again most of the time it’s not the battery. .

I have the same issue. Was working until my iOS app updated. Just contacted Amazon and created a ticket. Its ONLY with routines that contain motion sensors which are all from the ISY. So not sure if its a portal issue or issue on their end. They said they had 1 other report but not sure if that person used ISY.