ioBroker / ioBroker.zigbee

Zigbee communcation with Hue, Xiaomi, Lighttify... via TI CC2xxx USB stick
MIT License
313 stars 190 forks source link

Test before release 0.9.0 #153

Closed kirovilya closed 5 years ago

kirovilya commented 5 years ago

Hi guys. @Apollon77 @arteck @allofmex @modmax You are the advanced users of this adapter. Before the release of version 0.9.0, I am very concerned about the stability of the adapter. I do not have so many devices to test its operation, therefore, check on your test systems. Also, the last of our changes mixed up and now it’s difficult for me to make sure that what you made was not lost among other changes.

Please see the current dev-branch. If critical problems are not revealed until Monday, we will be released. Thank you!

arteck commented 5 years ago

@modmax we can flash the coordinator with software solution (SerialBootTool) or not ? @kirovilya I think we do not have to pair all devices with it.. right ??

modmax commented 5 years ago

I flashed the hex file from KoenkK from the dev branch. But for me I had to pair each device again; perhaps I made a mistake cause I always erase the cc2530 before programming. Also the paired devices are stored in the coordinator/router and I think flashing a new hex file will erase those bindings.

Edit: Okay .. I didn't know the SerialBootTool until now ... so maybe that will work.

kirovilya commented 5 years ago

@modmax 1) approx. maybe that was the reason, but I'm not sure :) 2) and this is my mistake, I overlooked the changes in the firmware (I thought there they concerned only minor parameters), it turned out that the main parameter is:

// Disabling MULTICAST is required in order for proper group support.
// If MULTICAST is not disabled, the group adress is not included in the APS header
#define MULTICAST_ENABLED FALSE

I am saddened. This means everyone users should reflash the sticks: (

Will have to build the bin-file for firmware via serialboottool and write instructions for reflashing ...

kirovilya commented 5 years ago

@arteck After flash the firmware - you need to pair again: (

modmax commented 5 years ago

Then that's the way to go .. also it depends on the vendor of the devices. For Hue,Tradfri and perhaps some more it seems to work without reflashing; for OSRAM and others a reflashing has to be done.

@kirovilya If you could provide a SerialBootTool for flashing a new firmware without CC-Debugger, then this would help people, which have bought an already flashed stick or are not able to reflash a stick themselves. Seperatly for the cc2531, cc2530 and cc2530+cc2591.

Important is, that there is a solutuion. So I think the version 0.9 may start at the weekend. I now have no further problems with the actual dev version. Other commens suggested ... :-)

arteck commented 5 years ago

@kirovilya i have here 35 Devices.. I am very sad when I must to pair all new

this modification is for Osram Groups only or not?

@modmax everything is ok here also... i have the dev ver from yesterday

Apollon77 commented 5 years ago

I use the dev version from 3 days ago already in production at home. works well with Hue devices and groups

modmax commented 5 years ago

@arteck The firmware version (dev fom koenkk) should be for all versions; but I think that this depends on the vendors if that works with or nor without that modification. Thats then call "vendor specific zigbee adjustments" ... :-)

So if your groups work, then there is no need for re-flashing. If they does not work (that was my case with Osram lamps), then reflashing is needed with the dev version from koenkk or any other firmware where the multicast is disabled.

kirovilya commented 5 years ago

ZNP_BIN_for_groups.zip Build firmware for updating via SerialBootTool by this instruction. https://github.com/Koenkk/zigbee2mqtt/issues/320 Amazing, my lamps were still working! Without pairing (although now there is a ping mechanism, maybe it helped)! Check out those who have OSRAM. First, with the old firmware, make sure that the groups do not work, then take and update with this firmware and check whether the groups will work without pairing.

arteck commented 5 years ago

@kirovilya I'll have a look... it would be great.. without new pairing

kirovilya commented 5 years ago

@arteck Carefully, it may not work with sensors, router only

arteck commented 5 years ago

fuxx it WORKS.. very very nice.. all Routers and Enddevices are reconnected

kirovilya commented 5 years ago

@arteck and groups with OSRAM works?

arteck commented 5 years ago

with plugs nope

grafik

i think this is the correct Version ..right ??

kirovilya commented 5 years ago

@arteck yes

kirovilya commented 5 years ago

@modmax @allofmex can you check the attached firmware above to work with OSRAM?

arteck commented 5 years ago

groups for enddevices (temp or switch) do not make sense.... grafik

kirovilya commented 5 years ago

@arteck these states are left from the previous version, you can delete them

arteck commented 5 years ago

ahh ok

modmax commented 5 years ago

@kirovilya Tested it right now withj an OSRAM plug. It works, but with confusion.

A:) Added the plug to a group Request done, but failed. BUT: The group is shown as added for the device. Error was: 2019-01-25 15:56:51.893 - error: zigbee.0 Zigbee publish to '0x84182600000f3511', genGroups - add - {"groupid":1,"groupname":""} - 3 failed with error Error: AF data request fails, status code: 233. MAC no ack. 2019-01-25 15:56:51.894 - error: zigbee.0 Failed to add device 0x84182600000f3511 to group 1. Error: AF data request fails, status code: 233. MAC no ack.

Needed to delete group from device and then added device to group again. This time no error occured. And now the plugs works within groups (of course state only). I think @arteck there was also an error in the log, so that the group has not been added.

I think something should be changed: If the "group addition" leads to an error, then the group should not be added to the device in device list and object. Otherwise it can confuse the users, when the group is added and shown up in device, but does not work.

But on the other side with a NO ACK it's no guaranteed, that the device didn't process the request. I.e. for changing color on a lamp or switching the plug the request has been executed, but then a NO ACK occured for that device; even if everything went okay.

arteck commented 5 years ago

@modmax you're right grafik

modmax commented 5 years ago

@arteck And when you delete and add the device again to the group?

arteck commented 5 years ago

groupe deleted from device group deleted also create new group add to device

nope not wroks

and no error in log

arteck commented 5 years ago

grafik

modmax commented 5 years ago

Confusing ... but i'm using the DEV firmware from Koenkk.

@kirovilya Are there any changes between those firmware and your firmware for the SerialBootTool? I have no test setupo right now ... so that I cannot test at the moment the flashing with serial boot tool, from old firmware to new firmware.

arteck commented 5 years ago

next test del device del group

add device create new group add device to group grafik

{"groupid":1,"groupname":""} where is the group name ??

modmax commented 5 years ago

Group name is optional ... so can be left empty. If missing "groupname" in object an error occurs, that the groupname is mandatory ... :-) Are you using the latest DEV version from the Zigbee Adapter? Tested addition of device to group without deleting the group before?

arteck commented 5 years ago

Group name is optional ...
i know and i have a group name

Are you using the latest DEV version from the Zigbee Adapter? yes

Tested addition of device to group without deleting the group befor yes..

modmax commented 5 years ago

If you have a test setup: can you flash the DEV firmware from Koenkk on it? Also erasing complete flash. Afterwards test if it works or not ...

kirovilya commented 5 years ago

@modmax

Are there any changes between those firmware and your firmware for the SerialBootTool?

I think no. I got last dev firmware patch and build firmware for SBL

modmax commented 5 years ago

Only thing it could perhaps be is the firmware of the plug itself ...

kirovilya commented 5 years ago

Or the firmware via SBT does not completely replace the existing firmware :) Another assumption: Adding groups occurs until the device is re-pairing, so messages may not reach. Groups are synchronized when the adapter starts. If @arteck add a group after a successful launch without restarting the adapter, will there be an error?

allofmex commented 5 years ago

Updated firmware to 2.6.3 rev 20181224 and zigbee adapter to dev version of today. Adapter upload/restart.

Bulbs (ikea, osram, philips), Eurotronics Thermostat and osram plug worked without re-pair. Only hue motion sensor needed a setup-button push (but no full reset), before "status code: 183. APS no ack".

But said to say, the groups still don't work for osram. Exact same behavior as older version (20180815). Group is set/deleted but no response to commands.

modmax commented 5 years ago

@allofmex You have used the SBT for flashing right? In opposite I dif a full reflash of the firmware with complete erasing the coordinator and therefore also my cc2530 router ... bulbs and lamps reset manually per script (5x on/off) .. and then paired each device again. Took about 2 hours for 15 devices ..., But now groups are working for bulbs and plugs ... and that all for OSRAM devices ... :hankey:

arteck commented 5 years ago

i have tommorow many errors here.. nothing work

grafik

all devices are offline.. after restart the adapter works also not...

wtf... after reboot works all perfect.. grafik

arteck commented 5 years ago

ok new knowledge.. after adapter start and first control of a bulb or plug takes it a long time.. with 35 device 2-5 min until the network is up...meantime i have errors no route found..or for plugs ACK fail..

grafik

on top is the last configuring devices and the bottom is the adapter start... look the time between this sequenz

arteck commented 5 years ago

2 hours later all my devices are offline.. Log has no erreos .. strange.. maybe the update was faulty.. any ideas ??

before I reflash all devices and cc2531

kirovilya commented 5 years ago

@arteck :( restart adapter not help? internal buffers may be filled. only full reflash...

arteck commented 5 years ago

Adapter restart not.. but reboot.. then is the buffer empty.. and run 2 hours... fuXX also new flash and receonnct all devices... lets go...

arteck commented 5 years ago

done.. all devices are connect with new firmware.. Test can begin

arteck commented 5 years ago

same problem as yesterday.. i thin the firmware is buggy grafik

adapter restart does not work..any ideas ??

I will reflash to old version

kirovilya commented 5 years ago

@arteck This is bad news... I do not know if it will help, but you can try the coordinator’s soft reset. if it helps, then add regular execution. https://github.com/ioBroker/ioBroker.zigbee/blob/dev/lib/zigbeecontroller.js#L103

arteck commented 5 years ago

i check this .. how long the coordinator works.. without reset.. the last stand is 2 hours.. this is not acceptable..

kirovilya commented 5 years ago

You can also test previous version 0.8.0 of adapter...

allofmex commented 5 years ago

Added reset button to adapter interface. https://github.com/ioBroker/ioBroker.zigbee/pull/170 Hope it helps.

Hard reset left all my devices as unpaired (icon in device tabs). So far as expected. But I just had to start pairing mode in adapter and they all paired themselfs (after simple power reset). No device reset or even pairing button press on device needed. Is this correct behavior? Or is shepherds hard reset not a real/full reset!

allofmex commented 5 years ago

Sadly the hard reset does not change anything for OSRAM groups

You have used the SBT for flashing right?

Yes, updated via SerialBootTool. I do not have a debugger for flashing manually. Is there any way to fully reset the CC2531 without debugger and without erasing the firmware itself?

modmax commented 5 years ago

@arteck have you erased the cc2531 and flashed the DEV firmware via CC debugger? I've done so and it works since 6 days. No problems with it.

On first start of zigbee adapter after flashing new firmware there was also a request timeout for shepherd, but after a restart of the instance it worked. Deleted the shepherd.db in zigbee_0 directory before restart; shouldn't have an impact but just mentioned to be complete.

@allofmex Sorry, I've no idea how that could be done.

arteck commented 5 years ago

further 24 hours works... after first day problem... strange very strange... but it is running now... :-)

arteck commented 5 years ago

so far publish 0.0.9 ??

allofmex commented 5 years ago

No serious issues on my side anymore. Go for 0.9.0...