rskirch

First of all, I want to acknowledge that this is on me. I took the time to read the README and understood that the API can be unpredictable at times due to its "mostly undocumented and unofficially supported" nature. As someone with over 25 years of software development experience, I recognize that issues can arise. In my past experiences with other Node servers, any bugs were usually addressed in a reasonable timeframe. I completely understand that work and personal scheduling conflicts can make it challenging to provide immediate updates. Given the unpredictability of the API, I was wondering if it might be more suitable to offer the software for free until these issues are resolved. It seems that, according to your disclaimer, other paid users might also encounter similar challenges at some point. Unfortunately, I don't have the flexibility (nor luck for that matter) in my current work and personal schedule to troubleshoot these issues myself after the hours I have already dedicated. I hope you can understand where I'm coming from.

Just an FYI for folks who are seeing this. I recently updated my Venstar CT's wireless network and IP address. I then changed it in the Node configuration. I was using the hostname: IP address custom parameter. It was on the same network as the eISY but was subsequently moved to a different VLAN. I then rediscovered the new IP and it appeared in the ISY, but the old IP Venstar was there as well. I deleted the old item from the ISY, and restarted the Node server. That did nothing. It just added it back in. Then I restarted the PG3, and still no change. You could see in the logs that the Node server had saved the IP address (as mentioned in the documentation), but would not let go. I had to uninstall the Node server. This is not desirable, as the ISY will comment out the lines in your programs referencing the Venstar and you will need to recreate them. Maybe this can be fixed in a future version?

Hey folks, I had purchased the KP200s a few months back. When I first wired them in, they seemed to work with the PG3 Node server. At some point within about a week, they stopped their connectivity to the eISY. I have removed and added back the plugs and the node server. I have reset the plugs a few times. I have set them up with static IPs, and have even removed one of the plug-pairs from accessing the internet, as a recent post had suggested. I purchased the node server and have sent the author the log files as requested in the help. It has been 2 1/2 weeks since the email. Is this still supported? Did I spend money for nothing? Is there a way to get that money back? Thanks in advance for anyone's response.

Last error message was None, IP is reserved, and the Node server log only had entries from today. That seems weird as that node says its uptime has been going for close to 2 weeks. So I ran the program (from Then), attached is the section where it started. [redacted by UD]

Hello, is it normal if I queue stations 1-3 manually for number 2 and 3 to show False on Station Queued? For that matter, Station 1 is showing as Status - Off. for what it is worth, he OpenSprinker Stations shows Stations queued 3

I know it has been a while, but I finally dealt with this. The devices wasn't being used so removed it from the EISY and then reset it. Things are fine now.

I spoke too soon. Now I am trying to add the button to another scene and am getting the same named file error.

That worked. I am not sure why I thought I had to remove the devices before I could delete the scene. Thank you.

Hey folks, I am getting this error when trying to remove a button or Insteon sensor from a scene. Essentially, it fails. I am not sure what to do at this point. firmwre: iox v5.8.0 Ui : same as above

Ok, that was the issue and this is fixed.

Done.

I don't think that is it. Even though I followed your instructions it didn't work. I have the latest for both the eisy and pg3, and any other node I can update or install with no issues. It is just this node in particular. Any other advice to try?

I don't know if this helps: 10/21/2023, 11:47:06 [pg3] error: Failed to get license 10/21/2023, 11:47:06 [pg3] error: AxiosError: Request failed with status code 403 10/21/2023, 11:47:06 [pg3] error: getNewLicense: TypeError: Cannot read properties of undefined (reading 'statusText')

Hello, I have been using OpenSprinker Node for a while now. At some point, it stopped working. I was seeing an update message for OpenSprinker, but when I clicked the update button on the OpenSprinkler Control page, nothing would happen. So I uninstalled and rebooted, but now I cannot re-install it again. It has the same behavior as the update button. When I click the install button, it looks pressed, but no pop-up like the other nodes.

EISY (5226) IOX v5.6.2 I believe this was happening even before I updated to 5.6.2. I think the eisy is communicating with the EZFlora irrigation system, but nothing happens at the sprinkler level. I am trying to troubleshoot. Is this a normal result of comparing the link tables?

Thank you, both, particularly ISY4Me! I have seen the above link and instructions for the polisy installation. What I was missing is snapping the board in half for the enclosure installation (eISY).

Nothing was included in the enclosure packaging. Anyone have a link. I tried installing myself, but I can't figure out how to add the antennae. I can't do it before installing the board as the black wires impede the board installation. If I put the board in first, I can't get the antennae in.

Yes. Now the programs are not working. I cannot express how frustrating it is to constantly have issues with this system. I have several programs that automatically control lighting, thermostats, outlets, etc. I can't afford to play the "let's troubleshoot" I don't have that kind of time. I just want the shortest path to get this working again. Should I reset the device and load the backup?

I applied the settings, rebooted, and the ISY Finder is the only thing running. Just to reiterate, I am not getting the menu item to pop up to select the admin console. So this is not a case of admin console slow or hanging, I have no way of launching it. Thanks.

Missing Programs - restored - can't get to console In the Admin Console, I selected to upgrade to 5.4.3. I backed up and it rebooted. cleared cache, used start.jnlp to create a new shortcut. ISY finder comes up and I click and select admin console. Things look fine until I click on programs. After literally 5 minutes, the interface shows I have no programs. I restore the back up, clear the cache and run start.jnlp. ISY Finder comes up and when I click nothing happens. I am not presented with a menu. P3 is working, but I cannot get to the admin console. Any advice?

removed all but one...failed. put in waits....failed.

I cleared the logs, Run Then, saved the logs. The only thing I see not related are the lines pertaining to the Climacell node communication. I haven't added anything to the system, if fact some sensors were removed in the last few months. There are items closer and much farther away that have no issues with communication. It just seems strange that 4 thermostats suddenly will not receive the time command. As a side note, those thermostats receive other commands and obey flawlessly. It is just the setting of the time.

This has worked for years on the ISY9. It just isn't working on IoP. Query and Set Clock - [ID 001C][Parent 0010] If On Sun Time is 3:00:00AM Then Set 'Thermostats / Down - Main' Set Time Set 'Thermostats / Upstairs - Main' Set Time Set 'Thermostats / Master - Main' Set Time Set 'Thermostats / Wireless - Main' Set Time Else - No Actions - (To add one, press 'Action')

Yes I notice that, but there is no reason. And I have 4 I am writing to in that program.

1. I am running it in the middle of the day manually (run then). 2. Ran program with event log at level three. Logs attached. 3. Only statement in If is On Sun, Time is 3:00am (sorry I thought it ran nightly, but apparently just once a week). Although, again, manually has the same behavior. Thanks. ISY-Events-Log.v5.4.1__Fri 2022.03.11 09.46.44 AM.txt