hobbyquaker
[FR] Improve duplicate herdsman config
Accidentally I had two herdsman configs, which resulted in a serious FUBAR of the entire installation.
In the end I did not manage to recover and had to delete all configs, dbs and assign a new panID, otherwise the error
Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port
would persist.
It would be a good improvement to prevent having multiple configs and / or mitigating this effect.
Hi
I wanted to try your example nodes in my config and bumped into the same situation after deploying it. For the two examples each it added two herdsman configs and resulted in the same error. :(
So there is no way to recover but delete all configs???
Sineos [email protected] ezt írta (időpont: 2019. dec. 22., V, 15:22):
Accidentally I had two herdsman configs, which resulted in a serious FUBAR of the entire installation.
In the end I did not manage to recover and had to delete all configs, dbs and assign a new panID, otherwise the error Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port would persist.
It would be a good improvement to prevent having multiple configs and / or mitigating this effect.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/hobbyquaker/node-red-contrib-zigbee/issues/83?email_source=notifications&email_token=AHVM6O3R42MOMOIHEW6T3G3QZ5Z2DA5CNFSM4J6L76N2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICF7O2A, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHVM6O6S6IINGQOEXCS43JDQZ5Z2DANCNFSM4J6L76NQ .
Well, your example brought me into this situation :-P Strange thing is that I left your config, hoping to not mess up yours as well. Apparently this part is very sensitive.
Well, for my part, I have not found a way to recover but to:
- Delete all herdsman config
- Delete the folders in /usr/local/addons/redmatic/var/zigbee
- Assign new panID
- Re-pair all devices
Edit:
- Restart whole Rasperymatic some 100x
Thought so... :/
I tried to follow your instructions but:
- I have no addons in /usr/local so nothing to delete
- Cannot assign new panId as by default it is ffff and if I change, it makes the frame of the value red
And now I cannot re-pair anything. It does not recognise any device... :(
Will I need to remove zigbee from my palettes and re-install it?
Sineos [email protected] ezt írta (időpont: 2019. dec. 22., V, 16:19):
Well, your example brought me into this situation :-P Strange thing is that I left your config, hoping to not mess up yours as well. Apparently this part is very sensitive.
Well, for my part, I have not found a way to recover but to:
- Delete all herdsman config
- Delete the folders in /usr/local/addons/redmatic/var/zigbee
- Assign new panID
- Re-pair all devices
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/hobbyquaker/node-red-contrib-zigbee/issues/83?email_source=notifications&email_token=AHVM6OYRD2IDUXB42ZCWMI3QZ6AQBA5CNFSM4J6L76N2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPSJDA#issuecomment-568272012, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHVM6O73UR5MNO5Y4G7K3WTQZ6AQBANCNFSM4J6L76NQ .
Are you using it in Raspberrymatic? If so, you definitively should have /usr/local/addons/redmatic/var/zigbee. You will need to log in to your Raspberrymatic via SSH.
Otherwise you need to check where your dev.db is located. It should also appear in the node-red log, like:
Dec 22 15:11:47 homematic-raspi daemon.info node-red[1285]: [zigbee-shepherd:zigbee-herdsman] Herdsman version: v0.12.17
Dec 22 15:11:47 homematic-raspi daemon.info node-red[1285]: [zigbee-shepherd:zigbee-herdsman] Converters version: v11.1.53
Dec 22 15:11:47 homematic-raspi daemon.info node-red[1285]: [zigbee-shepherd:zigbee-herdsman] persistPath /usr/local/addons/redmatic/var/zigbee/2bdb5b10.05ae14
It is the persistPath.
panID needs to be a valid hex value, i.e. 0-9 and A-F with 4 digits. Try 1A64
1A64 works, but several other valid hex numbers not. I also found the persistPath with a lots of subdirs containing dev.db, thanks. Not deleted yet, because somehow I got back to "connected" status and started to re-pair.
But now I am having "topic mismatch zigbee/0x00158d00033e9139///" messages in debug window... But for example sensor values are coming normally.
If not successful, I will follow all your suggestions.
Sineos [email protected] ezt írta (időpont: 2019. dec. 22., V, 18:01):
Are you using it in Raspberrymatic? If so, you definitively should have /usr/local/addons/redmatic/var/zigbee. You will need to log in to your Raspberrymatic via SSH. Otherwise you need to check where your dev.db is located. It should also appear in the node-red log, like:
Dec 22 15:11:47 homematic-raspi daemon.info node-red[1285]: [zigbee-shepherd:zigbee-herdsman] Herdsman version: v0.12.17 Dec 22 15:11:47 homematic-raspi daemon.info node-red[1285]: [zigbee-shepherd:zigbee-herdsman] Converters version: v11.1.53 Dec 22 15:11:47 homematic-raspi daemon.info node-red[1285]: [zigbee-shepherd:zigbee-herdsman] persistPath /usr/local/addons/redmatic/var/zigbee/2bdb5b10.05ae14
It is the persistPath.
panID needs to be a valid hex value, i.e. 0-9 and A-F with 4 digits. Try 1A64
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/hobbyquaker/node-red-contrib-zigbee/issues/83?email_source=notifications&email_token=AHVM6O6SHTH6FMSOHOXDLALQZ6MPNA5CNFSM4J6L76N2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPUYQI#issuecomment-568282177, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHVM6O2AVV5J4I6OQQDKCDDQZ6MPNANCNFSM4J6L76NQ .