Posts made by lunarok

Yes please check jeedom forum (follow the link on the plugin page)
The answer is given (I m in holidays, so no update before next week)
This is due to core nodejs update (and you can solve it)

Better to give a link to the sketch and copy the original part of code :
https://github.com/mysensors/Arduino/blob/master/libraries/MySensors/examples/WaterMeterPulseSensor/WaterMeterPulseSensor.ino

And yes there is only one sensor presentated to the gateway :
// Register this device as Waterflow sensor
gw.present(CHILD_ID, S_WATER);

But there is 3 differents messages created on the same sensor. So there is on this node a waterflower sensor, but also a volume sensor and a counter sensor.
Why just one sensor ?

@GizMoCuz I see you have done the latest changes on this sketch and part of it was the declaration of 3 differents messages types with only 1 sensor. Is this volontary ?

Hi,

Thank for replies. But actually, I don't need power consuption but power emission.
This is a "health" value, able to compare the emission of waves by wifi, microwave and other RF.

Hi,

Anyone has informations about the power of emission of our lovely NRF ?
I find only the maximum of the antenna one, around 100mW (like WiFi) at maximum force.

Will be interested by the average power of a classic NRF on a sleepig node (when he wakes up of course) for exemple.
To compare with some other chips and standards.

Thanks if anyone see the information somewhere or has it for sharing.

@Terence-Faul : did you still get this issue ? around that time (1 month ago) there was a beta release of the plugin creating such error of loops, nothing about IR (my fault)

@hek : IRLib decode the message, so it's not so long, around 12 characters. I use it myself, the node send to the controler any code received and you can store them. I have a scenario in Jeedom that is storing all codes receive until I erase it, like this pressing multiples button, I get all of them.
After that, you can create a V_IR_SEND and as the input use any of the codes you have received.

But must be working only for a protocole decoded by IRLib (at that time, I have try only my Sony remote) If not decoded, yes RAW message is too long to be used. And of course better to know what type of protocol it is so (but it's possible to send this value in another sensor for exemple)

My bigger problem with this library, it's the hardcoded Sender in PIN 3 (I don't understand why, and make me impossible to use a motion sensor at same time)

Hi,

Is it possible to get a small schematics/howto for using ATSHA204 chip ? Maybe some references on the shop page for exemple.
Maybe newbie question, but look that the best for this signing feature will be to connect Arduino with this chip. Only information is on A3, ok but I will feel more confident with some schematic for newbies

Hi,

Will be very interested in the developpment of this subject.
As for the Jeedom controller, I'm waiting the "best" way to do this part.
It can be done to send information/order to a node only when he wakes up as long there is a sign of it.
But my problem is that yes, the sketchs using sleep never care about waiting for unexpecting under send when they are sleeping.

So for me, if you have a way to implement it on the sketch part with the actual protocol untouched, I will be happy to test it (we have already some user expecting a possibility to get an order when their nodes awake)

@Giacometti-Michele : your sensor present itself with an ID 0.
That's not possible, the sensor must have an ID of 1 at least.
Can you try a clear eeprom ?

Now Jeedom is translated in english/russian and partialy in spanish/indonesian/italian. If you like Jeedom maybe you can help (for the latest one ? :)) We use transifex for translating.

Hi,

A new wish. Possible to have the network gateway listening for nodes also on the ethernet network. Looking for ethernet nodes inside the electric panel. No RF, no security break

Hi,

As for now I have start using mySensors with success for rf sensors, and I'm very happy with it.
Developping the plugin for Jeedom, I appreciate the power of the protocole and for exemple the presentation and that nothing is impossible.
But it's wireless information going in the house.

As I will need some central control for the relays inside the electric panel, I have look at different solutions :

• XPL and xplduino
• Arduidom

Mainly wanting to keep the communication on wire for this part and not as a clear wireless message (security)
XPL after tasting mySensors look heavy weapon for not better results. Hardware for xplduino is also complicate.
Arduidom is a plugin avalaible for Jeedom controlling an Arduino. But it's avalaible only for the Jeedom master, and mine will not be inside the electric panel. And you can have only one.

So, I come to an idea and want to share it here to see if it's a non-sense or interest people.
I want to buil an ethernet gateway let say with a Mega and connected to relay boards to control light and switch from the electric panel. This inside a RAIL DIN box.
It will be a standalone node, just reusing the mySensors plugin and mind.

This will need a plugin able to talk to more than one gateway, what I have planned for the Jeedom controller. This will be usefull anyway if a user as a NRF24 and RFM69 network, or let say 2 NRF24 in a big property.

So what I hope to come is a RAIL DIN box with ethernet connexion and relay boards. Talking to it in "mySensors" protocol.
And if I need more IO, adding a RAIL DIN box etc

Hi,

Is there any move on the V2 ? Can we see the actual status and what it is going to look like ?
Going to a V2 for the Jeedom controller, will like to see it coming with mySensors v2 changes.
Precisly will like to have a status about :

• reboot of node without needing a special bootloader (inside the lib will be the best)
• sending libversion from presentation including for gateway (this is include for nodes, I don't know for gateway)
• possible of sending V_type used during presentation, no need to wait to send data
• possible of sending a short desc name for each sensors created (can be helpfull when you create many sensors with same type and the difference is not only the order)
• possible to send the power source of node, I don't know inside battery or else. This will be very helpful with battery/plug or battery/solar source for exemple. So we can know how much the battery is full but also if the sensor is actually on battery.
• getConfig to be used for any paramteres instead of units, like this the node can request parameters from the conrtoler (think about a global sketch for a switch that can talk to a relay node, by the controller side you set which node it's controling)

Can we have a wiki page maybe with an actual status of where is the V2 ? And is there a dev version we can try ?

Hi,

Someone has get any success making a gateway with an ESP8266 ?

I have answer on jeedom forum.

Yes for security can be also a first presentation requiring a signing. Like what Puppet is doing, agents first present themself to the master, master is waiting for someone to accept a request, and after it gives the certificate to the client and then the client tell him verything about itself (facts in this view can be compared to the sketch and sensors presentation)

But I don't know if it's easy with arduino this type of exchange.
Other way can be a simple key we put in sketchs, and using the same on every of our home, and use it in the lib to encode the data.

Hi,

Please to see this post. As our plugin for Jeedom is complet now, I have some feedback to share.
First, is there a date and status of version 2 for now ?

Here my thoughs :

• about units, I agree with the fact that it's lightier to have the Arduino not taking care of it, but instead use some conversion on the controller side

• about value types, it will be better to have really type and not a notion of unit sometime here too like for power get only consuption and not kwh, really going all the way and give the unit control to the controller

• about value types and sensor types, after writing the plugin, still weird for me to have a sensor presentation giving some clue on what type it is, but need to wait for some value to be sure. I mean power sensor for exemple that can get some different type of values, this is not really clean I think. Or the weather sensor, in one case it will send a value type that is numeric, the other one is text (forecast)

• will it not be better to have some mechanism when it's an actuator to deliver the type of message it is accepting ? for exemple a heater, there is the off/on but also a mode type. How is it possible to know that the sensor is accepting all or only on/off ?

So, for me, something like after a presentation being able on the controller to say what type of data and what commands we can say, will be the best. And important too, what data it can be requesting. I mean, now with the scene_controller to extend functions, we need to get data from the automation software too. Imagine to display some informations from outside the mySensors network.
Maybe by completing the sensor_type and merging with value_types, removing the unit notion inside the value. And so during presentation we know all about the data it can send. And in second step during presentation, declare the actuator commands.

One other point important and asked by some users, is it possible to integrate some security in the protocol ? As soon you talk about actuator accepting command from anyone, that's unsecure. Key given during inclusion by gateway and use for encode the data ?

Thanks for reading

Cédric

@hek : can you update the mysensors lib in codebenders ? On scene controller page you ask to modify SOFTSPI, it's not on codebenders (unless it makes a copy for me) but it is on git

Hi,

Can't use the sketch.
From codebender include on mysensors it just say there was an error compiling it.
When I clone it, directly on codebenders it say there was a communication error.
When try with local IDE, there is a lot of errors about the time library

This type (for each month and day)
libraries/Time/DateStrings.cpp:18:18: error: variable ‘monthStr1’ must be const in order to be put into read-only section by means of ‘attribute((progmem))’
char monthStr1[] PROGMEM = "January";

Hi,

Not very usefull post for you here, but I want to say I'm very pleased to see this discussion and the news I can read here or what appears in dev on the github.

About the presentation of sub-type accepted. After getting an almost complete controller for Jeedom, we have difficulties to "predict" things to automate and make it very simple for user to use the plugin. Like for exemple, create commands. For relays and dimmer it was easy, but after when we look for servo or some extra type it's impossible to know for now what we can create.
So reading, the sensor will tell it in presentation it's just perfect.

Same for the presentation during node of lib used, that's just better than during the sensors, make sense.

I read also on the protocol page, that there is a way for a node to request data from gateway/controller. Can this point be clarified, maybe it needs also the sensor/node to say what it can request ? That's also for automation of autolink. For us (Jeedom plugin) and I think for other, if we know the sensor is able to request some data, we can automaticly create the information item and the user will have only to map it to the equipment it wants to point. I don't know if this is still included/planned as I'm aware many of the "smart" part must be on the controller side, but with beautiful things like Scene Controller and LCD display, I can imagine there is a need ?

I read also the OTA process will change a lot. So, is it better waiting 2.0 to include it on our side ? I mean, for the controller part, will this change a lot of things ?

And last point, there is actually a internal message type Reboot. This one is indicated only working for OTA bootloader. Is that true ?
If so, is it possible in 2.0 to include a way to request a complete presentation of an already started sensor. (that's why I ask for the Reboot message, simpler to request a reboot so the node will present itself at the same type)
Sometimes it's easier when migrating for exemple or reinstall, and we know the ID of sensor to ask it for presentating itself than going there to unplug it.

That's my thoughs after getting a little more in deep of protocol for the controler/plugin

Cédric

Yes, I get it from presentation messages, but like you say a little redundant
So, if I can send it once in setup, like this it's better for the controller, not too much work for nothing, just take care of the message send by setup and it's done.

Thanks for the answer, that's a good thing I think. Like this we can keep all informations on the controller at once and have an easy way to see them whatever we want to use OTA or manual update.

Waiting for 2.0, what is the best way to do it for now ?

Hi,

I know there is a type of internal message to send the library version : I_VERSION.
I will like to send this information during presentation, so during the setup. Like we show the sketch and version of sketch, I think it's a good place.
But I'm not sur what is the best way to do it. Do we have to use a general message and say it's type I_VERSION or is there a gw.sendVersion method for exemple ?

On the Jeedom controller I want to record the lib version. Doing it during presentation like sketch will be better than what I can do now (on every sensor presentation, so can be 20 for one node)

Thanks,

Cédric

Check with him. So we have some wiki page, screenshots and it's nicely working.
I will send you some data by mail.

Here the wiki : https://wiki.jeedom.fr/index.php?title=MySensors
Yes, I send you the mail in english, but Jeedom is a french community ... for now

Hi,

Will check with filoucaennais if he has already send you the pictures.
But I can add, we get an updated version of our MySensors plugin for Jeedom. Now it's supporting to be installed on a Jeedom node and also supporting the network gateway for MySensors. No more reasons for people to say they cannot use it

Thanks for your project, very useful and interesting DIY stuff. Just mussing some "PCB" files in the shop to order basic PCB and be looking more "finished"

Will it be possible to use with 3.5 LCD instead of 3.2 ? Many differences for the code to make ?
Because now we can find 3.5LCD directly connectable on 2560 and total is cheaper too.

For easier reading and understanding, can you list all the parts needed with your PCB ? like headers, capacitors, resistances ...
Thanks