OK, took me a bit to figure out how to test everything and here’s what I’ve come up with:
Verified with netstat that 4199 is open and listening:
Used MS Network Monitor to determine that the WS1100 is sending packets to port 4199. Set it up on my machine and pointed the 1100 to the IP of my machine and voila, traffic.
I ran netcat (nc -p 4199 -l) over on the pi to see if anything is getting through and nothing shows on the screen after I put the command in. Not sure if I’m using it right. I do have to delete the integration in HomeAssistant to do that, otherwise I get an error that the address is in use (which my research tells me should be perfectly normal). So, it seems that somehow the traffic is not getting through to the Pi and HomeAssistant.
Other things that I’ve tried: I’ve used the PowerShell tnc command to try to connect to that port while it’s open and listening. tnc IPADDRESS resolves. tnc IPADDRESS -port 4199 fails. ping succeeds but TcpTestSucceeded shows False. I also opened an elevated command prompt and tried “telnet ipaddress 4199” and for the following error: “Could not open connection to the host, on port 4199: Connect failed”
I can ping the ip of the WS1100 and the Pi
Yes, the WS1100 and the Pi are on the same VLAN. That wasn’t always the case but it is something that I corrected earlier in the game.
All of my other integrations are working (Plex, Tuya Switches, Vizio SmartTV). The Pi is also the primary DNS resolver for my entire network, so I know that other devices in the network can talk to it. One thing that I have noticed is that this instance of HomeAssistant doesn’t “find” stuff on my network like the first test version that I ran. I initially started out with an instance in a Linux VM on my main PC just to see if it was something I was interested in before I loaded it to the Pi.
The whole topic is about the Ecowitt integration (custom component). Froggit is an FineOffset clones the same as Ecowitt is. They all use the Ecowitt protocol to publish data locally. You need to configure the weather station unit with the WSView app to publish the data to your HA’s local address, where the integration receives and interprets it.
Just add Ecowitt integration and follow the instructions. After that, you get all the data as sensor entities in Home Assistant. It’s been ages since I did this but I remember it was surprisingly easy, I thought it would have been harder to set it up and working.
I tried the official integration but didn’t work for me (sensor were not appearing and got a webhook error in the log). It may be because I’m running it in docker, but the unofficial one works well at the moment and it’s too important in my setup to do many experiments.
To be clear I completely uninstalled the unofficial before trying (removed both the integration and the HACS install, restarting the system at every step, then installed the official one, restarted again but it didn’t work.
any way to migrate form hacs integration to official without affecting the entities?
It would have been good if it was migrated automatically, as has happened with others…
Not that I could figure out. But it took me a couple of minutes to rename the entities to match the old ones.
I needed to delete HACS integration, delete the old integration, RESTART Core, then add the new official integration before all worked OK.
