Screw Loose Dan

Do you know if you changed the HTTPS port as well? Might try going to https://<isyIP>/admin.jnlp (might get a certificate error, you should be able to get past it). That won't fix the problem, but might get you access to the admin portal.

Ahh...it's all coming together. Thank you. I had been focused on the documentation (and code) instead of looking at the examples. <doh> Speaking of the documentation, in the usage notes for MQTT commands, it appears to list the function names from the code and not the actual commands. Which led to some confusion on my part working that out (looking at the code quickly cleared it up in that case). For instance, the usage notes list: DoRestart: restart the console I took that to mean "DoRestart" was the message/command that needed to be sent, but the actual command that needs to be sent is "restart". DoRestart appears to be be what the function is in the code. Might help the next guy to make that clearer. FYI - I've been trying to figure out a way to clear the error notification via mqtt. I often look at the logs via ssh'ing into the RPi and would like to be able to clear the error from issuing an mqtt command after looking at them. Is that obvious too?? ?

Wouldn't mind in the least! In fact, I'm sure it will make it easier for me when upgrades happen. Perhaps link to my Github page for instructions? I've been doing some other projects with MQTT, but just getting around to getting Sonoff sensors to display on the console. I have my two consoles connected to a management broker and all that appears to be working (view/clear errors from either console, etc). And, I can get the softconsole subscribed to the tele topic, but not sure how to config to parses the json. Perhaps it's obvious and I'm just looking at it wrong? This would be what some of my sensor topics looks like: garage/wemos/tele/SENSOR {"Time":"2019-02-19T22:24:36","BME280":{"Temperature":54.2,"Humidity":40.1,"Pressure":1029.6},"PressureUnit":"hPa","TempUnit":"F"} bedroom/wemos/tele/SENSOR {"Time":"2019-02-19T22:24:43","AM2301":{"Temperature":65.5,"Humidity":45.4},"TempUnit":"F"} Any help pointing me in the right direction would be appreciated.

I gave a bit of thought and played around making my screens dim. While I am using MQTT now for other things, I didn't think it made a lot of sense for this particular application. I ended up cobbling together an alert script, lightsensor.py (heavily based on the networkhealth.py) and I am using the TSL2561 light sensors (here on Adafruit, cheaper else where). Currently I have the interval set at 5 seconds and been happy using it that way for the past ~month. If anyone is interested, the code and some instructions are here. @kck - If you want to play around with this, I have a couple spare sensors, I'd gladly send one you way. Hope you enjoyed your time with the penguins!

I received a Ring security system for Christmas (wouldn't have asked for it). The complete lack of integration between the Security and Doorbell products is astounding. They use the same app on my phone, but in the most awkward way possible. I've had the doorbell a couple if years and I like it. The security system, I'm not sold on yet. Apparently Ring doesn't publish their API, except to their "Partners". I have seen that there are some python libraries for Ring products, this one looks like it might be good as a starting point for a Polyglot NS, but no security system support from what I can tell (beyond basic hardware health). There is a Node.js API (the guy put it together after getting blown off by Ring on twitter) that seems well put together. And seems like there's a chance it will work with the security systems. Apparently the API's for the doorbell products and the security systems are a bit different. Best I can tell, the doorbells use rest and the Security system is primarily web sockets. This is all pretty far out of reach for myself. I'm learning as I go, but I'm a long way from putting all that together. But, I'd be a tester! ?

Yeah, don't expend any energy on this. I don't think the package that was trying to use python2 was even needed, it just broke the install of the node server in Polyglot. I manually uninstalled the offending package (with python temporarily set to python2) and have everything working at the moment. In another thread I'm asking that developer if the python2 package is even needed. I don't use any ZWave sensors (yet), so I'm not sure how they would appear in the softconsole, but I presumed as regular ISY devices. Did you upgrade to the latest version, Kevin just released it this morning. Tap the screen rapidly 5 consecutive times to get to the maintenance screen, then Select Version -> Download release (this will take a bit, it's downloading the code, mine takes a few minutes) -> Return -> Exit/Restart -> Restart Console.

@chrisb5 - Glad that worked out. You asked earlier about making a screen to view sensors, did you make progress with that? I don't bother having my leak sensors (or door sensors) on a normal screen, but rather use alarms for them. This gives the advantage of an instant visual clue something is wrong (none of my leak sensors should ever be wet!). Something like this in a file named alertLeaksDRC (again name doesn't matter, just include in config.txt): [Alerts] [[Leak Sensor1]] Type = NodeChange Node = LeakSnsr1-AqBelow-Wet Test = NE Value = 0 Invoke = LeakSnsr1 [LeakSnsr1] type = Alert BackgroundColor = white MessageBack = red CharColor = black Message = Leak Sensor, 1, Got Wet, Under Aqrm CharSize = 30, 30, 30,40 DeferTime = 2 minute BlinkTime = 1 KeyColor = maroon I have separate alert files for different types of alarms/sensors. Just makes things easier for administration.

Chris - I missed your questions. My setup, this information is in auth.cfg (along with the ISY info): [APIXU] type = WeatherProvider apikey = <myAPIkey> Then in a file named weathsources-drc.cfg (name it whatever, just include it on config.txt): [CV] type = APIXU location = 19426 And them my TimeTemp: [TimeTemp] type= TimeTemp label = 'Collegeville', location = CV TimeFormat = "%-l:%M %p %a %b %-d", ConditionFields = Sky,Temp,Humidity, ConditionFormat = "{d[0]} {d[1]:.0f}° {d[2]}%", ForecastDays = 4 FcstLayout = 2ColHoriz ForecastFields = Day,Sky,High,Low ForecastFormat = "{d[0]}","{d[1]}","{d[2]:.0f}°/{d[3]:.0f}°" ClockSize = 60 LocationSize = 0 CondSize = 50, FcstSize = 25, CmdKeyCol = blue BackgroundColor = black CharColor = lightgray Don't know if that's all best practice, but it works for me.

A quick attempt to try that and it failed (ImportError: No module named configobj). I'm guessing you are calling a subprocess. I'm guessing I'd be chasing that for a while... No big deal, I'd rather not spend time trying to figure out how to make softconsole work while running with an older version of python. I'll see what I can do on the other program. And, Pi zero's are cheap... Thanks! Enjoy your trip!

Kevin - In the install scripts you set up: update-alternatives --install /usr/bin/python python /usr/bin/python3.5 2 update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1 And you mention: I'm trying to run a Polyglot node server Presence-Poly, which installs (via apt) an application "python-bluez". This application won't install/run without python2.7 set as the desired alternative. Will that cause an issue for the softconsole?

That gives me a lot of ideas and thoughts on what to start playing with!! My initial thought is to connect a an ambient light sensor to a GPIO pin on the RPi that is running Polyglot. There is a Polyglot GPIO node server already and I *think* they expose an MQTT service as well...hmmm. Lots to play with. Thanks!!

I just downloaded and started using the latest release. So far no issues. A thought for a feature request...I recently purchased a Google Home Hub display. It amazes me with it's screen dimming. It has an ambient light sensor and gets extremely dim in a dark room, but is still readable. And, obviously it gets brighter as needed. As I type all that out, it doesn't come across as nearly astounding as it actually is, it's really quite remarkable. Google did there homework. One of the thing I've struggled with on the softconsole is finding a sweet spot for the dim settings., especially for the bedroom unit. Having an ambient light sensor would be awesome, but I realize that might open a whole other can of worms. Instead, perhaps a time based feature for dimming? So in addition to DimLevel/BrightLevel, also a DimLevelLate/BrightLevelLate as well as two variables to set the time to use the additional Dim/Bright levels (LateStart/LateEnd). I know, easy for me to suggest, probably not as easy to implement. ? If you have any suggestions on what to look at, I could perhaps poke around. Anyway, you mentioned you would be travelling out of country for a few weeks. Enjoy your trip! Safe travels.

You guys talking about SSL certificate errors, reminded me we had some of this conversation before. I did get it to work (with a trusted "trusted" cert), but ultimately found the softconsole was not very useful. Let me know you you make out.

I installed the new Beta about 30 minutes ago, and not a single "ISY reported and immediately cleared error" has shown up in the softconsole logs. They were sporadic (best I could tell), but usually appear every 5-15 minutes. So, I believe it's resolved. Thanks!

Ah yes, I had missed that EVictory was having similar errors. Sorry about that. I just switched to the Beta and my initial test shows much less logging of errors. I do see lots of this, but haven't looked to see what the issue might be on the ISY/Polyglot side of things: 01-06-19 00:31:21 Sev: 4 ISY reported and immediately cleared error for node: n001_t198772770918 () (seq:-99/50) 01-06-19 00:31:24 Sev: 4 ISY reported and immediately cleared error for node: n002_controller () (seq:-99/123) 01-06-19 00:31:24 Sev: 4 ISY reported and immediately cleared error for node: n002_a407b6bccac1 () (seq:-99/125) 01-06-19 00:31:25 Sev: 4 ISY reported and immediately cleared error for node: n003_controller () (seq:-99/127) 01-06-19 00:31:25 Sev: 4 ISY reported and immediately cleared error for node: n003_d_0 () (seq:-99/132) 01-06-19 00:31:26 Sev: 4 ISY reported and immediately cleared error for node: n003_d_2 () (seq:-99/135) 01-06-19 00:31:26 Sev: 4 ISY reported and immediately cleared error for node: n003_d_3 () (seq:-99/138) 01-06-19 00:31:27 Sev: 4 ISY reported and immediately cleared error for node: n003_d_4 () (seq:-99/146) Regarding the query on battery devices, I concur comm issues are rarely seen with battery devices, but it just stumbled upon it last week. As long as it's a fire and forget (like the 3 AM query), not a big deal at all. Just didn't want a tight loop or anything. Thanks again!

FYI - This sounds like a good idea (I currently use a program to do this for my garage door opener), but the thought I had when I read this was regarding battery devices. Do you handle them differently? Battery devices (motion detectors, leak sensors, door contact sensors, etc) won't respond to a query normally. Might not matter, just thought I'd mention.

I recently upgraded to ISY firmware 5.0.14 (it was fairly painless for me) so I could play with node servers/Polyglot. Today, I finally got around to updating my softconsole to the latest version. I checked the softconsole logs after the upgrade and I realized things had run a muck... I've been ignoring the error notification dot for so long now, I probably should have looked sooner as it's been filling my logs. Anyway, this is a sample of the errors I'm seeing: 01-05-19 15:07:12 Sev: 4 Problem with processing node: Ecobee Controller Address: n001_controller Pnode: n001_controller 128/true/'unknown' 01-05-19 15:07:13 Sev: 4 Problem with processing node: Ecobee - Thermostat Address: n001_t198772770918 Pnode: n001_t198772770918 128/true/'unknown' 01-05-19 15:07:13 Sev: 4 Problem with processing node: Presence Controller Address: n002_controller Pnode: n002_controller 128/true/'unknown' 01-05-19 15:07:13 Sev: 4 Problem with processing node: GS9 Address: n002_a407b6bccac1 Pnode: n002_controller 0/true/'unknown' 01-05-19 15:07:13 Sev: 4 Problem with processing node: AVRemote Address: n003_controller Pnode: n003_controller 128/true/'unknown' 01-05-19 15:07:21 Sev: 4 ISY Extra info in event: ST/Status/1/n001_controller/NoneOrderedDict([('fmtName', 'NodeServer Online')]) 01-05-19 15:07:21 Sev: 4 ISY reported and immediately cleared error for node: n001_controller () (seq:-99/9) 01-05-19 15:07:23 Sev: 4 ISY Extra info in event: GV8/**GV8**/1/n001_t198772770918/NoneOrderedDict([('fmtName', 'Connected')]) 01-05-19 15:07:23 Sev: 4 ISY Extra info in event: GV7/**GV7**/0/n001_t198772770918/NoneOrderedDict([('fmtName', 'Follow Me')]) 01-05-19 15:07:23 Sev: 4 ISY Extra info in event: GV6/**GV6**/1/n001_t198772770918/NoneOrderedDict([('fmtName', 'Smart Home-Away')]) 01-05-19 15:07:23 Sev: 4 ISY Extra info in event: GV5/**GV5**/60/n001_t198772770918/NoneOrderedDict([('fmtName', 'Dehumidification Setpoint')]) 01-05-19 15:07:27 Sev: 4 ISY Extra info in event: GV0/**GV0**/0/n003_d_3/NoneOrderedDict([('fmtName', 'Status')]) 01-05-19 15:07:27 Sev: 4 ISY Extra info in event: ST/Status/1/n003_d_3/NoneOrderedDict([('fmtName', 'Chromecast Online')]) 01-05-19 15:07:27 Sev: 4 ISY reported and immediately cleared error for node: n003_d_3 () (seq:-99/136) 01-05-19 15:07:27 Sev: 4 ISY Extra info in event: GV2/**GV2**/0/n003_d_4/NoneOrderedDict([('fmtName', 'Current App')]) 01-05-19 15:07:27 Sev: 4 ISY Extra info in event: SVOL/**SVOL**/41/n003_d_4/NoneOrderedDict([('fmtName', 'Volume')]) This is a small sample of the errors, they repeat as these nodes get updated quite frequently. Probably won't mean much if you aren't using Polyglot, but I'm using the Ecobee, AVRemote (for Chromecast devices), and Presence-Poly node servers. Have you started playing with ISY firmware 5 at all yet? Any interest in supporting it? Let me know if I can help provide more information.

On my TimeTemp screen, I use: LocationSize = 0, This eliminates it from displaying any location.

May it have something to do with another alert triggering while this Away alert is triggered? I just ran an errand and this is the typical soft console log of me coming home: 11-03-18 16:05:28 Sev: 1 Status change for Bay1-Sensor(24 2E A3 1) to 0 11-03-18 16:05:28 Sev: 2 Node alert fired: Garage Door1: NodeChange Alert (Armed) Trigger: Node 24 2E A3 1 status EQ 0 delayed 50 seconds IsTrue: True Invoke: Screen:GarageDoor1<screens.alertscreen.AlertsScreenDesc object at 0x73158690> 11-03-18 16:06:06 Sev: 1 Status change for Bay1-Sensor(24 2E A3 1) to 255 11-03-18 16:06:06 Sev: 2 Node alert fired: Garage Door1: NodeChange Alert (Delayed) Trigger: Node 24 2E A3 1 status EQ 0 delayed 50 seconds IsTrue: False Invoke: Screen:GarageDoor1<screens.alertscreen.AlertsScreenDesc object at 0x73158690> 11-03-18 16:06:27 Sev: 1 Status change for GarageHouseDoor-Sensor(2B 11 81 1) to 255 11-03-18 16:06:32 Sev: 1 Status change for GarageHouseDoor-Sensor(2B 11 81 1) to 0 11-03-18 16:09:07 Sev: 3 Alert screen AwayAlert cause cleared Here's one of the examples with the Anomolous alert: 11-01-18 19:39:24 Sev: 1 Status change for Bay1-Sensor(24 2E A3 1) to 0 11-01-18 19:39:24 Sev: 2 Node alert fired: Garage Door1: NodeChange Alert (Armed) Trigger: Node 24 2E A3 1 status EQ 0 delayed 50 seconds IsTrue: True Invoke: Screen:GarageDoor1<screens.alertscreen.AlertsScreenDesc object at 0x73158690> 11-01-18 19:40:14 Sev: 2 Alert event firedGarage Door1: NodeChange Alert (Delayed) Trigger: Node 24 2E A3 1 status EQ 0 delayed 50 seconds IsTrue: True Invoke: Screen:GarageDoor1<screens.alertscreen.AlertsScreenDesc object at 0x73158690> 11-01-18 19:40:14 Sev: 3 Alert screen AwayAlert deferring 11-01-18 19:41:17 Sev: 1 Status change for Bay1-Sensor(24 2E A3 1) to 255 11-01-18 19:41:17 Sev: 2 Node alert fired: Garage Door1: NodeChange Alert (Active) Trigger: Node 24 2E A3 1 status EQ 0 delayed 50 seconds IsTrue: False Invoke: Screen:GarageDoor1<screens.alertscreen.AlertsScreenDesc object at 0x73158690> 11-01-18 19:41:17 Sev: 3 Alert screen GarageDoor1 cause cleared 11-01-18 19:41:23 Sev: 2 Actual weather fetch for 19426(0) WU count: 95 11-01-18 19:41:50 Sev: 1 Status change for GarageHouseDoor-Sensor(2B 11 81 1) to 255 11-01-18 19:41:55 Sev: 1 Status change for GarageHouseDoor-Sensor(2B 11 81 1) to 0 11-01-18 19:42:14 Sev: 2 Alert event firedAway Alert: VarChange Alert (Armed) Trigger: Variable ISY:State:Cell_Home EQ 0 delayed 0 seconds IsTrue: False Invoke: Screen:AwayAlert<screens.alertscreen.AlertsScreenDesc object at 0x73158ed0> 11-01-18 19:42:14 Sev: 4 Anomolous VarChangeTrigger firing as task: Away Alert: VarChange Alert (Fired) Trigger: Variable ISY:State:Cell_Home EQ 0 delayed 0 seconds IsTrue: False Invoke: Screen:AwayAlert<screens.alertscreen.AlertsScreenDesc object at 0x73158ed0> One difference that caught my attention was the three times I've noticed this alert, the log entry "Alert screen AwayAlert deferring" always appears. While I see that at other times in the log, I don't see it very often. But, it's always present with the "Anomolous" message. Also, all three times the Anomolous message appeared, there happened to be a weather fetch in the mix.

Kevin - Your explanation initially seemed very likely. However I reviewed some of my logs, I'm not sure that's what's happening. Although, since ISY doesn't seem to log variable changes it's a bit hard to confirm. The condition has only happened 3 times since I installed the current version, so it's not happening very frequently and not at all a big deal. Just a curiosity. I use Tasker on my cell phone to update a variable on ISY based on location (via a php script on my home server). So, I was thinking it is entirely possible that it rapidly toggles a few times as I don't have any sort of delay or wait (or error checking) built into the process. However, I looked at my web server logs (since that's how my cell phone actually pushes the variable update) and it appears the phone app/Tasker is only making one call to change the variable when I've seen the log in the soft console logs. If there are multiple rapid variable changes happening, I'm not sure how. Not sure if it's helpful, but I should have also included the only other pertinent log entry on the soft console, which always happens at the same time as the Anomolous log entry. I have my logging set to "1", so I also see: Sev: 2 Alert event firedAway Alert: VarChange Alert (Armed) Trigger: Variable ISY:State:Cell_Home EQ 0 delayed 0 seconds IsTrue: False Invoke: Screen:AwayAlert<screens.alertscreen.AlertsScreenDesc object at 0x73158ed0> Like I said, not a big deal at all. Just a curiosity.

Kevin - I've gotten a couple of these errors in the logs. I haven't had much time to look into them, but any idea what they might mean? Sev: 4 Anomolous VarChangeTrigger firing as task: Away Alert: VarChange Alert (Fired) Trigger: Variable ISY:State:Cell_Home EQ 0 delayed 0 seconds IsTrue: False Invoke: Screen:AwayAlert<screens.alertscreen.AlertsScreenDesc object at 0x73158ed0> I never noticed this alert prior to the latest update. Any insights?

Thanks for the fix! I pulled it down a few hours ago and haven't had any errors since.

So, I've been playing around with the new weather provider, APIXU. Being fairly far out in the suburbs of Philadelphia, they don't seem to have many close stations. The temperature reported by APIXU for my zip code is usually ~2° cooler than what WU and my own outdoor thermometers display. I suspect this is because the actual location they are reporting for is a several miles north/west of my actual location. For all of WU's flaws, there were several folks in my neighborhood with PWS's, so it always seemed to have a good idea of what the local weather was doing. I did see on the Weather Underground API retirement announcement that they are indicating: I'll probably just learn to deal with the new weather service (2° is really not that significant for me). Perhaps if I get motivated I'll look at some other services...but that's not likely.

Certainly seems like your program gets triggered everytime the temp changes, even if it's below 80F. Personally I think I would have two programs set (two different) variables depending on the temperature. One program/variable for temps =>94F and one for <=80F. And, also have two different programs to control the outlet based on the state variables. I'm not an expert at this, but something like (probably need to add something to check after reboots): If temperature <= 80F Then stateVar_lowTemp = 1 Else stateVar_lowTemp = 0 If temperature => 94F Then stateVar_HighTemp = 1 Else stateVar_HighTemp = 0 If stateVar_lowTemp = 1 Then Set 'Outlet-AC' Fast Off Send Notification Else If stateVar_HighTemp = 1 Then Set 'Outlet-AC' Fast On Send Notification Else

So, I had looked at my ISY logs previously and didn't see anything there. I had presumed it was everything in the stream, as they log quite a bit. However, I looked at my programs...and that led to an "ah-ha!" moment. I run a program that updates a variable ISY_Uptime_Counter_hours, as one might imagine, hourly. I display this on a keyscreen (along with a bunch of other variables). I only have one idle screen (TimeTemp), which does not show this variable. And, I'm fairly certain the majority of the times I was seeing the error message I was not interacting with the softconsole and it was on the idle/dim screen (TimeTemp). To confirm all this, I initially removed that section from my variable screen, and sure enough the next hour no error message. To further confirm, I made a variable (Count_tmp) and another program that would update the variable every minute. I added the Count_tmp variable to my variable screen, and sure enough: 10-08-18 14:20:19 Sev: 4 Unexpected ISY event to screen: TimeTemp00 10-08-18 14:21:20 Sev: 4 Unexpected ISY event to screen: TimeTemp00 10-08-18 14:22:20 Sev: 4 Unexpected ISY event to screen: TimeTemp00 10-08-18 14:23:20 Sev: 4 Unexpected ISY event to screen: TimeTemp00 10-08-18 14:24:20 Sev: 4 Unexpected ISY event to screen: TimeTemp00 Not sure if this is the same issue that is occuring for you , but figured I'd pass it along. This is probably more information than you need, but if you want to reproduce it... This is a snippet from my variable config: [[Uptime]] type = VARKEY Var = ISY:Int:ISY_Uptime_Counter_hours Appearance = 0:48 red 'ISY Uptime $ hours',49:168 yellow 'ISY Uptime $ hours',169:17520 green 'ISY Uptime $ hours' [[Count-tmp]] type = VARKEY Var = ISY:Int:Count_tmp Appearance = 0:48 red 'ISY Uptime $ mins',49:168 yellow 'ISY Uptime $ mins',169:17520 green 'ISY Uptime $ mins' And this is my program to update the Count_tmp variable: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 1 minute $Count_tmp = 0 $Count_tmp Init To 0 Run Program 'Count-tmp' (Else Path) Else Wait 1 minute $Count_tmp += 1 $Count_tmp Init To $Count_tmp Run Program 'Count-tmp' (Else Path) My uptime program is identical, except different variable and only runs once an hour. With no If condition it kicks off at startup and continuously runs (mostly in a wait state). Hope it helps! At least I know it's really not an issue for me. Thanks again!