@Tag Absolutely right.
Initially i was worried about losing sensor data with the clocks moving and then wondered about actions in this period.
I wonder if all controllers have the same issue or if one or more have a work around to mitigate the issue?
I'll have a look but have not much free time for a while now.
@jkandasa Here is another suggestion to think of for version 2.0.......
It would be nice to have a feature that could be enabled or disabled with a click that will perform the following......
Random Action - I am thinking of lights here for security purposes and making a building look more occupied than ordinary timers will allow. So a feature that allows random on times and random off times, within a specified portion (or portions) of the day/week/etc.
Kitchen lights should be randomly turned on for minimum 2 minutes and maximum 5 minutes from 6am to 7.30am AND between 5pm -10pm.
Bedroom lights should be turned on randomly for minimum 10 minutes and mazimum 20 minutes betwee 5.30am and 6.30am AND between 8pm and 11pm.
And so on for different zones of lights.
Once the vatiable are set then it should simply be a matter of enabling all when going away and perhaps you can even add a nice auto-disable for when you are away for a known number of days..... ?
This could also apply to turning on/off radio etc to enhance the effect.
Senks, unfortunately I have not seen this post, but together we found a way out of this task
Thanks for the quick reply, but I did not look at the log at the time of adding. Or rather, no recordings caught my attention when I watched it later! With sensor detection and information I tried it, unfortunately the topology hasn't changed. It seems to me that this is due to the fact that the auto gateway is registered in the repeater state. I will check this later.
I have one more question: how to change the built-in MQTT broker to use SSL?
The various options for moquette described in the myController configuration do not change its initialization..
(I guess I'll create a separate question on this topic )
@BraydenM timestamp is the number of milliseconds that have elapsed since January 1, 1970 at 00:00:00 GMT.
Note: In java it is in milliseconds. But in UNIX/Linux it is in seconds.
In python, you can convert to date, time by using the function, datetime.datetime.fromtimestamp(1582439517).
I believe it should be seconds. So you have to do, received timestamp / 1000 = in seconds
I was unframiliar with what JSON were as I've never used java.
JSON is not a java specific. We can use it most of the languages. Examples in Python, https://docs.python.org/3/library/json.html
@mtiutiu said in REST API for smart sleep enabled nodes:
It would be nice to have that working using the sendRawMessage endpoint also. I can open an issue on Github if needed.
Yes, please open a ticket. I will check and update you. Thanks!