Looks like 2.2.7.126 fixed the concurrent error.
No... spoke too soon. The error is back. And it requires to send a command twice to get it to stick.
Maybe @bcopeland can tell us what is happening.
I used Aeotec siren 6 (not new) driver and it works without errors.
The problem with this old driver is that pressing the doorbell button does not generate event.
This error is really getting on my nerve. I have to manually and repeatedly send a stop command to get the siren to shut off. Please can something be done about this?
OK I understand. I do have Siren only, thats why its not an issue for me...
I am seeing this error now as well.
I have a rule in RM that triggers a door chime when a contact is opened. It seems to be triggering when the door is opened, and then again a few seconds later. Based on the logging the second chime sound is when the error occurs.
Just another example of how un-ready this product is for real use. Not only does my entire zwave network fail once a day, Hubitat makes up reasons why. Now this siren WONT STOP because of the above error and because it has a battery...OMG. My move BACK to wifi enabled everything is not going to happen soon enough. With a wifi6/unifi setup I dont know why I ever cared to test this...
Because your one anecdotal problem in no way resembles the results of thousands of other users using the platform. I've been "real use" ing this product for 3 years now zero issues.
2 Likes
Though I called out my issue it was more to call awareness to it as well. In general it works fine for me. Even this issue doesn't prevent my functions from working, i just get extra ding ding sound.
sure yet putting 1 device on this hub fails to work over and over and over again, so caveat emptor...I'm glad you and other are lucky enough not to have your fail...yet
but it should be embarrassing to any software/hardware developer to have this come over and over and over
dev:2252021-06-26 10:25:44.649 errorjava.util.ConcurrentModificationException: null (supervisionCheck)
In code they write, code they can remote monitor, and code they represent as ready.
Some people just cannot figure out how to drive a car, that doesn't reflect on and make automobile makers bad?
1 Like
This is fixed in the upcoming 2.2.8 release
5 Likes
and some people put stupid stuff in online boards, doesn't mean they have an iq above 50
An awful lot of hate just because Switch is spelled wrong. 
2 Likes
My Aeotec Siren 6 devices started to fire randomly or not at all after Hubitat updated to the Aeotec Siren 6 New device driver.
As a last resort before ditching my Siren 6 devices in favor of the Dome siren, I made an attempt to migrate Kevin LaFramboise’s Aeotec Siren 6 SmartThings device handler to Hubitat:
I replaced all instances of physicalgraph with hubitat per instructions on the Hubitat community forum:
Although I was expecting Hubitat to throw errors after installing the migrated device driver, I was pleasantly surprised that the migrated Siren 6 driver worked! The chime works by invoking “beep(), siren with siren(), and siren and strobe with both(). So far I have not encountered any problems, and the random firing of the siren has stopped. Neat! Thanks, Kevin!
1 Like
Thank You!
Attached is the link to Kevn LaFramboise's Aeotec Siren 6 driver documentation:
https://community.smartthings.com/t/release-aeotec-siren-6/164654?u=krlaframboise
I created a Github repository (my first) to share Kevin's Aeotec Siren 6 driver migrated to Hubitat.
https://github.com/scottmil/hubitat/blob/main/Aeotec_Siren_6-laframboise.groovy
