There is no way to directly set a time limit during the day for when notifications are generated or not. However, in general, if schedules are setup correctly (with set back of set points etc.), there should normally not be a reason for false notification unless there is something else, other than Pelican devices, controlling the equipment.
Below is an image of a thermostat's Notification Setting configuration:
Notifications Settings: Sensitivity Level
It is normally rare to need to adjust a thermostats notification sensitivity level. This just sets how “sensitive” your thermostat’s notification analytics are. It is rare to receive unnecessary notification from this type of notification, even when set to High, because these type of notification is designed to notify you because of an HVAC equipment failure and is only active when a heating or cooling cycle is running.
If you receive this type of notification it normally indicates an HVAC equipment mechanical failure which needs to be addressed. This is NEVER an indication of an issue with your Pelican solution.
For more information on notification sensitivity levels, click here.
Notifications Settings: Safe Range
This notification is designed specifically for unique environments where if the room temperature EVER exceeds the configured safe range, you want a notification.
Many Pelican customers accidently set this notification when it is not needed.
If you are getting unnecessary safe range notifications, navigate to that thermostat’s configuration and delete or extend further the temperatures placed in Safe Range.
Notification Settings: CO₂ Warning Level
If you have a Pelican thermostat with a CO₂ sensor, you can configure a CO₂ Warning Level. This will provide you with a notification anytime a room reaches the configured CO₂ level.
Note: If you do not see this configuration and you have Pelican thermostat with CO₂ sensors, contact Pelican technical support to upgrade your thermostat to V3.10 or later.