Forum Replies Created
No, it’s not hard, but (at the moment) require’s a Raspberry Pi to act as client to the cloud service.
If you’d like to know me, I’m available on email (skivy71[at]gmail[dot]com or skype – skiv211271
If you get stuck, my system can monitor, (control / override) and alert you via SMS of anything you want it to.
In this example, you could set a rule where, if the setpoint goes above x, set it to y, and tell you its happened.
This explains it further…
The heating products firmware is written in a way that has the start of the day at 06:00, and the end of a day at 05:59. The result of this is that when saving a schedule for Thursday, any heating which is due to switch between 00:00 and 05:59 needs to be added to Wednesdays schedule. The firmware of the heating products is not possible to be updated to alter this behaviour.
For example, if on a Thursday, you would like to have the heating set to 15C setback temperature, and 22C between 04:00 and 09:00, and again at 17:00 to 22:00, then you would need to have a schedule for Wednesday, to ensure the 04:00-06:00 part of Thursdays morning is covered
I found this on the API portal, which looks like to relates to your issue…
Note On earlier firmware of TRVs and Thermostats, there is an issue where an end time of 06:00 is not recognised. The client should use 05:45 as the last possible end time. This does result in the setback temperature running between 05:45 and 06:00, however. It is possible for a firmware upgrade to be applied to the units if ending the block at 05:45 is not suitable. This affect TRVs with a version less lower than 58, and Thermostats with a version less than 34
In my opinion, its much simpler to schedule operations etc. from a software service and this is how my system works.
If the LWRF skill works like mine, command are received from the cloud, not locally… so the echo would not need to be registered.
Why they never made the range modular is beyond me
You’ll be able to send on / off / level no problem at all using the rfxcom.
I know what you mean regarding the availability of UK smart dimmers, i’ve used both LWRF and fibaro and I still think there’s room for another range on the market.
I’d like to see something like the LWRF switch, but with the Z-Wave chipset (to gain status etc).
I have had both the single gang wireless switches and the mood switches.
When the 1 gang sw was pressed, the rfxcom received string only differed by the 00h (for off) and 01h (for on).
A sustained press made no difference to the rfxcom string.
The mood switches were similar, but they do have a switch on the back which allows them to become a multistate like switch.
This means that as well as the 00h and 01h, you also have other discrete states, but I forget the codes, might of been 02h – 05h perhaps.
None of these signals themselves send a level hex code.
I prefer the diode
I do too agree the Alexa / Echo system really makes HA fun and it very useful.
But for it to be of real use, it does need to work properly.
My system does the whole Alexa thing a bit different, but at the moment, needs a Raspberry Pi to act as the local client to my cloud service.
I’m currently recruiting some testers to put my Alexa skill through its paces, so if you are interested in trying mine, please let me know.
There’ll be no difference is message from the rfxcom based on button press, regarding on / off and dim.
All it will hear is the 01h and 00h command.
The decoded hex is either on / off or a set level between 0 – 31 (0 – 100 %).
Ah, that’s good then.
Maybe if you can sketch the wiring at each switch.
Need to know the type of cable (i.e. 2 core, 3 core) and the where they are connected now.
Did anyone make a note of connections to the original switches?
Hard to see from the wiring, but I can tell you that those metal back boxes MUST be earthed!