Oh thats awesome!, Well at least you get some kind of kickback from them. If they give you a new device do they give you the full specs for the device or do you have to probe it somehow to see what it responds to?
Also thanks to both of you for all the hard work on these drivers!!
They give me full specs usually. I also run some probs to check the settings and command classes out fully.
@bertabcd1234 I am finding that I have set the "Do not flash when motion is detected" I have set this twice now on the device and it still flashes when motion is detected. Not a huge deal but is there anything I can provide you to help troubleshoot this?
I am seeing this in my logs when i refresh a save
[dev:480](http://192.168.86.205/logs?tab=past&deviceId=480#)2024-12-16 09:19:30.393 PM[debug](http://192.168.86.205/logs?tab=past&deviceId=480#)parameter 183 (size 2) is null but should be 1; adding to commands...
[dev:480](http://192.168.86.205/logs?tab=past&deviceId=480#)2024-12-16 09:19:30.388 PM[debug](http://192.168.86.205/logs?tab=past&deviceId=480#)parameter 19 (size 1) is null but should be 0; adding to commands...
I don't believe these should mater but I'm not sure what these parameters are to just get rid of them in the warnings log
It seems like no matter what I set parameter 19 to the logs aways says:
"parameter 19 (size 1) is null but should be 1; adding to commands..." Its like its not getting this value maybe?
I'm assuming size 1 means it's a binary value and the check for null is to assume its not been set so this is the default value
Did you wake the device after saving the preferences, assuming you're on battery power? Parameter 19 sounds like the one you're looking for, and it has no stored/received value for that, hence the log entry about it wanting to send one to the device. Pressing and holding the Z-Wave button for 3 seconds on the device should wake it up, but consult your manual to be sure, as they like to keep you on your toes with unexpected changes. Sleepy Z-Wave devices won't listen for these commands unless they are awake. The driver will basically queue them until it knows it's awake.
No, that is the byte size of the parameter (not super relevant for setting the value as a user of the driver, more if you're writing the driver--there in case I mess something up...).
This is not a check for null; it's the last reported value, which the driver saves to economize and only send ones it knows to be different. This just means there has been no such report from the device.
It is likely at the default value per the device manual in this case, though even that may be explicitly reflected at some point.
If I have the device plugged in (no battery) should it get a setting update faster or will it still take time for the device to wake up?
No, that should be immediate. It's possible I just didn't test this device enough on mains power, or maybe something changed between generations. If you included it as battery-powered (I think the 800LR model is supposed to not care if you switch?), try temporarily reverting to that and waking the device to see if it helps.
I remember the manual warning about switching modes but that was because if you set it up on mains then switched to battery it would tell the device to be a z-wave repeater and will kill the battery in a few days. I can try to re-include it as a battery device. Im worried I wont get updates as fast though.. but I am assuming you mean once the parameter 19 is set just re-include it on mains?
If you exclude and re-include, it might reset and lose the value of the parameter.
I was thinking just revert to battery for a few minutes to test the above theory, particularly if you originally included the device on batteries and switched to mains.
You could also try another approach like the Basic Z-Wave Tool to set the parameter, though I am not sure offhand what is going on in the driver since that should also work if the above is not the case for you.
I have switched a few times from your driver to the builtin one. Might be the issue. NP Ill figure it out!
So If I use the Basic tool and I hit Get Parameter report With noting set so it should give a full list of set parameters) Nothing happens.. Does this normally mean that the device is offline or not awake?
NM It's in the logs not on the UI
Update: Setting Parameter 19 to 0 worked using the basic driver so were all good!!
Funny, just came here with similar issue about swapping batteries and mains power for Zse11. And I recall same warning about not using both, or you could brick the device.
Anyways, I finally installed ceiling outlets where I had my battery powered ZSE11’s (3x). After removing the batteries and plugging them in, they all behaved as expected. I changed preferences so they’d be more responsive to changes in lux, humidity, etc. All works swimmingly, except…
The powerSource attribute remains “Battery”, even after a Save and Configure. Is this expected? It’s only been 10-15 mins so maybe I need to learn patience (yeah right).
I could exclude/reinclude but selfishly I’d like to avoid all the app reinsertions.
Do you see anything in debug logs when you change power source? (Make sure they are enabled, of course.)
No I didn’t (and I looked).
When you say “change power source”, I’m interpreting that as simply removing batteries, plugging into mains power, waiting, then a few minutes later thinking I should hit the Config button. Kinda like that? 
That's pretty much what I was thinking, though "Configure" shouldn't be necessary (can't hurt if you don't see anything happen on its own, but I'm not sure it will do anything interesting, either).
hey thanks everyone. I just got my zse11 Q and I'm very excited to start using it but have been pretty disappointed with what I'm seeing in habitat C8. When I initially do z-wave inclusion it uses the default driver and only show limited information (as expected), but no motion status. Also when I cover the sensor the lux drops quickly and reflects that.
I have tried both the driver by @bertabcd1234 and @jtp10181 to no avail. I cannot get motion to work for the life of me. If I turn on debug logging, I can see that it show motion going to an active state, and is see the light flash on the device to indicate it detected motion, but if it does not show up in the device page under "status" and I can't trigger an automation off of it.
Any ideas? I'm getting pretty frustrated and will return if I can't get it to work. Any ideas?
here is what I have tried:
I'm open to anything as I really want this to work! appreciate any help!
Just to add one more bit of information. It doesn't seem any of my "statuses" in hubitat are updating in response to environment changes. I can see the values changing the in the log but they aren to updated on the device page.
This matches what I'm seeing in HomeAssistant which I have all devices in my hubitat connected to. For example, even though the lux right now is 1lx right now, the status in the device page is showing 239lx which matches what home assistant is showing
Can you share what information you see that supports this concluision? (A screenshot or perhaps well-formatted copy/paste of the relevant log entries, especially the ones labled "debug" but surrounding entries may also be helpful, is what I'm asking for.)
If every other device is working as expected for you, this is an odd problem. The only thing I can think of that might help is a Settings > Reboot with the option to rebuild your database checked under the advanced options. If that doesn't help, maybe a Settings > Shut Down, unplug the hub for about 30 seconds (after the LED turns red), then plug it back in -- the goal being to fully power cycle the Z-Wave radio.
Thanks @bertabcd1234 . I did the power cycle as you suggested and still nothing. no states are being updated on the device page but logs are showing things happening. I have attached a file with some relevant logs.
dev:462025-01-02 22:32:35.351errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-02 22:32:35.343infoMaster Bathroom Small Lights Sensor: motion set to active
dev:462025-01-02 22:22:55.528errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-02 22:22:55.521infoMaster Bathroom Small Lights Sensor: motion set to inactive
dev:462025-01-02 22:22:31.928errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-02 22:22:31.922infoMaster Bathroom Small Lights Sensor: illuminance set to 13lx
dev:462025-01-02 22:22:14.971errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-02 22:22:14.965infoMaster Bathroom Small Lights Sensor: motion set to active
dev:462025-01-02 22:17:12.627errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-02 22:17:12.621infoMaster Bathroom Small Lights Sensor: motion set to inactive
..............(break to show later lux and temp and humidity logs)
dev:462025-01-03 07:01:35.315errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-03 07:01:35.268infoMaster Bathroom Small Lights Sensor: temperature set to 62°F
dev:462025-01-03 03:33:08.901errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-03 03:33:08.862infoMaster Bathroom Small Lights Sensor: temperature set to 63.1°F
dev:462025-01-03 02:14:20.951errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-03 02:14:20.854infoMaster Bathroom Small Lights Sensor: humidity set to 47%
dev:462025-01-02 23:55:41.549errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-02 23:55:41.543infoMaster Bathroom Small Lights Sensor: humidity set to 53%
dev:462025-01-02 23:14:50.976errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-02 23:14:50.970infoMaster Bathroom Small Lights Sensor: illuminance set to 1lx
dev:462025-01-02 23:14:20.305errorcom.hubitat.app.exception.LimitExceededException: Device 46 generates excessive hub load on line 588 (method parse)
dev:462025-01-02 23:14:20.299infoMaster Bathroom Small Lights Sensor: illuminance set to 44lx
Download the Hubitat app
