Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Node.js Modules for MySensors

wpreul 19 Oct 2015, 17:49 last edited by

Here are a couple of node.js modules I wrote a while back for mysensors you all may find useful:

https://www.npmjs.com/package/sensors <- Parse and Stringify the protocol

https://www.npmjs.com/package/cowboymouth <- streams support for the protocol
Reply Quote 1
1 Reply Last reply
Loading More Posts
2
Posts

1.2k
Views
Reply

Reply as topic
Log in to reply
tbowmo Admin 20 Oct 2015, 06:19 last edited by

@wpreul

There are also modules available for node-red: http://forum.mysensors.org/topic/1965/nodered-injected-between-domoticz-and-mysensors

https://www.npmjs.com/package/node-red-contrib-mysensors
Reply Quote 0
1 Reply Last reply

2
Posts

1.2k
Views

Log in to reply

2 out of 2

Suggested Topics

Arduino Celebrates 10 years (Malmö/Sweden)
Announcements • 29 Mar 2014, 17:08 • hek 29 Mar 2014, 17:08

1

0
Votes

1
Posts

3.3k
Views

No one has replied
Home Assistant/MySensors quirks
Development • 17 Mar 2025, 02:35 • OldSurferDude 17 Mar 2025, 02:35

1

0
Votes

1
Posts

7
Views

No one has replied
LAN8720A - will mysensors work with this module
Development • 13 Nov 2024, 17:06 • Marcin 15 Nov 2024, 10:59

3

0
Votes

3
Posts

21
Views

15 Nov 2024, 10:59

Thanks for the answer. I meant that Mysensors has ESP32 support but only in terms of WIFI. It supports e.g. stm32 with ENC or W5500 modules - and the question is whether and how to add ESP32 support with LAN8720 module. I am not considering using ESPHOME or MQTT - I want to have native communication with the controller that implements my control schemes on its side. I try to program KC868-A16 but it does not matter - the question is whether such support can be added in a simple way.
MQTT-Help me understand about the MQTT Gateway.
Development • 2 Mar 2025, 01:44 • dpcons 12 Mar 2025, 23:39

11

0
Votes

11
Posts

46
Views

12 Mar 2025, 23:39

@dpcons MQTT sounds intimidating and looks imitimidating when you see all of the options available. Here's the scenario: You want to send a message. That's the -m option followed by a space and the message between " " the location, topic, is a tree, -t option, separated by forward slash / eg. MyRootTopic/MyTopicsSub/MyTopicSubSub It's as easy as that if your broker, the MQTT service (program) is on the same computer as the sending program. Usually it's not. Specifiy the location, the host, of the broker with the -h option followed by the host name or IP address The retain option, -r is important but explaining it is beyone the scope of this message Receiving, subscribing, to a topic is just the same, but you wouldn't have the -m message If you subscribe from the command line, the subscribe function waits indefinitely for messages published to the subscribed topic (unless you use the -C option) ^C to terminate the command. A tamotized device with the MQTT configured will create a number of topics on the broker. Home Assistant will see this automatically, if you have the Tasmota and MQTT Integrations installed. The MySensors MQTT gateway takes care of MQTT communication for a MySensors device. Again the MySensors and MQTT integrations. I use both. -OSD
Saving last known good state, but not in EEPROM
Development • 30 Jan 2024, 18:46 • OldSurferDude 15 Jan 2025, 08:51

6

0
Votes

6
Posts

33
Views

15 Jan 2025, 08:51

@OldSurferDude jus request counter states from controller on each reset, worked fine with Domoticz... or save in eeprom but increase location every write, on power up/reset search eeprom for largest value stored and carry on from that location, one long integer will fit 256 times in atmega328(p) eeprom, is that long enough for you ?
Radio waking up for no reason.
Development • 4 Jul 2020, 21:09 • Sasquatch 15 Jan 2025, 08:33

3

0
Votes

3
Posts

36
Views

15 Jan 2025, 08:33

Over 4 years on, and my node ran continuously sending 4 messages every 5 minutes. It's 700mAh LiFePo4 battery voltage dropped from initial 3.45V to 3.24V, according to LiFePo4 voltge/SoC tables It's just under 40% left. 700*60% = 420mAh. 100 mAH per year. using library 2.40 and blob message I could cut usage to ~25mAh/year, not bad

2
Online

11.5k
Users

11.1k
Topics

112.8k
Posts

Copyright 2019 TBD | Forum Guidelines | Privacy Policy | Terms of Service

1 / 1