Giter Site home page Giter Site logo

jeedom_mysensors's People

Contributors

azema avatar dough29 avatar lucguinchard avatar lujien39 avatar lunarok avatar octera avatar sarakha63 avatar yogui79 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

jeedom_mysensors's Issues

Les nouveaux nœuds ne sont pas détectés par Jeedom

Bonjour,

je fais suite au sujet ouvert sur le forum Jeedom ici : https://www.jeedom.com/forum/viewtopic.php?f=35&t=20324

Je créé hier un nouveau nœud MySensors sur une installation toute neuve et à jour sur un Raspberry Pi.

Dans les logs tout semble fonctionner car je reçois bien les messages du nœud dans le log Jeedom/MySensors :

Wed Nov 09 2016 00:00:47 GMT+0100 (CET) : http://192.168.0.3:80/plugins/mySensors/core/api/jeeSensors.php?apikey=APIKEY&gateway=master&messagetype=saveValue&sender=1&sensor=3&type=16&payload=1
Wed Nov 09 2016 00:00:47 GMT+0100 (CET) : 1;3;1;0;16;1
Wed Nov 09 2016 00:01:16 GMT+0100 (CET) : http://192.168.0.3:80/plugins/mySensors/core/api/jeeSensors.php?apikey=APIKEY&gateway=master&messagetype=saveValue&sender=1&sensor=4&type=16&payload=0
Wed Nov 09 2016 00:01:16 GMT+0100 (CET) : 1;4;1;0;16;0

Malgré que le plugin soit en mode "inclusion" rien ne se passe côté Jeedom.

Toutes les traces sont en niveau debug et rien ne sort dans les divers logs Jeedom.

Request ne fonctionne pas

Bonjour,

Lors de l'envoi d'une commande de request depuis le noeud, la commande arrive bien dans le plugin, mais la réponse est un '0'.

sendTime => UTC time instead of local time

When you use "requestTime" function on a node to request date and time from the controller. The answer is always UTC time with jeedom.
If think local time is more usefull than UTC for IOT that don't know their timezone.
Tell me if i'm wrong .

can we use :
var payload = new Date().getTime()/1000 + new Date().getTimezoneOffset()*60;
instead of
var payload = new Date().getTime()/1000;

Regards,
Mathieu

Multiple EthernetGateway node id collision

Dear Lunarok,
i use jeedom and mysensors together since couple of years and it works very well.

I decided to replace my arduino+NRF24 nodes and my Arduino SerialGateway to a bunch of ESP32 nodes directly on WIFI.

  • I setup the Jeedom Mysensors plugin as Network Server
  • I configured my ESP32 Nodes as GATEWAY_ESP32 (because node doesn't exist for WIFI protocol in MySensors)

Issue:

  • MySensors ESP32 EthernetGateways have all the same NODE_ID=0 even if they have different source ip address. And Mysensors developpers said this is a core feature mandatory for the design.
  • Jeedom MySensors Plugin identify Nodes only by the NODE_ID
  • Consequence my ESP32 Nodes are all considered as only one single node which is not the case

MySensors developers said that "most of controllers support multiple gateway".
https://forum.mysensors.org/topic/10214/ethernet-wifi-client-gateway-enhancement/7?_=1589067494769&lang=en-US

Do you have any recommendation to fix this issue?

Problem of compatibility with Serial 6.0.0

Impossible to instanciate SerialPort with baudrate options (lower case)

var SerialPort = require('serialport');
        gw = new SerialPort(gwAddress, { baudrate: 115200 });
        //compatibilité avec la nouvelle verion de serialport
        if ( gw.settings.baudRate ){
                gw.settings.baudRate=115200;
        }
/var/www/html/plugins/mySensors/node/node_modules/serialport/lib/serialport.js:127
throw new TypeError(`"baudrate" is an unknown option, did you mean "baudRate"?`);
^
TypeError: "baudrate" is an unknown option, did you mean "baudRate"?
at new SerialPort (/var/www/html/plugins/mySensors/node/node_modules/serialport/lib/serialport.js:127:11)
at launchGateway (/var/www/html/plugins/mySensors/node/mysensors.js:230:9)
at Object.<anonymous> (/var/www/html/plugins/mySensors/node/mysensors.js:319:1)
at Module._compile (module.js:435:26)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Function.Module.runMain (module.js:467:10)
at startup (node.js:134:18)
at node.js:961:3

Mauvais baudrate par défaut

Bonjour, il me semble avoir trouvé une faute de frappe, dans "jeedom_mySensors/node/mysensors.js"
ligne 230, la variable 'baudrate' doit s'écrire 'baudRate' avec un 'R' majuscule, sinon la gateway sera toujours configurée en 9600Bd.
gw = new SerialPort(gwAddress, { baudRate: 115200 });
Cordialement,
linju.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.