Ok..... so different alarm types would be good then. I'd have to see more of which ones get triggered and how they show up in the timelines.
1 Like
Next time I'm home alone I'll test the alarm with all debugging active to see if I can provide the data
Encountered a unique issue. I added an Abode Device. After I paired the new device, I was not sure how to get it into Abode; perusing the discussion, I decided to enable debugging & trace logging. That got it into Abode, so I thought all was well.
Then I realized that several automations were not working; going into the apps, I found the Abode devices referenced to "Broken", so I reinserted all the Abode devices.
Unfortunately that did not fix it and I seem to have sort of a mess
- If I go to the Hubitat device page, there is one child device for each Abode device, as it should be, and that listing returns the proper data for "Last Activity". All the room names, which I'm fairly sure I assigned are gone, and no devices show status (so I have to go back in and select what I want it to show). The device event log does show the events, such as open/close on a door sensor. This tells me that when I enable debugging & trace logging, perhaps all devices "reimported" into HE and erased all the previous data for these two fields.
- If I go to the Hubitat log, there are two instance of each Abode child device listed at the top, but absolutely none of the trigger events show up. I'm fairly sure they used to show...
Then I realized one of my automations did not have Logging turned on. As soon as I turned on logging, an "Initialized" entry appeared on the log and the automation started to work again.
So the issue that remains is all devices are listed twice in the log header....(Hubitat, left side menu "Logs", Past Logs.) If I filter by device, There are two entries on the drop down by which I can filter, they have different device numbers (light blue text to the left) and it shows the devices were "installed" 13 seconds apart, at the time I enabled debugging & trace logging.
What did I do wrong and how do I fix it?
Possibly a reboot? I have not encountered that. I did add a new device when I added the multi sensor and pretty much did what you said. Should only need to save prefs to be enough for it to traverse the list of devices again. Each device it uses the RF id number from abode. So should always be unique and not able to create multiple devices.
I'm really not sure how to fix it. Hence a reboot suggestion if you are only seeing a single device for each in in the Abode habitat list.
---Eric
1 Like
Thanks for the quick reply - that got me on the right track.
I did a standard hub reboot, but that did not fix it.
In the reboot, advanced options, it offers the option to "Rebuild database on reboot." I presume there is no downside to that and that would be the way to fix it, so tried it, but it also did not solve it.
Then I did another reboot, this time selecting advanced options, and checking both the "Rebuild database on reboot" option and the option to clear the log.
Seems like clearing the log is what finally fixed it...
That sounds like a bug in hubitat, or corruption somewhere. Could be left over devices if you had them and had to delete a while back. I am not sure, but that does not sound like a normal scenerio that should have to be done unless something strnage happens.
Glad it's figured out.
1 Like
@x86cpu Just wanted to give an update, not necessarily drivers related totally. I was able to successfully pair a new First Alert SMC0410 ZWave CO/Smoke combo to Abode today, and after updating the package via HPM it showed up as a child device.
The SMC0410 is the successor to the discontinued First Alert ZCOMBO, and after some back and forth through the Abode Support Team I was able to pair it. Its currently only able to pair with Hubs that are running a Beta firmware that Abode will send out sometime soon, but I was able to get the Support Team to update my Hub to the Beta and paired the SMC0410 successfully.
1 Like
