Did you delete the child device and let it recreate it as a contact?
Yes. It now shows as an "Insteon Contact Child".
When you make device changes with the setup, make sure you change the config.json, stop the server and client, then restart the server and client, then delete the child and click initialize, save preferences and then save device.
If you did all this, and it doesn't respond then your results are even worse than mine and the reason I don't think we're in a good place to use this a an input sensor. Contacts and Leak sensors responded fine in testing, but the IO is a different beast. I have a hell of a time just configuring mine in the Insteon app.
Yes. I've been restarting the server and client apps. Just to be safe, I've actually been completely removing the Parent device and recreating it as well.
That you do not need to do. Parent apps don't rely on the children, it's the other way round.
@peter_aquino open the hubitat log page in another window. Let's see if there are any logs coming through whilst you are triggering the device.
With the logs open, I see the remote button push, and the command sent to the relay, but there's no indication of any messages received from the contact sensor. I noticed that all of the dimmer child devices have an option to "Enable debug logging" but the contact and leak sensors do not have that feature. Would that be the reason I don't see anything for those 2 in the logs or should that show up automatically?
Just to clarify on how I have the I/O Linc setup in HE, I'm using the Parent/Child setup for the sensor and I have the relay configured using the HTTP Switch/Dimmer driver. I didn't configure the relay device for Insteon-Server since I don't need any status updates for it.
You should be able to see them if the logging is enabled, but might need to add some debug lines to those child devices? @cwwilson08 is that the reason?
All messages sent to the child devices should be logged first by the parent (all communication with the insteon hub / insteon server goes through the parent).
If the parent is not getting anything from the insteon server I would need to see the output of the insteon server.
@peter_aquino do you have the debug loggin switch on in the parent device?
1 Like
Yes
Ok sorry. It is just not going to work for now. It does not seem the insteon server is sending the stuff over that we need for this. If I see an easy fix I will let you know.
If it helps, here's what the Insteon Server is seeing...
Door Opening Events:
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"000001","extended":false,"messageType":6,"hopsLeft":1,"maxHops":3,"command1":"11","command2":"00","raw":"02503D4D5B000001C71100"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"000001","extended":false,"messageType":6,"hopsLeft":1,"maxHops":3,"command1":"11","command2":"00","raw":"02503D4D5B000001C71100"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"000001","extended":false,"messageType":6,"hopsLeft":1,"maxHops":3,"command1":"11","command2":"00","raw":"02503D4D5B000001C71100"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"393200","extended":false,"messageType":2,"hopsLeft":0,"maxHops":1,"command1":"11","command2":"01","raw":"02503D4D5B393200411101"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"393200","extended":false,"messageType":2,"hopsLeft":0,"maxHops":1,"command1":"11","command2":"01","raw":"02503D4D5B393200411101"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"393200","extended":false,"messageType":2,"hopsLeft":0,"maxHops":1,"command1":"11","command2":"01","raw":"02503D4D5B393200411101"}}
Got event for I/O Linc Sensor (3D4D5B)
Door Closing Events:
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"393200","extended":false,"messageType":1,"hopsLeft":0,"maxHops":1,"command1":"02","command2":"00","raw":"02503D4D5B393200210200"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"000001","extended":false,"messageType":6,"hopsLeft":2,"maxHops":3,"command1":"13","command2":"00","raw":"02503D4D5B000001CB1300"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"393200","extended":false,"messageType":2,"hopsLeft":0,"maxHops":1,"command1":"13","command2":"01","raw":"02503D4D5B393200411301"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"130101","extended":false,"messageType":6,"hopsLeft":2,"maxHops":3,"command1":"06","command2":"00","raw":"02503D4D5B130101CB0600"}}
Got event for I/O Linc Sensor (3D4D5B)
Found 1 accessories matching 3D4D5B
Hub command: {"standard":{"type":"50","id":"3D4D5B","gatewayId":"393200","extended":false,"messageType":1,"hopsLeft":1,"maxHops":1,"command1":"02","command2":"00","raw":"02503D4D5B393200250200"}}
Got event for I/O Linc Sensor (3D4D5B)
It looks like it's seeing events for both the relay and the sensor and maybe trying to figure out what to do with the commands that don't apply. For example, the sensor device wouldn't know how to process the relay command and vice-versa? I suppose the next test would be to remove the relay completely from HE and see if the contact sensor then gets the appropriate updates.
I see why the data is not coming across.
Be a little patient ill see if I can get something working for you while I fiddle with the server...
1 Like
HELP
SOOOOOOO CLOSE !!!
Hopefully someone can help me with an issue getting dimmers to work correctly.
Sorry for revitalizing an "old thread" but I have a problem I'm experiencing when attempting to use this driver 
I hope someone here can clear this up!
I'm using the express server without homebridge and am experiencing the same symptom as peter did (on/off works, dimming does not work).
If I MANUALLY DIM it works as expected, for example entering the following into a web browser always works:
http://172.19.100.169:3000/light/34c9b9/level/10
I TRIED to hack the driver to send the above command as-is which does work, however then I do not get the duration control and it changes instantly
I am OKAY WITHOUT status updates as I can query devices for status directly if needed. I only have switches (both dimmable and non-dimmable) on the network, and the network itself is rock solid so-far. I have a leak sensor too, BUT I have a backup leak sensor running Z-Wave, so, I'll live with that not working, ever, or try to get that one working later - no more rabbit holes. I'll avoid Insteon devices in the future (sadness) although I prefer that bus technology its such a pain to work with, such as in here , at least, without cloud service providers (I'm keepin' it local).
My cases
- With original HTTP driver, unedited, level does not do anything but present an error in the logs.
- I can manually set via URL in browser
- With a hacked driver I can also get the dimmer to work
- BUT, then my hacked version is instantaneous and not a very smooth transition
ORIGINAL DRIVER, LOG, Dim (no change occured)
dev:142022-01-31 10:24:49.752 am errororg.apache.http.conn.HttpHostConnectException: Connect to 347952:80 [/0.5.79.48] failed: Invalid argument (connect failed) on line 158 (method setLevel)
dev:142022-01-31 10:24:49.564 am debugdimming to 63
AFTER MY DIVER HACK, LOG, Dim (dims but too quickly):
dev:142022-01-31 10:51:32.133 am debugresp = [mac:00E04C0E8753, ip:ac1364a9, port:bb8, headers:[HTTP/1.1 200 OK:null, X-Powered-By:Express, Content-Type:text/plain; charset=utf-8, Content-Length:2, ETag:W/"2-nOO9QiTIwXgNtWtBJezz8kv3SLc", Date:Mon, 31 Jan 2022 16:51:29 GMT, Connection:keep-alive, Keep-Alive:timeout=5], body:OK, header:HTTP/1.1 200 OK
X-Powered-By: Express
Content-Type: text/plain; charset=utf-8
Content-Length: 2
ETag: W/"2-nOO9QiTIwXgNtWtBJezz8kv3SLc"
Date: Mon, 31 Jan 2022 16:51:29 GMT
Connection: keep-alive
Keep-Alive: timeout=5
, status:200]
dev:142022-01-31 10:51:32.114 am debugresp.json is null
dev:142022-01-31 10:51:31.749 am debugGET /light/34c9b9/level/25 HTTP/1.1
Accept: */*
User-Agent: Linux UPnP/1.0 Hubitat
HOST: 172.19.100.169:3000
Content-Type: application/x-www-form-urlencoded
Content-Length: 0
dev:142022-01-31 10:51:31.734 am debugdimming to 25
ORIGINAL DRIVER, LOG, Switch ON (light turns on correctly)
dev:142022-01-31 10:23:36.596 am debugresp = [mac:00E04C0E8753, ip:ac1364a9, port:bb8, headers:[HTTP/1.1 200 OK:null, X-Powered-By:Express, Content-Type:text/plain; charset=utf-8, Content-Length:2, ETag:W/"2-nOO9QiTIwXgNtWtBJezz8kv3SLc", Date:Mon, 31 Jan 2022 16:23:33 GMT, Connection:keep-alive, Keep-Alive:timeout=5], body:OK, header:HTTP/1.1 200 OK
X-Powered-By: Express
Content-Type: text/plain; charset=utf-8
Content-Length: 2
ETag: W/"2-nOO9QiTIwXgNtWtBJezz8kv3SLc"
Date: Mon, 31 Jan 2022 16:23:33 GMT
Connection: keep-alive
Keep-Alive: timeout=5
, status:200]
dev:142022-01-31 10:23:36.591 am debugresp.json is null
dev:142022-01-31 10:23:36.224 am debugGET /light/34c9b9/on HTTP/1.1
Accept: */*
User-Agent: Linux UPnP/1.0 Hubitat
HOST: 172.19.100.169:3000
Content-Type: application/x-www-form-urlencoded
Content-Length: 0
QUESTION: Any thoughts as to how I MIGHT be able to get dimming to work either with the provided driver or at least to enable me to slow down the timing when I manually set the levels?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
