webminster

Thanks for confirming. This is starting to be a bit too frequent.

Can't log into the portal, and the Alexa skill is broken. What's happening now? -Alan

I got logged into the portal OK, but the Echo integration isn't working.

I can log into the Portal now, but the Web console and Alexa skill is currently broken.

Support came through as usual, was a surprising reason. The cool setpoint on my thermostat somehow got set to 0.5 degrees (glad it was on heating mode!) and that made something mad. Changed the cool setpoint over 40 and it started workin again. -Alan

Yeah. Not the first time there's been an Alexa glitch where it temporarily says it couldn't do something - but not for this long and this persistently. And yeah, the Web Access in the portal. Looks fine there. -Alan

It's an Insteon (Venstar) thermostat, same one I've used for years. Works fine on the local network with my Polisy. I see it in the Smart Home listing, and in the UDI Portal. Have also tried a device rediscovery, it's there but "not responding". I've made no changes before when it started last night out of the blue. I have a ticket open as well. I've just tried to delete device from Alexa devices, and from UDI Portal, re-add to Portal and rediscover Alexa... Still "thermostat isn't responding". I do note that the Portal web display does show the current correct readings for the thermostat. -Alan EDIT: Looked in the Android Alexa app at the thermostat. It has no status or values. Does have the very helpful message "There was a problem."

Since yesterday my Echo has started responding "thermostat not responding" to all commands. Light controls see to work, but not the thermostat. Haven't changed configurations anywhere, and the Polisy control on it locally is working fine. Device rediscovery didn't change anything. How can I fix this? -Alan

I've deleted and recreated the message content, made sure saved. I've deleted and recreated the program. And made sure saved. It all looks fine until I restart the admin console, then the program notify action shows [Entry 12]. So, yes.

Thanks for that pointer, that works great.

I added a state variable to my favorites. Additionally, set a couple of map values on it, to map a 1 to value On and some icon, and 0 to Off and another icon. When I enter UD Mobile (Favorites), all the normal nodes (devices, scenes, etc.) are refreshed with their current values. But the variable is not - it has the default (x) icon, and no value. If I touch on the favorite I see its current value (as mapped). Back to the favorites grid, the value and icon are correct. Can variable favorites be fixed to show the current value when favorites are viewed? -Alan

I do not have any 1011 icons on my devices.

I don't have any programs making network calls. -Alan

My issues with slow program execution has nothing to do with network resources; the programs issue insteon commands based on insteon event conditions.

I was redirected over here from a different thread... I see at least 1 second delays on mosty of my programs, and am wondering if that's just the way it is, or there's something to make things more responsive. I've seen programs seem to take a second, or a few seconds to turn a device on or off. I attach a log that showed a 1-second lag compared to a scene, for a motion sensor program. Looking at it I don't think there's a comm error in there that stops it from working, to me it just looks like a slow program. What is the reasonable expectation for program execution or response speed? -Alan ISY-Events-Log.v5.4.4__Sat 2022.06.18 11.10.47 AM.txt

Are there ways to improve the speed/responsiveness of programs on the Polisy/IoP? It's not just the MS program above (went back to direct links)... I've other programs that seem to also have oddly long delays, like a program to detect when I've turned off my kitchen cans and island lights, to automatically turn off undercabs (inconvenient switch)... sometimes take a couple of seconds to run. Don't think there's a way I could do that with a scene.

Thanks for the reply. Appreciate the information, I expected a smidge extra delay because of the intermediate step, I'm just a little surprised it added a noticeable delay to the processing. -Alan

Recently I decided to change a motion sensor scene to program control instead. So I unlinked my 2842-222 MS from a scene with two 2466S switches and wrote a dead simple program, when MS sensor switched on, set scene on. Since that change, the trigger seems sluggish, like I see the MS blink, but the lights may delay almost a second coming on. I did have variability in the reaction speed of the direct linked scene, but the program version seems pretty consistently slow. I attach a part of the event communication log I think is appropriate, with 31.84.0B the MS, and 1D 87 34 and 1D 89 B0 the switches. What sort of delay is "normal" to be seen in a program like this? Can anyone see anything instructive in the log? Thanks in advance. -Alan PS: IoP version is 5.4.4. ISY-Events-Log.v5.4.4__Sat 2022.06.18 11.10.47 AM.txt

OK. Wasn't sure how much more I could offer than comments in https://forum.universal-devices.com/topic/35912-get_devicespy-dysoninvalidauth/?do=findComment&comment=336238 This was for the TP02 device support.

That's what I did for post 2, and I just redid it and tested. I am getting a trigger and send from that program 2 every time the temperature changes (and still is greater than the limit). E.g., 87.0, 87.1, 87.2... For comparison: test temp high - [ID 0082][Parent 0001] If 'SensorPushNodeServer / Media Closet' Temperature >= 87.0°F Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') mediaclosetTempAlert - [ID 0084][Parent 0001] If Program 'test temp high' is True Then Send Notification to 'Default' content [Entry 12] Else - No Actions - (To add one, press 'Action') In contrast, the version where I set a state variable and watch that does work. I don't know if this is an IoP issue or what... -Alan

No, it wasn't hysteresis. It wasn't bobbling back and forth over the limit. It was monotonically increasing (87.0, 87.1, 87.2).

I guess also I can use one program with the "if status temperature" condition, and a second program watching the program state and mailing. It's too bad I can't use the node reference node.#.name though. EDIT: I guess I can't do this... seems like if the temperature changes the program state changes, and I get an alert. Assumed the "then" state would filter out each little change... bad assumption I guess.

This may be an FAQ, if so I apologize. I want a program that watches a node server value (temperature) and sends an alert if it goes too high. So I created a condition: If 'SensorPushNodeServer / Media Closet' Temperature >= 87°F This triggers every time the temperature changes over 87, like 87.1 and 87.2... I guess I can set a variable to 1 each time the status changes and have a second program watch that. But is there a more elegant way? Thanks. -Alan

I've created a couple of new custom email notifications since I migrated to IoP (running 5.4.4 now). I have a couple of programs like the below: test temp high - [ID 0082][Parent 0001] If 'SensorPushNodeServer / Media Closet' Temperature >= 87°F Then Send Notification to 'Default' content [Entry 12] Else - No Actions - (To add one, press 'Action') My question is the "Entry 12". If I go re-save the notification config, it'll start showing as "sensorpush temp" (as I named it)... until I restart the admin console, at which point it reverts to "Entry 12". This isn't happening to pre-migration entries. Is this a bug? Thanks for any ideas. -Alan

I had a version of this plugin installed from the Beta store. It says it's version is 3.3.3 [Beta], and it won't restart ("automatic update failed"). I don't see it anymore in the beta store, and in production store I see 3.3.1 only. Did this disappear on purpose?