ShellyPro3EM en ligne mais sans remontées d'infos

Bonjour à tous,

J’utilise MQTT manager pour différentes applications.
Venant d’acquérir un ShellyPRO3EM, j’ai suivi les différentes discussions pour l’installer via JMQTT.
Mais je bloque car les remontées d’infos sont manquantes, malgré qu’il soit vu en ligne :

De plus dans les logs de JMQTT, j’ai bien des messages qui arrivent du Shelly :

4234|[2026-05-05 22:54:53,102] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014490.04,"em1:0":{"act_power":-3.1,"aprt_power":416.3,"current":1.801,"freq":50.0,"pf":0.01,"voltage":231.0}}}", QoS=1, retain=False)
4235|[2026-05-05 22:54:53,104] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1:0", payload="{"id":0,"voltage":231.0,"current":1.801,"act_power":-3.1,"aprt_power":416.3,"pf":0.01,"freq":50.0,"calibration":"factory"}", QoS=1, retain=False)
4236|[2026-05-05 22:54:58,100] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014494.04,"em1:0":{"act_power":-5.5,"aprt_power":416.8,"current":1.803,"freq":50.0,"pf":0.01,"voltage":230.9}}}", QoS=1, retain=False)
4237|[2026-05-05 22:54:58,102] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1:0", payload="{"id":0,"voltage":230.9,"current":1.803,"act_power":-5.5,"aprt_power":416.8,"pf":0.01,"freq":50.0,"calibration":"factory"}", QoS=1, retain=False)
4238|[2026-05-05 22:55:00,323] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014500.07,"em1data:0":{"total_act_energy":84.28,"total_act_ret_energy":12.39}}}", QoS=1, retain=False)
4239|[2026-05-05 22:55:00,326] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1data:0", payload="{"id":0,"total_act_energy":84.28,"total_act_ret_energy":12.39}", QoS=1, retain=False)
4240|[2026-05-05 22:55:00,326] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1data:1", payload="{"id":1,"total_act_energy":377.26,"total_act_ret_energy":19.48}", QoS=1, retain=False)
4241|[2026-05-05 22:55:00,327] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1data:2", payload="{"id":2,"total_act_energy":135.19,"total_act_ret_energy":926.79}", QoS=1, retain=False)
4242|[2026-05-05 22:55:00,327] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1:0", payload="{"id":0,"voltage":230.8,"current":1.799,"act_power":-3.0,"aprt_power":415.6,"pf":0.01,"freq":50.0,"calibration":"factory"}", QoS=1, retain=False)
4243|[2026-05-05 22:55:00,329] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyEvent","params":{"ts":1778014500.08,"events":[{"component":"em1data:0","id":0,"event":"data","ts":1778014440.00,"data":{"ts": 1778014440,"period": 60,"values":[[0.0000,0.0616,0.0000,0.0000,1.6,-7.7,417.8,414.6,231.011,230.400,230.798,1.808,1.796,1.802 ]]}}]}}", QoS=1, retain=False)
4244|[2026-05-05 22:55:00,330] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014500.12,"em1data:1":{"total_act_energy":377.26,"total_act_ret_energy":19.48}}}", QoS=1, retain=False)
4245|[2026-05-05 22:55:00,333] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyEvent","params":{"ts":1778014500.12,"events":[{"component":"em1data:1","id":1,"event":"data","ts":1778014440.00,"data":{"ts": 1778014440,"period": 60,"values":[[0.0001,0.0002,0.0000,0.0000,0.0,0.0,8.2,7.7,231.006,230.405,230.797,0.035,0.033,0.034 ]]}}]}}", QoS=1, retain=False)
4246|[2026-05-05 22:55:00,335] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014500.17,"em1data:2":{"total_act_energy":135.19,"total_act_ret_energy":926.79}}}", QoS=1, retain=False)
4247|[2026-05-05 22:55:00,338] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyEvent","params":{"ts":1778014500.17,"events":[{"component":"em1data:2","id":2,"event":"data","ts":1778014440.00,"data":{"ts": 1778014440,"period": 60,"values":[[0.0000,3.8786,0.0000,0.0000,-229.3,-236.5,245.6,238.4,231.031,230.429,230.827,1.062,1.032,1.047 ]]}}]}}", QoS=1, retain=False)
4248|[2026-05-05 22:55:00,340] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014499.04,"em1:0":{"act_power":-3.0,"aprt_power":415.6,"current":1.799,"freq":50.0,"pf":0.01,"voltage":230.8}}}", QoS=1, retain=False)
4249|[2026-05-05 22:55:03,097] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014501.03,"em1:0":{"act_power":-5.6,"aprt_power":418.3,"current":1.811,"freq":50.0,"pf":0.01,"voltage":230.8}}}", QoS=1, retain=False)
4250|[2026-05-05 22:55:03,099] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1:0", payload="{"id":0,"voltage":230.8,"current":1.811,"act_power":-5.6,"aprt_power":418.3,"pf":0.01,"freq":50.0,"calibration":"factory"}", QoS=1, retain=False)
4251|[2026-05-05 22:55:06,096] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014504.03,"em1:0":{"act_power":-1.2,"aprt_power":416.0,"current":1.801,"freq":50.0,"pf":0.00,"voltage":230.7}}}", QoS=1, retain=False)
4252|[2026-05-05 22:55:06,097] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1:0", payload="{"id":0,"voltage":230.7,"current":1.801,"act_power":-1.2,"aprt_power":416.0,"pf":0.00,"freq":50.0,"calibration":"factory"}", QoS=1, retain=False)
4253|[2026-05-05 22:55:08,095] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014507.03,"em1:0":{"act_power":-1.0,"aprt_power":415.7,"current":1.800,"freq":50.0,"pf":0.01,"voltage":230.7}}}", QoS=1, retain=False)
4254|[2026-05-05 22:55:08,097] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1:0", payload="{"id":0,"voltage":230.7,"current":1.800,"act_power":-1.0,"aprt_power":415.7,"pf":0.01,"freq":50.0,"calibration":"factory"}", QoS=1, retain=False)
4255|[2026-05-05 22:55:10,094] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/events/rpc", payload="{"src":"shellypro3em-5c013b05bed4","dst":"shellypro3em-5c013b05bed4/events","method":"NotifyStatus","params":{"ts":1778014509.03,"em1:0":{"act_power":-6.3,"aprt_power":415.9,"current":1.801,"freq":50.0,"pf":0.01,"voltage":230.7}}}", QoS=1, retain=False)
4256|[2026-05-05 22:55:10,095] INFO  Client879       Brk879Th        on_message() : Message received (topic="shellypro3em-5c013b05bed4/status/em1:0", payload="{"id":0,"voltage":230.7,"current":1.801,"act_power":-6.3,"aprt_power":415.9,"pf":0.01,"freq":50.0,"calibration":"factory"}", QoS=1, retain=False)

J’ai bien respecté la syntaxe du topic, le Qos est à 1 (dans MQTT manager il est à 0)

Est-ce que cela vient du retain = false?

Pour info j’ai utilisé le template Shelly pro 3EM.

Par avance merci pour votre aide.

Bonjour,
je suppose que vous avez utilisé un template pour créer l’objet. Je vous conseille de cocher la case ‹ ajout automatique des commandes › pour que ce soit l’appareil qui remplisse les commandes.
Sinon, vérifiez que vous utilisez les bon chemins. sur le mien, ils sont différents de votre copie d’ecran:
xxxxx/xxxxx/status/em1:0
xxxxx/xxxxx/status/em1:2
etc…

1 « J'aime »

Bonjour,
Pourquoi utiliser jMQTT ? On peut l’intégrer directement dans MQTT Manager, avec la découverte des commandes…

Bonjour @mjeanne,

Merci pour la piste, en effet, il me manquait les commandes que j’ai créées une à une avec le bon topic.
Un peu long mais ça fonctionne!

Bonjour @MaGoo ,
Je me suis posé la question lorsque j’ai installé mon Shelly…
Mais je ne sais pas dire quels sont les avantages et inconvenients de chacun des plugins.
Utilisant déjà MQTT Manager, ce ne serait pas déconnant.
Je vais chercher et tester…

Dans le shelly, tu active MQTT avec l’adresse de Jeedom (login et pass si besoin).
Tu créé un objet avec le topic de ton shelly et active la découverte auto.
Tu vas voir arriver les infos.

Utiliser jMQTT, c’est, d’après moi, pour que Jeedom soit client et se connecte à un autre broker externe.

Ah oui en effet très simple!
Merci @MaGoo pour l’info!
Question, on a un recap des noms de chaque commandes pour savoir à quoi cela correspond? Certaines sont faciles à déduire, d’autres moins…
Comme :

  • eventsrpcparamsevents0datavalues0x
  • eventsrpcmethod
  • etc

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.