I am pretty new to my sensors. Definitely new to creating pcbs. But I did manage some how to create a small pcb in eagle, did the laser toner transfer method and etched it at home, drilled the holes and soldered it all up and go it working. Next step is to design and 3dprint my custom case and get it mounted.

Thanks for all the help you guys have given me.

Hey Guys,
Figured I would try to start a new thread for this. Last week I posted the code so far as I have for the milight integration in to 2.0 here.

https://github.com/brunkj/MySensorsMiLight

I have not been able to work on it since. If anyone wants to take a crack at it and has some milights, feel free :)

I think this could be a very cheap way to replace hue and the $$ that goes with it.

My uploaded code as of now will allow you to pair with your bulb, you have to send the "ON" command with in something like 3 seconds of turning on your light. That's how it pairs. Once you pair, you can send on and off. There is code there from previous versions for some of the other stuff like color change and dim. But I have not figured that part out as far as how I need to send the data.

If @ted is still around he may be able to help even more so since he wrote the original. Im just hack jobbing his code up to 2.0 lol

So, I have looked in to this. I even had a fitbit that i was hoping to use to determine if I fell asleep at night and turn off lights in my home automation system.

The down side I ran into is this. I had fitbit setup with ifttt since that was something it could interface with. The sleep detection worked. HOWEVER. It only actually posted info to IFTTT when you woke up, at that point, all sleep related data was submitted. So it didn't track it real time.

I have been looking in to how to integrate sleep in to my HA but also like you mentioned quality of sleep. The fitbit utilizes motion to determine "restless" sleep. Attaching a bunch of sensors to myself doesn't seem like it would yield comfortable natural sleep. So potentially stuff like a mesh of piezo sensors under a mattress topper would work. that would detect when the values change indicating turning, movement.

Temperature should be easy (fitbit probably does it, i had a cheap one so it did not).

If you want to get crazy (which if i had time i would go this route) you can get a fitness watch with a certain chip in it, and reprogram it.

https://www.youtube.com/watch?v=SBHyQ1OSM-4

That's what he did. This could be REALLY REALLY cool. You could code in your own parameters and what not, since it's bluetooth LE you could track it via phone or just remote sensors.

Once you have some basic "restless" night tracking you could do some experimenting (even with the fitbit).

• track your sleep for a week or 2 to get a baseline of how much time each night you sleep "restless"
• change thermostat temp up/down - track again and compare.
• monitor body temp and see if warmer/colder = restless. find sweet spot.
• integrate body temp monitor to HA system to control thermostat to keep you correct temp

If you make any progress, definitely let me know, i would be interested to see what you come up with!

any plans to add an RTC on this and be able to timestamp the log entries? I have some sensors that only wake up and do readings every 90 minutes. But sometimes they just stop doing it. So time stamps on the logs would be good to see if there is anything happening right around the time it stops reporting.

So I have a new development. I noticed something strange. The mysgw stopped again today. I went digging through the syslog around the same time. Didn't see anything just before it went offline, but i did notice that shortly after it went offline it said that the carrier dropped for the nic.

Apr  2 15:50:55 raspberrypi mysgw: TSF:MSG:READ,200-200-0,s=2,c=2,t=25,pt=0,l=0,sg=0:
Apr  2 15:50:55 raspberrypi mysgw: GWT:TPS:TOPIC=mygateway1-out/200/2/2/0/25,MSG SENT
Apr  2 15:51:07 raspberrypi mysgw: TSF:MSG:READ,200-200-0,s=2,c=1,t=23,pt=2,l=2,sg=0:25
Apr  2 15:51:07 raspberrypi mysgw: GWT:TPS:TOPIC=mygateway1-out/200/2/1/0/23,MSG SENT
Apr  2 15:52:27 raspberrypi dhcpcd[377]: eth0: carrier lost
Apr  2 15:52:27 raspberrypi kernel: [  461.474897] smsc95xx 1-1.1:1.0 eth0: link down
Apr  2 15:52:28 raspberrypi dhcpcd[377]: eth0: deleting address fe80::669:d81d:83fb:3aaa
Apr  2 15:52:28 raspberrypi avahi-daemon[226]: Withdrawing address record for fe80::669:d81d:83fb:3aaa on eth0.
Apr  2 15:52:28 raspberrypi avahi-daemon[226]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::669:d81d:83fb:3aaa.
Apr  2 15:52:28 raspberrypi avahi-daemon[226]: Interface eth0.IPv6 no longer relevant for mDNS.
Apr  2 15:52:28 raspberrypi dhcpcd[377]: eth0: deleting default route via 192.168.2.1
Apr  2 15:52:28 raspberrypi dhcpcd[377]: eth0: deleting route to 192.168.2.0/24
Apr  2 15:52:28 raspberrypi avahi-daemon[226]: Withdrawing address record for 192.168.2.71 on eth0.
Apr  2 15:52:28 raspberrypi avahi-daemon[226]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.2.71.

So i decided to check a few other times in the last 48 hours and sure enough. Same thing. It seems that something is causing the nic to think it lost it's connection to the switch. The mysgw seems to go in to a weird state. Not sure what error checking is in it or what i could do to log more since i am already on debug for the logging of mysgw.

Next step i guess will be instead of dhcp reservation ill static assign it. See if that changes anything, and see swap network cable. Maybe hard set some things like the speed/duplex on the switch.

Just figured i would throw out my latest finding.

Ok I got it to work. I misunderstood how the interrupts worked. Got it now. The culprit was the if statement detecting if the state changed. Since the state was being maintained while sleep, it wasn't firing when I pushed the button.

Thanks for everyones help!!

@zboblamont good to know! I have 2 florescents in my garage that i swapped for LED. These didn't need to bypass the ballast. Might be worth a test to swap those out for the ones in the bathroom (where i see the most interference)

Guess i know what im going to try when i get home!

So a little new info. Last night i had the lights turn off with the door closed, and no one turned on/off the kitchen/bathroom lights. But what did happen, I turned off a little space heater in my room. When i turned it off, the lights off. Finding this very interesting, i grabbed my phone (in the dark) and check the HA status. The motion detection was triggered... ok... so maybe it's not the PIR/repeater that's the issue...

It's the LIGHT MODULE!! There is a good chance that the power fluctuations aren't messing with the repeater itself, but actually resetting the arduino with my lamp relays. I think this weekend i need to pull that out, check the code to see if i am saving state to eeprom and also throw some capacitors on the incoming power to see if that helps.

Is there anything like this going to be done in the US? I would love to help/attend.

@mfalkvidd roger that :)

What could this be used for? You have to be with in range of your RF network right?

I have put my mods on github.

https://github.com/brunkj/MySensorsMiLight/

I have not been able to mess with it since the weekend. Still trying to get some info on the RGB part. If anyone wants to take a shot at it let me know if you make any progress :)

so my 1 message a second is literally like nothing as far as the mysensors RF protocol is concerned. Shouldn't impact at all?

So right now I have my mysensors gateway(s) setup on 2 raspberry pi's. They are both setup for mqtt gateway which is on a diff server.

I use keepalived to determine which pi should be running the mysgw binary.

This works pretty well. However I am considering changing over to 2 network gateway configurations and use a floating virtual IP.

Does anyone have any pro's/cons for one method over the other?

The pro that I can see is being able to use other programs that can communicate over the network gateways to do OTA updates. As well as being able to use bindings for things like discovery.

@martinhjelmare being a fan of quads.... i like this idea haha

any updates? I have a couple milight bulbs ready to test :)

Small update. I switched to a radio from different batch and seemed like that fixed it. Saw the smart sleep message in mqtt until I went to bed. But around 4:30am it stopped again. Im going to go pull it again and see what it's outputting. I feel like I need to hook up a bluetooth hc-05 or something so i can just connect over bluetooth at this point to get the serial data lol

@mfalkvidd I will put up a write up on what i did. Including my health check script (which may address some of the other items on how I handle the failures ect)

Keepalived with the check script and health script is what I use to keep tabs and it also moves that virtual IP back and forth allowing for the same ip to stay in use and restart the binary when needed

updated to 1.6.9 and it's there. oh well. probably needed to update anyway :)

I look forward to seeing this project progress. Go get it!! :)