Scene Controller

[gregl]

@hek thanks Hek

[RJ_Make]

@hek
Man you are costing me a fortune... Now there's another project I will need to try.. :-)

Seriously though, very cool!

[lunarok]

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.

[hek]

@lunarok

It depends on if the display is supported by the UTFT library I used in the example.

[John]

Very cool display, well done!

[lunarok]

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";

[lunarok]

@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

[hek]

Codebender has a bug when library contains large files (UTFT in this case). This has been reported to them and they will fix it eventually. In the meantime I have just re-uploaded the libraries without these binary (pdf files). But I think they need to clear some caches before it actually compiles.

Enabling SOFTSPI in the MySensors lib-config just for the SceneController is harder because we can only keep one version of the MySensors library at the time in our "repository" on codebender.

Regarding the DateStrings compilation error .. I've just pushed an update which works in IDE 1.5.8 now.

[tbowmo]

@hek
Can't you define the SoftSPI settings in the sketch, before you load the library header file? (And then make some conditional defines in the library)

(I admit, I don't know the arduino toolchain fully, so I could be mistaken here.. But in "normal" c/c++ compilers you can do it)

Or is the libraries at codebender precompiled?

[hek]

Nope, it doesn't work in the crappy Arduino builder.

And I thing codebender tries to simulate Arduino as much as possible.

[Hoffan]

Does this look right?

I ask because i have installed tge scene controller
But i cant understand how i will set up a scene with this

[hek]

Looks right.

1. Cretate a scene (under Automation).
2. Create new trigger on "Arduino ScheneCtrl 2:1"
3. Choose the appropriate scene action

[tbully]

I've been playing around with this quite a bit and have it working great. That said, I know I remember seeing a thread where cases (3D printed) were being discussed . However, I can't find the link.

Anyone have it handy?

[tbully]

Still trying to find a case while tinkering and came up with another question.

Has anyone figured out how to "toggle" a scene? I think it'd be cool to have it somehow know if a scene was active and if so run an "off" version of that scene. Likewise, if the scene is "off", run an "on" version.

Maybe another way is to abandon the scene functionality altogether and just somehow control the zwave switch individually.

Just thinking out loud.

Very cool project.

[quocanhcgd]

Can i use Arduino Uno to make scene controller? If okie, please teach me to do it? thanks

[hek]

@quocanhcgd

Yes, but you cannot use the touch screen. Here is a couple of example of scene activators using buttons:
http://forum.mysensors.org/topic/1018/contest-3d-printed-battery-powered-wall-remote-control
http://forum.mysensors.org/topic/93/weather-station-with-scene-activator

[tbully]

Bringing back an old thread. As you can tell, I'm not much of a developer. ..... apologies....

I'm updating all of my sensors to 1.5 but am having issues with this one. When I compile (using IDE 1.6.5) and a new libraries directory, I get the following error.

Any ideas?

TouchDisplaySceneControllerSensor:67: error: no matching function for call to 'MySensor::MySensor(int, int)'
TouchDisplaySceneControllerSensor.ino:67:18: note: candidates are:
In file included from TouchDisplaySceneControllerSensor.ino:37:0:
C:\Users\tbully\Documents\Arduino\libraries\MySensors/MySensor.h:158:2: note: MySensor::MySensor(MyTransport&, MyHw&)
  MySensor(MyTransport &radio =*new MyTransportNRF24(), MyHw &hw=*new MyHwDriver()
  ^
C:\Users\tbully\Documents\Arduino\libraries\MySensors/MySensor.h:158:2: note:   no known conversion for argument 1 from 'int' to 'MyTransport&'
C:\Users\tbully\Documents\Arduino\libraries\MySensors/MySensor.h:149:7: note: MySensor::MySensor(const MySensor&)
 class MySensor
       ^
C:\Users\tbully\Documents\Arduino\libraries\MySensors/MySensor.h:149:7: note:   candidate expects 1 argument, 2 provided
no matching function for call to 'MySensor::MySensor(int, int)'

[AWI]

@tbully It looks like you are using the "old" gw(pin,pin) call. This has been replaced with a separate initialisation for the radio. In case you use the default pin definitions gw(9,10) you can just replace gw(.., ..) ; by gw ;

[tbully]

Thanks @awi. I meant to come back and correct my post. I did see that after going back and looking at the old 1.4 API (you are correct). It has been many months since I've looked at this sketch. However, I'm not using the default PINs here so I guess I have to change MyConfig for this sketch?

/**********************************
*  NRF24L01 Driver Defaults
***********************************/
#define RF24_CE_PIN		   9
#define RF24_CS_PIN		   10

[AWI]

@tbully The new API uses a separate radio class initiator Something like (from one of my own 'learnings' , Ceech board in this case)

MyTransportNRF24 transport(7, 8); // Sensoduino (8,7) Ceech board, 3.3v (7,8)  (pin default 9,10)
MySensor gw(transport);