-
Posts
41 -
Joined
-
Last visited
Recent Profile Visitors
619 profile views
chrisb5's Achievements

Member (3/6)
3
Reputation
-
Just tried it out - looks great! Thanks!!!
-
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
-
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?
-
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.. ?
-
@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?
-
Dan - Thanks!! That works beautifully!
-
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... ?
-
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).
-
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!
-
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
-
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
-
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
-
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!
-
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?