Not (necessarily) driver related, but seeking input. I’m having these issues identifying devices and at lease one device not pushing to hubitat. I will be replacing vs my actual weather station (upgrading from an accurite 7 in 1) with a Witt boy this weekend. Would it be advisable at this point to just remove all of my devices ( about 8 devices) from the gateway, resetting and register with the gateway one by one,
Each physical device has dip switches that correspond to its RF channel that the gateway is receiving on, i.e. 1 thru 8.
You can match up the dip switches to channel assignments in the Ecowitt app or on a physical console screen.
I’ll check on the one sensor., but they were all already included in the system on my old gateway. My issue cropped up when I replaced my GWQqpp with the GW 2000 (the old gateway kept dropping off the WiFi, the new one is connected by a POE Ethernet connection. Most came across just fine. But I picked up one device I don’t have and one I do have isn’t there. They aren’t the same device (already checked) because the mystery device isn’t reporting the same information as the missing device displays on its screen.
If u deleted it yiu NEED to do.tge resync
I have, several times. The one device isn’t showing up, the other device comes back. I’ve though it was the same device and may I change the name, but the data (temp humidity) in the device page doesn’t match what displayed on the screen in the device itself. Honestly this iswhy I asked if the Ecowitt device ID could be included in the device page, Hoping it would be an easy way to confirm which device is which. I get it that it’s not passed on so there is no way that it could be, that’s not @sburke781 problem, I’m just thankful for the work he’s doing! Now I just need to figure out another way. My thought was since I’m adding the wittboy tomorrow, just redo all of it. Nuclear option for sure, just hoping someone had a better suggestion.
Which app. The website will be behind the normal.app and even the ws view uodates only every few minutes so.doesnt necessarily match the sensor.
1 Like
Just “Ecowitt “
I finally got hubitat to find the missing device. I disabled it in the Ecowitt app (pictured above), then pulled batteries for about 2 hours . I while I was doing that I went through and verified the Device ID, channels, name, location , and temp (f or c) settings of the other temp/ humidity sensors. Then I put a label on the back of each so I don’t have to do that again. Then I reenabled the device in the app, put the batteries back in, and reregistered it. Once that was done resynced in hubitat and it was finally found. All good. I still have the other device showing. Question, would the gateway itself show up as a separate RF sensor as a child like the others? That is the ONLY other thing I can think that this one device could be. Thoughts?
This “extra” sensor isn’t just a little off , it’s all from all the other known Ecowitt sensors by seven to fifteen degrees. Interestingly, it is close (within about 5 degrees) of a sonof temp sensor in the same closet as the hubs and gateway, hence why I was wondering if the gateway shows up as a child rf sensor?
UPDATE: Annnd it’s gone again.
Yes the gateway at least the older ones is what reports indoor temp humidity and pressure
If its coming and going i would say its too far from base or somthing is blocking it.
Sorry I have been a bit "quiet" on this.... Though, in the end, I was not likely to have added anything meaningful... Glad to hear you have mostly resolved the issue. In terms of removing the old sensor... the best I can offer is removing it from HE manually and seeing if it reappears.
I completely understand,
Mostly. I’m beginning to think maybe this sensor is bad. I got it to include once yesterday, ten minutes later, it was gone again. Haven’t been able to get back, even putting it in the same room as the gateway. But the good thing is when the wittboy arrives today I don’t think I’ll need to employ the nuclear option.
I now think what I thought was the old gateway, is in reality the temp/humidity sensor in the new gateway.
1 Like
Every chance @kahn-hubitat has already pointed this out.. but the sensor driver does pick up the
WH25 and WH65 battery readings in the same way.... Not sure what that may mean without some more thought...
case ~/batt[1-8]/:
case "wh25batt":
case "wh65batt":
state.sensor = 1;
updated = attributeUpdateBattery(val, "battery", "batteryIcon", "batteryOrg", 0); // !boolean
break;
Though what doesn’t make any sense, the disappearing sensor Does show in the Ecowitt app fine, with a strong signal. Just doesn’t pull over to Hubitat.
Deleted original question, figured it out. New question, why does this have two temps? Using template 3 and 6
Sorry @lcw731 , was meaning to get back to you earlier. Yes, the templates recommended for PWS are the one's that would best suit the Wittboy, but any that include similar attributes could also be used.
The first temperature is the... well, temperature 
The second temperature is the Dew Point.
For a more complete list of the templates that are configured, you can look here
1 Like
About 12 hours into including the Wittboy, and an interesting observation. This does somewhat relate to my disappearing sensor issue. It still disappears, but it's not as much of a concern. If you previously had a WN (WH)32 Outdoor Temp Humidity sensor (the one that keeps disappearing and that Hubitat can rarely seem to find), when you add a WS90 (Wittboy), the temp /humidity reading from the Wittboy is pushed out in favor of the Wh32 (in the Ecowitt app). I assume this is happening at the Gateway level, (in my case a GW2000B). At the same time, the Ecowitt drivers in Hubitat, now see the single Wh32 sensor as part of the Wittboy weather station and report it with the rest of its information. My conclusion is that Ecowitt must be using the same sensor chip in the WS90 they used in the Wh32 since the gateway can only include one WH32-type sensor. What this means for anyone who has the single channel outdoor WH32 temp/humidity sensor is you can't use that on the same gateway as the WS90. You will have to choose which one you want. In my instance, I was hoping to keep the outdoor stand-alone sensor to keep track of temps on my patio in the shade since the weather station is out in the open in the sun. For my use, I will just opt to use the sensor for visual reference (since it has the display screen) and not expose it to the gateway so that I can prioritize exposing the actual weather station to the gateway and get my temperature/humidity reading from that.
UPDATE:
When you add a WS90 (Wittboy), the temp /humidity reading from the Wittboy is pushed out in favor of the Wh32
To clarify a little on this. Once you disable the Wh32 in the Ecowitt App (so that the gateway is no longer listening for it) it reverts to the Temperature/humidity sensor on the WS90 (wittboy), hence why ill just be using this sensor for visual reference on the patio weather than including it in my system.
My next question then is, are these templates supposed to have the Icons included with them? or do they need to be added? using them in sharptools, I get the text, but I'm not getting any icons. I suspect that is why the two temps looked odd to me, like maybe ab icon would have tipped me off to what the second temp reading was.
Yes and no... The icons require some additional CSS, achieved by importing the CSS file from my GitHub repository (actually my GitHub.io repository. If you look at the HTML Templates section of the EcoWitt Readme:
GitHub - sburke781/ecowitt: Hubitat Ecowitt Gateway Integration
You will see step 2 is where the CSS file import is described, describing adding this line to the Custom CSS section of the HE dashboard:
@import url("https://sburke781.github.io/ecowitt/html/ecowitt.css");
The CSS does both the work of adding the icons to the front of each reading in the tile and makes reference to a True Type Font used for the icons, also hosted on my GitHub.io repository.
Importing the CSS file in a HE dashboard will make the icons appear. I am not sure what options you may have in SharpTools, I do not use it myself.
Ahhh ok, I must have missed that. That's what I get for skimming!! There is a place in the theme for custom CSS, i'll check and see if this will carry over there as well. I have to admit, it's been interesting working through this with Sharptools. took me a few days just to figure out the HTML part.
1 Like
Keep in mind that if you are displaying an attribute in a Custom Tile, those run in a sandboxed environment, so Custom CSS applied in the dashboard settings won't apply inside the custom tile.
Also note that browsers are very particular about @import statements. They have to come before any other CSS styles are applied, so that could be tricky.
But if you are using it in a Custom Tile, you should be able to convert it to reference the CSS stylesheet directly. You would convert it into a format like the following and put it at the very top of the code for the Hubitat HTML Attribute Custom Tile:
<link rel="stylesheet" href="https://sburke781.github.io/ecowitt/html/ecowitt.css">
Super Tile
You could also consider using a Super Tile to achieve the same effect. You could drag multiple attribute and icons into a tile layout and position them and customize them however you see fit.
1 Like
