how to connect DIYruZ geiger counter to Tasmota-flashed zb-gw03 #19116

Eugen-Ku · 2023-07-14T23:38:03Z

Eugen-Ku
Jul 14, 2023

Hi.
I'm having tough time trying to connect ZigBee Geiger counter by DIYruz geiger to my Tasmota-flashed zb-gw03.
All that the gateway can show me is couple of MQTT-topics like short address, link quality, manufacturer, modelID and name.
How do i make my gateway read the rest of data from device? Maybe make some additional settings?
Please answer as much detailed as possible, as soon as i'm novice in ZigBee and MQTT.
Thank You very much in advance.

Answered by s-hadinger

Jul 16, 2023

Here is the content

#Z2Tv1
# DIYRuZ_Geiger
# https://modkam.ru/2020/06/05/indikator-radioaktivnosti-zigbee/
:*,modkam.ru
0400/F000%21,GeigerSensitivity
0400/F001%10,GeigerLedFeedback
0400/F002%10,GeigerBuzzerFeedback
0400/F003%20,GeigerSensorsCount
0400/F004%30,GeigerSensorsType
0400/F005%23,GeigerAlertThreshold

View full answer

s-hadinger · 2023-07-15T08:14:08Z

s-hadinger
Jul 15, 2023
Collaborator

Can you provide logs when you pair the device?

5 replies

Eugen-Ku Jul 15, 2023
Author

03:40:38.849 ZIG: Subscribe to group 0 'ZbListen0 0'
03:40:38.951 MQT: tele/tasmota_5794CC/RESULT = {"ZbState":{"Status":0,"Message":"Started"}}
03:40:38.954 ZIG: Zigbee started
03:40:38.999 ZIG: Zigbee device information found in File System (3 devices - 163 bytes)
03:40:39.007 ZIG: Zigbee device data in EEPROM (87 bytes)
03:40:39.037 ZIG: ZbLoad '<internal_plugin>' loaded successfully
03:40:44.937 MQT: tele/tasmota_5794CC/STATE = {"Time":"2023-07-16T03:40:44","Uptime":"0T00:00:26","UptimeSec":26,"Heap":123,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":40}}
03:40:48.614 MQT: tele/tasmota_5794CC/RESULT = {"ZbState":{"Status":21,"Message":"Pairing mode enabled"}}
03:40:48.618 MQT: stat/tasmota_5794CC/RESULT = {"ZbPermitJoin":"Done"}
03:40:54.956 MQT: tele/tasmota_5794CC/STATE = {"Time":"2023-07-16T03:40:54","Uptime":"0T00:00:36","UptimeSec":36,"Heap":123,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":40}}
03:40:56.226 MQT: tele/tasmota_5794CC/RESULT = {"ZbParent":{"Device":"0x0000","Children":3,"ChildInfo":["0xA4C1387EAA1738E5","0xA4C13879EFF13299","0xA4C138D14A9CAE5A"]}}
03:41:00.051 ZIG: {"ZbEZSPReceived":"2400FB76A74ED11E004B120001000000"}
03:41:00.065 MQT: tele/tasmota_5794CC/RESULT = {"ZbState":{"Status":34,"IEEEAddr":"0x00124B001ED14EA7","ShortAddr":"0x76FB","ParentNetwork":"0x0000","JoinStatus":1,"Decision":0}}
03:41:00.266 MQT: tele/tasmota_5794CC/RESULT = {"ZbState":{"Status":30,"IEEEAddr":"0x00124B001ED14EA7","ShortAddr":"0x76FB","PowerSource":true,"ReceiveWhenIdle":true,"Security":false}}
03:41:00.471 MQT: tele/tasmota_5794CC/SENSOR = {"0x76FB":{"Device":"0x76FB","0003!01":"","IdentifyQuery":true,"Endpoint":1,"LinkQuality":183}}
03:41:00.559 MQT: tele/tasmota_5794CC/RESULT = {"ZbState":{"Status":32,"ActiveEndpoints":["0x01"]}}
03:41:00.835 MQT: tele/tasmota_5794CC/SENSOR = {"0x76FB":{"Device":"0x76FB","ModelId":"DIYRuZ_Geiger","Manufacturer":"modkam.ru","Endpoint":1,"LinkQuality":180}}
03:41:02.311 MQT: tele/tasmota_5794CC/RESULT = {"ZbState":{"Status":33,"Device":"0x76FB","Endpoint":"0x01","ProfileId":"0x0104","DeviceId":"0x000C","DeviceVersion":2,"InClusters":["0x0000"],"OutClusters":["0x0400","0x0006"]}}
03:41:02.940 ZIG: Zigbee Devices Data saved in File System (205 bytes)
03:41:04.352 ZIG: auto-bind `ZbBind {"Device":"0x76FB","Endpoint":1,"Cluster":"0x0006"}`
03:41:04.569 MQT: tele/tasmota_5794CC/RESULT = {"ZbBind":{"Device":"0x76FB","Status":0,"StatusMessage":"SUCCESS"}}
03:41:05.008 MQT: tele/tasmota_5794CC/STATE = {"Time":"2023-07-16T03:41:05","Uptime":"0T00:00:47","UptimeSec":47,"Heap":118,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":40}}
03:41:06.353 ZIG: auto-bind `ZbBind {"Device":"0x76FB","Endpoint":1,"Cluster":"0x0400"}`
03:41:06.555 MQT: tele/tasmota_5794CC/RESULT = {"ZbBind":{"Device":"0x76FB","Status":0,"StatusMessage":"SUCCESS"}}

Edit: formatting

s-hadinger Jul 16, 2023
Collaborator

Thanks, looking at Zigbee2MQTT, there are 2 proprietary attribute to Illuminance cluster.

Can you try:
ZbSend {"Device":"0x76FB","cluster":"0x0400","read":["0xF000","0xF001","0xF002"]}

ZbSend {"Device":"0x76FB","cluster":"0x0400","read":["0xF003","0xF004","0xF005"]}

Once you confirn, I can write a small plugin file for this device.

s-hadinger Jul 16, 2023
Collaborator

Please download this file on your computer, unzip.
Then copy DIYRuZ_Geiger.zb to the Tasmota file system, reboot and try the above 2 commands.

DIYRuZ_Geiger.zb.zip

s-hadinger Jul 16, 2023
Collaborator

Here is the content

#Z2Tv1
# DIYRuZ_Geiger
# https://modkam.ru/2020/06/05/indikator-radioaktivnosti-zigbee/
:*,modkam.ru
0400/F000%21,GeigerSensitivity
0400/F001%10,GeigerLedFeedback
0400/F002%10,GeigerBuzzerFeedback
0400/F003%20,GeigerSensorsCount
0400/F004%30,GeigerSensorsType
0400/F005%23,GeigerAlertThreshold

Answer selected by Eugen-Ku

Eugen-Ku Jul 16, 2023
Author

It worked, thank You very much!!
I suggested there's gonna be some kind of trick with low-level commands, but did not know how to do that.
Now will try to add the plugin with definition, will report back.

Eugen-Ku · 2023-07-16T18:15:08Z

Eugen-Ku
Jul 16, 2023
Author

Great, thank You very much for help, now it becomes more understandable for me.

Hmmm... Now it looks more nice, but there seems to be an error in names definition.
As soon as in zcl_app.h file there is:
#define ATTRID_RADIATION_EVENTS_PER_MINUTE 0xF001
#define ATTRID_RADIATION_LEVEL_PER_HOUR 0xF002

So, for cluster 0x0400 it must be kind of:

0400/F001,radioactive_events_per_minute
0400/F002,radiation_dose_per_hour

Now trying to deal with the rest of defined variables...
Ok, i got some variables working.

But I cannot do anything to change these settings!
When i try command like:
zbsend {"Device":"0x03ED","Cluster":"0x0401","Send":{"0xF002":1}}
nothing still changes.

0 replies

s-hadinger · 2023-07-17T20:47:27Z

s-hadinger
Jul 17, 2023
Collaborator

Where did you get the following definitions?

#define ATTRID_RADIATION_EVENTS_PER_MINUTE 0xF001
#define ATTRID_RADIATION_LEVEL_PER_HOUR 0xF002

Why would you want to write to 0400/F001, whether led_feedback or radioactive_events_per_minute this does not look like a writable attribute.

If you want to write, you got the syntax wrong:
ZbSend {"Device":"0x03ED","Write":{"GeigerAlertThreshold":50}}

3 replies

Eugen-Ku Jul 17, 2023
Author

Thanks again for the answer, will try syntax You provide.
I really appreciate the time You spend explaining me this.
I got attributes definitions from the source code, in the link i placed in the first message: https://github.com/diyruz/geiger
File name: geiger/source/zcl_app.h
Spent couple hours digging into the source codes, and found this:

/*********************************************************************
 * MACROS
 */

#define NW_APP_CONFIG 0x0401

#define R ACCESS_CONTROL_READ
//ACCESS_CONTROL_AUTH_WRITE
#define RW (R | ACCESS_CONTROL_WRITE | ACCESS_CONTROL_AUTH_WRITE)
#define RR (R | ACCESS_REPORTABLE)

#define BASIC ZCL_CLUSTER_ID_GEN_BASIC
#define GEN_ON_OFF ZCL_CLUSTER_ID_GEN_ON_OFF
#define POWER_CFG ZCL_CLUSTER_ID_GEN_ON
#define ILLUMINANCE ZCL_CLUSTER_ID_MS_ILLUMINANCE_MEASUREMENT
#define ILLUMINANCE_CONFIG ZCL_CLUSTER_ID_MS_ILLUMINANCE_LEVEL_SENSING_CONFIG


#define ATTRID_RADIATION_SENSOR_SENSIVITY 0xF000
#define ATTRID_RADIATION_LED_FEEDBACK 0xF001
#define ATTRID_RADIATION_BUZZER_FEEDBACK 0xF002
#define ATTRID_RADIATION_SENSORS_COUNT 0xF003
#define ATTRID_RADIATION_SENSORS_TYPE 0xF004
#define ATTRID_RADIATION_ALERT_TRESHOLD 0xF005

#define ATTRID_RADIATION_EVENTS_PER_MINUTE 0xF001
#define ATTRID_RADIATION_LEVEL_PER_HOUR 0xF002


#define ZCL_UINT8 ZCL_DATATYPE_UINT8
#define ZCL_UINT16 ZCL_DATATYPE_UINT16
#define ZCL_UINT32 ZCL_DATATYPE_UINT32
/*********************************************************************

And there is another piece of code in the file geiger/Source/zcl_app_data.c

/*********************************************************************
 * ATTRIBUTE DEFINITIONS - Uses REAL cluster IDs
 */

CONST zclAttrRec_t zclApp_AttrsFirstEP[] = {
    {BASIC, {ATTRID_BASIC_ZCL_VERSION, ZCL_UINT8, R, (void *)&zclApp_ZCLVersion}},
    {BASIC, {ATTRID_BASIC_APPL_VERSION, ZCL_UINT8, R, (void *)&zclApp_ApplicationVersion}},
    {BASIC, {ATTRID_BASIC_STACK_VERSION, ZCL_UINT8, R, (void *)&zclApp_StackVersion}},
    {BASIC, {ATTRID_BASIC_HW_VERSION, ZCL_UINT8, R, (void *)&zclApp_HWRevision}},
    {BASIC, {ATTRID_BASIC_MANUFACTURER_NAME, ZCL_DATATYPE_CHAR_STR, R, (void *)zclApp_ManufacturerName}},
    {BASIC, {ATTRID_BASIC_MODEL_ID, ZCL_DATATYPE_CHAR_STR, R, (void *)zclApp_ModelId}},
    {BASIC, {ATTRID_BASIC_DATE_CODE, ZCL_DATATYPE_CHAR_STR, R, (void *)zclApp_DateCode}},
    {BASIC, {ATTRID_BASIC_POWER_SOURCE, ZCL_DATATYPE_ENUM8, R, (void *)&zclApp_PowerSource}},
    {BASIC, {ATTRID_BASIC_SW_BUILD_ID, ZCL_UINT8, R, (void *)&zclApp_ApplicationVersion}},
    {BASIC, {ATTRID_CLUSTER_REVISION, ZCL_UINT16, R, (void *)&zclApp_clusterRevision_all}},

    {ILLUMINANCE, {ATTRID_RADIATION_EVENTS_PER_MINUTE, ZCL_UINT16, RR, (void *)&zclApp_RadiationEventsPerMinute}},
    {ILLUMINANCE, {ATTRID_RADIATION_LEVEL_PER_HOUR, ZCL_UINT32, RR, (void *)&zclApp_RadiationLevelParrotsPerHour}},

    {ILLUMINANCE_CONFIG, {ATTRID_RADIATION_SENSOR_SENSIVITY, ZCL_UINT16, RW, (void *)&zclApp_Config.SensorSensivity}},
    {ILLUMINANCE_CONFIG, {ATTRID_RADIATION_LED_FEEDBACK, ZCL_DATATYPE_BOOLEAN, RW, (void *)&zclApp_Config.LedFeedback}},
    {ILLUMINANCE_CONFIG, {ATTRID_RADIATION_BUZZER_FEEDBACK, ZCL_DATATYPE_BOOLEAN, RW, (void *)&zclApp_Config.BuzzerFeedback}},
    {ILLUMINANCE_CONFIG, {ATTRID_RADIATION_SENSORS_COUNT, ZCL_UINT8, RW, (void *)&zclApp_Config.SensorsCount}},
    {ILLUMINANCE_CONFIG, {ATTRID_RADIATION_SENSORS_TYPE, ZCL_DATATYPE_ENUM8, RW, (void *)&zclApp_Config.SensorType}},
    {ILLUMINANCE_CONFIG, {ATTRID_RADIATION_ALERT_TRESHOLD, ZCL_UINT32, RW, (void *)&zclApp_Config.AlertTreshold}},
};

So, i understood that there are 3 clusters used, 0x0000 Basic, 0x0400 Illuminance Measurement and 0x0401 Illuminance Level Sensing.
As soon as i'm completely new to ZigBee, had to dig into "ZigBee Cluster Library User Guide"...

s-hadinger Jul 18, 2023
Collaborator

Thanks, I got it wrong in the first attempt and didn't realized there was 2 clusters.

Could you try the following:

#Z2Tv1
# DIYRuZ_Geiger
# https://modkam.ru/2020/06/05/indikator-radioaktivnosti-zigbee/
:*,modkam.ru
0400/F001%21,GeigerRadiationEventsPerMinute
0400/F002%23,GeigerRadiationLevelPerHour
0401/F000%21,GeigerSensitivity
0401/F001%10,GeigerLedFeedback
0401/F002%10,GeigerBuzzerFeedback
0401/F003%20,GeigerSensorsCount
0401/F004%30,GeigerSensorsType
0401/F005%23,GeigerAlertThreshold

Eugen-Ku Jul 19, 2023
Author

Yes, this seems to work better now, thank You.

Before that i had problem with setting of GeigerAlertThreshold because of incorrect data type, now it's OK.

21:05:55.870 RUL: RULES#TIMER=2 performs "ZbSend {"Device":"0x03ED","cluster":"0x0400","read":["0xF001","0xF002"]}"
21:05:55.875 MQT: stat/tasmota_5794CC/RESULT = {"ZbSend":"Done"}
21:05:55.886 RUL: RULES#TIMER=2 performs "zbsend {"Device":"0x03ED","Cluster":"0x0401","Read":["0xF001","0xF002","0xF003","0xF004","0xF005"]}"
21:05:55.891 MQT: stat/tasmota_5794CC/RESULT = {"ZbSend":"Done"}
21:05:57.282 MQT: tele/tasmota_5794CC/SENSOR = {"RM_Geiger":{"Device":"0x03ED","Name":"RM_Geiger","GeigerRadiationEventsPerMinute":63,"GeigerRadiationLevelPerHour":38,"GeigerLedFeedback":1,"GeigerBuzzerFeedback":1,"GeigerSensorsCount":1,"GeigerSensorsType":0,"GeigerAlertThreshold":0,"Endpoint":1,"LinkQuality":139}}

21:11:04.929 CMD: ZbSend {"Device":"0x03ED","Write":{"GeigerAlertThreshold":"25"}}
21:11:04.935 MQT: stat/tasmota_5794CC/RESULT = {"ZbSend":"Done"}
21:11:05.912 MQT: tele/tasmota_5794CC/RESULT = {"ZbResponse":{"Device":"0x03ED","Name":"RM_Geiger","Command":"0401_04","Status":0,"StatusMessage":"SUCCESS","Endpoint":1,"LinkQuality":139}}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

how to connect DIYruZ geiger counter to Tasmota-flashed zb-gw03 #19116

{{title}}

Replies: 3 comments 8 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

how to connect DIYruZ geiger counter to Tasmota-flashed zb-gw03 #19116

Eugen-Ku Jul 14, 2023

Replies: 3 comments · 8 replies

s-hadinger Jul 15, 2023 Collaborator

Eugen-Ku Jul 15, 2023 Author

s-hadinger Jul 16, 2023 Collaborator

s-hadinger Jul 16, 2023 Collaborator

s-hadinger Jul 16, 2023 Collaborator

Eugen-Ku Jul 16, 2023 Author

Eugen-Ku Jul 16, 2023 Author

s-hadinger Jul 17, 2023 Collaborator

Eugen-Ku Jul 17, 2023 Author

s-hadinger Jul 18, 2023 Collaborator

Eugen-Ku Jul 19, 2023 Author

Eugen-Ku
Jul 14, 2023

Replies: 3 comments 8 replies

s-hadinger
Jul 15, 2023
Collaborator

Eugen-Ku Jul 15, 2023
Author

s-hadinger Jul 16, 2023
Collaborator

s-hadinger Jul 16, 2023
Collaborator

s-hadinger Jul 16, 2023
Collaborator

Eugen-Ku Jul 16, 2023
Author

Eugen-Ku
Jul 16, 2023
Author

s-hadinger
Jul 17, 2023
Collaborator

Eugen-Ku Jul 17, 2023
Author

s-hadinger Jul 18, 2023
Collaborator

Eugen-Ku Jul 19, 2023
Author