NodeManager: plugin for a rapid development of battery-powered sensors
-
@gohan
Definitely, if I put a pir sensor to monitor a security access I will never know if I had an intrusion if I have a false alarm
-
if it reports "no motion" it is not a false alarm. The important thing is it must report when there is "motion"
-
@gohan said in NodeManager: plugin for a rapid development of battery-powered sensors:
if it reports "no motion" it is not a false alarm. The important thing is it must report when there is "motion"
Agree with what @gohan says. But I'll look into this anyway @mar-conte, reporting no motion when waking up should not happen even if it is a minor issue (https://github.com/mysensors/NodeManager/issues/71). What should not happen at all is reporting motion (payload 1) but as far as I've understood this is the case.
Thanks
-
@user2684
So with version 1.5 do I solve my problem too?
-
I noticed that the battery report if set to one hour does not happen every hour ...
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
So with version 1.5 do I solve my problem too?
I'll look into it by then. Feel free to follow the github issue to see how it will evolve. Thanks!
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
I noticed that the battery report if set to one hour does not happen every hour ...
More details please
Does not happen at all, it is not regular, happens every other hour, etc. what is the case?
Thanks!
-
@user2684
It happens even if i put 6 hours or every 3 hours so in the specified hours it is not regular the report sometimes jumps some report
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
It happens even if i put 6 hours or every 3 hours so in the specified hours it is not regular the report sometimes jumps some report
Ok, I'd probably need both MySensors and NodeManagers's logs to troubleshoot this, just to ensure there is no failure in sending out the messages as I've seen in the other logs you have previously shared.
Thanks!
-
@user2684
Ok Tanks
-
Then solved the problem of the accuracy of the battery report: basically I did not realize that the sleep wait time started from the last pir movement then if i put an hour of sleep and during this active time the pir time resumes; The communication problems I solved them by letting antenna from rfm69 so every hour the battery report does not even send pir moviment
....Very strange my rfm69 modules communicate better without an antenna even at a distance of 10 meters with a wall
-
There is a risk of damaging the radio module if you don't use an antenna. Also a wrong tuned antenna will make transmitting more difficult.
-
@gohan
Ok Tanks, but the 86 mm wire for 868 what is Ideal diameter and thread type for simple antenna no dipole e non ground ant?
-
Found in another forum
433 1/4 wave = 164.7mm
433 1/2 wave = 329.4mm
433 full wave = 692.7mm868 1/4 wave = 82.2mm
868 1/2 wave = 164.3mm
868 full wave = 345.5mm915 1/4 wave = 77.9mm
915 1/2 wave = 155.9mm
915 full wave = 327.8mmTry shortening a little bit. What kind of wire are you using?
-
@gohan
Wery good Tanks gohan
-
@gohan
Normal wire electric 1 mm diameter
-
Single core or threaded?
-
@gohan
Threaded
-
You need to use single core, that's why it is not working well
-
@gohan
Should it be isolated or even without a sheath?
-
I think you can leave insulation on; there are some guides on how to make antennas for rfm69,just Google it. In addition there are also spring single wire antennas for different frequencies you can buy.
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
I did not realize that the sleep wait time started from the last pir movement then if i put an hour of sleep and during this active time the pir time resumes
Yes, when the pir wakes the node up, the sleep is aborted and when going back to sleep, it starts from scratch without resuming it. If this is not creating an issue, I'll keep the current behavior. Regarding the antenna, I'm using the small antennas from the store for my RFM69 and have a decent range without big issues.
-
@user2684
Tanks of course bye
-
I'm trying to build sensor to drive 3 relays and connect it to Domoticz. Simple sketch:
// before void before() { // setup the serial port baud rate Serial.begin(MY_BAUD_RATE); /* * Register below your sensors */ int przek1 = nodeManager.registerSensor(SENSOR_RELAY,3); int przek2 = nodeManager.registerSensor(SENSOR_RELAY,4); /* * Register above your sensors */ nodeManager.before(); }sensors are visible into Domoticz as switches but It's not possible to turn it on/off from Domoticz. It looks that Nodemanager expect REQ message to change state of relay but Domoticz sends SET message to change state:
RECV S=0 I=3 C=1 T=2 D=1
RECV S=0 I=3 C=1 T=2 D=0When I've used MYSController and send C_REQ message all is working fine.
I think that in case of "output" sensors logic of getting/setting should be reversed.
-
Hello, I think I was able to implement most of the requests discussed here during the last few weeks in a pre-release v1.5 version. Please consider it still as a dev release which gone through very limited testing but since I had to make quite a few changes to core code, would be great to start collecting some feedback now.
Is is available here: https://github.com/mysensors/NodeManager/tree/9a485cdcaf8e9856219338553335e2dce7253eb3
It is complicated to reference each of you who requested something so please whoever is interested the full list of new additions/fixes is available here https://github.com/mysensors/NodeManager/milestone/5?closed=1. I did my best to add verbose comments so you should find all the details there. Please add any comment and report any problem directly to the existing issues on github so I can better understand the context. The documentation has been updated as well.
Thanks
-
-
I've just pushed out 1.5-dev3 on https://github.com/mysensors/NodeManager/tree/702a05c7e2f4425c188d5abf62b4a119fea29bc8 fixing a critical bug for the BME280 sensor and providing a way to automatically detect which i2c address the sensor is on for both BME280 and BMP085/BMP180 if anybody is interested.
I'm planning some additional tests so to release a stable v1.5 in a week or two (unfortunately starting from June the real life will become very demanding with me). So please share any feedback by then in case you will have the chance to test the latest dev release. Thanks
-
Just in time, I am going to get my BME280 sensor soon
-
May I ask you a favor? Could you add also the MCP9808 I2C sensor?
-
@gohan done but I don't have such a sensor to test the code so if you could give it a try I'd really appreciate it. Available in v1.5-dev4 you can get from here: https://github.com/mysensors/NodeManager/tree/38fd51c99e47b6ec90f4885ff1cb0cfe33857ab4.
Instructions on https://github.com/mysensors/NodeManager/issues/87
Thanks!
-
Can you please consider support for MCP23017 IO-Expander And TTP226/TTP229 Touch control sensor modules in I2C mode?
-
I can help test them both for sure...
Will it be a good idea to have external file based extension to Node Manager?
I will like to extend the configuration child and probably add node authentication through another security-child. Self Healing Network capabilities are next on my list.
-
@user2684 Sorry for noob question but how do I get data from the sensors?
I have registered sensors like this to test them outnodeManager.setSleep(SLEEP, 10, MINUTES); nodeManager.registerSensor(SENSOR_MOTION, 3); nodeManager.registerSensor(SENSOR_BME280); nodeManager.registerSensor(SENSOR_MCP9808);
-
@vikasjee tracking both with https://github.com/mysensors/NodeManager/issues/90 and https://github.com/mysensors/NodeManager/issues/92. Mean while I will order the samples and wait for their delivery, if you have any link with demo code to share, please feel free to do so on the two github issues.
Regarding the external file based extension, this is definitively a good idea. I did spend some time at the beginning trying to identify the best way to package this but my weak programming skills prevented me to identify an optimal solution I'm sure. I did not go for multiple files mainly because I thought during upgrade this would have required overwriting multiple files in multiple projects so I gave up. As a workaround, I also tried to put all NodeManager's files in a dedicated folder or create an arduino library but it didn't work (but don't remember why).
So the only way now to expand the existing code in a clean way is to write in your main sketch an inline class deriving from the Sensor class or the other NodeManager's classes and use registerSensor() providing an instance of this class. But I am of course open to any other better way to achieve the same
-
@gohan since you have set a sleep interval of 10 minutes, what you should see in the logs (and in your gateway) is NodeManager starting up, presenting all the child nodes (one of more for each sensor), running SENSOR_BME280's and SENSOR_MCP9808's onLoop() and a bunch of messages set out with the measures and finally going to sleep for 10 minutes and waking up and sending out a V_TRIPPED message if SENSOR_MOTION triggers.
Generally speaking you can get the measures in the serial output, in the controller or by sending the node a REQ message to each of the child ids. Do you see something different?
Thanks
-
Ok, I mean from code like if I want to use them to show on local LCD
-
@gohan never thought about it but it is a good idea to add some "output" capabilities. Tracking this with https://github.com/mysensors/NodeManager/issues/95 but would require some time since it has a few dependencies. Thanks!
-
I'll give you a feedback sooner or later... I lost so many hours trying to figure out what was wrong with my test sensor but at the end it was a fried nrf24 module that was working since some time ago
-
I've added a rain gauge out-out-the-box sensor for the latest dev release called 1.5-dev5 (https://github.com/mysensors/NodeManager/tree/126812a9d01311640416222be8225fdcca1e7266). This is intended to be the last enhancement for the upcoming v1.5 version but of course I'll wait for some additional days to collect (and fix) any issue all the new sensors might have.
The implementation of the rain gauge sensor has to be different than the one from the build section for a good number of reasons and limitations. All the details here: https://github.com/mysensors/NodeManager/issues/90.
-
Sorry but the name of the sketch can be different both in the node and in the gateway?
-
Sure, that's for your use to know what software is running on each sensor
-
@gohan
Should the gateway have the right nodemamager sketch?
Tanks
-
Why do you need nodemanager on gateway?
-
@gohan
User2694 say:"Setup MySensorsSince NodeManager has to communicate with the MySensors gateway on your behalf, it has to know how to do it. Place on top of the config.h file all the MySensors typical directives you are used to set on top of your sketch so both your sketch AND NodeManager will be able to share the same configuration. For example:"
link text
-
He is referring on the node side, on the gateway you can just run the default sketch
-
@gohan
Ok Tanks
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
Should the gateway have the right nodemamager sketch?
Just to confirm what already discussed: a node/sensor with NodeManager running does not require a gateway with NodeManager on it. Generally speaking, there are two situations in which you may want use NodeManager on a gateway as well (available starting from v1.5):
- It as to run on a Sonoff device which requires to be configured as a gateway
- The gateway has sensors attached to it so you may want to use NodeManager's capabilities to configure your sensors in an easy way
There is also a third situation: you are just lazy and have NodeManager already open in the arduino IDE so you just configure the gateway's settings in config.h and upload the sketch
-
-
Last chance guys to report any issue for those who had tested the dev version of v1.5
The final version will be out in a day or two otherwise.Thanks!
-
I am waiting for the LCD mod
-
@gohan LCD unfortunately has to wait for the another release (https://github.com/mysensors/NodeManager/issues/95), I would like to find a way to provide the info on the LCD without the need for the user to configure it for every sensor but this would require investigating on the best generic approach and will take some time
-
If you could provide a method to retrieve sensor data from main loop(), it is quite easy for everyone to print it to LCD
-
@gohan I wonder if something can be done even right now based on what you're saying. In the main sketch, after invoking nodeManager.loop(), you can actually retrieve the instance of each sensor and do something. The last "value", depending on the type of the sensor, is stored in a variable (e.g. _value_int) BUT it is private. I'll add a getValue() function so you can get out this value. Not ideal but I think it can be a workaround I can easily add before releasing 1.5 (https://github.com/mysensors/NodeManager/issues/104)
-
The problem is how do I know the name of the instance of the sensors
-
@gohan I mean if you declare a global int to store the child id, then you can save it when calling registersensor() (which returns the id of the sensor) in before() so eventually in loop() you can call getSensor() and then retrieve the value or do whatever else. Something like:
NodeManager nodeManager; int sensor_id; void before() { Serial.begin(MY_BAUD_RATE); sensor_id = nodeManager.registerSensor(SENSOR_THERMISTOR,A1); nodeManager.before(); } void loop() { nodeManager.loop(); float value = ((SensorThermistor*)nodeManager.getSensor(sensor_id))->getValueFloat(); }Just the getValueFloat() is missing. Not ideal but a starting point. Don't you think? Thanks!
-
That would work, at least for me
-
@gohan cool, just added it to the dev code. I'm packing now the final v1.5 and about to post it here in a few minutes. Thanks!
-
At least now we can add some more code besides the default created by nodemanager
-
Very true also because I'd avoid having the users customizing their NodeManager.cpp (even if it is always possible) to prevent issues during the upgrade. For your information the alternative to create an inline class inheriting from Sensor and then invoking registerSensor() with an instance of this class is always valid even if clearly much more complex.
-
Version 1.5 of NodeManager is finally available here!
https://github.com/mysensors/NodeManagerI've done my best to implement most of the requests received so far since unfortunately I'm expecting starting from June very little spare time to spend here so I tried to hurry up a bit
The result is a pretty long change log and a total of 26 between ad-hoc and generic out-of-the-box sensors supported up to this release:- Added support for ACS712 current sensor
- Added support for HC-SR04 distance sensor
- Added support for BMP085/BMP180 temperature and pressure sensor
- Added support for Sonoff smart switch
- Added support for Rain Gauge sensor
- Added support for MCP9808 temperature sensor
- Added forecast output to all Bosch sensors
- Added I2C address auto-discovery for all Bosch sensors
- Added support for running as a gateway
- Added option to retrieve the latest value of a sensor from outside NodeManager
- Remote reboot now does not need a reboot pin configured
- A heartbeat is now sent also when waking up from a wait cycle
- When waking up for an interrupt, only the code of the sensor expecting that interrupt is executed
- Added capability to retrieve the time from the controller
- Optimized battery life for DS18B20 sensors
- SLEEP_MANAGER has been deprecated (now always enabled) and setMode() replaces setSleepMode()
- New mode ALWAYS_ON to let the node staying awake and executing each sensors' loop
- ESP8266WiFi.h has to be included in the main sketch if MY_GATEWAY_ESP8266 is defined
- Added receiveTime() wrapper in the main sketch
- Fixed the logic for output sensors
- Added common gateway settings in config.h
I've added upgrade instructions as well in the documentation. Generally speaking to upgrade it is safe to just replace the existing NodeManager.h and NodeManager.cpp files but with this release I had to do some minor changes to the main sketch as well, as documented in the release notes.
Thanks everybody for all the advice and for reporting any issue always in a constructive way
-
Hi, only for those having problems with a too high utilization of the dynamic memory preventing NodeManager to run smoothly (e.g. generating random data / outputting garbage characters / rebooting, etc), a quick fix is to decrease from 255 to a small number like 5 or 10 the size of the Sensor* _sensors array. This saves more than 20% on a pro mini which is huge. Of course you also need to change every cycle in NodeManager.cpp which is using that 255.
This of course will be also fixed in the next release. Very silly mistake I know to initialize such a big array but I couldn't image 255 pointers were consuming so much
-
Hi, i wanted to know in which section of the sketch I turn on and turn off a led when the node controls the battery because at night the led me starts the pir; Now I've put the digitalwrite after nodemanger.loop
-
@mar.conte NodeManager does not control any led so I think you are free to place your code where you think is most appropriate for your needs. Thanks
-
@mar.conte put a capacitor on the PIR vcc/gnd and increase the size until it is stable.
-
@gohan
Good idea Tanks
-
Hi, I've added a "How to contribute" section in the documentation of the dev release in case anybody is interested to contribute to this project: https://github.com/mysensors/NodeManager/tree/development#contributing.
I'm not a git expert so I hope those instructions to have some sense
-
Pretty big enhancement in the development branch of NodeManager if anybody is interested. I spent quite a good amount of time working on the core code to introduce mainly two features opening up the door to a good list of enhancements.
The first one is a sort of countdown utility. Can be based on the number of sleeping cycles or minutes. It detects automatically a sleeping node and instead of using millis sum up the sleep interval and reports when the time is over. This approach has been used to:
- Allow different sensors reporting at different timeframes (e.g. by configuring a specific sensor to report every e.g. 5 minutes or 10 sleeping cycles instead of at the end of each cycle)
- For output sensors optionally use the input value as an elapsed time (e.g. the output will be turned on and the input value will be used as a timer to turn it off automatically). For example by sending 3 to a relay, it will be turned on and after 3 minutes turned off automatically. Useful if you already know for how long the output should stay on.
- For output sensors optionally set a safeguard (e.g. after a relay is set to on, turn it off automatically after 1 hour). Useful if e.g. you are controlling a boiler and you are afraid something could prevent the command to turn it off to reach the board.
- Add timeframe option for reporting battery level (e.g. instead of reporting every 10 sleeping cycles, report every 1 hour regardless of how long is the sleeping cycles).
The other big change is a an complete remote API. With the current version you could send to NodeManager's service child id a limited list of commands to change the behavior of the board remotely, mainly to alter the duration of the sleep cycle. In the development release instead, almost every function of both NodeManager AND of every sensor can be invoked remotely. This is done by sending a V_CUSTOM message with a function_id and optional value to pass along to the service child id or each sensor's child id. More details here: https://github.com/mysensors/NodeManager/tree/development#communicate-with-nodemanager-and-its-sensors
This development branch is available here: https://github.com/mysensors/NodeManager/tree/development
-
Do you think it may be possible to add the function to use a digital pin to power a PIR sensor to turn it on only when setting it armed? (to save a little power)
-
Why does the power manager use two pins to power the sensor? Could we just use one pin for Vcc, and assume that the GND is permanently connected?
-
But i'm trying to test a Pir of panasonic EKMB1201113 papirs series cost a bit but they have low power consumption
1 to 100 microampers in sleep mode, just connect a 100 kohm resistance in pulldown and it is very precise up to 12 meters
-
@gohan interesting use case. I personally prefer to have the arm/disarm logic on the controller but I can understand there are also different situations. I've opened https://github.com/mysensors/NodeManager/issues/138 for this. Thanks for the suggestion!
-
@rakeshpai said in NodeManager: plugin for a rapid development of battery-powered sensors:
Why does the power manager use two pins to power the sensor? Could we just use one pin for Vcc, and assume that the GND is permanently connected?
I usually use the power pins when either I need to save power or I do not have vcc/gnd pins available on the arduino board. But yes, you're right, there are other scenarios to consider. I've opened https://github.com/mysensors/NodeManager/issues/139 for this. Thanks
-
saving pins is always good
-
Hello how can i enter the commands type 254; 200; 2; 0; 48; BATTERY in a lua script of domoticz?
-
@mar.conte said in NodeManager: plugin for a rapid development of battery-powered sensors:
Hello how can i enter the commands type 254; 200; 2; 0; 48; BATTERY in a lua script of domoticz?
Sorry, I don't use domoticz so I cannot help with that. I hope somebody else here will have an answer for you
-
Guys, @hek has been so kind to offer a dedicated section within the forum for NodeManager so feel free to open new topics directly under https://forum.mysensors.org/category/43/nodemanager. I hope this can facilitate new users to better find the answers they are looking for and you guys to follow the discussions in a smoother way without the need to jump here and there along the same long thread.
-
Hello All,
I've just released on GitHub (https://github.com/mysensors/NodeManager) a hotfix (v1.5.1) for NodeManager in order to include the memory optimization improvements already part of the development version.
This is to allow saving up to 20% of memory on a pro mini and prevent the board to crash or become unpredictable when approaching the memory limit. No new features or enhancements have been added to this hotfix.
If instead interested in testing out the development version or contribute please refer to https://github.com/mysensors/NodeManager/tree/development and https://github.com/mysensors/NodeManager/milestone/7.
Thanks
-
Hello, NodeManager's version 1.6 is almost ready. Plenty of new things and fixes are about to be available but I'd need some diverse testing before officially releasing it.
The first step would be to ensure that what was working with the current version is still working with this new release
All the new things are instead detailed here https://github.com/mysensors/NodeManager/issues?utf8=✓&q=milestone%3Av1.6 is%3Aclosed label%3Afixed and in the associated PRs.
The code is available at https://github.com/mysensors/NodeManager/tree/development.
Whoever is willing to give it a try, please report any issue directly on github whenever there is already an issue open or on https://forum.mysensors.org/topic/7266/nodemanager-v1-6-dev-comments-and-issues otherwise.
Ideally I'm targeting mid August for releasing a stable v1.6.
Many thanks!
-
@user2684
Hello,
I'm using NM for all my projects and I really like it!
Will NodeManager support APDS-9960 RGB and Gesture Sensor in the future?Thanks
-
@Getz99 thanks for your feedback! I've created https://github.com/mysensors/NodeManager/issues/201 to track this request. Keep in mind no new features will be part of v1.6 which should be released soon so I've added this to the v1.7 backlog. Thanks
-
@user2684 Thanks! I understand it will not be in v1.6, I'm waiting for that release!
-
Hi, kind of the the last chance to share any feedback regarding NodeManager v1.6-dev which is almost ready and should be out in a week or two.
Instructions on how to test the pre-release and report issues here: https://forum.mysensors.org/topic/6183/nodemanager-plugin-for-a-rapid-development-of-battery-powered-sensors/184
Thanks!
-
Hello All,
NodeManager v1.6 is finally available! Download and upgrade instructions can be found as always on https://github.com/mysensors/NodeManager
First of all I want to thank everybody contributing to the project, especially those who have submitted pull requests to the repository.
In v1.6 we have 36 out-of-the-box sensors as well as a good number fixes and enhancements. The most notable are for sure the capability to customize any sensor remotely through a brand new remote API and a more flexible and effective way to configure reporting intervals and sleep cycles:
- Introduced new remote API to allow calling almost ALL NodeManager's and its sensors' functions remotely
- Reporting interval configuration is now indipendent from the sleep cycle
- Reporting interval can be customized per-sensor
- All intervals (measure/battery reports) are now time-based
- Added support for BMP280 temperature and pressure sensor
- Added support for RS485 serial transport
- Added support for TSL2561 light sensor
- Added support for DHT21 temperature/humidity sensor
- Added support for AM2320 temperature/humidity sensor
- Added support for PT100 high temperature sensor
- Added support for MH-Z19 CO2 sensor
- Added support for analog rain and soil moisture sensors
- Added support for generic dimmer sensor (PWM output)
- Added support for power and water meter pulse sensors
- Radio signal level (RSSI) is now reported automatically like the battery level
- SensorRainGauge now supports sleep mode
- SensorSwitch now supports awake mode
- SensorLatchingRealy now handles automatically both on and off commands
- SensorMQ now depends on its own module
- Added safeguard (automatic off) to SensorDigitalOutput
- Any sensor can now access all NodeManager's functions
- DHT sensor now using MySensors' DHT library
For those who have previously forked the repository, please ensure to merge the updated development branch first before submitting any new PR.
Thanks!
-
Hi,
thanks again for your great work!
As I said, I will try to include my Chirp module into 1.7 via a github branch/fork. You wrote in your explanation of "contributing to the code", that it is not allowed, to change config.h. But how should I include the lines for the chirp sensor?
And in wich way can the documentation be modified? (chirp sensor paramaters)Best regards
Betonmoewe
-
@betonmoewe if I wrote that config.h cannot be changed, I wrote something wrong
You can change whatever of course, just keep changes to config.h and the main sketch to the minimum since those can only be upgraded manually and not just by replacing the files. To add a new sensor, have a look at one of the existing sensors. Documentation can be updated as well by changing the README file. Should you have any doubt or issue feel free to open a new thread on https://forum.mysensors.org/category/43/nodemanager. Thanks!
-
When do you plan to release V1.7 ?
-
@vikasjee realistically it will take a while unfortunately
I'm now spending most of my little spare time on https://github.com/mysensors/NodeManager/pull/229 which is kind of difficult to fix. Only after I will go through the (long) list of fixes/requests queued for v1.7
-
@vikasjee FYI the blocking issue which was slowing down v1.7 development has been solved now (https://forum.mysensors.org/topic/6534/nodemanager/133). Still a long way to get there but at least a bit closer now
Thanks
-
Hi @user2684
Is it possible to add sensor MG996R Servo in V1.7? I know the list is long for fixes but it would be nice if you could squeeze it in.Thanks!
-
@getz99 I've added this feature request for this: https://github.com/mysensors/NodeManager/issues/253
Thanks!
-
@user2684 Thanks, Very much appreciated!
-
I grabbed the latest development branch tonight to try this out. I saved the NodeManager.ino as a new name and copied the NodeManagerLibrary.h and NodeManagerLibrary.ino files into the new folder. I enabled USE_DIGITAL_OUTPUT and added a SensorDigitalOutput and SensorRelay child in my sketch and tried to compile. Unfortunately I got these errors:
In file included from ino:244:0: sketch/NodeManagerLibrary.h:549:27: error: 'SR_RX_RSSI' was not declared in this scope int _signal_command = SR_RX_RSSI; ^ /NodeManagerLibrary.ino: In member function 'virtual void SensorSignal::onLoop(Child*)': /NodeManagerLibrary.ino:741:45: error: 'signalReport_t' was not declared in this scope int16_t value = transportGetSignalReport((signalReport_t)_signal_command); ^ /NodeManagerLibrary.ino:741:75: error: 'transportGetSignalReport' was not declared in this scope int16_t value = transportGetSignalReport((signalReport_t)_signal_command); ^ exit status 1 Error compiling for board Arduino Nano.All seems to be related to signal reports but even if I disable signal reporting the errors still occur. Guessing I did something wrong so any ideas would be appreciated.
Thanks!
-
@jsiddall thanks for this hit, the issue seems to be related to SR_RX_RSSI which is only available with 2.2.0-beta version of the MySensors library, not 2.1.1 which I guess you are using. Something which needs to be fixed on the NodeManager's side, I've opened https://github.com/mysensors/NodeManager/issues/256 for this. Thanks
-
@user2684 Great, thanks for the quick response.
UPDATE: Confirmed, all is good with MyS 2.2.0-rc2. Not sure what resolution you had in mind for issue #256 but a note in the installation section of this page:
https://www.mysensors.org/download/node-manager
...stating the required version of MyS for both the stable and dev versions of NodeManager would probably have been enough to keep me out of trouble!
Thanks again for NodeManager. It does everything I had been doing manually before, using pages of sketch, and shrinks it down to a few simple lines.
-
@jsiddall thanks, fixed in the development branch right now. Adding a compatibility table between NodeManager and the MySensors library version sounds like a good idea, I've added https://github.com/mysensors/NodeManager/issues/261 for this. Thanks again
-
GHi, the rfm95 is compatible with nodemanager?
And the esp32 also?
-
@mar-conte everything supported by the core MySensors library is supported by NodeManager since using the same code behind the scene but I'll add some default defines in the main sketch to make this configuration easier (https://github.com/mysensors/NodeManager/issues/262). Thanks
-
@user2684
Ok Tanks
-
I need help!!!
I have e mcp23017 Matrix espander i/o in esp nodemecu board, the mcp receive state sensor from my system wired alarm(pir, sismic etc) ; this signal received i want send to my domoticz controller, is the sensor custom the solution? Can i present 16 input sensors from my node to my controller?
Tanks
-
@mar-conte if using NodeManager, this is still not possible since mcp23017 is not supported by NodeManager yet. Thanks!
