#Morning I have a CORE install on Fedora
hasty solar
barren heart
share the driver logs with dpaste.org or something so someone can jump in and help when they're around
hasty solar
2023-01-13T15:42:10.130Z SERIAL » 0x011d001303169f03e300ac3454ac81e49d43f0acf7af9df77b75dc772509a7 (31 bytes)
2023-01-13T15:42:10.132Z DRIVER » [Node 003] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 9
└─[Security2CCMessageEncapsulation]
│ sequence number: 227
└─[SupervisionCCGet]
│ session id: 53
│ request updates: true
└─[ConfigurationCCSet]
parameter #: 2
reset to default: false
value size: 2
value format: UnsignedInteger
value: 32
2023-01-13T15:42:10.135Z SERIAL « [ACK] (0x06)
2023-01-13T15:42:10.139Z SERIAL « 0x0104011301e8 (6 bytes)
2023-01-13T15:42:10.140Z SERIAL » [ACK] (0x06)
2023-01-13T15:42:10.141Z DRIVER « [RES] [SendData]
was sent: true
2023-01-13T15:42:10.154Z SERIAL « 0x010500130900e0 (7 bytes)
2023-01-13T15:42:10.154Z SERIAL » [ACK] (0x06)
2023-01-13T15:42:10.155Z DRIVER « [REQ] [SendData]
callback id: 9
transmit status: OK
2023-01-13T15:42:10.167Z SERIAL « 0x011700040003119f031b00ff9e2f0a5dc55f55965b7e2fd1e2 (25 bytes)
2023-01-13T15:42:10.169Z SERIAL » [ACK] (0x06)
2023-01-13T15:42:10.170Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 27
└─[SupervisionCCReport]
session id: 53
more updates follow: false
status: Fail
duration: 0s
2023-01-13T15:42:11.197Z SERIAL » 0x01160013030f9f03e400644c7e3bf071cb7da15705250a08 (24 bytes)
2023-01-13T15:42:11.198Z DRIVER » [Node 003] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 10
└─[Security2CCMessageEncapsulation]
│ sequence number: 228
└─[ConfigurationCCGet]
parameter #: 2
shut gorge
what make/model?
hasty solar
Minoston MP21Z
shut gorge
if i recall those are hunks of crap not worth the plastic they're made from
hasty solar
I have not tired other devices yet. My next device will be a motion switch, but I will need to untie the motion for directly controlling the switch.
shut gorge
you will need to get your full driver log and open an issue on the zwavejs github for assistance with that device
hasty solar
if i recall those are hunks of crap not worth the plastic they're made from
Oh. Did not know that. So, far I think it works fine, when controlled directly. The 2 param is an auto time off. ( which I can do in HA without using the device param )
shut gorge
based on your snippet, it's reporting that it supports supervision CC but it actually doesn't
Al would be able to tell you once you post your driver log into an issue on the zwavejs github page
hasty solar
OK, the same log I shared here? ( As I'm not aware of another log. )
hasty solar
OK.
Thanks for helping. In the meantime, maybe I will try one of my other devices.
Are the "Enbrighten Z-Wave Plus Smart Motion Sensor Light Switch, On/Off, Vacancy / Occupancy" OK?
shut gorge
i hear they suck
hasty solar
Crap.
hasty solar
K.
shut gorge
like you can't adjust the motion timeout or some jazz like that
hasty solar
Ok thanks, I also have "Zooz 700 Series Z-Wave Plus Mesh Network Scene Controller ZEN32"
barren heart
i hear they suck
They suck
Aeotec is good too just overpriced
As a rule of thumb I wouldn’t just throw anything on your mesh and I’d ask for hardware recommendations here to confirm you don’t buy crap implementations
shut gorge
if you're looking for smart plugs, I'd go with the Zooz ones
barren heart
Or Wi-Fi ones flashed with esphome
shut gorge
depends on your taste or if you're trying to build out your zwave mesh
barren heart
Low bandwidth mesh means you gotta work within those constraints and to me power monitoring doesn’t fit within them well
I.e. how they can’t be reporting on whatever interval you want because it will cause the mesh to always be busy
Not worth having to fight that / work around it imo
shut gorge
assuming they're using it for power monitoring
barren heart
Yea
shut gorge
even then it's not that much of an issue