Sure thing. Thank you.
Hi - installed the new version today, and am happy to report that since installed the Abode parent device log is free of errors!! Thank you !
However, also since I installed the update, the Abode Parent Device log has multiple "Got unknown child event:" debug entries. This never used to happen, so it is related to the update.
These entries are exactly correlated with Cam2 Video Capture events from several Cam2's.
Is it possible that the driver for the doorbell is picking up the Cam2 events?
Well.... this is very disappointing. I do not see any devices. Was there any other log output?
I tried removing the parent device and reinstalling from scratch. Unfortunately it’s still only producing one child:
Power cycle your hub and then check for the child devices.
I 100% believe you. I just have no idea why it's not logging any of the child devices. And just to be sure (I know you said it). You have "Create child devices" checked? Try enabling trace/debug again and save Prefs.... then open log in another area, find the Abode live logging, then once again save prefs to see if anything at all shows up. It only probes child devices when you "Save Preferences".
The "Components" mark is not needed, it just lets you delete them on your own later. I'm very stumped as the logs show nothing about any child device probing or logging.
This is my full prefs I use. Some may or may not apply
Is there a way to deal with the Abode Cam 2 child? It is triggering the unknown child + json dump on the logs. I commented out the + json part on line 727(?) but perhaps there is a better way. Thanks
Can you post a snippet of the logs so I can see and try to filter it out?
Is there a way to bring in the Cam2 as a device, and allow people to both use the triggers for automations or in rules?
Triggers would be motion detected in standard mode, person, package or pet detected in smart detect mode.
Being able to turn on a light when it detects a person would be awesome.
I can do my best, yes. I would just need to see some timeline event logs, OR other debug/trace logs that flag what device, event, etc... So I can capture/trigger them. I believe also I would need the debug to get the Cam2 added as a device.
I did get a "free" cam2 when I got my set. I just have not set it up yet, so I may take some time to do that. Not a lot of free time at the moment though (year end things at work).
1 Like
Hi - first, thank you so much for doing this. I was bummed that the original version was abandoned. Using the child devices is so much easier than the gateway timeline, especially since I also pass these devices to other software via Maker API, so I was needing to decode the timeline there as well.
I saw the discussion about the islogged in value not showing correctly, which is an issue I'm having as well. I use MFA and I'm able to log in to Abode via this app with no problem. It clearly is logged and everything works as expected, the the "isloggedin" value says false. In the past, I used this to drive a rule to notify me if it got logged out. (Which hasn't happened with this new version, but I'd still like to monitor it).
The discussion here got pretty confusing - but if I'm using MFA, is there a solution to that parameter not showing the correct value?
( I do have the original Abode app still installed - perhaps I need to uninstall that ? )
So....if you copied/pasted the 2024 Abode Alarm on top of the other code. It will change the "namespace" name. The 2024 name space is "x86cpu", while the isLogged in device probably is the older namespace, so the new one does not have permission to adjust the older device.
You can try deleting the isLogged in, but it may affect all other rules with it. If you cannot delete it, go down, "save device", then "remove". It's marked as a component device, which you cannot easily remove. The new 2024 drivers should auto-create it again if it is missing.
The BEST way I think to upgrade..... (hard forme to try). Paste the new 2024 driver version on top of old Abode Alarm code in drivers area. (or importurl). Save that. Remove the islogged device like above.
Then use HPM to match up to the new 2024 driver, then also re-install the 2024 driver so it gets all the children. Only then.... flip the create child devices.
Hi I am experiencing similar troubles with child devices not showing. Installed via HPM, logged in with MFA, am able to arm/disarm, however no other child devices are showing other than "Abode Alarm 2024-Is Armed". I've tried disabling MFA, entering data in the MFA seed box, uninstalling/reinstalling, hitting save preferences every minute, enabling logging info, create child devices is activated, power cycling, etc. All drivers are showing up as well.
Nothing is coming up as "error" as of now either.
Is there something I am doing wrong that is preventing child devices from showing up?
Agree with everyone else. Your wonderful. so happy you started this back up.
Can we add water leak sensor child? is there something I can provide to help create it?
1 Like
There was another user that had this issue too. See [RELEASE] Abode Alarm system driver 2024 - #87 by x86cpu
Basically need debug/trace output enabled, then save prefs and see what devices it finds.
Just need output for the device when you have trace/debug enabled. Then I can see what it looks like. Once I add it, I may need the output again when it detects a "leak" and "clear" in order to determine events to send.
Thanks, i can do that. i will get you the info shortly and then can get you any other info you need.
This is what I am seeing currently:
I am a novice at all this, but it looks like its only showing a Motion Sensor as a found device?
Yes. you need to enable trace/debug, save prefs. Then you'll want to save prefs a 2nd time. Check logs. The logs should indicate all the devices and if you have the child devices checked then it should log and create all those devices.
From that log is sees motion as a device, but may not have created the child devices yet.
