Screw Loose Dan

You should be able to always download the admin console from http://your.isy.IP.address/admin..jnlp and run it.

The ISY is generally standalone and core functionality requires no internet connection - with a couple exceptions. If you use email, you might be using UD servers (or you can use any other email server). If you use the UD portal, for things like Google, Alexa/Amazon, or IFTTT, you would be using Universal Devices servers. But, the core functionality of controlling Insteon or Zwave devices does not require the Universal Devices servers. Was there a reason for your question?

Well, I'm not sure this counts as a battery device. A hybrid, I suppose. It does have a battery, but it's plugged in 99% of the time. The battery in this device is intended only as a backup (it only lasts ~4 hours). And, I have no issues making changes to the device, it writes my updates immediately. It just shows in the UI that's it's still "WRITING". Also, I'm not overly familiar with ZWave but I don't know of any way to put this device (or the other ZWave devices I have) into the equivalent of linking mode. I have excluded the device (that seems like the only way this device will go into a linking state?), reset the device, and then re-added the device. I also tried synchronizing the ZWave device. But, as I said, everything appears to work. Here's me updating the volume on endpoint #2 and doing a query 14 seconds later. Wed 12/09/2020 10:38:10 AM : [ZWAVE-TE ] [79/05] CC=0x79 cmd=0x05 [0000] ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:10 AM : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:10 AM : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[3B825B0E1909A301] ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-WAKEUP 14.002] Query device ZW014_002_1 Wed 12/09/2020 10:38:24 AM : [ZWAVE-TE ] [79/01] CC=0x79 cmd=0x01 [] ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[69E1398235CA2B98] ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-RX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-TX ] ... Wed 12/09/2020 10:38:25 AM : [ZWAVE-RD ] [010E00130E07600D020079021E25003D] REQ ZW_SEND_DATA Wed 12/09/2020 10:38:25 AM : [ZWAVE-TE ] [79/09] CC=0x79 cmd=0x09 [] ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[22B5218F19FA27A7] ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-RX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-TX ] ... Wed 12/09/2020 10:38:25 AM : [ZWAVE-RD ] [010E00130E07600D0200790A0025002F] REQ ZW_SEND_DATA Wed 12/09/2020 10:38:25 AM : [ZWAVE-TE ] [79/06] CC=0x79 cmd=0x06 [] ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:26 AM : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[FBAEBF3A8F2A6797] ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:26 AM : [ZWAVE-RX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:26 AM : [ZWAVE-TX ] ... Wed 12/09/2020 10:38:26 AM : [ZWAVE-RD ] [010F00130E08600D02007907001125002C] REQ ZW_SEND_DATA Wed 12/09/2020 10:38:26 AM : [D2D EVENT ] Event [ZW014_002_1] [SVOL] [0] uom=51 prec=0 Wed 12/09/2020 10:38:26 AM : [ ZW014_002_1] SVOL 0 (uom=51 prec=0)

I probably need to open a ticket as well with them regarding the siren. It all works, but regardless what I do it's constantly says it's writing to the device. It's the only device I have with this behavior, so I'm not sure if it's the device or something with the ISY.

I believe I was able to change the volume of the tamper alarm, including muting it. Your post prompted me to look into and try to figure it out as it's annoyed me on occasion. My initial testing shows that I was able to mute it. When I add it to ISY, I get a bunch of different devices listed. From what I could tell in this document, the tampering alarm is end point #2. So, I muted the volume on the 2nd device and it appears to mute the tampering alarm. See the attachment for what mine looks like (I'm on 5.3.0 firmware), but it I believe the the device you want to change the volume on will be like "ZWXXX_002_1". See if that works.

I presume the logs actually show the motion detection? You aren't just going by the light being turned on, correct?

I have both styles of leak sensors. I don't personally care if they reset or not on their own, but it did cause me a bit of confusion when I got the newer ones. I didn't read the instructions either.

While I don't have quite the redundancy Kevin has, I agree with his approach. For the most critical of things, I put them on an offsite server and also a backup USB drive. The offsite server is for any local catastrophes (ie. fire) and the USB drive is kept offline and only occasionally plugged in to make a new backup, so it covers the historical scenarios (ie. ransomware). One could pretty inexpensively get in a routine of using USB drives for backups, but it's typically a bit more manual process. Life happens. Hardware will fail in unexpected ways at unexpected times. With a NAS, it's very easy to put all your eggs in one basket and feel safe about it (it has built in redundancy!), but that's not wise. Any singular backup is but one tool in the tool chest. I'm still not completely comfortable running critical applications in virtual/abstract environments. With Home Assistant, they build and support the Docker images (even the VM is a bunch of Docker apps bundled together), so it makes me feel slightly better that the development team is so on board with it. And, so far I don't have HA doing anything critical (other than the UI), I'm keeping all the important routines on the ISY for now. But, I feel it is something to consider. As far as Synology hardware, I generally WAY over buy for what I actually need. I don't have a good measure or rule of thumb to tell you. I currently have a DS1515+ and a DS920+. The DS1515+ is 5+ years old I believe. The drives are starting to get bad sectors, so I'm in the progress of migrating to the DS920+. Both seem to have plenty of horsepower. Running VM's and certain Docker apps can chew through some memory, so that may be a desired upgrade.

I run my HA in a VM (VirtualBox) running on a Ubuntu server I have for other things. I also have a Synology NAS and have considered running the VM on it instead, but decided the Ubuntu server had more horsepower (not that HA takes much at all). Running in a VM, you get the complete HA OS, which works better for me. My first play with HA was a Docker on the Synology.

Yes, I agree the UI of Home Assistant makes a very good front end for the ISY. It's gotten the stamp of approval from a very non-technical significant other. I've also found their integrations to seemingly work in a much more consistent manner than the Polyglot integrations. I realize with any open source project, there's probably many variations and I have a pretty limited view. But, there's several things I can do with HA that I can't (easily) do with ISY. I haven't committed to the Polyglot/Polisy yet. I have run polyglot on a RPI and currently run it on a Ubuntu server. But, I haven't found it reliable nor useful enough that I would spend money for the Polisy (yet). But, several of the Home Assistant Integrations I immediately put to use and they seem relatively stable, so far. I had been figuring I would eventually need to buy a Polisy, but now I'm wondering if Home Assistant might be the solution I need.

The only one they sell any more is the 500 series. If you order from UD directly or Orchestrated Homes (both linked from the wiki), you'll get a 500.

I've been using Home Assistant for about a week now (and upgraded to 0.117 the other day), and I too am impressed. I haven't noticed any issue with dimmer devices. They just seem to work as expected. What issue are you experiencing?

Good job! I like this a lot and can think of a few use cases. I just installed and did some testing. It took ~3 seconds to do the backup and less then 60 seconds to restore (according to ISY Inventory NS, I have 188 nodes. Looking at the logs from the backup, it appears it attempted to restore 106 nodes). I like the idea of keeping things simple, makes sense. But, maybe a prefix exclusion, set as a configuration parameter, wouldn't be too hard? Also, looks like it's backing up and trying to restore my leak sensors: $ grep '2E 2 49 2' debug.log 2020-10-18 15:47:05,999 Controller polyinterface INFO backup:discover: Saving 2E 2 49 2/LeakSnsr3-BsmtLaundry-Wet value 0 2020-10-18 15:49:18,955 Controller polyinterface INFO backup:restore: Calling http://10.1.10.100/rest/nodes/2E 2 49 2/cmd/DOF Not sure how easy it would be to exclude, just pointing out a device type there would be no need for a restore. Another device I would personally like to exclude are the IO Links. They often seem to have trouble reporting correct values and in my testing, I changed the value of one with the restore. This isn't a problem with your code, it's a problem I always have (I generally work around it by programmaticly doing a device query first, which might work in this case as well, I just didn't think about it prior to doing the backup manually).

I had not heard that. I do use the micro's quite a bit (but, not as much as switches). Fortunately, I bought a whole bunch a couple years ago for a project that I never did, so I have spares for a while. I believe there are Z-Wave counterparts (like Aeotec's Nano Switch and Dimmer) that might suffice presuming you are using Z-Wave with your ISY, but IMO still less than ideal.

If all you need to do is turn on the humidifier, I would agree an On/Off plug-in module with a transformer is likely the best solution. The IOLinc is powerline only, meanwhile the current on/off modules are all rf/powerline, so it should have more reliable communication. The IOLinc would probably work fine and if you need the input, it's the way to go.

I've had ~19 devices in GH for a while, without issue. I just added five more (24 total) and didn't have any issues, yet. I hope they can address the issue you are experiencing.

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!