beninsteon

Hi @Jimbo.Automates I know it's depreciated, but thought I'd ask. I've been using my isy 994i for years without problems, including your pg2 ecobee plugin. Unfortunately the ecobee plugin has stopped working lately. It crashes about 10 minutes after startup. The first 10 minutes work perfectly. Here's the log. Anything I can do to fix this at my end? 2024-04-28 20:43:43,955 Controller polyinterface INFO Controller:_endRefresh: cleared lock 2024-04-28 20:43:44,084 Controller polyinterface INFO Controller:getThermostatSelection: Getting Thermostat Data for 411966560035 2024-04-28 20:46:41,463 Controller polyinterface INFO Controller:getThermostatSelection: Getting Thermostat Data for 411966560035 2024-04-28 20:49:41,460 Controller polyinterface INFO Controller:getThermostatSelection: Getting Thermostat Data for 411966560035 2024-04-28 20:52:41,465 Controller polyinterface INFO Controller:getThermostatSelection: Getting Thermostat Data for 411966560035 2024-04-28 20:52:41,634 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver t411966560035 - CLIHUM: 50, uom: 22 2024-04-28 20:52:41,636 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver s411966560035 - CLIHUM: 50, uom: 22 2024-04-28 20:55:41,472 Controller polyinterface INFO Controller:getThermostatSelection: Getting Thermostat Data for 411966560035 2024-04-28 20:55:41,639 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver t411966560035 - CLIHUM: 49, uom: 22 2024-04-28 20:55:41,641 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver t411966560035 - CLIFRS: 1, uom: 80 2024-04-28 20:55:41,663 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver s411966560035 - CLIHUM: 49, uom: 22 2024-04-28 20:58:41,484 Controller polyinterface INFO Controller:getThermostatSelection: Getting Thermostat Data for 411966560035 2024-04-28 21:01:41,502 Controller polyinterface INFO Controller:getThermostatSelection: Getting Thermostat Data for 411966560035 2024-04-28 21:01:41,668 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver t411966560035 - CLIFRS: 0, uom: 80 2024-04-28 21:01:41,683 Controller polyinterface ERROR polyinterface:write: Exception in thread Controller: Traceback (most recent call last): File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner self.run() File "/usr/lib/python3.7/threading.py", line 865, in run self._target(*self._args, **self._kwargs) File "/home/pi/.local/lib/python3.7/site-packages/polyinterface/polyinterface.py", line 854, in _parseInput self.longPoll() File "/home/pi/.polyglot/nodeservers/Ecobee/nodes/Controller.py", line 159, in longPoll self.updateThermostats() File "/home/pi/.polyglot/nodeservers/Ecobee/nodes/Controller.py", line 502, in updateThermostats self.nodes[address].update(thermostat, fullData) File "/home/pi/.polyglot/nodeservers/Ecobee/nodes/Thermostat.py", line 168, in update self._update() File "/home/pi/.polyglot/nodeservers/Ecobee/nodes/Thermostat.py", line 278, in _update self.check_weather() File "/home/pi/.polyglot/nodeservers/Ecobee/nodes/Thermostat.py", line 113, in check_weather self.weather.update(self.tstat['weather']) File "/home/pi/.polyglot/nodeservers/Ecobee/nodes/Weather.py", line 50, in update 'GV6': windMap[currentWeather['windDirection']], KeyError: ''

This won't work - monitoring the status of an Ecobee thermostat. All I can use is Status, and this triggers the IF.

Thanks. Just to make sure I understand what you're suggesting, the disabled program will still run and conditions in the IF statement evaluated when called from another program (Run if), but since it's disabled ISY won't use those conditions as triggers?

Hi, Can anyone suggest how to use the state of a device as a condition for program execution, rather than as a condition and trigger, which is the default IoX behaviour. I've managed this problem in the past by using integer variables to track device states, but this is overly complex. Wondering if there are other ways to achieve this. Thanks.

The solution to the all on trouble is simple. Replace old switches/dimmers with newer versions that don't respond to the all on command. Most importantly don't use the iolinc relay for critical or security related actions (garage doors, fireplaces, etc). Use another relay the isy can control with network resources (eg global cache ip2cc).

has it not been noted with eISY as well?

That's what I thought for the first 5 years or so before I had my first All On experience. Then it happened, and I learned 😃 B

You should *never* use an I/O link for critical applications (like controlling your main water supply). They are subject to the "Insteon/ISY All On" bug and can be triggered without cause. I replaced all my I/O lincs relays with Global Cache Ethernet relays after I came home a few years ago and found my garage door open and gas fireplace had been turned on. I still use I/O lincs as Insteon sensors.

I would recommend against anything that is cloud dependent/connected. Additionally, given the importance of what this is doing, zwave or even wifi are not ideal. I am using a hard wired motorized valve (eg. https://www.amazon.ca/Motorized-Stainless-Polarity-U-S-Solid/dp/B06XWG6ZLS) controlled via a Global Cache GC-100 (IP2CC would work also https://www.amazon.ca/Global-Caché-Ip2Cc-P-Contact-Closure/dp/B002ZV8FVI), connected to my network via Ethernet. Using programs/network resources in ISY to trigger valve closure when water detected where it shouldn't be.

@bmercier I have the same problem. Has been an issue for many months, if not years. An update would be much appreciated. Here's a previous post I made about this issue without any resolution

glad to hear nodelink is working with polisy. i presume this will be this same with eisy what about polyglot 2? i understand that i can't run polyglot 2 on eisy, but can i run it on a rpi and use its nodeservers on eisy?

Hi, I'm thinking about making the jump from my ISY994i to an eisy. I have several nodes with Polyglot 2 and NodeLink (both servers running on a RPi3 for years without issue). I understand that I can't run Polyglot V2 or NodeLink on the eisy itself, but will these nodeservers continue to work with the eisy and my RPi3, like it has been with the ISY994? Thanks

Has anyone successfully gotten home assistant running on eisy? If so, please share steps

Great question and I look forward to the reply. I don't think docker is compatible with freebsd though.

the proposed changes will allow fan level selection in programs. no sure how to do that without these changes

Just submitted a pull reqest to the PG2 NS on GitHub to allow direct access to high/med/low fan speeds through admin console and programs. Hopefully this can be merged for PG2 and updated in PG3 version as well. Thanks

Hi @xKing I submitted a pull request to your Polyglot 2 MQTT repo to allow direct access to high, medium and low fan speeds with iFan03 Hopefully you can merge these changes into the main repo. I have tested these changes and it's working well. Also hope you can add this to the PG3 Node Server. Thanks

On PG2 I can see source code of node servers and change it as needed. This NS in particular is amenable to adding new device types if the source can be modified. Wondering if that's possible.

Thank you. Can it be modified like the PG2 NS to add devices as well? I don't have PG3 yet so not sure if I can access source code for node servers or not

@xKing does this ns work in the same way as the mqtt node server for pg2? Thanks

What OS is eisy running? It would certainly be nice to have HA (and other software like pihole, samba server, etc) run concurrently on the same box. Could be marketed as the ultimate smarthome hardware. Ben

Most have realized the ISY reliability and programming structure is second to none, but HA offers an excellent front end and many more integrations. Hence many of us run both platforms and the ability to consolidate software on a single hardware platform (i.e. eisy/polisy) would be excellent. UD may be reluctant though given their push for further node server development with direct ISY integration, and the additional software/dependencies may compromise the stability of the IoX box.

https://www.ebay.com/itm/284894157779?hash=item425503dbd3:g:V5oAAOSwZLhiza0c

Hi, It's been ages since I've had to make an Insteon scene. I'm trying to do so now that will turn on an insteon switch when an insteon open/close door sensor is opened. Using the ISY I was able to make this scene, but unfortunately when the door closes the scene also triggers and turns the switch off. I've made an ISY program that manages this the way I want (only turn switch on when door opens and do nothing when door is shut), but I'd rather use an insteon scene because they are inherently faster. Is this possible? Thanks.

Thanks for the suggestion. I had done already, no love. @bmercier, any suggestions?