-
Posts
401 -
Joined
-
Last visited
Everything posted by JTsao
-
Enbrighten/GE/Jasco 26931 Motion Sensor / Switch Question
JTsao replied to JTsao's topic in Z-Wave - Series 700
FWIW I think I have a workaround for this device - The 26931 has two logical switch devices, in my case they are ZW010 On Off Switch and ZW010.1 On Off Switch - both control the lights in a manner where the most recent On or Off from either device will set the light state, even if the two switches are in different states - the ZW010 On Off Switch is associated with the physical on off buttons, whereas the ZW010.1 On Off Switch is not - therefore, I can use the "status" of the ZW010 On Off switch, in conjunction with some programs and a state variable to control the scene properly - the ZW010.1 On Off switch is in the scene, the ZW010 switch is not, but its status is checked to run a program to control the scene - the ZW010 motion sensor is also checked to control the scene I still don't understand why the IoP can't interpret the transition in the ZW010 on off switch as "switched on or off" so that programs will trigger -
Enbrighten/GE/Jasco 26931 Motion Sensor / Switch Question
JTsao replied to JTsao's topic in Z-Wave - Series 700
I have an Enbrighten switch (no motion sensor) in another location and it does trigger a program with the switched on condition but the 26931 definitely does not - this is causing a problem because the 26931 controls the actual load = floodlights for a scene containing two Insteon switches and the 26931 - turning the Insteon switches on correctly turns the scene on - including the. 26931 - turning the 26931 on manually will turn on the lights but the Insteon switches don’t turn on because the program won’t trigger - I don’t expect the zwave device to properly act as a scene controller in this capacity so I was doing things with a program to control the scene but apparently the program won’t trigger for some reason - although the IoP does see the proper state of the 26931 - so shouldn’t the IoP be able to detect the switched on transition? -
Can anyone explain why the following program never triggers when I manually press the ON button on an Enbrighten 26931 Motion Sensor/On/Off switch? If 'Kitchen / Devices / Kitchen Floodlight Sw ZW010' is switched On Then Send Notification to 'Jeff Text' content 'Kitchen Switch ON' Else - No Actions - (To add one, press 'Action') The switch ON in the If statement never triggers, however, the status in the IoP is correct - anyone? Is this a bug?
-
No worries - every time I have encountered a problem like this (although the possibility of having to factory reset scares me), you have fixed it quickly - thanks!
-
All - thanks - fixed after an email from Michel instructing me to do another round of updates via SSH (although, I tried that on my own earlier - I suspect something in the earlier update caused a problem and I think UDI fixed it in the following update)
-
The admin console says "ISY not found" Thanks - I'll try that when I get home I'm only running PG2 node servers - I think that may have something to do with the port #, unless I'm mistaken I did that first thing - I am hopeful that there is a fix - I just updated via the web page this morning, not sure what happened...
-
also appears that all services are running: udx, pg3, polyglot, isy and I cannot seem to get the credentials to connect to the ISY under "settings->Polyglot Settings" as the red notice always appears even after I have saved the proper credentials (and I have also tried admin/admin)
-
6/10/2022, 09:00:21 [polyglot] info: MyQ(11): n011_cg08464cd743 GV0 set sucessfully to 2550 : UOM 58 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] error: MQTTS: clientError: polyglot_frontend-uVWTm read ECONNRESET 6/10/2022, 09:00:30 [polyglot] info: Caught SIGTERM/SIGINT Shutting down. 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: Rachio(4): Processing command: connected 6/10/2022, 09:00:30 [polyglot] info: HueEmulator(2): Processing command: connected 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: HarmonyHub(3): Processing command: connected 6/10/2022, 09:00:30 [polyglot] info: WeatherBit(6): Processing command: connected 6/10/2022, 09:00:30 [polyglot] info: Ecobee(9): Processing command: connected 6/10/2022, 09:00:30 [polyglot] info: Virtual(7): Processing command: connected 6/10/2022, 09:00:30 [polyglot] info: Push(12): Processing command: connected 6/10/2022, 09:00:30 [polyglot] info: Rachio(4): Node server Disconnected. 6/10/2022, 09:00:30 [polyglot] info: HueEmulator(2): Node server Disconnected. 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MQTTS: Client Disconnected: 6/10/2022, 09:00:30 [polyglot] info: MyQ(11): Processing command: connected 6/10/2022, 09:00:30 [polyglot] info: HarmonyHub(3): Node server Disconnected. 6/10/2022, 09:00:30 [polyglot] info: WeatherBit(6): Node server Disconnected. 6/10/2022, 09:00:30 [polyglot] info: Push(12): Node server Disconnected. 6/10/2022, 09:00:31 [polyglot] info: Ecobee(9): Node server Disconnected. 6/10/2022, 09:00:31 [polyglot] info: Virtual(7): Node server Disconnected. 6/10/2022, 09:00:31 [polyglot] info: EnvisaLink-DSC(1): Processing command: connected 6/10/2022, 09:00:31 [polyglot] info: iAquaLink(10): Processing command: connected 6/10/2022, 09:00:31 [polyglot] info: MyQ(11): Node server Disconnected. 6/10/2022, 09:00:31 [polyglot] info: iAquaLink(10): Node server Disconnected. 6/10/2022, 09:00:31 [polyglot] info: EnvisaLink-DSC(1): Node server Disconnected. 6/10/2022, 09:00:31 [polyglot] info: MQTT Client Services Stopping Gracefully. 6/10/2022, 09:01:42 [polyglot] info: Starting Polyglot.... 6/10/2022, 09:01:42 [polyglot] info: Settings: Polyglot Version 2.2.13 6/10/2022, 09:01:42 [polyglot] info: Settings: Retrieved config from database 6/10/2022, 09:01:42 [polyglot] info: Running in Polisy mode 6/10/2022, 09:01:42 [polyglot] info: Settings: Retrieved config overrides from .env and updated database 6/10/2022, 09:01:42 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883 6/10/2022, 09:01:43 [polyglot] info: MQTT Client Service: Started 6/10/2022, 09:01:43 [polyglot] info: HTTPS Interface Service: Started - Address: 0.0.0.0 Port: 443 6/10/2022, 09:01:43 [polyglot] info: MQTTS: polyglot authenticated successfully. 6/10/2022, 09:01:43 [polyglot] info: MQTTS: Client Connected: 6/10/2022, 09:01:43 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: connection exceeded max re-tries. Aborting. Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: EnvisaLink-DSC(1): NS getNodesFromISY RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 at new RequestError (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/errors.js:14:15) at Request.<anonymous> (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:46:31) at /snapshot/polyglot-v2/node_modules/request/request.js:185:22 at Request.emit (events.js:315:20) at Request.onRequestError (/snapshot/polyglot-v2/node_modules/request/request.js:881:8) at ClientRequest.emit (events.js:327:22) at Socket.socketErrorListener (_http_client.js:426:9) at Socket.emit (events.js:315:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 6/10/2022, 09:01:43 [polyglot] info: NS: Starting Local Node server EnvisaLink-DSC profile number 1 :: Version 2.1.7 6/10/2022, 09:01:43 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: connection exceeded max re-tries. Aborting. Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: iAquaLink(10): NS getNodesFromISY RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 at new RequestError (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/errors.js:14:15) at Request.<anonymous> (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:46:31) at /snapshot/polyglot-v2/node_modules/request/request.js:185:22 at Request.emit (events.js:315:20) at Request.onRequestError (/snapshot/polyglot-v2/node_modules/request/request.js:881:8) at ClientRequest.emit (events.js:327:22) at Socket.socketErrorListener (_http_client.js:426:9) at Socket.emit (events.js:315:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 6/10/2022, 09:01:43 [polyglot] info: NS: Starting Local Node server iAquaLink profile number 10 :: Version 1.0.7 6/10/2022, 09:01:43 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: connection exceeded max re-tries. Aborting. Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: ISY: RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:43 [polyglot] error: MyQ(11): NS getNodesFromISY RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 at new RequestError (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/errors.js:14:15) at Request.<anonymous> (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:46:31) at /snapshot/polyglot-v2/node_modules/request/request.js:185:22 at Request.emit (events.js:315:20) at Request.onRequestError (/snapshot/polyglot-v2/node_modules/request/request.js:881:8) at ClientRequest.emit (events.js:327:22) at Socket.socketErrorListener (_http_client.js:426:9) at Socket.emit (events.js:315:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 6/10/2022, 09:01:43 [polyglot] info: NS: Starting Local Node server MyQ profile number 11 :: Version 2.3.17 6/10/2022, 09:01:43 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:44 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:44 [polyglot] error: ISY: connection exceeded max re-tries. Aborting. Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:44 [polyglot] error: ISY: RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:44 [polyglot] error: Push(12): NS getNodesFromISY RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 at new RequestError (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/errors.js:14:15) at Request.<anonymous> (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:46:31) at /snapshot/polyglot-v2/node_modules/request/request.js:185:22 at Request.emit (events.js:315:20) at Request.onRequestError (/snapshot/polyglot-v2/node_modules/request/request.js:881:8) at ClientRequest.emit (events.js:327:22) at Socket.socketErrorListener (_http_client.js:426:9) at Socket.emit (events.js:315:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 6/10/2022, 09:01:44 [polyglot] info: NS: Starting Local Node server Push profile number 12 :: Version 1.0.6 6/10/2022, 09:01:44 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:44 [polyglot] error: ISY: connection failed. Retrying... Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:44 [polyglot] error: ISY: connection exceeded max re-tries. Aborting. Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:44 [polyglot] error: ISY: RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2022, 09:01:44 [polyglot] error: HueEmulator(2): NS getNodesFromISY RequestError: Error: connect ECONNREFUSED 127.0.0.1:8080 at new RequestError (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/errors.js:14:15) at Request.<anonymous> (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/snapshot/polyglot-v2/node_modules/request-promise-core/lib/plumbing.js:46:31) at /snapshot/polyglot-v2/node_modules/request/request.js:185:22 at Request.emit (events.js:315:20) at Request.onRequestError (/snapshot/polyglot-v2/node_modules/request/request.js:881:8) at ClientRequest.emit (events.js:327:22) at Socket.socketErrorListener (_http_client.js:426:9) at Socket.emit (events.js:315:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21)
-
I updated the Polisy via the web page this morning and I can tell that the ISY is not working, as certain events have taken place with no notification, and I cannot get to the admin console - I have rebooted the Polisy several times - also "Settings->Polisy Configuration" hangs indefinitely - have cleared Java cache, redownloaded admin console app, etc. but no success - any suggestions?
-
I have created a pushover account and can use the e-mail gateway to get my IoP messages to my iPhone in a timely fashion (Verizon e-mail to text has become very unreliable), but I was trying to use and understand the PG2 Pushover Node Server - I have not moved anything to PG3 yet because there is 1 node server not yet available under PG3 - anyways, I understand how to put in the api_key and user_key into the configuration - I have also added "home" into the configuration with no value - this has created a "home" under the Push arrow icon in the IoP main tab and "home" has a message button and drop down menu (and I can add program code to send a pushover message from the drop list) but when I run the program or push the message button - I never get the message - the node server log file says it is sending a message but nothing ever happens - I have read a lot of info. on this but this node server is not straightforward - can anyone assist on this?
-
It's disappointing whenever UDI removes features and refers users to a non-existent Node server for replacement. First IR, then WOL. In my opinion, native support of features like IR and WOL in IoP would be way better than having to research and manage a 3rd party plugin that can be problematic. I've been running several node servers for a couple of years and it seems that I always have to restart one or work around some kind of issue.
-
Does anyone know of an on-line site that can be used to create audio clips via text-to-speech messages for playback on this device? I discovered this: http://www.fromtexttospeech.com/ on some guys website discussing the Aeon Doorbell https://darwinsden.com/audio-clips-for-smart-home-automation-systems/ but the site doesn't work for me - the file is never accessible
-
The Ecolink Chime looks useful to me - I am going to buy one - thanks for the write-up
-
Thanks for the suggestions - I am going to start to investigate this as well as moving all of my node servers to PG3
-
OK this happened again - all email to text messages sent after 6:30PM or so did not show up until the next morning and they are out of sequence - hoping this problem fixes itself because there's really nothing I can do...
-
The reason that I use the Virtual node server is related to getting Harmony remote controls to trigger a program on the IoP - the ISY994 had IR input capability which doesn't exist on the IoP - the Harmony Companion remote has dedicated remote buttons for home automation that are somewhat limited in what they can control - I have to use the Hue Emulator node server on the Polisy to get the remote to turn lights on and off - but the Hue Emulator node server only really supports turning scenes on and off - this does not trigger programs, but if you put a Virtual button into the scene, then you can trigger a program from your Harmony remote - kind of a hassle to do something that was easy on the ISY - I really believe that UDI should add native IR support to the IoP via a USB IR receiver, but that is the subject of another discussion...
-
Is there a non-destructive way to move this from PG2 to PG3? If I delete and add to the same slot and create the same switches with the same numbers, will the IoP programs still require updating?
-
It's in the title - for some reason, my IoP programs that send me a text have not been doing so over the past couple of hours - I ran some programs manually and did not get any messages through - I am using the default server and emailing to #@vtext.com to convert messages to a text EDIT: This morning, messages from last night seem to be arriving, (although some are out of order) - about 12 hours late - not sure what happened, but only my phone (Verizon) was effected, my family (T-Mobile) was not
-
Has anyone tried the $27 Minoston MP21Z Z-Wave Plug?
JTsao replied to JTsao's topic in Z-Wave - Series 700
Good tip, setting parameter 1 to value=2 (1 Byte) turns off the LED -
Has anyone tried the $27 Minoston MP21Z Z-Wave Plug?
JTsao replied to JTsao's topic in Z-Wave - Series 700
I like them - ended up buying several and am using them mainly for controlling some lamps, plug in lights and fans - some are part of lighting scenes and work fine with Insteon equipment except for a small delay turning on/off - I like the fact that they are small and only cover 1 of 2 outlets - range is not an issue - I have them working in a few locations around the house - the only bad thing is they emit a blue light which is noticeable if it happens to be on in your bedroom at night -
Wow I just learned about the Bond Bridge - the thing I like about it is that it allows to use the native RF controllers that came with my ceiling fans (Casablanca and Minka Aire models) - that would allow for accurate control of 3 speeds. I was running Fanlincs and the speeds were always off. Over the years, the Fanlincs failed (5 of 6) and I ended up replacing them with an Insteon On/Off switch paired with a capacitor which left me with a single speed fan. (I have two switches wired in each room per fan, one for the light, one for the fan). I just installed an Enbrighten Z-Wave Fan Control in 1 location for $40 - but I could have purchased the Bond Bridge instead for $100 for 6 fans and started using all of the RF controls that I already have sitting in a box. Darn it. is it necessary to buy the Bond Bridge Pro? Or does the regular Bond Bridge suffice to control multiple RF ceiling fans?
-
I agree about preferring a hard button remote vs. the iPhone and would love to have a replacement for the ISY994 IR input. What happens when a USB keyboard is plugged into the Polisy? There is a USB device known as a Flirc, that converts learned IR commands into keystrokes. It has low cost and I can't imagine it being a stretch to get a Linux based microcomputer (the Polisy) to process keyboard entered commands. Any thoughts?
-
There is no IR on the ISY-Polisy (IoP). I was using IR on the ISY994 but now on IoP I am using only the dedicated home control buttons on Logitech Harmony companion remotes to control lighting and fans via the Hue Emulator Node server and the Virtual Node server. In my case, pressing a home control button turns on a virtual switch, which can cause a program to run. The switch has to be in a scene that is associated with the Hue Emulator (Notes->Spoken="1"). I am also using the UD Mobile app more in my house for controlling things.
-
I would agree that the USB stick is not as good as a PLM, but I have been staying with it since my switch to IoP and overall it seems OK - one thing that happened to me, that may or may not apply to others switching to IoP and trying the stick is that it seemed like the device links were not all what they should have been for a lot of Insteon devices after the IoP change and the restore PLM operation - After checking a lot of device links vs the ISY links and doing a lot of "restore device" operations, things improved (a time consuming task)
-
Updated and everything seems OK. Question - how do we know if the Polisy requires a re-boot after updating? I have been rebooting after updating in the past, but now with IoP running, I don't really want to reboot unless it is needed. Is it better to update via SSH + "sudo pkg update sudo pkg upgrade" vs. the web page? (because there is more feedback via the SSH terminal about the update vs. just a couple of beeps). If you type "pkg info | grep -i ISY" before and after the update and see that the ISY, PG3, Polyglot2 and udx versions have not changed, does that imply that each of those things does not have to be restarted?