You're not !
I'm also exclusively on linux, and I use MySensors !
I was using Arduino IDE, and now I'm using atom.io, but both are working on linux !

I see in the domoticz code that there are some fields to record Signal Level for other sensors types.
Making domoticz handle the signal level would then be possible.
There is 2 enhancements to do so :

• Handle a standard variable or subtype in MySensors to carry the signal or RSSI level (github issue 581 : https://github.com/mysensors/MySensors/issues/581)
• Modify the domoticz code to show somewhere the Signal Level for MySensors devices. (no github issue yet)

That would be interresting, since it would also allow to trigger some custom scripts if a device falls in a poor level...

That's not a software interrupt. In facts, the atmega supports interrupt on all pins, and also waking-up the device from any pin change, but the sleep function only support "external interrupts" which can only be triggered on pin 2 and 3.

Yes, I know that fsck repair the partition, but it's not really convenient to run a fsck at 4' AM because the server has crashed and doesn't want to startup because of corrupted FS ;)

Thanks !

Hi,

I have the same question, but a little bit different ;)

I use a RFM69 with the Mysensors 2.2.0 beta.
I don't sleep my node with the provided function, since I don't want to sleep for some time, but until a Pin Change Interrupt is triggered (via pin A0 or A1). So, I can't use the sleep() function.
I do put my node to sleep with avr core functions (setting registers, calling power_all_disable() and sleep_cpu()...) but I suppose the radio is never put on sleep !

Is there a function I can call to sleep the radio, and if yes, is there another function I should call before sending, to awake the radio ?

Thanks !

@gohan No they should'nt, as soon as they need to be modified.

There is probably better filesystems which are powerfail-resistant, but I'm not an expert and can't name any of them !
The main subject is still applicable : beware of wear ! Userdata which moves frequently such as databases should not be on a sd-card. Why not on an external HDD (or SSD...)

@gohan If you are using dietPi, you just have to run the command "dietpi-drive-manager" (sorry not sure of exact spelling, I'm not near a dietpi !)
Then, you'll have a menu that will allow you to choose per-partition read only or read-write.

@dbemowsk That's a good point to avoir SD wear-out, but it didn't avoided me the corrupted ext4 partition on a power-fail.
That's why I did choose to set the root partition as RO, so I'm sure the system will not hang at startup because of "partition not clean, cannot mount it" ;)

I've found a neat project for such uses :
It's called "DietPi" : it's a debian based distribution available for Raspberry pi, Orange PI and many others.
Many advantages :

• It's really lightweight.
• By default, logs are not written on SD card but in a RAM FS.
• Dropbear as SSH server instead of (more) heavy openSSH.
• and at last, but not least : ability to set root filesystem as READ ONLY. This is a BIG pros because the extFS is really more robust when not mounted RW.
  This way, you can still put your databases on another partition which would be more tolerant to power failures....

That's great for "IOT" which need to be powered-off without needing to shutdown linux. I use it for some "connected speakers" : I plug them, they start, I listen to music, and when I'm done, I unplug them ! Never fail !!

BUT, IMO for a home automation server, the best and only option is an UPS (uninterruptible power supply) : either an AC one, or a powerbank-like battery : some of them are able to charge and deliver their juice without failing.

Hi @tekka
Would you share your poc so I could try to enhance it ?

Regards

Hi @tekka,

Any news about RFM69 for MYSBootloader ?

I've had another look in the code, too much complicated for my skills !

Hi !

Not so much news,
The PCB are at home ;)
Missing time to test them, but I should start in a few days !

I've added some pictures, and an ebay link for the board only (not 10 boards, only one !)

Yes of course !!

I have some of them available to purchase (pcb only).

I'll do an ebay link this morning.

What I'm doing is something similar to you :

I've made "dimmer boards" for lights, which doesn't have input buttons.
I've made "switch boards" which runs on batteries. Each board sleeps until a button is pressed. When the button is pressed, I send a message to the light that needs to be switched on/off...

I can explain more if you're interrested.

You're not totally right :
RFM69 can be used with a raspberry pi, you must use a usb (serial) gateway.
That's what I'm doing, and I've got very good results : My house is made of outside concrete walls; with my gateway in the middle of my house, I can walk outside 60-70 meters before starting to loose some packets.
And that's only with a dirty cheap 8cm wire antenna. I'm sure that a better antenna (see GPA-Ground Plane Antenna on internet) will allow some meters better...

Some people are talking about +1Km ranges with propers antenna.

I didn't go the NRF24 way because I wanted to use sensors outside the house, and without repeaters that wasn't possible.
PS : I use 868Mhz RFM modules : using 433 could also rise the range.

Hi there !
I know this thread is almost one year old, but I haven't found any recent thread about broadcast messages.

Is there a way to broadcast messages ?
My switchs are meant to drive groups of light.
Instead of sending multiple messages, each switch could broadcast a message which each light could intercept, check if the "group id" is the correct one, and turn on ;)

Great !
Now I have to implement a circular buffer and the solution will be perfect !

Edit : This reading is interresting : http://hackaday.com/2011/05/16/destroying-an-arduinos-eeprom/
The user did a test to wear out EEPROM, and did managed to get more than 1M writes before it started to fail !

Quick thought :

At least, if the old value is the same as the new value, don't write it !
I'm sure we can avoid a big amount of updates in case of the controller resend the same value...

I did thought of a kind of circular buffer , but it's too late for my brain to find a working solution :joy:
Reading the atmel doc will surely be easier !