The Parent is V1.1.0. The Child is V1.2.1. The Driver you have on GitHub is V1.4.0 even though you have āDriver v1.5.0ā listed at the top of the thread.
I just removed all of the child and parent apps and will start from scratch. Give me a few to test through.
The app needs a new report for it to action anythingā¦
In other words, something needs to change before it reports (then performs an action)
The quickest way to test is to change from F to C and back again (you might need to force poll)
This will give you two very different numbers and you can try different thresholds to test
Alright, hereās the latest:
SmartTiles - For some unknown reason, when I created a second virtual switch and selected that in SmartTiles, it wouldnāt work. I would get a blank screen with some message error. So I went back to my original WU device, loaded the default driver and SmartTiles is working fine.
WeatherSwitchApp - I followed the same process as above, only I created a second virtual switch using your custom 1.5 non-SmartTiles driver. It seems to be working now. The switch turns on and off based on the programed behavior. Iām going to lay back for a bit so I donāt blow over my number of polls based on my api etc.
So far the app is working for forecast high and low. I'll update you in a few days to make sure it's going well.
Strangely the SmartTiles code won't work:
At some point, my ADD will get the better of me and I'll need to see if I can hack the drivers so I only have one WeatherUnderground device but that'll have to wait.
The driver just needs the capabilities put back in with prehaps some āsendeventā statements to use the old variables.
I removed them because they are not being used for WS and my attributes have different names
E.g
I use āForecast_Lowā instead of āforecastLowā
You can easily make a driver to do both but it would show duplicate reading on the ādeviceā page
(Which is one of the reasons I removed the capabilities)
If you decide to add the capabilities then make sure you still have the version number and namespace intact or it wonāt work with WS (the app checks for them)
Actually, you could make it switchable so if not using Smarttiles it would not show the duplicate entriesā¦ hmmmā¦ I might think about that when I have some more time
Ok. So later came sooner than I expected. I started playing with the driver and now I have one driver with both SmartThings and Weather Switch. Here's where my ignorance has really gotten the best of me. All I did was add the following:
I suspect that Smarttiles is querying the driverā¦
The sendevents are needed for WS to āsubscribeā to the events (and therefore act upon them)
Do you have duplicate entries on the ādeviceā page now?
That would explain it. I learn something new every day. Here's a screen shot. And, point-of-fact, the SmartTiles are reading the lower case temperature which isn't accurate.
As you donāt have the sendEvent statements for the lower case info, it wonāt update correctly (if at all)
What you are seeing is probably legacy data
If you donāt mind the duplicate entries then I can probably get this to work for SmartTiles as well as WS
Itās 1am in the UK now so Iāll have a look tomorrow for you.
Get some sleep! This is a fantastic app and Iām so happy you wrote it. I think there are really only 4 items that need a bit of nudging:
weather
temperature
humidity
feelslike
I need to step off and get some food and grog. Iāll take a swing at it a bit later (Iām -8 hours from you). I was just focusing on the driver. Now that Iāve taken a bit of a look at the child-class code, it doesnāt seem insurmountable.
I am working on the driver and app anyway tomorrow
Iām going to try to get the driver to compile a sort of āreportā so I can get WS to send via SMS or pushover (until we have TTS then Iāll get Sonos to speak it)
I canāt use the built in report (fcctext or fcctext_metric) because I prefer to use a mixture of imperial and metric
In WS I plan to trigger the report with a virtual momentary switch so I can get it any time.