apostolakisl

Yes, and often times that ability to be interrupted is a useful tool. If you intend to have a wait or repeat always execute to completion, you need to have a separate programs for trigger and execution. If whatever you want Then Run then program 2 If blank Then disable program 1 do something wait do something wati etc. enable program 1 I use interruptible waits all the time as a hysteresis type mechanism. My dryer has a wrinkle protector that turns it on every few minutes. And using the notation option in an ISY program you save yourself confusion when a year or two or whatever later you can't remember. The notes included below are in the program, not added by me to this post. This sort of explanation in your programs is invaluable. Master Drier Copy - [ID 0163][Parent 00F7] If 'WebControl8 / Input8' Status is 0 Then Wait 5 minutes Enable Program 'Master Drier' Else - No Actions - (To add one, press 'Action') Input 8 is 1 when drier off. When air vent flapper opens input becomes 0. If the drier is on for 5 continuous minutes, master drier is enabled. At this point, the next time the flap closes (or in other words when it shuts off), it will send a notification and disable itself. It will not send a notification again until it the drier has run for 5 continuous minutes. Master Drier - [ID 00C6][Parent 00F7][Not Enabled][Run At Startup] If 'WebControl8 / Input8' Status is 1 Then Send Notification to 'lou text' content 'Master Dryer Done' Wait 1 second Disable Program 'Master Drier' Else - No Actions - (To add one, press 'Action')

You could pay to have small runs of the hardware made, but you still need to flash them with firmware that you don't have.

2476d or 2477d? I do not recall ever having a 2477d fail, but the earlier 2476d's did. I don't have any 2476d's left anymore as I replaced everything with dual band quite a few years ago. I probably had about a dozen in a box of "failed" 2476d's out of maybe 50-60 I had bought. I replaced caps on them and maybe 8 of them came back to working normal. Some were not truly failed, but rather buzzed funny, took forever to boot when powered up, and/or periodically would hang-up and need to be rebooted.

Capacitors are like 90% of what ever fails with Insteon. I had a bunch of the 2476d's that were dead and replaced caps on them and almost all of them came back to life. So if capacitor replacement is in your wheel house, just replace them. Likely to get most of your devices working again.

@JaviI tried your new widget for turning switches on/off/slider. I applied it to a scene and instead of all the devices turning on/off together, they are staggered. I guess the widget just isn't meant for scenes?

If soldering is in your comfort zone, might just pull the relay and test it independently.

I did a package update from the AC. Now none of my PG2 or PG3 nodes will run. They all say "not running". If I try to run them, they just don't do anything, still "not running". This is every single node on both pg2 and 3. I tried multiple reboots of individual nodes, PG2, PG3, ISY, and the entire polisy. I put in a ticket, but I'm hoping someone can give me a quick fix. Here is an example log from one of the nodes. 2022-08-28 17:25:41,345 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2022-08-28 17:25:41,351 Command udi_interface.interface INFO interface:stop: Disconnecting from MQTT... localhost:1888 2022-08-28 17:25:41,352 Command udi_interface.interface INFO interface:_disconnect: MQTT Graceful disconnection. 2022-08-28 17:27:26,528 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-08-28 17:27:36,651 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.47 Starting... 2022-08-28 17:27:36,756 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.0.62 [ISY: 5.3.3, Slot: 7] 2022-08-28 17:27:36,759 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.9', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'} 2022-08-28 17:27:36,762 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-08-28 17:27:36,863 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-08-28 17:27:36,864 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:38:63_7 - MID: 1 Result: 0 2022-08-28 17:27:36,872 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2022-08-28 17:27:36,884 MainThread udi_interface.interface INFO interface:addNode: Adding node Push(controller) [None] 2022-08-28 17:27:36,886 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2022-08-28 17:27:36,910 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-08-28 17:27:37,426 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ST to 1 UOM 25 2022-08-28 17:27:37,715 Thread-1 udi_interface.interface INFO interface:addNode: Adding node hello(hellolo) [None] 2022-08-28 17:27:37,720 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Office Alarming(officealarming) [None] 2022-08-28 17:27:37,725 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Cadiz Alarming(cadizalarminng) [None] 2022-08-28 17:27:43,905 Thread-3 udi_interface INFO push-poly:start: Started Push Node Server 2022-08-28 17:27:43,907 Thread-3 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2022-08-28 17:27:51,594 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h3>Enter your Pushover credentials:</h3>\n\n<pre><code>Key Value\n\napi_key aslkti34cexample9faspff9bs\nuser_key 11lkj3an4kfother8s089exmpl90\n</code></pre>\n\n<h3>Enter things:</h3>\n\n<pre><code>Key Value\n\nFront Door you can leave this blank\nGarage Door\nEtc\n</code></pre>\n\n<p>The node address is derived from the first 12 characters and last 2 characters of the Key therefore each key needs to be unique.</p>\n\n<p>Be sure to save changes and restart the Node server.</p>\n'} 2022-08-28 17:27:51,745 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2022-08-28 17:27:52,394 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2022-08-28 17:33:15,216 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for Push(controller) 2022-08-28 17:33:21,530 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for hello(hellolo) 2022-08-28 17:33:29,111 MQTT udi_interface.interface ERROR interface:_message: error No valid API calls provided 2022-08-28 17:33:29,112 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'message' {"set":[]} 2022-08-28 17:33:41,586 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ST to 1 UOM 25 2022-08-28 17:40:27,232 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for Push(controller) 2022-08-28 17:40:27,385 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ST to 1 UOM 25 2022-08-28 17:40:27,829 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for hello(hellolo) 2022-08-28 17:40:27,908 MQTT udi_interface.interface ERROR interface:_message: error No valid API calls provided 2022-08-28 17:40:27,909 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'message' {"set":[]} 2022-08-28 17:45:48,111 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for Office Alarming(officealarming) 2022-08-28 17:45:48,213 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for Cadiz Alarming(cadizalarminng) 2022-08-28 17:45:48,228 MQTT udi_interface.interface ERROR interface:_message: error No valid API calls provided 2022-08-28 17:45:48,229 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'message' {"set":[]} 2022-08-28 17:45:48,268 MQTT udi_interface.interface ERROR interface:_message: error No valid API calls provided 2022-08-28 17:45:48,269 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'message' {"set":[]} 2022-08-28 18:15:07,361 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2022-08-28 18:15:07,362 Command udi_interface.interface INFO interface:stop: Disconnecting from MQTT... localhost:1888 2022-08-28 18:15:07,363 Command udi_interface.interface INFO interface:_disconnect: MQTT Graceful disconnection.

I seem to have this working thanks to @Panda88 and @bpwwer The Tesla node server, with long poll set to 86400 and short poll set to 86399 (not sure if short poll is needed) lets the car sleep but you can send commands to it or query it when needed. The Emporia Vue node along with the device itself lets you monitor current real-time watt draw. There is a test version of the app that has this functional. Then I wrote a series of programs which seem to be doing the trick. I also have the programs in a folder which is linked to my phone geofence such that the programs only run when I am at the charging location in question. I don't want to have Tesla start and stop charging based on electricity usage at a location where the Tesla is not charging. It seems like a lot of programs, but I couldn't see a way to do it in fewer. I want the car to stop charging if power usage is above 14kw and then to resume when it drops below 9kw. I have the car set to charge at 3kw. I also don't want it to stop charging if there is just a quick spike from say a motor start, so I have a delay of 5 seconds, it checks again and then shuts down the car charger if it is still high wattage. Also, the Emporia Vue wattage is a state value and it updates every 2 seconds, meaning it will trigger an if clause every 2 seconds since the value always changes. So I didn't want the program to send a "start" or "stop" command repeatedly every 2 seconds once it has already started or stopped. Not sure if that would be a problem, but it just seems like a bad idea. Tesla - [ID 005C][Parent 0094] Folder Conditions for 'Tesla' FOLDER RULE If 'GeoFence Office / LouS22' Occupied is True Then Allow the programs in this folder to run. Tesla Charge Start - [ID 0062][Parent 005C][Not Enabled] If 'emporia VUE test' Killowatts < 9.0000 kW Then Run Program 'Tesla Charge Start 2' (Then Path) Else - No Actions - (To add one, press 'Action') Tesla Charge Start 2 - [ID 0066][Parent 005C] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Disable Program 'Tesla Charge Start' Set 'Raymond / EV Charging Info' Charging Control Start Enable Program 'Tesla Charge Stop' Else - No Actions - (To add one, press 'Action') Tesla Charge Stop - [ID 0060][Parent 005C] If 'emporia VUE test' Killowatts > 14.0000 kW Then Run Program 'Tesla Charge Stop 2' (Then Path) Else - No Actions - (To add one, press 'Action') Tesla Charge Stop 2 - [ID 0064][Parent 005C] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Disable Program 'Tesla Charge Stop' Wait 5 seconds Run Program 'Tesla Charge Stop 3 always disabled' (If) Else - No Actions - (To add one, press 'Action') Tesla Charge Stop 3 always disabled - [ID 00D8][Parent 005C][Not Enabled] If 'emporia VUE test' Killowatts > 14.0000 kW Then Set 'Raymond / EV Charging Info' Charging Control Stop Enable Program 'Tesla Charge Start' Else Enable Program 'Tesla Charge Stop'

It 100% has to be either the transformer bleeding down or coming on weird. You can disconnect the 24vac and reconnect all day long and no probs, the thermostat boots up fine each time. It is only when power is cut to the transformer while it is running the thermostat, not when power is cut between the transformer and the thermostat. So, it seems the obviously solution is to open the circuit between the transformer and the switch upon power failure and delay the reconnection until the transformer has fully powered up. I found these 5 for $10 relays on ebay that are designed for cars where when 12v is applied, the relay will turn on after a user specified delay. The intention is that you start your car and then a few seconds later your electronics turn on. Assuming it is a power up problem, this would fix it. And it is dirt cheap. So I will give it a shot.

Already on the latest versions of IoP and PG. Not sure when I last updated the Polisy OS/libraries, probably a few months. I will go ahead and do that. However, Polisy did not crash nor did PG2/3. IoP was the only thing that crashed. Though, like I mentioned, it did not reconnect to the portal until I rebooted Polisy. Maybe I was impatient, but after waiting 5 or 10 minutes I figured it should have connected.

Thanks. Not sure I need support, I was just reporting an issue should UDI care to investigate. I didn't even know that UDI mobile was discontinued. Even though it is no longer listed in the google play store, it still transferred over when I bought my new phone a few weeks ago, so it was just there. I don't believe that the configuration step in setting up geo fencing has anything to do with UDI mobile. I forget now, but I believe the configuration step just sets up the node between portal and ISY. UDI mobile then updates the node whenever you cross in or out of a geofence. I believe you can use other apps and have them send to a unique url for entry/exit. But this brings up another point. If UDI Mobile is no longer to be used, then why is it still there on the portal?

UDI mobile is not an app to control ISY. It is a geofence app that integrates with ISY. It is the only app listed for geo-fencing. I suppose I could use some other geo-fence app and put in the url for in/out, but I assume since UDI Mobile is still the only one listed, that it is preferred. Also, the crash occurred during the "configuration", I do not believe that running the configuration tool has any connection to UDI Mobile. UDI Mobile, while being installed on my phone, had never been opened. It is a new phone that transferred automatically but I had yet to open it and it had no association yet with my ISY.

I was integrating UDI mobile/occupancy and this resulted in a full out crash of IoP. I had previously had my ISY linked to UDI mobile occupancy, but I guess that all got lost when I migrated to IoP. As I tried to add phones and locations, it said I need to configure. Upon opening the occupancy configuration tab and then asking it to "configure connection", IoP crashed. This is the first time I believe I have ever seen ISY crash. It self-rebooted, but did not sync with the portal upon reboot. The portal said "offline" even though I could log into the AC over my LAN. I proceeded then to reboot the entirety of Polisy from the PG2 GUI. Upon reboot this time, ISY did sync with the portal, but the node servers needed to be individually rebooted on both PG2 and 3 before they would sync with ISY, the nodes were all unpopulated prior. Rebooting Polisy seems to usually require the individual nodes to be rebooted, perhaps because they boot faster than ISY and then don't sync, I don't know. At this point I was able to configure occupancy. Anyway, something wasn't right.

UD has already designed a whole new PLM. I wonder if they would sell that minus the Insteon chip and let people swap out a chip of their own.

Sorry for your issues. I have not had any issues with these 10 thermostats except for power outage reboot issue. They aren't the fanciest thermostats in the world, but that is fine because ISY does everything, they fulfill my needs completely and have done so now for maybe 10 years. I also got them for a song, I think maybe $30/ea?. I am also able to lock them out so only people I've allowed access from the app can adjust them. I can't tell you how often people would set the AC and then put it on "hold" and the AC would just run for days with no one in the building. I don't need a smart thermostat, I need a thermostat that ISY can control, that is about it. I wonder if they had made these thermostats with a battery backup if that would have prevented this issue. My office thermostats have 2 AA batteries for that purpose.

This is a church, they would never spend that kind of money just to keep electronics from needing to be reset. Plus it is 3 phase. Tesla doesn't do 3 phase. It isn't that big of deal to not have power, it is just having things come back online all by themselves when power is restored.

I just looked at the wiring diagram, and there is just a single 24vac power input and that is used to power the unit as well as to switch 24vac back to the hvac unit on the various heat/coo/fan/etc conductors. Obviously, the electronics don't run on 24vac, so perhaps I could look at the board and figure out where it is converting 24vac to low level dc voltage and splice in a different power supply (ie 5vdc) there might be possible, but tricky.

Two buildings, one with 4 units and one with 6. They are just regular 5 ton split-system heat-pumps each running independently. The only thing that makes these guys different than a standard residential unit is that the compressors are 3 phase. It is not the way I would have designed a big commercial building, but it is what it is and changing it would be quite the challenge. The upside is that they use standard residential thermostats, so lots of HA options available. I suppose I could just switch them all over to one of the other brands that now work with ISY because we have node servers. When I installed these, it was Insteon only.

2 different buildings. Some of the units are all located in the same equipment room, so I could put those together on the same UPS.

It is either how it died or how it powered on. Every time we have a power outage, at least half of them need the secret button pressed. When they boot up, the screen stays blank. You would assume they are completely dead, except you can sort of communicate with them from ISY . . .you can query and set the temp for example, but it won't report temp and it won't turn the units on. If you power them down by cutting the 24v (pop them off the wall bracket) and then pop them back, they always work fine. So it must have something to do with partial voltages during the transformer power up/down. To the best of my knowledge, the secret button is not a factory reset but rather a memory dump? I don't know, but you don't lose your settings, so it can't be a factory reset.

Crossed my mind, but 10 of them adds up and then I have to deal with 10 batteries going bad every few years. And I don't know about you, but those stupid small UPS units tend to cause me more problems than they solve.

Yes, but I think this would be the one I would want. https://smile.amazon.com/dp/B07CGCL5W6/ref=sspa_dk_detail_1?pd_rd_i=B07CGCL5W6&pd_rd_w=FNRoV&content-id=amzn1.sym.4d0fffec-3aba-4480-8fad-c6bd8f7f6b41&pf_rd_p=4d0fffec-3aba-4480-8fad-c6bd8f7f6b41&pf_rd_r=3EWZ336PTWAYJ9MVP74A&pd_rd_wg=RBdI0&pd_rd_r=3a7daec9-4002-4b91-b680-29231654d2a4&s=hi&sp_csd=d2lkZ2V0TmFtZT1zcF9kZXRhaWxfdGhlbWF0aWM&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEyRFhMWlE5R1ZDTEM3JmVuY3J5cHRlZElkPUEwNDQ0NjA3MTIzRlpTVTZLS05COSZlbmNyeXB0ZWRBZElkPUEwOTE2MDk4MVMxQzE1UkgzODA3NiZ3aWRnZXROYW1lPXNwX2RldGFpbF90aGVtYXRpYyZhY3Rpb249Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU&th=1

Maybe this https://www.ebay.com/itm/175357094229?_trkparms=amclksrc%3DITM%26aid%3D1110002%26algo%3DSPLICE.SOI%26ao%3D1%26asc%3D241433%26meid%3D67e10adba1314f67925d679946c861dc%26pid%3D101196%26rk%3D4%26rkt%3D12%26sd%3D175304946248%26itm%3D175357094229%26pmt%3D1%26noa%3D0%26pg%3D2047675%26algv%3DPromotedSellersOtherItemsV2WithMLRv3%26brand%3DUnbranded&_trksid=p2047675.c101196.m2219&amdata=cksum%3A17535709422967e10adba1314f67925d679946c861dc|enc%3AAQAHAAABELB59iZaq6L1SxCGLGoiBqHdpPz8nqKyKuGL1QIa0H%2B47SsVltB%2Bw0rtaIhMqUN4rojJhp1wcQEr%2BAzUZqgK5SfqMmP1JjWjR%2B6il7Kc4Ode7h%2B8R0xDI1KNJWhgq%2FJ9auZYMiCmiHZpxLlEU3rzPq39ndKJXwoF%2FPjpzw%2BbIC5ggWXc5x240AGAFTLBp1U2LppX2uTi%2BpHvGx1XJNF5uG4cQIgvyfp95u4TNgqUHtl9OE4ORbFOaAfb7cIPT9w4mAyI7mdsNVd3M2nTuED6gzvaCXJSsRJX6LjuHtMcqLcBO%2FEishRmfkWIyujm1MjR9SEPctZ2aa2vXvCVXI4kLcISZgCBrYaP63PzWU4MJhBW|ampid%3APL_CLK|clp%3A2047675 Looks like I could use 120vac line to power the unit and use the relay to interrupt 24vac output from the transformer. Should cut the 24vac almost immediately when the line voltage goes out, and if I understand correctly, when line voltage returns, it can be set to delay the relay closure for an adjustable amount of time. EDIT: never mind, I would still need a 12vdc transformer and thus it would not shut down right away since those tend to bleed down over a few seconds. Of course the shut down may not be the problem, it may be the restart.

I would need to figure a way to shut down immediately (easy part) but have a delay for turning back on (hard part).

It just occurred to me, maybe the issue is that the power outage/restore doesn't result in the 24ac transformer giving a clean on/off. Maybe if I put a relay that kills the 24vac when power goes out and thus gives a clean on/off? Obviously, don't actually need the thermostat to stay working when power is out, just need it to reboot when power comes back on.