The null isEmpty error I'll need to fix and set the seed to empty on installed. I'll also put a null check to prevent it.
For now though, you should be able to save preferences and that should set the MFA seed to something other than null.
Oh... I'm not sure what exactly will happen with both installed at the same time. There are some overlap of device names, so it may not work as well with both installed. I'd recommend one or the other. I can only assist with the 2024 version though.
I have not forgotten about setting up my new devices. Been very busy lately and have not had a chance to. I do have a motion and multi sensor now, so once I set it up that should help getting those to respond with better data.
1 Like
AND update.....
The Multi Sensor should be fixed now, pulling in all values.
The Motion only sensor that did not always send an inactive now will auto inactive after 60 seconds (could make this configurable).
I added some hardcoded debugging in the event a GLASS or Smoke event triggers. All this means is if a Smoke or GLASS sensor goes off it will be in logs, if anyone sees it, could I have a capture of that logging reply?
Another update.... only to try to handle a null mfa_seed from other errors.
Edit 2:
Back to my original post: Even when the Hubitat is connected to Abode, the IsLoggedIn field = false. However, WebSocketconnected = true, and the Abode device on Hubitat is receiving data from the Gateway timeline.
Logged in false is not what I am seeing as shown below. You have filled in your my.goabode credentials? Just in case you or another reader uses a whole house VPN - Something I found helpful was to assign Abode and Hubitat static DHCP addresses then exempt them from my routers VPN. Abode is particularly picky about connections through a VPN. But so is Google for some things. I wound up exempting the Nest door bell and Abode camera among a few other WiFi devices too.
Current States
- gatewayMode : standby
- gatewayTimeline : Hub=Disarmed - Standby
- isLoggedIn : true
- lastResult : 200 PUT /api/v1/panel/mode/1/standby successful
We're you finally able to get updated to the 2024 version?
@x86cpu : My first update to the 2024 version was via Github, before you had it on HPM. I've never been able to get the Abode 2024 version to update via HPM.
I just now went to your Github, copied the driver code, and pasted it, so I'm using the most up to date driver. I'm also hoping that resolves the problem with HPM not updating.
I just sucessfully changed Abode system status from Standy to Home using Hubitat, so I know it is connected. Still shows as "IsLoggedIn : false"
Enable logs and see if anything stands out.
The only thing I can suggest at this point is uninstall and install the 2024 version. I am not fully sure, as swapping should work. I know the "Abode Alarm-isArmed" may not fully work if not deleted and recreated as it has a different namespace which changes in the 2024 version.
