RaspBee II built in daylight sensors

Dresden-Elektronik Hardware
1

Hi, hope its the right category for a question regarding my RaspBee II.

The builtin virtual daylight sensor raised my attention, what it is at all etc. So, I found out its kind of a “astro light” sensor providing a generalized sun position. I am really impressed of the precison, magically it detected fairly good its right position on that beautiful planet. Here compared to the openHAB Astro binding going along the precise latitude, longitude and altitude:

openhabian@openhabian:~ $ grep deConz /var/log/openhab/openhab.log /var/log/openhab/events.log
/var/log/openhab/events.log:2024-01-08 16:16:37.029 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'deKonz_licht_level' changed from Daylight to Sunset
/var/log/openhab/events.log:2024-01-08 16:42:37.067 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'deConz_tageslicht_wert' changed from 180 to 190
/var/log/openhab/events.log:2024-01-08 16:46:37.032 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'deConz_tageslicht_wert' changed from 190 to 200
/var/log/openhab/events.log:2024-01-08 16:54:15.178 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'deConz_licht_level' changed from NULL to Dark
/var/log/openhab/events.log:2024-01-08 16:54:15.183 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'deConz_dunkel_status' changed from NULL to ON
/var/log/openhab/events.log:2024-01-08 17:22:57.030 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'deConz_tageslicht_wert' changed from 200 to 210
/var/log/openhab/events.log:2024-01-08 18:02:47.034 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'deConz_tageslicht_wert' changed from 210 to 220
/var/log/openhab/events.log:2024-01-08 18:40:47.033 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'deConz_tageslicht_wert' changed from 220 to 230


openhabian@openhabian:~ $ grep Sun_Phase /var/log/openhab/openhab.log /var/log/openhab/events.log
/var/log/openhab/events.log:2024-01-08 16:42:00.010 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Sun_Phase' changed from DAYLIGHT to SUN_SET
/var/log/openhab/events.log:2024-01-08 16:46:00.007 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Sun_Phase' changed from SUN_SET to CIVIL_DUSK
/var/log/openhab/events.log:2024-01-08 17:23:00.007 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Sun_Phase' changed from CIVIL_DUSK to NAUTIC_DUSK
/var/log/openhab/events.log:2024-01-08 18:02:00.003 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Sun_Phase' changed from NAUTIC_DUSK to ASTRO_DUSK
/var/log/openhab/events.log:2024-01-08 18:40:00.004 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Sun_Phase' changed from ASTRO_DUSK to NIGHT

What actually puzzle’s me is the -30/+30min offset for sunset resp. sunrise. Why is that the default definition and where to change in Phoscon?

Thanks in advance.

Regards

2

sunriseoffset / sunsetoffset: Sensors - deCONZ REST-API

3

Ok, so I need to manipulate that REST API value, uff …

4

This is easy:

$ curl -XPUT http://<ip address>/api/<api key>/sensors/<sensor id>/config -d '{"sunriseoffset": 0, "sunsetoffset": -0}'
[
  {
    "success": {
      "/sensors/<sensor id>/config/sunriseoffset": 0
    }
  },
  {
    "success": {
      "/sensors/<sensor id>/config/sunsetoffset": 0
    }
  }
]
1 Like