webCoRE also supports charts now...
1 Like
I recived a notification this morning to updste my firmware on my GW1100-B to 2.1.7. Was it suggested (determined) this s is a bad update and should be avoided ? Or is it ok tp update?
Hmmm... was about to say, go for it, but looking back through @kahn-hubitat 's comments, maybe, maybe not.... Am I right in saying you saw the same issue in both GW1000 and GW1100 @kahn-hubitat? My gut feel is it should be ok, I couldn't see any flood of comments on the EcoWitt forum suggesting there was some widespread issue.
1 Like
I haven't seen any issues (but haven't been paying that close attention either). For my use, the current firmware seems to be fine, I just didn't want to install a problem.
I'll admit for me, systems like these are typically set and forget, unless I have a problem I don't tend to touch them. The only reason I installed this one was to be a test case for the average user, no adverse results so far, but not the same model number as you are using....
No only the gw1000b
1 Like
New twist. I added an additional Wh31 yesterday. For some reason the device attributes aren't the same in Hubitat :
The previously added sensor:
The Newly added senor:
It appears empty and Full battery voltage fields are missing.
I didn't have any issues setting up my EcoWitt WIFI Gateway and one sensor. However, I'm trying to follow the instructions for Simon Burke's package in HPM and struggling.
Where I guess I'm being thrown is once you get to "Capturing Configuration Settings and Turning off the data feed." The first step asks you to open the EXISTING Ecowitt Wifi Gateway virtual device. This is the step after you just created a virtual device, but that is the only one I see on Hubitat. Are the directions possibly asking you to login to EcoWitt's site and gather the MAC / IP Address information from there?
I need to amend those instructions now, they were more so for those transitioning from a previous EcoWitt setup. Without looking at the instructions in detail, I'm going to say ignore that part and I will get back to you later today.
2 Likes
Sorry, I completely forgot about this, it was quite late when I made my last comment and had a busy day trying to repair a dishwasher.... 
I do still need to get back to tidying up the different installation notes for those moving off the old drivers. I should have really directed you to look at the Readme page on the GitHub repository, which are located here (also something I need to make clearer at the top of this topic):
Given you are midway through, I'll try to guide you through what I think is left.
If you have:
- The gateway and sensor setup in the WS View App on your mobile / tablet
- The HE drivers installed from HPM and a virtual device created
- But no readings coming through
Then I think what you need to do is:
Make sure you have covered off steps 1 and 2 in the installation instructions I linked above, relating to the WS View App. I expect it will be step 2 that you need to complete, setting up the feed of data from the EcoWitt Gateway to your HE hub.
Complete Hubitat setup steps 4 and 5, locating the EcoWitt Gateway's MAC Address or IP Address, either through the WS View App or through your router's configuration. Enter this MAC / IP address into the HE virtual device edit page. Wait for the next push of data, based on the frequency configured in the WS View App. Keep an eye on the virtual device page to see the sensors / data come through. You may also want to have the HE Logs page open in case something pops up there.
That should essentially complete the setup of the devices / sensors in HE. From there you can look at configuring automations and/or dashboard tiles, also covered in the Readme I linked above.
Again, sorry for the confusing start. Hopefully these notes get you started, but please post back here if you have any questions or still can't get your gateway setup, and we can help.
1 Like
Yes, I should be upset with all the free development and support you are giving me. lol...thanks for your help.
Your instructions couldn't have been clearer. Worked on the first try. Thanks again.
5 Likes
Excellent, glad to hear you got it working.
1 Like
Well, here I am deep in the ecowitt rabbit hole. Everything went well per your readme instructions. I have child devices showing. I installed the WH31/1100 combo (channel 1) per recommendation in the "Attic Temp" thread. BUT I'm also showing a WH25 child populated as "Indoor Ambient Sensor" -- is that the gateway?
2 Likes
Yup.
And indeed, it is a rabbit hole!
2 Likes
How to I rename sensors? Ambient Sensor 1 was assigned to the WH31 child when it populated the device table. I've tried WS View via gateway IP login and can change the "channel 1" name on Live Data but that doesn't show up on HE.
Change them direct in hubitat, under devices there's a parent and child devices for your ecowitt. Any device (not just ecowitt) has a secondary name/device label you can set to anything.
Ie
In ecowitt.net you can click on the names and change them there but that has no effect in hubitat.
3 Likes
Ahh! The HE Device Label (smacks forehead)! I was focused on the naming, but the secondary will do just fine. Thanks.
116F in the attic. I was expecting closer to 125f.
2 Likes
You can also change the primary name as well, but that can get confusing when you later go back in to do maintenance and figuring out what is what.
2 Likes
The 'store data to text file' option in @bptworld 's Quick Chart app is working and makes for a quick, easy way to log a sensor's output. No RM, no variables. The chart is handy, but what I need is the file, heh.
I saw this post this morning.. Should you not ask Bryan where the file is likely to be stored locally so you can find it and use it for whatever you need?
