-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outstanding Devices #10
Comments
device_type.door_contact
Dimmer level stored in statusEx. Only dimmer and hue change dim level. |
For Temp/Humidity/Light Sensor - Let me know if this is the right data or if you need additional info. { |
@MisterWil I've also got mini door/window sensors as well as the thin strip door/window sensor if that helps. |
@MisterWil as per @shred86's advice, i'm posting this here. I'd love to be able to get my Smoke/CO zwave devices into Home Assistant and/or abodepy. Here is a JSON of the device [ |
This. Would love this. |
Dome Water Main Shut-Off (DMWV1) { |
@MisterWil Since you're doing updates and whatnot... If there's any chance you can add them to abode.py so that we can tie them into HA and other apps, we'd be very grateful (we're all very grateful for this project and the work you've already done). Thank you! |
|
I just tested my Abode smoke listener and it doesn't report anything from the device JSON. However, Abode's socketio server does push out an event that the event_controller is currently processing:
At least for Home Assistant, I wonder if there is a way to update the entity state based on these event reports. |
I would probably need to see more information about the event because from what I can see here its just a timeline event and I'm not sure if timeline events identify what device caused the fault. Unfortunately I don't seem to be outputting a debug-level log for the full event data. If you feel like it, adding the line: |
@medic459 I'm pretty sure valves are already supported by AbodePy after running some tests today. |
Posting this just for future reference in case the current integration breaks. I just received the new Abode Occupancy sensor. It pairs as two separate devices, one motion sensor and one temp/humidity/lux sensor: The motion/occupancy sensor:
The temp/humidity/lux sensor:
|
Again, just for future reference. Keypad 2 pairs to Abode as two devices, one keypad and one motion sensor: Keypad:
Motion sensor:
|
New to this project, but I'm curious: how do you suppose it would show its status? There is the 'status: "Online"' and 'status_display: "Online"' fields which appear the same as they do for occupancy sensors that are not tripped. I haven't actually tripped the smoke/co detector and Abode's website implies that doing a test on the First Alert device doesn't actually generate an alarm signal to the gateway. My understanding is the only way to fully test the device and have the monitor center call is to physically trigger it with a smoke emulator substance (or actual smoke, I guess). Only then would we be able to see the difference between the idle state and a tripped state. And that begs the question...does the device tell you if it was smoke or CO that tripped the alarm? I see a "statuses" field that is empty for smoke/co detector, but has "motion" values for occupancy. Is that what would indicate there's no status that gets reported? I guess at some point I can actually trip one of these with a match to see how or if the status changes so it can be monitored. |
It's reported through one of these timeline events:
Some sensors only report their state internally to the gateway as well, like the Iota motion sensor, meaning it doesn't report motion in the JSON message via Abode's socketio server but rather just to the local Iota hub (or itself in this case). This is why you're able to setup CUE automations with it based on motion but don't actually see its motion state in the web UI. I've triggered my smoke detector before (I realize this isn't the Smoke/CO2 detector) and it didn't report anything in the JSON data. It was just a timeline event. |
Once I have a chance, I'll trip on of my First Alert smoke/CO detectors to see what happens. How exactly will I be able to confirm the alarm actually throws an event with JSON data and not simply a timeline entry? |
You will just have to watch for the actual device JSON data and timeline event as both will be pushed. Just save both and share them here if you can. |
JSON data for the Abode Smoke Alarm Monitor. It doesn't show any updates when smoke is detected, but just for future reference:
|
@MisterWil do you know abodepy can set add a new code for a keypad? Or if it's even possible to do so via the API? |
If it an be done via the web interface then it's likely you can do so via an API, but I've not investigated it. |
JSON for the Abode Cam 2:
|
@MisterWil looks like the existing camera code works for the Cam 2 after I add the type tag |
Below is an incomplete and possibly duplicated list of devices that are supported by Abode but that are not currently supported by this library because I do not have the device json responses of.
If these devices are to be added to this library then I need the json values of the devices. This can be done by inspecting the network activity on the Abode webapp and pulling the data from the devices request.
Getting Devices through Web App
Getting Devices through AbodePy
abodepy -u USERNAME -p PASSWORD --devices
to get a list of devicesabodepy -u USERNAME -p PASSWORD --json DEVICE_ID
with the device ID of the device you'd like to shareDevices and Open Issues
The text was updated successfully, but these errors were encountered: