Unhandled ASCII message type received #72
Comments
|
So I Confirmed this is being caused by something in the new HS4 Version of the Insteon Plugin (MNS Insteon). |
|
I am wondering if this is because the new plugin is trying to follow the requirement of the root device in HS4 and is labeling all the root devices as 'Device Name - Root' Wondering if the '-' being added is impacting your plugin au,default,default |
|
So i am pretty sure the So i am not sure i see antyhing in the logs as why the new version of homeseer MSN insteon plugin causes this intgrateion to no longer work. I don't get status updates if i try to turn a switch on home seer show it go on then shuts it off right away. but the switch stays on. So for now i am running the old homeseer insteon plug and your intigration and have no issues. I have my Homeseer box setup so i just need to shutdown the service and move folders around and restart to switch between the 2 differnt version. |
|
More debug logging would assist with this. What happens in the logs when you toggle a switch in HA? What happens in the logs when you control with switch in HS? I don’t think the ‘-‘ should matter and the unhandled message type messages can be ignored here, they are generated by a ping that keeps the telnet connection alive. |
|
Here is what it does when i try to turn something on. It will trun on the device but then home assistant resets the status back to off even thought its on and homeseer says its. And from that point i can't shut it off here is the logs for turning something on it then HA setting status back to off. This is all that showed up in the logs during that time 2022-02-03 21:41:24 DEBUG (MainThread) [libhomeseer.listener] ASCII message received from 172.16.1.10:11000: b'DC,36,100,0\r\n' 2022-02-03 21:41:24 DEBUG (MainThread) [libhomeseer.devices] Updating data for Main Living Room Side Gate - Button B (36) 2022-02-03 21:41:25 DEBUG (MainThread) [libhomeseer.homeseer] HomeSeer request response from 172.16.1.10: {"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":true,"Devices":[{"ref":36,"name":"Side Gate - Button B","location":"Living Room","location2":"Main","value":100.0,"status":"On","device_type_string":"Dual-Band KeypadLinc Dimmer","last_change":"/Date(1643942484338-0500)/","relationship":4,"hide_from_view":false,"associated_devices":[165],"device_type":{"Device_API":513,"Device_API_Description":"Undefined API=513","Device_Type":0,"Device_Type_Description":"Undefined API 513, Type 0, SubType 0","Device_SubType":0,"Device_SubType_Description":"Dual-Band KeypadLinc Dimmer"},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/on.gif","voice_command":"","misc":12544,"interface_name":"Insteon"}]} |
|
Here is with Home Assistant saying its off but its really on and me trying to turn it on in HA. As soon as I toggle it HA toggles it back off. 2022-02-03 21:46:09 DEBUG (MainThread) [libhomeseer.homeseer] HomeSeer request response from 172.16.1.10: {"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":true,"Devices":[{"ref":36,"name":"Side Gate - Button B","location":"Living Room","location2":"Main","value":100.0,"status":"On","device_type_string":"Dual-Band KeypadLinc Dimmer","last_change":"/Date(1643942484338-0500)/","relationship":4,"hide_from_view":false,"associated_devices":[165],"device_type":{"Device_API":513,"Device_API_Description":"Undefined API=513","Device_Type":0,"Device_Type_Description":"Undefined API 513, Type 0, SubType 0","Device_SubType":0,"Device_SubType_Description":"Dual-Band KeypadLinc Dimmer"},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/on.gif","voice_command":"","misc":12544,"interface_name":"Insteon"}]} Again thats all that showed up in the logs |
|
Here is me turning on the same item with the HS3 version of the plug in which works: 2022-02-03 22:08:02 DEBUG (MainThread) [libhomeseer.listener] ASCII message received from 172.16.1.10:11000: b'DC,36,100,0\r\n' 2022-02-03 22:08:02 DEBUG (MainThread) [libhomeseer.devices] Updating data for Main Living Room Side Gate - Button B (36) 2022-02-03 22:08:04 DEBUG (MainThread) [libhomeseer.homeseer] HomeSeer request response from 172.16.1.10: {"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":true,"Devices":[{"ref":36,"name":"Side Gate - Button B","location":"Living Room","location2":"Main","value":100.0,"status":"On","device_type_string":"Insteon Dual-Band KeypadLinc Dimmer Button B","last_change":"/Date(1643944082903-0500)/","relationship":4,"hide_from_view":false,"associated_devices":[35],"device_type":{"Device_API":4,"Device_API_Description":"Plug-In API","Device_Type":4,"Device_Type_Description":"Plug-In Type 4","Device_SubType":0,"Device_SubType_Description":""},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/on.gif","voice_command":"","misc":4352,"interface_name":"Insteon"}]} |
|
looking at the 2 responses wasn't sure if these would be any help. In HS3 version of plugin In the new HS4 version of the plugin |
|
Just wanted to bring up i am still having this issue. With the MSN Insteon HS4 Plugin if i revert back to the the MSN Insteon HS3 plugin everything works. i don't have anything in the log differnt then last time 2022-06-27 23:49:26 DEBUG (MainThread) [libhomeseer.listener] Pinging ASCII connection at 172.16.1.10:11000 When i try to turn on a a Insteon Keypadlinc button like Button H. The button turns on in HA and on in homeseer. The device turns on. But in a few seconds HA switches teh device to off, but in Homeseer and device is still on i see in HA its showing as unavaible:
So there is some communication happening and i don't know whats breaking. |
|
Here is me turning it on and off in Homeseer 2022-06-28 00:03:05 DEBUG (MainThread) [libhomeseer.listener] ASCII message received from 172.16.1.10:11000: b'DC,42,100,0\r\n' In homeassistant it still shows as unavaible. |
|
I found the issue and am trying to see if this is something wrong with HomeSeer and the plugin or how they want new HS4 plugins to work. This is the error that keyed me in to this 2022-06-30 22:24:30 DEBUG (MainThread) [libhomeseer.homeseer] HomeSeer request response from 172.16.1.10: { "Response":"Error, controlling device, value not found" } the issue is the crontols are not 0 = off and 100 = on now. So when you send the json with a 0 or 100 it errors out. Found the cause. Its because of the Edit Controls and Edit Status Values. All the Edit controls are changed in the new hs4 plugin. In HS3 version the 2 sets hat matching values here is what i see in the HS3 version and in the HS4 version of the plugin: Here is the homeseer forum page i have for this: So to control a device in HS via json you have to use the control value which are 101 and 102 now. Like i said i have a forum entry open and ticket to see if this is how home seer should react (if so you plugin would need changed) or if this is an issue with the plugin or Homeseer it self. |
|
I was able to get around this by changing my local copy of the component i changed the switch.py and the light.py From To: I also had to set the manesfest to pull the newest version of libhomseer 1.3.0 as it curently only pulls 1.2.2 |
|
Created pull request 76 for changes to switch.py and light.py to use the values to determine status of devices |
I just updated my homeseer to the latest version 4.2.7.0 and also updated my Inteon plug in to the new HS4 version. and I am noticing this now i can't controll. I think this is caused by the new Insteon HS4 plugin as my homeseer nest plugin seems to be reporting values to HomeAssistant. If i revert back it works fine. i will try reverting back and then updated the homeseer and still see if the HS3 version plugin causes the same issue to narrow down which is causing this.
2022-01-27 15:22:38 DEBUG (MainThread) [libhomeseer.homeseer] HomeSeer request response from 172.16.1.10: {"Name":"HomeSeer Devices","Version":"1.1","TempFormatF":true,"Devices":[{"ref":107,"name":"Plant Light","location":"Office","location2":"Basement","value":0.0,"status":"Off","device_type_string":"Dual-Band On/Off Module","last_change":"/Date(1643162400545-0500)/","relationship":4,"hide_from_view":false,"associated_devices":[199],"device_type":{"Device_API":513,"Device_API_Description":"Undefined API=513","Device_Type":0,"Device_Type_Description":"Undefined API 513, Type 0, SubType 0","Device_SubType":0,"Device_SubType_Description":"Dual-Band On/Off Module"},"device_type_values":null,"UserNote":"","UserAccess":"Any","status_image":"/images/HomeSeer/status/off.gif","voice_command":"","misc":12544,"interface_name":"Insteon"}]}
2022-01-27 15:22:40 DEBUG (MainThread) [libhomeseer.listener] Pinging ASCII connection at 172.16.1.10:11000
2022-01-27 15:22:40 DEBUG (MainThread) [libhomeseer.listener] ASCII message received from 172.16.1.10:11000: b'4.2.7.0\r\n'
2022-01-27 15:22:40 DEBUG (MainThread) [libhomeseer.listener] Unhandled ASCII message type received from 172.16.1.10:11000: 4.2.7.0
The text was updated successfully, but these errors were encountered: