I keep getting this error: es3zonestate with code 2830, and room lighting fails to turn on lights, and sometimes turning them off.
Here is what a room light rule I have that has lost connectivity with a z wave light:
Those two problems are undoubtedly unrelated, the other one you mentioned being a product of a community app (Echo Speaks) that is unlikely to fit into your Room Lighting setup. Either way, when an app is not behaving as expected, the best thing to do is to enable all logging options it has and then check the output of Logs for clues. See: How to Troubleshoot Apps or Devices | Hubitat Documentation for more on this technique.
But because I can't resist a guess:
Room Lighting, or any app, does not connect directly to Z-Wave, Zigbee, etc. -- it ust sends commands and reads attributes as reported by the driver, all of which are ultimately handled by the that and your mesh network. If the light truly "falls off" your network, i.e., stops responding to commands on the device detail page and stops reporting back (though reporting back can be odd with old Z-Wave devices for physical changes, so you might want to share what specific device this is anyway), the problem lies with the driver (unlikely if you're using the right one), device, or your network. These are all separates issue from the app but ones you'd need to troubleshoot for any app to work correctly.
But first: logs. 
How does this and Echo Speaks fit?
What two problems are you referring to?
I missed something.....
The light in this screenshot is a Evalogik dimmer using the built in driver, NOT a community driver.
Other lights have failed to react in the past though...
A ZOOZ zen77 dimmer has also failed to turn on and sometimes off as well, and when I checked, the red X was in it's room lighting app just like my screenshot above, but in a different rule of course.
A note though....
I just added two of the Linptech z wave mm wave presence sensors, and noticed in hub info that things have been running alot higher than I previously have seen. Here is a screenshot with only one of the sensors paired with my C8:
The temp is high also at 111F to 116F!
I am going to remove the remaining sensor to see if things get quieter as I have been reading that these sensors are a little chatty.
Just thinking that these sensors might be flooding my Zwave network and stepping on other devices. They aren't ready for prime time yet.....
I went through my logs and found two other es3's with different values happening at the same time, so I investigated and found they were due to Echo Speaks enabling two different zones:
The tipoff was they occurred at the same time.
I deleted both zones in echo speaks and we'll see what happens with the es3 errors.
I didn't know that these were echo speaks errors, but I guess that is the es for echo speaks. Would have been a little more intuitive if the error actually indicated echo speaks!
I don't think those are are errors at all. They just look like location events to me...
That's what the "es3" (Echo Speaks, version 3) stands for. 
But yes, that took a good guess and look at the code to verify. In any case, naming is the best you can do for these, as location events are tied to your "location" (hub) and not a specific device by definition. What use they have in this case, I don't know...They're rarely used outside of hub events you might care about, mostly built-in...but I don't use this app.
That makes sense... I didn't know what the es3 meant, and I thank you for clearing that up! Makes sense now.
I thought they were errors since they seemed to occur when the zwave devices went off line, but probably a coincidence.
another note.... looking at my zwave details, I found a ghost! Last week I bought (and have since returned) an Ultralock pro, and included it to test.
When trying to remove it, things went a little strange and I THOUGHT it had removed, but didn't check.
Well it did NOT remove and left a ghost.
I just removed it with the Zstick so I will watch things and see how it goes.
I know this is getting off topic but wanted to add this here.
So now both mm wave sensors are gone and the ghost lock.
Hub is still busy and warm though....
Download the Hubitat app
