mqtt client connection closed #561
Assignees
Comments
|
@gguuss can you have a look at this IoT issue or re-assign please. Thanks. |
|
@roccomuso This issue could occur if the pubsub topic was incorrectly created; try using the state topic instead to see if the issue persists. |
grayside
pushed a commit
that referenced
this issue
Oct 26, 2022
🤖 I have created a release \*beep\* \*boop\* --- ## [2.4.0](https://www.github.com/googleapis/nodejs-tasks/compare/v2.3.6...v2.4.0) (2021-09-07) ### Features * turns on self-signed JWT feature flag ([#561](https://www.github.com/googleapis/nodejs-tasks/issues/561)) ([9fde4fe](https://www.github.com/googleapis/nodejs-tasks/commit/9fde4fe9a7274493ce0b4bb1a2d25bd85a3e9af2)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
grayside
pushed a commit
that referenced
this issue
Nov 3, 2022
🤖 I have created a release \*beep\* \*boop\* --- ## [2.4.0](https://www.github.com/googleapis/nodejs-tasks/compare/v2.3.6...v2.4.0) (2021-09-07) ### Features * turns on self-signed JWT feature flag ([#561](https://www.github.com/googleapis/nodejs-tasks/issues/561)) ([9fde4fe](https://www.github.com/googleapis/nodejs-tasks/commit/9fde4fe9a7274493ce0b4bb1a2d25bd85a3e9af2)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
ace-n
pushed a commit
that referenced
this issue
Nov 11, 2022
* Added retries to automlTablesPredict sample test * Convert arrow functions
ace-n
pushed a commit
that referenced
this issue
Nov 11, 2022
* Added retries to automlTablesPredict sample test * Convert arrow functions
ace-n
pushed a commit
that referenced
this issue
Nov 14, 2022
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
ace-n
pushed a commit
that referenced
this issue
Nov 14, 2022
* Added retries to automlTablesPredict sample test * Convert arrow functions
ace-n
pushed a commit
that referenced
this issue
Nov 15, 2022
* Added retries to automlTablesPredict sample test * Convert arrow functions
ace-n
pushed a commit
that referenced
this issue
Nov 15, 2022
* Added retries to automlTablesPredict sample test * Convert arrow functions
ace-n
pushed a commit
that referenced
this issue
Nov 17, 2022
* Added retries to automlTablesPredict sample test * Convert arrow functions
ace-n
pushed a commit
that referenced
this issue
Nov 17, 2022
* Added retries to automlTablesPredict sample test * Convert arrow functions
ahrarmonsur
pushed a commit
that referenced
this issue
Nov 17, 2022
* Added retries to automlTablesPredict sample test * Convert arrow functions
ace-n
pushed a commit
that referenced
this issue
Nov 21, 2022
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
ace-n
pushed a commit
that referenced
this issue
Nov 21, 2022
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Shabirmean
pushed a commit
that referenced
this issue
Feb 16, 2023
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using IoT core with the Node.js mqtt client.
After a successful connection, if I try to publish a message, the connection gets closed. Is it a normal behavior?
Anybody tested the mqtt_example ?
I'm publishing to the standard topic
/devices/<DEVICE_ID>/eventsThe text was updated successfully, but these errors were encountered: