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

Remove space before colon (#17483)

Browse Source 
Fix spelling of occurred

Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk>
This commit is contained in:
Jacob Laursen 2024-09-29 12:09:47 +02:00 committed by GitHub
parent b8905e5b69
commit c4576bb0f5
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
20 changed files with 52 additions and 50 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -73,7 +73,7 @@ There can be following reasons why Miniserver status is `OFFLINE`:
- _Internal error_
- Probably a code defect, collect debug data and submit an issue. Binding will try to reconnect, but with unknown chance for success.
- _Other_
- An exception occured and its details will be displayed
- An exception occurred and its details will be displayed
- **Communication Error**
- _Error communicating with Miniserver_
- I/O error occurred during established communication with the Miniserver, most likely due to network connectivity issues, Miniserver going offline or Loxone Config is uploading a new configuration. A reconnect attempt will be made soon. Please consult detailed message against one of the following:
@ -84,7 +84,7 @@ There can be following reasons why Miniserver status is `OFFLINE`:
- _Timeout due to no activity_
- Miniserver closed connection because there was no activity from binding. It should not occur under normal conditions, as it is prevented by sending keep-alive messages from the binding to the Miniserver. By default Miniserver's timeout is 5 minutes and period between binding's keep-alive messages is 4 minutes. If you see this error, try changing the keep-alive period in binding's configuration to a smaller value.
- _Other_
- An exception occured and its details will be displayed
- An exception occurred and its details will be displayed
### Security

2
bundles/org.openhab.binding.mycroft/README.md
View File

@ -50,7 +50,7 @@ A Mycroft thing has the following channels:
| utterance | String | The last utterance Mycroft receive |
| player | Player | The music player Mycroft is currently controlling |
| volume_mute | Switch | Mute the Mycroft speaker |
| volume | Dimmer | The volume of the Mycroft speaker. (Note : Value unreliable until a volume change occured) |
| volume | Dimmer | The volume of the Mycroft speaker. (Note: Value unreliable until a volume change occurred) |
| full_message | String | The last message (full json) seen on the Mycroft Bus. Filtered by the messageTypes properties |
The channel 'full_message' has the following configuration available:

2
bundles/org.openhab.binding.smsmodem/README.md
View File

@ -67,6 +67,7 @@ The _smsconversation_ thing is just a shortcut to address/receive messages with
## Channels
The _smsconversation_ supports the following channels:
| channel | type | description |
| -------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| receive | String | The last message received |
@ -76,6 +77,7 @@ The _smsconversation_ supports the following channels :
## Trigger channels
The _smsmodembridge_ and _smsmodemremotebridge_ has the following trigger channel:
| Channel ID | event |
| -------------- | ----------------------------------------------------------------------------------- |
| receivetrigger | The msisdn and message received (concatened with the '\|' character as a separator) |