Hi everyone.

I have built a dimmer node for my home which has its own buttons and can also be controlled over mysensors net. I am using Mysensors 2.00 development branch.

BUT...what happens if, for some reason, the radio module is not present, or its initialization fails, or something else happens, causing mysensors boot to fail. What happens now, is that the program get freeze at startup.

Wouldn't be a good idea, is spite of mysensors failing, to continue with the program? I would like to have the dimmer working with its buttons, despite of the mysensors net state. Maybe the gateway is down, or the node can't find a parent.

There are several example of nodes that should, or would be nice to work as standalone, despite the radio network condition?
Don't you agree?

Maybe this could be optional with some definitions in config files.
Regards!

Hi Tekka.
Great software, thanks for sharing.

I 've being doing some tests and found a problem that seems to be related to my own sketches.

When I upload through OTA the TimeReporter sketch, it uploads fine, and I am able to change the firmware afterward for another one.
But when I upload my own sketch, It uploads fine, and works fine, but it stops to answer MYScontroller commands, such as reboot or assing firmware. So I am stuck with that sketch in that node. To flash another sketch in that node, I have to reflash MYSBootloader again via usbASP and later on, upload the desire sketch wit MYSController.

Am I skiping something in my code that allows MYSBootloader to respond to MYSController commands?
Could you please upload the TimeReporter.ino sketch as example of a working sketch with MYSController/MYSBootloader?

Thanks, regards!

Gonzalo

Hi again @TimO .

Just an idea.

What do you think about solving this problematic in this way:

We create a group whose members are all those items that later will populate the binding's memory. I have a group named mysqlpersisted where I put all the items whose data will be stored in my SQL DB. So I could use that group. For this example, let's call it "MemoryGroup"

Then, we can create the following rule:

rule "Populate MySensors binding memory"

when 
System started
then

(maybe add a delay to allow persistance services to load)

MemoryGroup?.members.forEach[i |
        postUpdate(i.name, i.previousState(true))
]

Using this method, memory would get populated everytime OH boots up, with data belonging to the persistance service that we use. And we use postUpdate, so no command is sent to the nodes.

With this I think we solve both problems as data in the binding will be concurrent with the persistance service data.

Let me know what you think about this.

Regards!

What happened with this project? Has been abandoned or finished successfully?
Have you tried automatic calibration?

Ok, thanks for that.

I finally found my problem.
The Node was sleeping most of the time. In spite of waking up twice per second, it was not enough to enter the uploading mode in the mysbootloader, so the node wasn't answering back to the gateway, nor MYSController.

Now I have a questions

How can I OTA update/upload the firmware of a sleeping node? Should the gateway, or a relay node, send the upload message to the sleeping node as soon as it wakes up for transmiting its data?
I guess that in order to do that, the sleeping node should always wait for an aknowledge or some kind of message after waking up. I mean:

Sleeping node wakes up
Then, it send its data to controller or to relay node
Afterwards, it wait for the controller to acknoledge the data just send, and to tell him (sleeping node) if there is a firmware upgrade for it.
If there's not, go back to sleep. If there is, go to OTA upgrade routine.

Thanks, regards.

Thanks @TimO. Now I get it.
What do you think about having two gateways, one with NRF radio and the other one with RFM69 radio?

Will the binding support both gateways simultaneusly with no issues?

Another question..Will you support HearbeatRequest for the development branch?

Thanks, regards.

Please kindly check my contribution in the git issue. Maybe it will help to clarify your issues.

@LastSamurai said in openHAB 2.2 binding:

@gonzalonal said in openHAB 2.2 binding:

Yes, sure. I'll do that to keep track.

By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?

You can find the issues here. Basically you (I ;)) can't set RGBW nodes to display pure white colors via openhab, dimming is not working (error confirmed by TimO) and most importantly ACK isn't working properly (for me at least). If you can help with any of this (especially the conversion HSB <=> RGBW) you are most welcome.

Please kindly check my contribution in the git issue. Maybe it will help to clarify your issues.

@LastSamurai said in openHAB 2.2 binding:

@gonzalonal said in openHAB 2.2 binding:

Yes, sure. I'll do that to keep track.

By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?

You can find the issues here. Basically you (I ;)) can't set RGBW nodes to display pure white colors via openhab, dimming is not working (error confirmed by TimO) and most importantly ACK isn't working properly (for me at least). If you can help with any of this (especially the conversion HSB <=> RGBW) you are most welcome.

Yes, sure. I'll do that to keep track.

By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?

Hi @TimO and @andreacioni.
Back in the day link we discussed about request type of messages being supported by the binding and the complex scenario it created.
Are there any plans to continue developing this feature?

Today brand new setup with fail results.

I have installed a brand new OH2 snapshot build #1047 and the latest relese of the binding available.

I am using just a single node as ethernet gateway. After a couple of minutes the binding stops sending the messages to the node. It logs as it would send them but nothing is really sent out. I have sniffed the connection with wireshark.

Sometimes, while looking the binding debug logs at OH2 console, it hangs and I have to restablish the connection. This last issue seems more related to OH2 itself but maybe something wrong in the binding is causing it. Again, the is not a single clue in the logs about this.

I have just installed the OH2.1 stable release with the latest release of the binding and everything runs great yet.

Anyone with a similar experience?

Hello.

Is there an easy way to send a message from the gateway (or nodo also) to the controller as a log message? That meaning internal message type and I_LOG_MESSAGE.

I am looking for something like:

send(log, "My log message here");

thanks!

@TimO you just need to toggle the DTR line.

Try:
serialPort.setDTR(true);
Thread.sleep(500);
serialPort.open();
serialPort.setDTR(false);

@mfalkvidd actually looking at the code of mysbootloder, it does support STK500 protocol. I haven't test if it really works...maybe it doesn't.

Hi @gohan

@gonzalonal said in Concept: Proxy Node: multi protocol proxy:

Hi @gohan.

Yes I know about protocols, I'm a teco engineer.
That same congestion you talk about, is already present in the current networks we are building. So, I don't believe it's a real limitation.

There are critical task in home automation that needs messages confirmation or to resend (as TCP does), but there are many more, the vast majority, that doesn't need confirmation. Who would bother to lose a humidity reading.

Offcourse. We agree. Those mode critical messages/commands should be send with the ack bit enabled so as to receive delivery confirmation, and if not, to resend.

@wallyllama said in Concept: Proxy Node: multi protocol proxy:

I think most of the problems could be overcome, but they will take time and effort, which would take away from other projects unless a volunteer comes forward. Im not ready for something like this yet, so I should propbably keep my mouth shut.

@gohan said in Concept: Proxy Node: multi protocol proxy:

Right, since this is community driven project it is difficult to put all that effort into it given that developers have their lives like everybody else

Again, we agree. It's just a concept that I would like to share. Nothing else. We all have many things to do in life and in MySensors as well, but I believe talking about this kind of things, slowly builds the idea in our heads, and may be prone to guide the platform development into it or some other great ideas.

What today seems overkill or impossible, tomorrow we'll see.
Thanks for your comments.

Hi @gohan.

Yes I know about protocols, I'm a teco engineer.
That same congestion you talk about, is already present in the current networks we are building. So, I don't believe it's a real limitation.

There are critical task in home automation that needs messages confirmation or to resend (as TCP does), but there are many more, the vast majority, that doesn't need confirmation. Who would bother to lose a humidity reading.

Hi @gohan . Thanks for showing interest on the topic.

It's sure a hard thing to accomplish, but keeping in mind that daughter networks should be kept as small as possible (around 3~5 nodes) and that, for instance, nrf24l01 has its own fifo buffer, and atmegas has it's own uart buffer (for RS485 example) I believe it would be posible. Maybe creating a software fifo queue.

I know we are very hardware limited, but as hardware evolves, this may become a easily doable task. Not sure if it's doable in a atmega328p but for sure in the newer SAMD platform.

Let me know what you think.
Regards!