spanishpolt.blogg.se - Abode iota code

#Abode iota code how to#

However the issue reported above by troyc appears to be a bug in the Abode cloud api, such that motion sensor status coming back in reply/response from that api is always stuck as “on” (or “motion detected”). The motion sensor in IOTA device is accurate and does correctly report the on/off status when motion is detected. That means there is no need to use Abode integration in HA and sign-in to Abode account and depend on the long route through cloud/internet to have HA talk to Abode IOTA device… as long as HA and IOTA are on the same in-home network/wifi. See links below for details.īenefit: no need to create separate Helper (binary_sensor) and related automations in HA, and no need for additional CUE automations in Abode app, and no need to create junk email address to receive notifications from Abode automations…īonus Benefit: This method will create a direct connection between HA and IOTA device within your local network. This doesn’t fix the underlying problem where the actual IOTA motion sensor state is not correctly being reported, only works around it with another sensor.Īnother alternative is to use the HomeKit Controller integration in HA, and use that to connect Abode IOTA device within your local network. In the GUI, it behaves just as you would expect it should with motion state changes and icon color changes. Now I have a motion binary sensor that is tripped by the execution of the CUE automations on Abode instead of always showing “Motion Detected”. Value_template: ""Įntity_id: input_boolean.iota_motion_boolean

When this is done, your iota_motion_boolean should follow the state of the motion sensor.

For the action, use the input_boolean.turn_on or. Use the CUE automation name as the “device_name” field.

In Home Assistant, create an automation that is triggered by the execution of those CUE automations with the Event:abode_automation trigger.

In Home Assistant, create an input_boolean called “iota_motion_boolean”.

Let’s call these CUE automations iota_on and iota_off. Since there’s no “no-op” type action in Abode, I had to create a dummy user account to where I could send a bogus notification.

Create two CUE automations on Abode that are triggered by ON and OFF of the IOTA motion sensor.

To work around this problem, I’ve created my own binary sensor to replace the problematic IOTA motion sensor notification.

#Abode iota code how to#

Is there a way to debug the lower levels of this code at the point when the Abode integration code is setting the state of this motion sensor?Īnd as a workaround, Is there also a way to create an automation or script that changes the internal state of the motion sensor back to “off” shortly after it gets turned on? I see in the automation actions I can call services, but I haven’t seen how to change the internal state of the sensor without using the developer tool interface. What I need to know is whether or not this is a bug in the Abode Code Integration code in HA, or is a problem with the Abode actually reporting the wrong state of the sensor when it triggers. Note that the Abode system itself knows the state has changed properly since its own CUE automations respond as expected to the sensor state change.

Then, when the sensor is supposed to send an “off” report after a minute of no motion, the HA state again switches on “on”. I can then set the internal state of the sensor back to “off” using the developer tool. So with the sensor state set to “off”, after physically triggering motion the HA state goes to “on”. After playing with the state of the motion sensor in HA, I’ve found that HA is seeing all status updates from the sensor as “on”. The Iota has a motion sensor that always shows as “motion detected” in HA. I have an Abode system that now has the Iota as the base unit.