Jump to content
AT&T to end email-to-text ×

chrisb5

Members
  • Posts

    41
  • Joined

  • Last visited

Everything posted by chrisb5

  1. Any way to leverage the ISY to log the temperature/humidity/other sensor values the ISY is already retrieving from the sensor - and logging it somewhere so I can generate reports or graphs of the values? Thanks!
  2. Thanks. I have a LARGE variety of equipment in the house that come under the various categories I've seen as noise-generators or signal-suckers; multiple refrigerators, freezer, various fluorescent, CFL and LED lights, several UPSes, lots of computers and TVs, fans, portable HVAC units, electric blankets/space heaters, etc. spread across 3 panels and around 50 active breakers. Way too many floating around to just unplug one at a time and test -not to mention the communications doesn't fail all the time so that doesn't give me a good means of validation either. Considering the XPPF but with only a 5A limit it wouldn't be a good fit for my larger appliances. And would really like to find an affordable meter I could use to actually determine WHICH devices are really problems and hopefully measure a difference when filtered. -Chris
  3. Since Filterlinc's are rather hard to come by (and I've seen references to them melting sometimes - and at least one I have apparently stopped working) anyone have references to a reliable/affordable plug-in replacement to help filter out the various noise sources in the house? I have lots of questionable items running that "may" be generating noise - but no way to prove it currently. I also still have a fair amount of old single-mode Insteon devices (powerline traffic only) that "sometimes" fail to respond to commands. I found these Greenwave filters- but can't find specs on them to see if they would help Insteon/powerline traffic - or consider that powerline traffic "noise" and block it? https://greenwavefilters.com/product/greenwave-dirty-electricity-filter/ Would also like to find a inexpensive-as-feasible meter to let me know how bad my power noise is and determine what steps I take actually help (and how much)... Same vendor sells a spiffy looking meter for US$130 but I have no experience with these folks and their web page specs look more like hype than science? Opinions on their meter (or recommendations for other/better -but not outrageously expensive for a homeowner) meters? https://greenwavefilters.com/product/emi-meter/ Thanks in advance! -Chris
  4. Just tried it out - looks great! Thanks!!!
  5. Any way to get the page (room) name/title to show on the console so we can tell which room we're looking at? Thanks! Sent from my SM-G935V using Tapatalk
  6. Having fun now LOL. Any way to print the name of the current screen ON the current screen? So you can tell what screen/room you're looking at?
  7. Key color question; For the basic Insteon (or other ISY supported types) is it possible to configure the standard buttons for each to be something simple like Green if ON and Red if OFF? Either the background color for each button - or if not that just the text (label) color perhaps? Or even the outline color - default seems to be outline in white=ON outline in black=OFF.. ?
  8. @Screw Loose Dan Thanks! I was just reading through the docs and sample configs trying to figure that out - but I agree the alert seems to be a better representation for those sensors. I setup my leak sensors and smoke/CO2 sensors based on your examples and they seem to be working. I even had one of my sensors tripped and got to see what the alert screen looks like - very nice! Not sure how to pull the temp from my AEOTEC sensors though (for display in my screens). All the values show up in the ISY console (i.e. it knows how to parse them and I can use the sensor values in conditions in programs via built-in pulldowns) but (and I"m running v4.7.3) I don't see any option to set a variable to the value from a sensor/device. Also I see that I'm getting lots of the "ISY reported and immediately cleared error for node:" messages in my logs... so I suspect I may also need to select the new beta release to get around that - though I don't know if the SSL ignore-certificate-errors fix got applied there yet?
  9. Dan - Thanks!! That works beautifully!
  10. Sorry; but I am not figuring out the weather format config files for a simple APIXU feed? I'd like to change my HomeScreen to a TimeTemp screen and I tried copying one of your examples that looked as close/simple as possible... but the console won't start (keeps failing with an error saying: Sev: 5 Error accessing ScreenParams:store['store']KeyError('store',) -- and then reboots over and over. Most of the samples utilize MQTT which I'm not using... In my main config.txt I added the following: [APIXU] type = WeatherProvider apikey = <myAPIkey> [SpringfieldVA] type = APIXU location = 'Springfield, VA' refresh = 59 And then the screen config file I tried was the following: [Springfield] type= TimeTemp label = Springfield, VA location = 'Springfield, VA' TimeFormat = "%-l:%M:%S%P %a %b %-d", ConditionFields = Sky,Temp, WindDir, WindMPH ConditionFormat = "{d[0]} {d[1]:.0f}","{d[2]} @ {d[3]}" FcstLayout = 2ColHoriz FcstIcon = True CondIcon = True ForecastDays = 10 SkipDays = 0 ForecastFields = Day,Sky,High,Low,WindDir,WindSpd ForecastFormat = "{d[0]} {d[1]}","{d[2]}/{d[3]} {d[4]}@{d[5]}" ClockSize = 35 LocationSize = 0 CondSize = 25, 25,15 FcstSize = 20, 15 CmdKeyCol = blue Which was a blatant copy of one of the sample configs with just the label/location changed. I added the Springfield screen name to the list of screens and set it as the HomeScreenName in the main config.txt and things went badly... ?
  11. Re: the ambient light/console dimming questions; you might consider some of the AEOTEC multisensors if you have any ZWave capability. I have several of them and the ISY (I have the ZWave module on my ISY) discovers them natively and reports (in addition to temp/humidity/motion) the "luminance" level and UV light levels. The sensors can be battery or USB powered and work well on the ISY as triggers for events/programs/etc. They're just under US$50 last I checked. I use them for motion sensing around the house and keeping track of temperatures in several rooms; and even have some rules that know not to turn on devices when it's "already lit" (based on the luminance levels).
  12. Some quick newbie-to-the-console questions: Never dealt with the weather services before and I understand some are going away/unreliable; what do you recommend for a quick/easy free service so I can get a basic weather summary on my console? I'd like to show status of my (Insteon) smoke and CO sensor on the/a screen. They obviously don't warrant a click to turn on/off; I would just like a button or some labelled indicator showing a good/bad or red/green status. Doable? Same request for some Insteon leak sensors. I have several AEOTEC (ZWave) multisensors that report temp/humidity/light & UV level/motion/etc and would like to show at least the temperature (+humidity) of some of these sensors on some screen(s)... How might I go about that? Thanks - and enjoy the penguins!
  13. Your code fix above did the trick!! I have a functional button on the display now... Will need to learn the config files now so I can have some real fun BTW personally I prefer your (temporary) solution of ignoring certificate issues with SSL certs... I can't imagine many people going to the expense of paying for a commercially signed/trusted server certificate for their home automation controller... I'm sure almost everyone would opt for a self-signed certificate - and the steps to add that self-signed cert to a local trust store on the Pi could be done - but not sure if the effort is worth it. I've had to script such code in bash and perl but never python so not sure I'd be much help there either but if you choose to go that route I will assist in any way I can. *I do use https on my ISY and have for years; true initial connections are slower but it hasn't caused me any problems. And since I manage my own firewall and lots of other servers (and use the Agave app to control my stuff from my phone) having https and decent passwords on my ISY made opening a proxy up in my firewall for access from the outside (for Agave) worthwhile. -Chris B
  14. It is a self signed certificate so unless the client trusts it I would expect verification to fail I guess. Is there a library name I can research to see about adding it to the trust store that library uses? Sent from my SM-G935V using Tapatalk
  15. Here's the latest file in that (.HistoryBuffer) directory. Looks like it's creating one of these files every minute... Thanks again! 113-01-06-19 20%3A12%3A29
  16. Also having trouble grasping the config structures; I'd like a home display with temperature, smoke sensor, and some leak sensor statuses... Then buttons perhaps buttons for each room (roughly grouped by floor if there's enough screen space) that each take me to a secondary screen specific to that room...? I see how you define ISY devices in each cfg file but not clear how you define buttons that take you to another screen? Thanks though! Getting excited about the app!
  17. The display is the official Raspberry PI 3 7" Touchscreen Display. I selected the 7pi (or whatever that option was) in the list of display choices in the config screen. The screen is showing ok; I selected the default setup and I can click through and select the date/time screen, maintenance screen, etc. My ISY isn't setup to allow non https access - and my address = line in auth.cfg specifies https:// plus the IP address and :PORT (I use a non standard port). At the moment I do have a Dell USB keyboard hooked up to the Pi as well; not sure if that was the source of the keydown/up events?
  18. Thanks! Using the desktop distro made all the difference. Install ran all the way through and I did finally get a console display... though I think there is an issue communicating with my ISY? I'm currently running v4.7.3 (https) though I'm hoping to make the jump to v5 shortly to experiment with polyglot. The one switch I named in the setup shows up with a big "X" across it on the console and I see ISY related errors in the log file - though I do seem to be able to turn the switch off and on via the touch screen - though I'm not sure how and it's not clear from the display if it's on or off? Anyway the log is showing lot of messages like these: 01-06-19 17:34:07 Sev: 3 ISY: WS stream thread 1 setup 01-06-19 17:34:07 Sev: 4 ISY WS stream 1 closed: None:None 01-06-19 17:34:07 Sev: 4 ISY QH Thread 1 exiting 01-06-19 17:34:08 Sev: 4 ISY Failed Thread Restart 01-06-19 17:34:08 Sev: 3 Starting helper thread (1) for: TouchHandler 01-06-19 17:34:08 Sev: 4 Thread for: ISY is dead 01-06-19 17:34:08 Sev: 3 Restarting helper thread (2) for: ISY 01-06-19 17:34:08 Sev: 5 ISY Unexpected error on WS stream: ISYUnknown 01-06-19 17:34:08 Sev: 3 ISY: WS stream thread 2 setup 01-06-19 17:34:08 Sev: 3 ISY Delaying Hub restart for probable network reset: 90 seconds 01-06-19 17:35:38 Sev: 4 ISY WS stream 2 closed: None:None 01-06-19 17:35:38 Sev: 4 ISY QH Thread 2 exiting 01-06-19 17:35:39 Sev: 4 ISY Failed Thread Restart 01-06-19 17:35:41 Sev: 4 Thread for: ISY is dead 01-06-19 17:35:41 Sev: 3 Restarting helper thread (3) for: ISY 01-06-19 17:35:41 Sev: 5 ISY Unexpected error on WS stream: ISYUnknown 01-06-19 17:35:41 Sev: 3 ISY: WS stream thread 3 setup 01-06-19 17:35:41 Sev: 3 ISY Delaying Hub restart for probable network reset: 90 seconds 01-06-19 17:35:56 Sev: 3 Entering Maintenance Screen: Maintenance 01-06-19 17:36:00 Sev: 3 Entering Log Screen 01-06-19 17:36:36 Sev: 5 Unknown main event <Event(2-KeyDown {'mod': 0, 'scancode': 28, 'key': 13, 'unicode': '\r'})> 01-06-19 17:36:36 Sev: 5 Unknown main event <Event(3-KeyUp {'mod': 0, 'scancode': 28, 'key': 13})> 01-06-19 17:36:39 Sev: 5 Unknown main event <Event(2-KeyDown {'mod': 0, 'scancode': 1, 'key': 27, 'unicode': '\x1b'})> 01-06-19 17:36:39 Sev: 5 Unknown main event <Event(3-KeyUp {'mod': 0, 'scancode': 1, 'key': 27})> 01-06-19 17:36:50 Sev: 3 Entering Maintenance Screen: Maintenance 01-06-19 17:36:50 Sev: 3 Entering Maintenance Screen: Flags0 01-06-19 17:37:04 Sev: 3 Debug flag ISYdbg = True 01-06-19 17:37:11 Sev: 3 Entering Maintenance Screen: Flags1 01-06-19 17:37:11 Sev: 4 ISY WS stream 3 closed: None:None 01-06-19 17:37:11 Sev: 4 ISY QH Thread 3 exiting 01-06-19 17:37:12 Sev: 4 ISY Failed Thread Restart 01-06-19 17:37:14 Sev: 4 Thread for: ISY is dead 01-06-19 17:37:14 Sev: 3 Restarting helper thread (4) for: ISY 01-06-19 17:37:14 Sev: 5 ISY Unexpected error on WS stream: ISYUnknown 01-06-19 17:37:14 Sev: 3 ISY: WS stream thread 4 setup 01-06-19 17:37:14 Sev: 3 ISY Delaying Hub restart for probable network reset: 90 seconds 01-06-19 17:37:15 Sev: 3 Entering Maintenance Screen: Maintenance 01-06-19 17:37:19 Sev: 3 Entering Log Screen 01-06-19 17:37:40 Sev: 5 Unknown main event <Event(2-KeyDown {'mod': 0, 'scancode': 28, 'key': 13, 'unicode': '\r'})> 01-06-19 17:37:41 Sev: 5 Unknown main event <Event(3-KeyUp {'mod': 0, 'scancode': 28, 'key': 13})> 01-06-19 17:37:41 Sev: 5 Unknown main event <Event(2-KeyDown {'mod': 0, 'scancode': 54, 'key': 303, 'unicode': ''})> 01-06-19 17:37:41 Sev: 5 Unknown main event <Event(3-KeyUp {'mod': 0, 'scancode': 54, 'key': 303})> 01-06-19 17:37:45 Sev: 3 Entering Maintenance Screen: Maintenance 01-06-19 17:37:49 Sev: 3 Exiting Maintenance Screen 01-06-19 17:38:45 Sev: 4 ISY WS stream 4 closed: None:None 01-06-19 17:38:45 Sev: 4 ISY QH Thread 4 exiting 01-06-19 17:38:45 Sev: 4 ISY Failed Thread Restart 01-06-19 17:38:47 Sev: 4 Thread for: ISY is dead 01-06-19 17:38:47 Sev: 3 Restarting helper thread (5) for: ISY 01-06-19 17:38:48 Sev: 5 ISY Unexpected error on WS stream: ISYUnknown 01-06-19 17:38:48 Sev: 3 ISY: WS stream thread 5 setup 01-06-19 17:38:48 Sev: 3 ISY Delaying Hub restart for probable network reset: 90 seconds 01-06-19 17:40:18 Sev: 4 ISY WS stream 5 closed: None:None 01-06-19 17:40:18 Sev: 4 ISY QH Thread 5 exiting 01-06-19 17:40:19 Sev: 4 ISY Failed Thread Restart 01-06-19 17:40:21 Sev: 4 Thread for: ISY is dead
  19. Got a couple RPIs for Christmas so I'm trying to build a new version of the console on a RPI 3B with the Raspberry 7" LCD touchscreen. I started with the raspbian stretch lite image on an 8Gb microSD. On the initial run of /boot/pisetup.sh I got the following errors: 2019-01-06 00:00:18 (10.9 MB/s) - ‘lxterminal.conf’ saved [1365/1365] Traceback (most recent call last): File "getsetupinfo.py", line 2, in <module> from future.builtins.misc import input ImportError: No module named 'future' Proceed? I went on and after the reboot ran the /home/pi/installconsole.sh script. This bombed badly; apparently the "pip" package was not present (not on that distro?). Also I see an error about cannot remove tmp: *** Setupconsole *** Created: Console Created: consolestable Created: consolebeta Created: consolerem --2019-01-06 00:12:27-- https://github.com/kevinkahn/softconsole/archive/currentrelease.tar.gz Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112 Connecting to github.com (github.com)|192.30.253.113|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/kevinkahn/softconsole/tar.gz/currentrelease [following] --2019-01-06 00:12:27-- https://codeload.github.com/kevinkahn/softconsole/tar.gz/currentrelease Resolving codeload.github.com (codeload.github.com)... 192.30.253.121, 192.30.253.120 Connecting to codeload.github.com (codeload.github.com)|192.30.253.121|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-gzip] Saving to: ‘currentrelease.tar.gz’ 0K .......... .......... .......... .......... .......... 1.17M 50K .......... .......... .......... .......... .......... 2.06M 100K .......... .......... .......... .......... .......... 1.92M 150K .......... .......... .......... .......... .......... 2.29M 200K .......... .......... .......... .......... .......... 2.39M 250K .......... .......... .......... .......... .......... 2.39M 300K .... 2.14M=0.2s 2019-01-06 00:12:27 (1.92 MB/s) - ‘currentrelease.tar.gz’ saved [311361] Stage standard stable release ./scripts/upgradeprep.sh: line 3: pip: command not found ./scripts/upgradeprep.sh: line 4: pip: command not found ./scripts/upgradeprep.sh: line 5: pip: command not found ./scripts/upgradeprep.sh: line 6: pip: command not found ./scripts/upgradeprep.sh: line 7: pip: command not found ./scripts/upgradeprep.sh: line 8: pip: command not found ./scripts/upgradeprep.sh: line 9: pip: command not found ./scripts/upgradeprep.sh: line 10: pip: command not found Initial install Setup systemd Dir: /home/pi/consolestable Installed staged stable ---------------------------------------------------------- ---------------------------------------------------------- Set Console to Start at Boot Sun 6 Jan 00:12:29 EST 2019 ---------------------------------------------------------- ---------------------------------------------------------- Failed to enable unit: File softconsole.service: No such file or directory rm: cannot remove 'tmp': No such file or directory ---------------------------------------------------------- ---------------------------------------------------------- Install and setup finished Sun 6 Jan 00:12:29 EST 2019 ---------------------------------------------------------- ---------------------------------------------------------- ---------------------------------------------------------- ---------------------------------------------------------- Rebooting in 5 seconds Sun 6 Jan 00:12:29 EST 2019 ---------------------------------------------------------- ---------------------------------------------------------- Rebooting 5 Rebooting 4 Rebooting 3 Rebooting 2 Rebooting 1 Reboot . . . I manually installed that per instructions on the wikipedia page (curl https://bootstrap.pypa.io/get-pip.py | python) and tried the installconsole.sh script again. It made it through the script to the end after that but the console doesn't start; and when I try manually I get: $ python -u console.py Traceback (most recent call last): File "console.py", line 26, in <module> import pygame ImportError: No module named 'pygame' Running out of steam at this point. What to do? -Chris B
  20. Just tried another install myself and seeing some odd behavior. Trying the https: connection to my ISY and a 3.5 TFT display; after going through most of the install dialog got the following. Note that no where in this output did the program actually allow me to enter anything though it looked like it was supposed to wait for input for the display configs? I haven't tried starting anything after this since i'm not sure what it failed to install? Any log I can examine? Here's the output (forgot to increase screen memory in my PuTTY session so here's just the end of the dialog but it shows the error messages):: HTTP request sent, awaiting response... 301 Moved Permanently Location: https://raw.githubusercontent.com/adafruit/Adafruit-PiTFT-Helper/master/adafruit-pitft-helper [following] --2018-02-27 22:11:25-- https://raw.githubusercontent.com/adafruit/Adafruit-PiTFT-Helper/master/adafruit-pitft-helper Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.200.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 12048 (12K) [text/plain] Saving to: ‘adafruit-pitft-helper’ 0K .......... . 100% 920K=0.01s 2018-02-27 22:11:26 (920 KB/s) - ‘adafruit-pitft-helper’ saved [12048/12048] --2018-02-27 22:11:26-- https://raw.githubusercontent.com/adafruit/Adafruit-PiTFT-Helper/master/adafruit-pitft-helper2.sh Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.200.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.200.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 16938 (17K) [text/plain] Saving to: ‘adafruit-pitft-helper2.sh’ 0K .......... ...... 100% 819K=0.02s 2018-02-27 22:11:26 (819 KB/s) - ‘adafruit-pitft-helper2.sh’ saved [16938/16938] ---------------------------------------------------------- ---------------------------------------------------------- Run PiTFT Helper 35r Tue Feb 27 22:11:26 EST 2018 ---------------------------------------------------------- ---------------------------------------------------------- This script downloads and installs PiTFT Support using userspace touch controls and a DTO for display drawing. one of several configuration files. Run time of up to 5 minutes. Reboot required! Select configuration: 1. PiTFT 2.4", 2.8" or 3.2" resistive (240x320) 2. PiTFT 2.2" no touch (240x320) 3. PiTFT 2.8" capacitive touch (240x320) 4. PiTFT 3.5" resistive touch (320x480) 5. Quit without installing SELECT 1-5: Select rotation: 1. 90 degrees (landscape) 2. 180 degrees (portait) 3. 270 degrees (landscape) 4. 0 degrees (portait) SELECT 1-4: [PITFT] Checking init system... Found systemd /boot is mounted [PITFT] System update Updating apt indexes... ......... Reading package lists... ......... [PITFT] Installing Python libraries & Software... Installing Pre-requisite Software...This may take a few minutes! Reading changelogs... ./adafruit-pitft-helper2.sh: line 145: warning: command not found [PITFT] Exiting due to error: Unable to install software Created symlink from /etc/systemd/system/default.target to /lib/systemd/system/graphical.target. ---------------------------------------------------------- ---------------------------------------------------------- Reboot now installconsole.sh will autorun as root unless aborted Tue Feb 27 22:16:16 EST 2018 ---------------------------------------------------------- ---------------------------------------------------------- Install will set Personal N and AutoConsole N ---------------------------------------------------------- ---------------------------------------------------------- Chose to manually reboot and run installconsole.sh Tue Feb 27 22:16:16 EST 2018 ---------------------------------------------------------- ----------------------------------------------------------
  21. I'm not familiar with git but I did pull down copies of the files that appear to need updates to accommodate https:// console connections onto my dev box and made changes I think will take care of allowing http or https connections (as well as the ws:// vs wss:// connection probably needed in isyeventmonitor.py. No idea how to test these though since the scripts all want to pull from the git repo and I'm not git savvy. Happy to zip up the 5 files though and email them or something. Changes are pretty minimal - along the lines of: if config.ISYaddr.startswith( 'http' ) : config.ISYprefix = config.ISYaddr + '/rest/' else: config.ISYprefix = 'http://' + config.ISYaddr + '/rest/' and updating the prompt in getsetupinfo.py to request the full URL to access the console (i.e. http://1.2.3.4/ or https://1.2.3.4:9999). Checks everywhere I found references to the ISYaddr check for the old format (no http prefix) so either should work. My server certificate is self-signed and last I tested some of the modified code myself I did get warnings from one of the libraries (lost the note I kept on that) but it wanted to have warnings disabled I believe - probably a urllib3.disable_warnings() type setup. -Chris B
  22. I too got a pi3 for Christmas but have had less luck with the install... My isy is setup secured (i.e. requires https and a non standard port). The :port is accepted by the isy ip prompt but https required code changes I just started digging in to... and warnings from one of the libraries due to my self signed certificate. - Chris B Sent from my SM-G920V using Tapatalk
×
×
  • Create New...