This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

Zigbee gateway integration
Yes no data corruption. It was not us, SE did it. In our app it is as stated in our documentations.
------------------------------
Ctrl+F5
Reply
(16.11.2024, 11:45)stianj Wrote:
(15.11.2024, 13:16)admin Wrote: @stianj, enable debug logging in ZigBee app then reset and pair your lamp again. Send the logs afterwards.

Thanks. Logs attached. I enabled debug logging, deleted the bulb from the app, reset the bulb, opened the network, re-joined the bulb, configured all the GA's, then turned it on and off and changed brightness using the GA's.

The bulb in question has address 001788010b270b60

But result is still the same, the status GA's do not update unless I use "Read" on the Control and status page. This goes for all six Hue bulbs I have.

I can't quite see I'm doing anything wrong here, but I'm very open to you proving me otherwise Smile

I feel a bit ignored Angel
Reply
(20.11.2024, 10:10)stianj Wrote:
(16.11.2024, 11:45)stianj Wrote:
(15.11.2024, 13:16)admin Wrote: @stianj, enable debug logging in ZigBee app then reset and pair your lamp again. Send the logs afterwards.

Thanks. Logs attached. I enabled debug logging, deleted the bulb from the app, reset the bulb, opened the network, re-joined the bulb, configured all the GA's, then turned it on and off and changed brightness using the GA's.

The bulb in question has address 001788010b270b60

But result is still the same, the status GA's do not update unless I use "Read" on the Control and status page. This goes for all six Hue bulbs I have.

I can't quite see I'm doing anything wrong here, but I'm very open to you proving me otherwise Smile

I feel a bit ignored Angel
We identified the issue but it require some development on our side and it will take some unspecified amount time.
------------------------------
Ctrl+F5
Reply
(20.11.2024, 10:42)Daniel Wrote: We identified the issue but it require some development on our side and it will take some unspecified amount time.

Thanks! That's fine, it's just nice to know that my issue is real - not just something I'm doing wrong, and also that you are working to fix it.

Appreciate it! Smile
Reply
Hello Daniel,

I am trying to read the rms current from a smart socket. But the code is not correct. Is it possible for you to give some guidance?

Code:
zb = require('applibs.zigbee.zigbee')

local address =  '70b3d52b600a3f9c'
endpoint = 3
cluster = 0x0B04 --
attrs = { 254 , 69 ,17, 401 }



-- Get rmscurrent from HaElectricalMeasurement cluster
local res, err = zb.cmdsync('getrawattribute', address, cluster, 401)

-- Log the result or the error
if err then
    log("Error retrieving rmscurrent: " .. err)
else
    log("RMS Current: " .. tostring(res))
end


--[[

Manufacturer: _TZ3000_okaz9tjs
Model: TS011F
Firmware version: 500+TZSKT31BS102

Device type: Router
Power source: Mains
Receive when idle: Yes

Endpoint 1
Profile: 260
Input clusters
- Basic (0)
- OnOff (6)
- Identify (3)
- Groups (4)
- Scenes (5)
- 57345
- HaElectricalMeasurement (2820)
- SeMetering (1794)

Reported attributes
- calclevel: 254
- currentsummdelivered: 665
- haactivepower: 69
- onoff: true
- prevlevel: 254
- rmscurrent: 401
- rmsvoltage: 241

]]--
Reply
(19.11.2024, 17:15)admin Wrote: Have you done reset and pair procedure after updating the app?

Yes i did it but no change
Reply


Forum Jump: