demus/openhab-addons
1
0
Fork 0
mirror of https://github.com/openhab/openhab-addons.git synced 2025-01-25 14:55:55 +01:00
Code Issues Packages Projects Releases Wiki Activity

[wundergroundupdatereceiver] Use html entities where in normal body (#13831)

Browse Source 
Fix spelling

Signed-off-by: Daniel Demus <daniel-github@demus.dk>
This commit is contained in:
Daniel Demus 2022-12-04 00:39:14 +01:00 committed by GitHub
parent 56728b6091
commit 193b54107c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
bundles/org.openhab.binding.wundergroundupdatereceiver/README.md
View File

@ -5,7 +5,7 @@ Many personal weather stations or similar devices are only capable of submitting
This binding enables acting as a receiver of updates from devices that post measurements to https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php.
If the hostname is configurable - as on weather stations based on the Fine Offset Electronics WH2600-IP - this is simple, otherwise you have to set up dns such that it resolves the above hostname to your server, without preventing the server from resolving the proper ip if you want to forward the request.
The server thus listens at http(s)://<your-openHAB-server>:<openHAB-port>/weatherstation/updateweatherstation.php and the device needs to be pointed at this address.
The server thus listens at http(s)://&lt;your-openHAB-server&gt;:&lt;openHAB-port&gt;/weatherstation/updateweatherstation.php and the device needs to be pointed at this address.
If you can't configure the device itself to submit to an alternate hostname you would need to set up a dns server that resolves rtupdate.wunderground.com to the IP-address of your server and provide it as the DHCP dns-server to the device.
Make sure not to use this dns server instance for any other DHCP clients.
@ -164,7 +164,7 @@ Thing wundergroundupdatereceiver:wundergroundUpdateReceiver:ATHINGID "Foo" [stat
}
```
The pattern for a given channel is `Type <channel type id> : <request paramter> []` from the channel types table.
The pattern for a given channel is `Type <channel type id> : <request parameter> []` from the channel types table.
Casing of the request parameter is significant.
None of the current channels take config.