Breezyken

Thanks Bob. Found a lower case that needed to be upper; my error. I made several different v1 calls and they still work, so I'll stick with that as well. Now to make use of the data in a program!

I have had this plugin running for a couple of years now, but I had to reinstall with EISY and a new desktop PC. Error indicates bad parameters in api call, but I have verified the configuration and all password variations. Maybe you can see something I am missing. The documentation needs updating and the api calls there no longer work. I could use an updated api example to assist in troubleshooting. I have attached the plugin startup log, and these are the significant lines; MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. Thread-4 (start) udi_interface ERROR query:get_data: request failed: Expecting value: line 1 column 1 (char 0) DavisWeather_1-7-2025_91748_PM.zip

Michel says the SD card slot is not supported - so much for that idea.

Yes, that will help. After reading a few more posts, I should have asked if the SD card slot on the EISY is actually supported. That arose in another older post and was never answered. If not I'll just get an SSD and install it. if no response in 24 hours I'll open a ticket.

I'd like to install a uSD card in EISY to store some audio files for playback via this plugin. I'm familiar with Debian Linux tools, but the EISY OS lacks most of those. I'm looking for the steps necessary to do this, how the card should be formatted, (ext4?), how it will appear in the device list, necessary permissions etc. I'm logged in as admin: should I continue as admin or add a user? I've reviewed most of the posts here, but most are old and incomplete. Thanks, as I think there may be others that want to do this as well. An up to date tutorial on the subject would be great!

I finally have the HS-300 power strip nodes installed and working. Even though it was connected to my WiFi and could be controlled via the Alexa app, apparently it needs a stronger connection while the PG3 node install is made. I ended up relocating it nearer the wireless access point and the install completed without error. One thing to note, and YMMV, when it shows up in the admin console, it was way down off screen in my list of many devices because it installs with the label beginning with SmartStrip, not Kasa. I kept looking for the plug nodes under Kasa Controller, and they were not there. Maybe the name in the install script could be changed to group it with the main controller node?? Anyway, Jimbo, thanks for bearing with me through this process.

Was I wrong to enter the IP address of the Kasa device?

I updated IoX to 5.8.4. I've corrected the kasa IP address in configuration, I've deleted and reinstalled Kasa node several times. I've restarted admin console over and over, shut down EISY and restarted. The admin console shows the node connected, but it is unable to add the nodes for the outlets. I had the trial version last year and it worked fine. Log files tell me the install can't find db_getNodeDrivers: tplkasactl . Has this software been tested with the HS-300 ??? Has anyone installed this node server for this device? It's on my network (no sub networks) and my iPhone app works perfectly with it and also through Alexa voice commands. That tells me there is something wrong with the node installer. It's obvious that EISY is unable to communicate with Kasa HS-300. Is there any little test routine I can use to test communication between EISY and Kasa HS-300? I have edited out a lot of repetitive ERROR lines in the attached log file generated after the last install. Error level is set to WARNING. IoX Firmware & UI at v.5.8.4. Other node servers such as WeatherLink work perfectly. I am running WIN 11 PRO on my desktop. Install Log 20241227_1629.log

I have removed the Kasa trial version(expired) and installed the paid version. Configured according to instructions and it shows connected on admin console. There are no nodes (plugs) shown. Upon restart I recieve the following error: 2024-12-23 11:29:39.536 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 192.168.1.38 trying to connect to 192.168.1.38 Discover is not working for the plug nodes. How do I get them installed? I disabled my firewall and I did another restart and discover in PG3 and get the following error: 12/23/2024, 11:35:25 [pg3] warn: Request for customtypedparams. Not found in database Also, I have set change_node_names to true. The existing names have been picked up from the app on my phone. Is this a problem/conflict? Looking for answers. Thanks!

I have a Kasa HS300 6 outlet plug strip and I want to install the node server on my eisy. I previously had the trial version of the node, so I deleted that, purchased the current paid version and installed that. Going to the admin console I selected Kasa, but was unsure how to proceed from there. My choices are ADD NODE or ADD ALL NODES. Selecting Add Node gives me a list of Kasa devices but no model numbers. I might guess at any of the first four, but then I get a window asking for Name(whose name?), Node Address, Primary Node Address(what is this?), so I stopped there. So far the Kasa Controller shows up in the admin console Device list, but no outlets. Searching the wiki's etc. I found one that said all this should be automatic and #1 do NOT open the Node Servers option. General info about installing node servers does not help. I believe I am up to date with Kasa 3.1.4, PG3x 3.2.17 & IoX 5.7.1. I've been at this for over three hours now, and it's very frustrating. I just stopped the server and will wait for help. LOG Follows: 2024-12-22 12:42:29.797 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: User=0021b9026837_4 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026837_4 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026837_4 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6Njg6MzciLCJwcm9maWxlTnVtIjo0LCJsb2dMZXZlbCI6IldBUk5JTkciLCJ0b2tlbiI6Ik0/VGwqSndEZ2tOJkN4V2EiLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNyIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJTdGFuZGFyZCJ9 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-12-22 12:42:29.834 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-12-22 12:42:30.334 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-12-22 12:42:30.558 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-12-22 12:42:30.559 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-12-22 12:42:30.559 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-12-22 12:42:30.559 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-12-22 12:42:30.559 MainThread udi_interface INFO __init__:<module>: Loading OAuth module 2024-12-22 12:42:30.560 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-12-22 12:42:30.560 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.3.14 Starting... 2024-12-22 12:42:30.659 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.17 [ISY: 5.7.1, Slot: 4] 2024-12-22 12:42:30.659 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.38', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'} 2024-12-22 12:42:30.660 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2024-12-22 12:42:30.660 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: tplkasactl not found in database. 2024-12-22 12:42:30.660 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026837_4.cert key: 0021b9026837_4.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2024-12-22 12:42:30.660 MainThread udi_interface.interface INFO interface:addNode: Adding node Kasa Controller(tplkasactl) [None] 2024-12-22 12:42:30.660 MainThread udi_interface.interface INFO interface:setController: Using node "tplkasactl", driver "ST" for connection status. 2024-12-22 12:42:30.661 Interface udi_interface.interface INFO interface:_startMqtt: MQTT keepalive is 300 seconds. 2024-12-22 12:42:30.710 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with Reason code: Success 2024-12-22 12:42:30.710 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:68:37_4 - MID: 2 Result: MQTTErrorCode.MQTT_ERR_SUCCESS 2024-12-22 12:42:30.752 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Successfully for Message ID: 2. Reason codes: ['Granted QoS 0'] 2024-12-22 12:42:30.836 Thread-5 udi_interface WARNING Controller:handler_data: No custom data 2024-12-22 12:42:30.980 Thread-11 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded params=None data=True... cnt=600 2024-12-22 12:42:32.152 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a14343 not found in database. 2024-12-22 12:42:32.239 Thread-20 udi_interface WARNING Controller:handler_data: No custom data 2024-12-22 12:42:35.241 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434301 not found in database. 2024-12-22 12:42:35.242 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434302 not found in database. 2024-12-22 12:42:35.242 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434303 not found in database. 2024-12-22 12:42:35.243 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434304 not found in database. 2024-12-22 12:42:35.243 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434305 not found in database. 2024-12-22 12:42:35.243 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434306 not found in database. 2024-12-22 12:42:35.402 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434301 not found in database. 2024-12-22 12:42:35.403 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434302 not found in database. 2024-12-22 12:42:35.403 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434303 not found in database. 2024-12-22 12:42:35.404 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434304 not found in database. 2024-12-22 12:42:35.404 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434305 not found in database. 2024-12-22 12:42:35.405 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434306 not found in database. 2024-12-22 13:09:07.511 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-12-22 13:09:07.511 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: User=0021b9026837_4 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026837_4 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026837_4 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6Njg6MzciLCJwcm9maWxlTnVtIjo0LCJsb2dMZXZlbCI6IldBUk5JTkciLCJ0b2tlbiI6Ik0/VGwqSndEZ2tOJkN4V2EiLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNyIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJTdGFuZGFyZCJ9 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-12-22 13:09:07.549 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-12-22 13:09:08.051 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-12-22 13:09:08.277 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-12-22 13:09:08.278 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-12-22 13:09:08.278 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-12-22 13:09:08.278 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-12-22 13:09:08.279 MainThread udi_interface INFO __init__:<module>: Loading OAuth module 2024-12-22 13:09:08.279 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-12-22 13:09:08.279 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.3.14 Starting... 2024-12-22 13:09:08.353 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.17 [ISY: 5.7.1, Slot: 4] 2024-12-22 13:09:08.353 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.38', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'} 2024-12-22 13:09:08.354 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2024-12-22 13:09:08.354 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: tplkasactl not found in database. 2024-12-22 13:09:08.354 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026837_4.cert key: 0021b9026837_4.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2024-12-22 13:09:08.354 MainThread udi_interface.interface INFO interface:addNode: Adding node Kasa Controller(tplkasactl) [None] 2024-12-22 13:09:08.355 MainThread udi_interface.interface INFO interface:setController: Using node "tplkasactl", driver "ST" for connection status. 2024-12-22 13:09:08.355 Interface udi_interface.interface INFO interface:_startMqtt: MQTT keepalive is 300 seconds. 2024-12-22 13:09:08.406 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with Reason code: Success 2024-12-22 13:09:08.407 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:68:37_4 - MID: 2 Result: MQTTErrorCode.MQTT_ERR_SUCCESS 2024-12-22 13:09:08.450 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Successfully for Message ID: 2. Reason codes: ['Granted QoS 0'] 2024-12-22 13:18:53.241 Thread-203 udi_interface ERROR udi_interface:write: Exception in thread 2024-12-22 13:18:53.241 Thread-203 udi_interface ERROR udi_interface:write: Thread-203 2024-12-22 13:18:53.242 Thread-203 udi_interface ERROR udi_interface:write: : 2024-12-22 13:18:53.242 Thread-203 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2024-12-22 13:18:53.242 Thread-203 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2024-12-22 13:18:53.242 Thread-203 udi_interface ERROR udi_interface:write: self.run() 2024-12-22 13:18:53.243 Thread-203 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2024-12-22 13:18:53.243 Thread-203 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2024-12-22 13:18:53.243 Thread-203 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026837_4/nodes/Controller.py", line 461, in handler_typed_data 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: self.add_manual_devices() 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026837_4/nodes/Controller.py", line 140, in add_manual_devices 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: res = future.result() 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 446, in result 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: return self.__get_result() 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: raise self._exception 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026837_4/nodes/Controller.py", line 147, in _add_manual_devices 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: LOGGER.info(f"Adding manual device {mdev['address']}") 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: KeyError 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: : 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: 'address'

And then I created a new account at Resideo.com and I still can't log in to the redirect in API configuration. error shown in attached clip.

I'm having similar problems. I've had a developer account for several years, but my old API did not work. I created a new API, got my Keys, and when I enter my Keys on the azure website and asked to log into Honeywell Home, I'm told my login is incorrect. I'm not sure if this is the same site I use to access my thermostats, but I can log into that site (https://www.mytotalconnectcomfort.com/portal) successfully. Do I need an account on a third site? Attempts to reset my password fail (as others have stated above), saying my email address is unrecognized in the system. I'll stay tuned here to see what develops.

Thanks Bob, that fixed the Daily and Month observations. The log is still showing the same parsing error for the yearly obs. Ken

I have installed the current DavisWeather poly (2.0.1), configured the settings, and loaded all the nodes. However, only the current conditions from the console are displayed. None of the observations data is being filled in. I queried the server with https://api.weatherlink.com/v1/NoaaExt.json?user=<my Station ID>&pass=<my password>&apiToken=<my token> and that returns ALL the data, including Daily, Month, and Yearly (But maybe not enough data to parse?). My configuration parameters were copied directly from the node configuration and pasted into the URL. Why is it not populating on the admin console? My station is a Vantage Pro 2. I don't have a solar radiation sensor. I've attached the first part of the log, but the rest is just repetition of the parse error. I also attached a sanitized response to the API call. DavisWeather Debug Log.txt JSON Message.txt

I just upgraded to EISY and Kasa is one of the first node servers I have installed, although I had WeatherLink running on Raspberry Pi earlier. I have been having similar problems as above with the HS300 power strip, with the admin console showing Kasa connected, but no nodes appeared. I have Iox 5.7.1, Kasa 3.1.4, PG3x 3.2..16, udx ?.? (don't know where to find that one). I finally installed the Dev packages, reinstalled Kasa node server, restarted everything, and the power strip appeared in the admin console, so now it is working fine. Thanks for all the background and answered queries above.

I'm not really concerned with the status of the relay because I am using it in momentary mode 'C' with the logic. I have it displayed because that is the icon that seems to control the door. Although I'm using momentary mode 'C', the relay status seems to toggle On after I touch the status icon, and the door does not operate. Sometimes a second touch of the status will operate the door and toggle the relay status. This is just not repeatable or reliable. I'll try your suggestion on mode B and maybe a single press on the status will work. I'm old school: the only thing I find reliable is hard wired and old fashioned relays. Thanks for listening.

I am using Orchestrated Mobilinc on my iPad & iPhone. There appear to be two apps called Mobilinc, so perhaps that adds to the problems. I know I am confused. The I/O linc relay is configured for momentary to work with my hard wired buttons. The Garage Door Status Icon on both the iPad & iPhone is labeled as a status device only. There is no option there for control, and touching it does nothing. When I use something like a mini remote to control it everything is OK. When I use one of the wired buttons (which are used 80% of the time) it's all out of sync.

I use an Insteon 2450 I/O Linc to control my garage door via the UDI ISY994i and Orchestrated Mobilinc on iPhone and iPad. There are two icons on the Dashboard or Favorites page, one for Garage Door-Relay and one for Garage Door-Status. These stay in sync when the door is controlled by any of the Insteon devices such as the mini remote. The problem arises when I activate the door with any of the wired momentary buttons connected directly to the door controller. The Garage Door-Status correctly indicates the door position via the I/O Linc, but the Garage Door-relay is out of sync because it was never activated. So now one icon indicates the door is closed and the other says it is open. I could get rid of or hide the relay icon, but that is the only one that actually controls the door, as the status is just that; only status. I've read many of the posts regarding the garage door control but can't find any that address this issue. There must be others with this problem as almost all doors have a wired momentary button to open/close the door. Can anyone suggest a way using a program or variable to keep this in sync? My open/close sensor is a micro-switch mounted near the bottom of the door, so it indicates anytime the door is NOT closed, which could effect any programming timing. I'm open to any suggestions. Thanks

Thanks for the suggestions, but I am not having any luck upgrading to 4.7.5 or 5.0.16. I either get the error that my UI is not compatible with installed admin console version or "Upgrade Failed :Failed uploading file (reported written size is invalid)". I'm using the v.5.0.16C Admin Console. I have the latest Java (C:\Program Files (x86)\Java\jre1.8.0_241\bin\javaw.exe). That is the only thing that shows up in the java console Java tab. I have no idea what else to add there. My Admin Console Run target is: C:\ProgramData\Oracle\Java\javapath\javaws.exe -localfile -J-Djnlp.application.href=http://isy.universal-devices.com/994i/4.6.2/admin.jnlp "C:\Users\Ken\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\48\719ee830-7b8308c8" Where or how can I download the user interface that is compatible with firmware 4.7.3. My UI is currently 4.6.2. Firmware and UI need to be the same version and they are NOT. I don't know why. I am assuming that Admin Console and UI terms are synonymous. I want to upgrade to firmware 4.7.5 first. Please read my original post before replying and answer those questions if you can. Thanks - this is very frustrating.

I am unable to update from 4.7.3 to 4.7.5 as available in Admin console. (Automatic Upgrade) UI is at 4.6.2. Why didn't it update when I upgraded to 4.7.3? Automatic upgrade to 4.7.5 gives me the "Upgrade Failed :Failed uploading file (reported written size is invalid)" Is this due to the mismatched Firmware and UI? How do I update the UI to 4.7.3 so they match? Eventually I would like to upgrage to 5.0.16C the Prerequisites: Say - You must use the 5.0.9 Admin Console or greater to upgrade to this release (5.0.16). I don't have a 5.x.x Admin console. Are the instructions written in the incorrect order? I have downloaded the 5.0.16C zip file. How can I install this if I don't have the 5.x.x Admin console? Someone needs to make these upgrade instructions clear for various upgrade paths!

Thanks for confirming my suspicions, and I did realize the OP had a different scenario. Ken

I have several programs that are triggered by Insteon commands that then send an X10 command. This did not work well until I added a one second wait to the THEN section before issuing the X10 command. I may be way off, but I suspect there is interference between the Insteon and X10 power line signals. Simplified, it looks like this: If Control 'Car Remote.b' is switched on Then Wait 1 second Send X10 'A15/On (3)' I realize that your event sequence is different, but this could be an issue. Perhaps someone with more experience can comment on the timing, but it works for me.

Thanks for the heads up about the re-evaluation of the variable from the wait state. That clears up a mystery for me. As to the other questions, a system reboot got everything straightened out. I did receive a random "Leak repaired" e-mail, which was NOT preceded by a "Leak Detected" message which I can't explain. Status of the sensors on the main page was OK, but one of the variables did not reflect that status. I guess I don't understand how they can be different. Everything has been OK over the next 25+ hours. This event driven programming is new to me, although I'm familiar with several other languages.

First let me thank Rabbit for all the work and time he has put in on this programming. I have implemented two leak sensors including the January "FIX 2" and I have a couple of observations/questions for anyone using this technique. 1. Looking at the sensor status on the main page I see what I would expect: Dry = ON, Heartbeat = ON, and Wet = OFF . I assume Heartbeat = ON means heartbeat received. Does anyone know how often a heartbeat is sent? 2. On the Program Summary page both of my "Heartbeat Missed" programs are running 'Then' (for the last 4 days). Should these run all the time? 3.I'm far from accomplished on the ISY programming technique, and I'm shaky on how the variables interact with the programs, even after reading the explanations of them, but I can't see a way to exit the "Sensorname" - Heartbeat Missed program. After the 25 hour wait, the HB variable is set to 0 which is just the opposite of what I would expect given my current heartbeat status of "ON". Then it looks like it enters a continuous 12 hour repeat loop with no exit! Maybe I need to read up on the effect of the "Control" command. Can anyone help clarify any of this?

Thanks for the responses. I'll keep tuned to the UDI development and hope to see native support soon!