ioBroker.telegram
ioBroker telegram adapter
Use telegram service to communicate with ioBroker
Documentation
Sentry
This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.
Changelog
3.0.0 (2023-11-06)
- (boergegrunicke) BREAKING CHANGE: Socks5 support has been removed.
- (PeterVoronov ) Extended and improved the returned list of processed messages.
2.0.2 (2023-11-06)
- (mcm1957) Dependencies have been updated.
2.0.1 (2023-10-10)
- (boergegrunicke) Incorrect trailing zero in callback of sendTo() has been fixed. [#680]
- (mcm1957) Dependencies have been updated.
2.0.0 (2023-10-09)
- (bluefox) Packets were updated.
- (bluefox) BREAKING CHANGE: The minimal node.js version is 16
- (boergegrunicke) BREAKING CHANGE: Return an object with chatId and messageId instead of the message count
1.16.0 (2023-06-16)
- (foxriver76) We have added support for the
notification-manager
adapter
License
The MIT License (MIT)
Copyright (c) 2016-2023, bluefox dogafox@gmail.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.