Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle message with too short or incorrect topic #32

Closed
wants to merge 1 commit into from
Closed

Handle message with too short or incorrect topic #32

wants to merge 1 commit into from

Conversation

Domochip
Copy link

@Domochip Domochip commented Jan 2, 2021

Bonjour,

Petite gestion d'erreur concernant :

  • les publications MQTT courtes (1 seul niveau et payload non-JSON).
  • les publications MQTT finissant par '/' (payload non-JSON). (Ce second cas étant beaucoup plus rare :-D)

Exemple si on publie sur le topic "jeedomTest" le payload "90" :

[2021-01-02 23:42:12][DEBUG] : 16 : Client MQTT received PUBLISH (d0, q0, r0, m0, 'jeedomTest', ... (2 bytes))
[2021-01-02 23:42:12][DEBUG] : Message 90 sur jeedomTest
[2021-01-02 23:42:12][INFO] : Message texte : 90 pour information : jeedomTest sur :
[2021-01-02 23:42:12][INFO] : Saving device
[2021-01-02 23:42:12][ERROR] : Le nom de l'équipement ne peut pas être vide : MQTT Object ( [id:protected] => [name:protected] => [logicalId:protected] => [generic_type:protected] => [object_id:protected] => [eqType_name:protected] => MQTT [eqReal_id:protected] => [isVisible:protected] => 0 [isEnable:protected] => 0 [configuration:protected] => Array ( [topic] => [type] => topic ) [timeout:protected] => 0 [category:protected] => [display:protected] => [order:protected] => 9999 [comment:protected] => [tags:protected] => [_debug:protected] => [_object:protected] => [_needRefreshWidget:protected] => [_timeoutUpdated:protected] => [_batteryUpdated:protected] => [_changed:protected] => 1 )
[2021-01-02 23:42:12][DEBUG] : 16 : Client MQTT sending DISCONNECT
...

@Domochip Domochip closed this Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant