INNR, Plugwise and Ubisys Zigbee Apps

[kasteleman]

@JonathanS Did you already swap the FL 130 C? It seems that there will be a possible method to update the app. Have to look in to it and then report back!

[JonathanS]

Thanks! However, I opted for another creative solution:

DIY GUIDE: Build your own cheap Philips Hue LED Strips

[kasteleman]

Just pushed a new version to the app store for stable firmware and a new test version for the V5 firmware. Added some devices like the OPL, FL etc.

[rvdeijk]

@kasteleman So finally I have Homey V5 and the firmware of my plugwise plug is etrx_PLUG_R0004, is it old?

@Edwin_D

however, each time Homey is restarted, some of the INNR’s are marked as could not connect with the red icon. When I restart the app one or twice they usually all work fine again and keep doing so until the next restart.

@Ollem

This happened for my Innr SP120 plugs too

@Ranney

Only problems with the innr app with SP120 Wall plugs. After reboot of homey there are some plugs not available.

I experience exactly the same. After Homey V5 upgrade and one hour later an extra reboot and PtP, the two sp120 plugs mentions it can’t initialize. Tomorrow I will try a PtP or make the sp120 powerless for a short time.

Report: 1eaf2d6c-de6f-470b-9ac1-8bf744fe0e1c

Edit:
Maybe this is related, message after V5 upgrade:

I unplugged one sp120 and plugged it again and after an app restart that sp120 was available again.

[kasteleman]

The log states that the device is indeed unreachable. So unfortunately i can’t do anything about it. Next time try to restart the INNR app report back if that solves the issue.

[Ranney]

Restarting the innr app multiple times fixes the problem. But after a reboot of homey, the problem is back. The not working sp120 plugs are, as far as I can see, random. I have 16 of them.

[kasteleman]

@Ranney Any other INNR devices in use? If so, they don’t have the problem?

[tlangelaar]

@kasteleman, I have the same situation. Some of the SP120 sockets show a red triangle in Homey app. I have other INNR devices (including a led strip) which are working fine. Have not yet performed a PTP, Zigbee reset, app restart or Homey reboot.

developer.homey shows “Available No (Kon dit Zigbee apparaat niet initialiseren)” for the failing SP120 sockets. The on/off capability shows a last-updated from after the Homey v5 update and after the update of the INNR app to v2.1.2. But that capability is not updated when switching the socket with the physical button.

I have been able to reinclude one of those sockets which gave me a new device in Homey and Homey had removed the old one. That one now does not report any problem. I’m working on the other 2 sockets that have the triangle.

You can PM me if you want some joined debugging activity.

[rvdeijk]

Have you unplugged the sp120’s from power? Cause I did it, based on the text I received on the homey timeline after V5 upgrade. “Some Zigbee devices possibly need to be switched off and on before Homey can connect to them”.
Since then the red triangle are gone and even when I reboot Homey the sp120’s are working fine.

1. disconnect sp120 from power
2. Connect sp120 to powersocket
3. Restart Innr homey app

[DaanV]

Hi, after the update to version 5 and a complete Zigbee reset i can’t connect my INNR RS 128 T GU10 lights. In the Zigbee panel he says Unknown. And when i add the device Homey says ''Zigbee kan het apparaat niet toevoegen. I reset the light several times. Is there a solution to add my lights?

[kasteleman]

The RS 128 T shows in the screenshot if I’m not mistaken right? Does it show in the Homey App?

[DaanV]

Yes thats the light. But in the Homey App does not show that light. When i press the refresh nodes button in de Developers page then the RS 128 T is gone.

[kasteleman]

Can you try again and then immediately after that send a debug report?

[Edwin_D]

Removing them from power doesn’t make a difference. it is a persistent problem, that kept on even after a zigbee reset and adding them fresh. If the app starts some devices are in error and that doesn’t change until you restart the app once or twice. When they work, they keep working until a Homey restart. It is clearly something in the initialization phase of the app, and it may very well be related to the fact that after a restart Homey is very busy while the INNR app starts.

[DaanV]

4951b423-52f6-411c-8528-75ca910887be

[kasteleman]

2021-02-20T12:03:16.072Z zigbee-clusters:endpoint ep: 1, cl:
colorControl (768), error while responding with send frame to
handle frame Error: Kan niet met dit apparaat communiceren.
at Remote Process
{
response: ZCLStandardHeader {
frameControl: Bitmap [ disableDefaultResponse ],
trxSequenceNumber: 2,
cmdId: 11,
data:
}
}

Can you try resetting the bulb, stop the INNR app and try to include
the bulb? Does it then get included? If not, please send a diagnostic
report to Athom

[Ranney]

Still not sure what exactly the problem is. But cannot get it working stable. After every reboot I need to restart the app sometimes (1-14 times) before all my 16 sp120 plugs are working without an red Mark.
What I know for now:

• Re-adding is not the solution
• as far as I can see, it is random. Not always the same plug
• PTP is not the solution
• If I restart the app, every plug is red. Then 1 after one they will be online and after ca 10 sec, suddenly some plugs are marked red and this will not recover after days.

Anybody with an idea / solution? Thanks for help!

[MrTomTom]

Hi,

since fw5.0 update I am facing the same problem. I have around 20 Innr devices. Bulbs and plugs.
They all become unavailable after a restart of homey. Red triangle, message: Zigbee device could not be initialized". Restarting the Innr App or disable/enable the app does not solve it for all devices.

Any idea how this can be fixed?
Diagnostocs report: 2389d625-5049-440d-a6b4-a942bb11931f

Best regards,
Tom

[JerryP]

So after the V 5.0 update i got several problems with multiple devices from INNR. Finally i contacted Atom support, send them several reports and at last completely reinstalled my Homey.
All devices from Hue, Aquara, Lidl, Ikea, Heiman where re-added and all worked fine. As was the same with several other apps from klikaan klik uit, and many more. In total i have now 40 working Zigbee devices of which 22 are routers.

However from my INNR devices my SP220 worked fine as was the same with 185C and 285c color e27bulbs. My RB 148 T and RB 145T failed to add with the message"Er ging iets fout bij het toevoegen van dit apparaat, probeer het nog eens” The same happened with the some some RS 125 and RS 225 GU10 lights where others where never found. All lights where reset using 6x turn on and off and some also reset-ted with an hue remote.
The homey was clean installed with all firmware, Innr app was removed and reinstalled.
Atom support suggested contacting the App developer since the only problem was with INNR devices.
All lights worked fine before migration to version 5.01.
Is there anything i could do?

Regards,
Jerry
PS. the RB 285 C light gives a red mark after a reboot of Homey. Interviewing is still possible and returns the following:

“ids”: {
“modelId”: “RB 285 C”,
“manufacturerName”: “innr”
},
“endpoints”: {
“endpointDescriptors”: [
{
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 269,
“applicationDeviceVersion”: 0,
“_reserved1”: 1,
“inputClusters”: [
0,
3,
4,
5,
6,
8,
768,
4096
],
“outputClusters”: [
25
]
},
{
“endpointId”: 242,
“applicationProfileId”: 41440,
“applicationDeviceId”: 97,
“applicationDeviceVersion”: 0,
“_reserved1”: 0,
“inputClusters”: ,
“outputClusters”: [
33
]
}
],
“endpoints”: {
“1”: {
“clusters”: {
“basic”: {
“attributes”: [
{
“id”: 0,
“name”: “zclVersion”,
“value”: 2,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 1,
“name”: “appVersion”,
“value”: 16,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 2,
“name”: “stackVersion”,
“value”: 21,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 3,
“name”: “hwVersion”,
“value”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 4,
“name”: “manufacturerName”,
“value”: “innr”,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 5,
“name”: “modelId”,
“value”: “RB 285 C”,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 6,
“name”: “dateCode”,
“value”: “20190114-27”,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 7,
“name”: “powerSource”,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 8,
“name”: “appProfileVersion”,
“value”: 0,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 9,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 10,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 11,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 16384,
“name”: “swBuildId”,
“value”: “2.1”,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“identify”: {
“attributes”: [
{
“id”: 0,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“groups”: {
“attributes”: [
{
“id”: 0,
“name”: “nameSupport”,
“value”: {
“type”: “Buffer”,
“data”: [
0
]
},
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“scenes”: {
“attributes”: [
{
“id”: 0,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 2,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 3,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 4,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 5,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“onOff”: {
“attributes”: [
{
“id”: 0,
“name”: “onOff”,
“value”: false,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 16,
“minInterval”: 0,
“maxInterval”: 300,
“status”: “SUCCESS”
}
},
{
“id”: 16384,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 16385,
“name”: “onTime”,
“value”: 0,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 16386,
“name”: “offWaitTime”,
“value”: 0,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 16387,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“levelControl”: {
“attributes”: [
{
“id”: 0,
“name”: “currentLevel”,
“value”: 254,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 32,
“minInterval”: 0,
“maxInterval”: 300,
“minChange”: 10,
“status”: “SUCCESS”
}
},
{
“id”: 1,
“name”: “remainingTime”,
“value”: 0,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 15,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 16384,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“colorControl”: {
“attributes”: [
{
“id”: 0,
“name”: “currentHue”,
“value”: 0,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 32,
“minInterval”: 0,
“maxInterval”: 300,
“minChange”: 10,
“status”: “SUCCESS”
}
},
{
“id”: 1,
“name”: “currentSaturation”,
“value”: 0,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 32,
“minInterval”: 0,
“maxInterval”: 300,
“minChange”: 10,
“status”: “SUCCESS”
}
},
{
“id”: 2,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
},
{
“id”: 3,
“name”: “currentX”,
“value”: 29991,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 33,
“minInterval”: 0,
“maxInterval”: 300,
“minChange”: 10,
“status”: “SUCCESS”
}
},
{
“id”: 4,
“name”: “currentY”,
“value”: 26872,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 33,
“minInterval”: 65535,
“maxInterval”: 65535,
“minChange”: 65535,
“status”: “SUCCESS”
}
},
{
“id”: 7,
“name”: “colorTemperatureMireds”,
“value”: 370,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 33,
“minInterval”: 65535,
“maxInterval”: 65535,
“minChange”: 65535,
“status”: “SUCCESS”
}
},
{
“id”: 8,
“name”: “colorMode”,
“value”: “colorTemperatureMireds”
},
{
“id”: 15
},
{
“id”: 16
},
{
“id”: 17
},
{
“id”: 18
},
{
“id”: 19
},
{
“id”: 21
},
{
“id”: 22
},
{
“id”: 23
},
{
“id”: 25
},
{
“id”: 26
},
{
“id”: 27
},
{
“id”: 32
},
{
“id”: 33
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“touchlink”: {
“attributes”: [
{
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1,
“reportingConfiguration”: {
“status”: “UNREPORTABLE_ATTRIBUTE”,
“direction”: “reported”
}
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
}
},
“bindings”: {
“ota”: {}
}
},
“242”: {
“clusters”: {},
“bindings”: {}
}
}
}

[kasteleman]

Hi Jerry,

I assume the mesh is ok because you could add other routers and you did not add the sensors first. You stated some failed while others of the same model could be added without an issue. Did you add them in a short period of time? Can you make a list of the current situation? For example are there some specific models that you did not succeed in adding and none of that model could be included?

Regards,

Martin