Simple Temp/Light/Time setup with LCD 1.4 (no beta anymore)

[korttoma]

Thanks for the sketch @JOHN
It gives me a few ideas how to set things up but it seems like you are using a different lcd library then I had in mind.
That one use way to many digital pins for my taste.
I was planing on using the LiquidCrystal_I2C.h once my ordered display gets here.

Thanks again ;)

[John]

@korttoma
Your welcome. Yes it does use too many pins, but this one i had just laying around doing nothing and was playing with the libraries. i2c would definitely be better imho.

[korttoma]

I found my LCD in the mailbox just now. Time pull something together.

[John]

@korttoma Succes!

I've made a couple of small changes:
Having a NPN laying around the display's back-light is now handled by the Atmega. And the display now shows overall users status (Awake/Sleeping/Away).
The display turns on when the users status change, when a button is pressed or connection is "lost" (No server response). After 20 seconds of user change/button press/"connection" back the display's back-light goes off again.

Planning: An extra button to send a signal to the server where it toggles user status to sleep/awake (all lights off etc.../morning routines) depending on time settings on the server.

That leaves one pin unused. Any idea's?

[John]

A little update:

The below setup will run for a while until i have founded some suited casing for it... It has the same functionalities as above but in the end will get more buttons via a binary encoder i have laying around. So, it now is soldered and put in a case used in an other project (explains the BIG cutout where the LCD is seen. At the top the LDR, an the left a tactile used for the display backlight, and at the bottom (not seen) is a tmp36 sticking out.

[John]

I'm also busy with mysensors integration in the server i'm creating... below is a work in progress screenshot of a mysensors device to be added. All though it is shown in the screenshot, automatic node addressing is not yet supported. Also automatic device creation is not done yet, you will need first to define the device yourself (fields etc..).

I'm also working on a desktop and mobile client.. This is how it looks in the desktop client when this specific device is added to the server and assigned to the floor planner with light intensity (LUX) enabled. Currently i only have one device active with lux (which is the device on this page).

I hope to get full mysensors implementation soon done, i will also include mysensor example devices to the mysensor device declarations.

[hek]

Ohh.. nice @John

Need a couple of screenshots for the web. Ok if I use these?

[John]

@hek
Yeah sure no problem, all though there is an extra button upcoming in the next couple of days(/week?) which will say something like "Auto create device" where the driver then will be able to create the needed xml for the shown device. I'm extremely busy at the moment need to prepare for a hell lot of things the upcoming weeks so there is no real ETA for that button yet.

Maybe it is handy to put an extra screenshot on how it looks when you add the serial gateway for the first time (page auto refreshes when an usb device is plugged in):

[John]

I have updated the support this evening and the implementation now also shows the last 20 messages being requested to be logged by the gateway.

Also i have added the possibility to auto assign node ID's but can not test it because the project i started this post with is running live with a server instance and is used in triggers which control my lighting... Current method is to turn on a sensor node, take a look at the last 20 messages (refresh the page by clicking on the MySensors driver). If the log shows an address is assigned, restart the sensor node.

Automatic creation of devices is put on hold because of thread: http://forum.mysensors.org/topic/304/unit-standardization-1-4 so devices still need to be created by hand.

[EDIT]
Maybe handy to create a different post about the mysensors support if that is allowed of course
[/EDIT]

[John]

I have added a device editor to the server. It uses the sensor types as a group and the sensor variable as the control.

Group (sensor):

Control (sensor variable):

This will be my last post here because my controller has got it's own controller page :)