Hi, im integrating an Airzone Aidoo AZAI6ZWUMEL z-wave module for my Mits mini-split. It paired ok but joined as Device, so I guess the fingerprint is not in the database yet. I can provide if needed. I set it to Generic Z-Wave Plus Thermostat, and it seems to be talking. I cant seem to set it to Auto mode. Not sure where the disconnect is with that, but the main issue for me posting is that even with Text Logging and Debug logging enabled, im not getting any logs from the device at all since it paired. Is the driver just not enabled to do any logging? it sure would help to see the activity back and forth to know what's going on with it, ie supported modes might be missing Auto. Thanks.
Did you try the Generic z-wave dt thermostat driver?
No, if you have debug logging enabled, everything coming in from the device should appear in Logs, first as at least debug entries starting with "parse:" and possibly later with more human-friendly information about which Z-Wave command classes it got parsed into (and, if descriptionText logging is enabled, later information about what events were generated from that).
If debug logging is on and none of this is happening, it's not the driver but the device. What hub model are you using, and do you see a "Switch to Legacy Z-Wave" or ""Switch to Z-Wave JS" button in Settings > Z-Wave Details? (Don't do anything with either; it will just reveal information about your hub's Z-Wave configuration that would be good to know.) This is both generally true but also something I verified on this specific driver in case there was a typo, etc.
You could try the driver mentioned above, though either should log commands (reports, etc.) sent to the hub by the device. That could mean it stopped working, but if it's still receiving commands (like setpoint changes), it must not have. I'd try a "reboot" of the device (disconnecting it from power for a few seconds for a thermostat) to see if that helps, or you could try an exclusion and re-inclusion (being careful to remove it from any apps you might already be using it in first, or swap it out with a virtual device to easily hold its place temporarily if you want to use Settings > Swap Device to make it easy while still being able to do a proper Z-Wave exclusion in the meantime).
1 Like
Thanks I eventually got it working, not sure why it wasn't at first, I tried the Device driver, and then the DT driver, and I think then it started logging, went back to the regular z-wave plus thrermostat driver, and its still logging, so all good. Its on a C-5 in case that relevant, so definitely not JS.
