it finally thawed out . storm total was two feet now I need to write fxs to go back and fix totals
only took about 200 firings of the heater according to reports. Now will see how the 8 batteries last. it seems to not be suited for freezing drifting snow that can cover the sensor..
Hello! I'm stuck on Step 1. I went to that webpage and downloaded the block of code, then saved it to a TXT file because that's what I assumed I needed to upload into the File Manager. I assume I'm making an obvious mistake, but since I'm coding illiterate...sorry!
I believe I have Step 2 worked out, but I'm pretty sure that updated Ecowitt code is going to call for a CSS file that isn't in my File Manager.
Again, sorry for the confusion. Can I change the filename of my TXT file to "ecowitt1.css" and it will work? Or...is there a method of saving that weppage that I'm ignorant of? I'd play with it, but I don't want to 'break' my weather station. Thanks a lot!!
Yes, that is what you will need to do, remove the .txt extension, leaving the .css. Don't worry, you can't break it with this file.
I could likely make use of some of the newer file handling features of the platform to download it automatically. I'll add it to the growing list 
Thanks! I renamed my text file to ecowitt1.css and uploaded it to my File Manager. Easy. But I think there's another step to make the Dashboard tile work.
My pre-existing tile now says "Please Select an Attribute". But there's no longer an HTML option in the dropdown list. Do I need to update the Advanced area of my Dashboard to reflect the new template repository location? This is from the Read Me docs:
I assume it's just looking for the new template in the wrong place? How do I get it to reference the CSS file in my File Manager? (Assuming my guess is correct) Please advise and thanks!!
I will be getting back to questions / requests soon... Should be able to sort this one out relatively easily...
@brian17 ,
Looking back at the earlier conversation... I think it would be best to rename the file you have downloaded to your hub as ecowitt.json instead of using the css extension. This file contains the template information, used to construct the contents of the html attributes on the sensor devices in HE. The equivalent file in my GitHub repository uses the json extension. The ecowitt.css file referenced in the dashboard (from your last screenshot) is used to add styling to the tiles, particularly icons. If you want to maintain your own copy of the templates (json) file locally, and I eventually start including this file in the HPM package, then it may also be worth adjusting the name of the file to avoid it being overridden and losing your changes, so ecowitt_local.json or something similar.
Whatever file name you go with, if you do change the file name used, be sure to update the driver code as @kahn-hubitat guided you through earlier.
To answer your questions:
From what I explained above, this file is not the same as the one you downloaded. I would suggest continuing to reference it from the GitHub link, although I would also suggest re-pointing your Dashboard to look at my copy rather than Mirco's. While I don't believe there is any difference at the moment, if I do apply any changes in the future then you would not see these come through if you left this as-is or used a local copy.
So change that line to:
@import url("https://sburke781.github.io/ecowitt/html/ecowitt.css");
While now not relevant for your situation, based on what I just described, for future reference, if you do need to use a local file for any reason in the future, the equivalent link would be:
@import url("http://< he-hub-ip >/local/ecowitt.css");
using the IP address of your HE hub.
This will not be related to the import line in the dashboard I was just describing, but more likely an issue with the device / driver being able to produce the html attribute you are not seeing. I would check:
Can n you also provide a screenshot of your preference settings for the device?
I've just added GW1200 gateway to my home to pick up some soil sensors that my HP2553 were too far away from and have one sensor that is still a bit marginal in level.
I have both stations and their respective sensors all working well in Hubitat using your excellent driver and thought as the RF levels of each sensor on the GW1200 are shown in the Ecowitt App (under sensor management), then maybe this data is available in the weather station data push?
It would be a handy feature to have the RF level of each sensor displayed on my Hubitat / Sharptools Dashboard and perhaps rules in place to alert of low RF level in case a soil sensor has been dislodged or other factor that has affected the sensor RF level and its ability to regularly provide updates but not reduced enough to drop right off and cause the weather station to report it orphaned.
I found this occurring on a few distant sensors (hence the addition of the extra gateway), where they were a showing a constant value for moisture, despite watering etc and investigation found the device events were showing only intermittent updates but was still showing the Device not Orphaned (false).
i believe you need to follow the instructions and go into the app and go under the calibration section and put in the measured air depth from tip of sensor to ground in order for the depth be reported and shown.
Can't see in the app. I Probably need to log into the GW3000 hub interface and set it there my next trip.
no its in the app ws view plus or wsview but you need to be local.. so hopefully if you are not at the house you have a vpn or somthing to ge on the local net and run the app.
Found it! Its on the phone app, didn't see it on the PC app. Very cool..
Hi Roger (@RSZ ),
Thanks for offering your suggestion for the sensor signal strength. That is a good suggestion and one that would be nice to add to the driver. Unfortunately, from all I can see coming from my older Gateway, the RF signal strength is not something that is available in the data I receive... if more recent Gateway devices offer this in the data feed, I'd be happy to add it. To see what data is available, open the Gateway device in HE and adjust the Log Verbosity Preference setting to Trace and review the logs.
If anyone else has any thoughts on this, I'd be happy to take a look.... at some point....
Thanks Simon, I set the log verbosity as suggested on the newer gateway (GW1200C) and looks like the RF level of the sensors is not available.
There was only one attribute in the data that was reporting as unrecognizable, extract below in case you havent seen it before or of any interest.
Hello, I've been using this driver for a couple years now with great results but randomly one of my sensors has started reporting a bunch of info logs. No other sensors do it and I have 7 total. Any idea why this might have changed?
Nothing springs to mind. Maybe send me some logs and a screenshot of the preference settings?
Download the Hubitat app
