seems to be same error as before.
when you check the location information is the information here correct?
thanks.
seems to be same error as before.
when you check the location information is the information here correct?
thanks.
There looks to be a bug introduced in a previous commit of yours.
The code started throwing an error of āgroovy.lang.GroovyRuntimeException: Could not find matching constructor for: java.util.Date(java.lang.Long, sun.util.calendar.ZoneInfo)ā on June 6, the day after you made updates to the code. I see that there are changes to your date formatting and would look into that, such as this:
The issues reported by pcgirl65 are unrelated to account migration as the errors started 2 days after migration. My guess is the repo wasnāt updated until that time at which point the errors started.
ahh ok. understood the error started with the account migration. thanks for confirming it did not ā¦ will dig and fix.
thank you.
The issues did start after the migration. I just didnāt contact them until two days later. I am having other issues since migrating also. Some of the Routines arenāt working such as my Night Routine which is supposed to turn lights off when Motion Detection has stopped. This isnāt working. And Good Morning isnāt working when Motion Detection starts.
got it. cant help with the other issues ā¦ hopefully ST will work with you to get those resolved.
but for this i plan to take a look and see if i can get it working by doing something different. will post an update with that before eod. please give that a try and let me know how it goes.
thanks.
updated to github with following changes:
* Version: 0.50.0
*
* DONE: 6/30/2018
* 1) added icons to main settings page for a room in hubitat. ST already shows these icons on the settings page.
* 2) added option to hide advanced settings.
* 3) added setting to adjust cooling and heating temperature by 0.5ĀŖF when outside temperature is respectively over 90ĀŖF and below 32ĀŖF.
* 4) rewrote temperature management to be more consistent.
* 5) cleaned up rooms manager settings.
* 6) added option for how often device health message should be announced.
* 7) fixed a bug here and there.
It seems to be working! I have a question though about the appā¦when we set up rules do we still need to set the lights to turn on in the Occupied and Engaged Settings? I donāt have anything set for "Which Switch turns ON " in the Occupied and Engaged Settings because I have rules setup. It seems to work but just wondering if I am missing something.
Also, does the same program work in Hubitat? After having a number of power outages lately, I am thinking of maybe trying Hubitat out.
glad to hear its working now. sorry for the trouble you had after the ST account migration.
yes. wanted the user to have the flexibility for which lights/switches turn on in occupied state vs in engaged state and maybe use different level settings or colors for each of those states. you dont have to ā¦ but the rules give you the flexibility of doing that.
if in both occupied and engaged state all of the same lights/switches should turn on with the same level/color temperature/color ā¦ just create one rule where both occupied and engaged states are selected and set which switches to turn on optionally with level, color temperature and color.
Iāve just discovered this fabulous code and am testing it on a few rooms in my house.
Two things Iām not quite clear about:
Thank you so much for this great code. Itās the first Iāve seen to accomplish what I need to move over from my old automation server.
thats awesome to hear.
strange. are you using the latest code - version 0.50.0? what is the timeout setting for checking state?
what i found was occupied works well if you are moving around in a room. but if you are sitting and watching TV you are likely not moving enough to trigger the motion sensor and keep the room occupied. couple of choices here:
in the latest version temperature i may have introduced an unintentional bug. will take a look at this and make sure the temperature management is driven only by the rules even in vacant state.
note that if you have a single whole house thermostat and are not using automatic vents or in room ACs / heaters ā¦ probably best to just set the temperature setting in one room to turn it on and off because its always cooling all areas and has no way of really controlling per room temperature.
thank you for the kind words ā¦ this is music to my ears.
Iāve just updated the code to the latest you have posted. Will see how the ācheckingā thing goes.
I understand your reasoning for āengagedā and Iāll probably use it at some point. With that said, Iām coming off an automation server setup Iāve been using for basically 20 years using old X10 motion sensors. My logic to mark a room as āoccupiedā there was simply how long as it been since a sensor in that room has seen motion. Nothing more fancy. Iām trying to duplicate this same kind of simple logic for now in your code to see if I can replicate the functionality of what Iāve used in this code. For my purposes, a room is either occupied or vacant.
Iām noticing that the ācheckingā setting is now gone in the room configuration so maybe something youāve changed (used to be under the āengagedā setting).
Screenshot_20180701-233445_SmartThings|243x499
I have two HVAC units and have only one āroomā assigned to monitor the one Iām testing.
Thanks for all your work. Iāve had this Smartthings hub for a year and while Iāve played around with trying to replace my exisiting system here and there over that time, no solution looked to solve what I needed. Your work seems to duplicate what Iāve been doing so Iām excited to see if I can retire the old girl.
cool.
understood. once everything works with occupied and vacant may be then explore other settings to take advantage of everything else that is possible.
see the screenshot below. this is what the current version of the settings page looks like. if you turn on easy settings or hide the advanced settings it looks different. if you are not seeing the checking settings turn off the hide advanced settings if that is on and you should see it again.
you are quite welcome. thats awesome to hear that this app might be able to replace the old girl and become your new girl.
please feel free to ask questions if i can clarify anything or to suggest features if there is functionality i could add.
thanks again.
working on updating docs with a feature list at the top because i know like me most people enjoy reading all the rest of the docs
once finalized will probably add these at the top of the main post ā¦
Thank you for the fixes!
I have been monitoring the errors on our end and the errors went from ~1,500 a day to zero as users have updated the code!
sure thing.
thanks for sharing the data point ā¦ they are always helpful.
UPDATE: updated to github with the following changes:
* Version: 0.52.5
*
* DONE: 7/9/2018
* 1) added occupany icon to rooms device state for use with Hubitat.
* 2) added icons to settings for rooms device for Hubitat
* 3) added icons to settings for rooms manager for Hubitat
* 4) optimized performance of device health check on Hubitat.
* 5) started cleaning up code for room state replay.
* 6) added option to announce sunset and sunrise with speaker along with the color option that was already there.
* 7) added more granular control for window shade level.
* 8) added processing for room cool or heat rules on room state change.
* 9) swatted a bug here and a bug there.
The GE dimmers DTH should be out next weekā¦Thanks to @bangali for adding the code in to his great app!