Other Node ID, change IDX number Topic is solved
Moderator: leecollings
-
- Posts: 45
- Joined: Monday 02 July 2018 23:35
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.100xx
- Location: Alkmaar, The Netherlands
- Contact:
Other Node ID, change IDX number
Hello all here at the Domoticz forum,
Today I connected my first Mysensors node to another gateway, I had combined an ethernet gateway and node, but now I have made RS 485 gateway because I want to connect more node's.
Now the node in the old situation had ID-0, and now ID-110.
So, with the result that the old "sensors" no longer receive an update, now you could say, with the new node ID you can still see the data, and that's right, but unfortunately I don't see the historical data from the sensors ( temperature and soil moisture)
Is there perhaps a possibility to import the log files from the old IDX to the new IDX?
Thanks for contributing ideas
dzjr
Today I connected my first Mysensors node to another gateway, I had combined an ethernet gateway and node, but now I have made RS 485 gateway because I want to connect more node's.
Now the node in the old situation had ID-0, and now ID-110.
So, with the result that the old "sensors" no longer receive an update, now you could say, with the new node ID you can still see the data, and that's right, but unfortunately I don't see the historical data from the sensors ( temperature and soil moisture)
Is there perhaps a possibility to import the log files from the old IDX to the new IDX?
Thanks for contributing ideas
dzjr
NUC Proxmox VM Stable & Raspberry Pi-3 Domoticz Beta
Tradfri Pluging by Moroen, Home made MySensors, Luftdaten, Home & Garden automatisation.
APC Back-UPS XS 700U, Modbus RTU & Janitza UMG103, RF-Link
Sonos plugins
Tradfri Pluging by Moroen, Home made MySensors, Luftdaten, Home & Garden automatisation.
APC Back-UPS XS 700U, Modbus RTU & Janitza UMG103, RF-Link
Sonos plugins
-
- Posts: 370
- Joined: Monday 05 October 2015 10:16
- Target OS: -
- Domoticz version:
- Contact:
Re: Other Node ID, change IDX number
- go to the temp/weather tab.
- click on the edit button of your new device
- then you chould have a popup window with a replace button
- Click it and sekecr your 'old' device and the thransfer into 1 with the history
- click on the edit button of your new device
- then you chould have a popup window with a replace button
- Click it and sekecr your 'old' device and the thransfer into 1 with the history
-
- Posts: 45
- Joined: Monday 02 July 2018 23:35
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.100xx
- Location: Alkmaar, The Netherlands
- Contact:
Re: Other Node ID, change IDX number
@stlaha2007 ,
Thank you for your reply,
It all worked out, I have the old log in the new sensor!
Thank you very mutch !!
Thank you for your reply,
It all worked out, I have the old log in the new sensor!
Thank you very mutch !!
NUC Proxmox VM Stable & Raspberry Pi-3 Domoticz Beta
Tradfri Pluging by Moroen, Home made MySensors, Luftdaten, Home & Garden automatisation.
APC Back-UPS XS 700U, Modbus RTU & Janitza UMG103, RF-Link
Sonos plugins
Tradfri Pluging by Moroen, Home made MySensors, Luftdaten, Home & Garden automatisation.
APC Back-UPS XS 700U, Modbus RTU & Janitza UMG103, RF-Link
Sonos plugins
-
- Posts: 848
- Joined: Sunday 23 February 2014 17:56
- Target OS: Raspberry Pi / ODroid
- Domoticz version: mixed
- Location: Hengelo(Ov)/NL
- Contact:
Re: Other Node ID, change IDX number
Raises a question.
In the Manual for Replacing Batteries (see page 33), the reverse order is described:
- go to Edit for old device and select Replace by new Device
Are both descriptions correct, but applicable for different situations?
In the Manual for Replacing Batteries (see page 33), the reverse order is described:
- go to Edit for old device and select Replace by new Device
Are both descriptions correct, but applicable for different situations?
Set1 = RPI-Zero+RFXCom433+S0PCM+Shield for BMP180/DS18B20/RS485+DDS238-1ZNs
Set2 = RPI-3A++RFLinkGTW+ESP8266s+PWS_WS7000
Common = KAKUs+3*PVLogger+PWS_TFA_Nexus
plus series of 'satellites' for dedicated interfacing, monitoring & control.
Set2 = RPI-3A++RFLinkGTW+ESP8266s+PWS_WS7000
Common = KAKUs+3*PVLogger+PWS_TFA_Nexus
plus series of 'satellites' for dedicated interfacing, monitoring & control.
-
- Posts: 370
- Joined: Monday 05 October 2015 10:16
- Target OS: -
- Domoticz version:
- Contact:
Re: Other Node ID, change IDX number
Wrote it, straight out of my head.
Having a few devices(rfx433) that reset/change there ID, and therefor following that procedure regulary.
Used to have read the manual also, however it didn't work for me sometimes.
Ran into changed IDX's for Dashboards and so.
Perhaps the manual is correct, and i have memorized it incorrectly or just works both.
So the changed idx should be looked after, gonna test it today, i have to replace batteries today for 2 of those changing ID devices
Having a few devices(rfx433) that reset/change there ID, and therefor following that procedure regulary.
Used to have read the manual also, however it didn't work for me sometimes.
Ran into changed IDX's for Dashboards and so.
Perhaps the manual is correct, and i have memorized it incorrectly or just works both.
So the changed idx should be looked after, gonna test it today, i have to replace batteries today for 2 of those changing ID devices

- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: Other Node ID, change IDX number
The description in the manual is correct. On my system the sequence described in this thread leads to the loss of logdata. This only becomes visible after a cache refresh or domoticz / stop-start.Toulon7559 wrote: ↑Wednesday 24 April 2019 7:44 Raises a question.
In the Manual for Replacing Batteries (see page 33), the reverse order is described:
- go to Edit for old device and select Replace by new Device
Are both descriptions correct, but applicable for different situations?
source device: [edit] [replace] choose target device ==>> logdata is transferred to target device. Source device is removed from database
Last edited by waaren on Wednesday 24 April 2019 15:52, edited 1 time in total.
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Re: Other Node ID, change IDX number
So besides the 'replace' button a 'merge' button might be an idea?
-
- Posts: 370
- Joined: Monday 05 October 2015 10:16
- Target OS: -
- Domoticz version:
- Contact:
Re: Other Node ID, change IDX number
Just tested with an Alecto Rain sensor.
It doesn;t mather which device replaces the other. The last(higher number) IDX stays.
Replacing source idx 1668 to target idx 1670 becomes idx 1670.
Replacing source idx 1674 to target idx 1672 becomes idx 1674.
The log/device data get's merged either way. Or beter said: get the new idx-number in the database.
Conflicts (double data) appears to be solved by saving the latest.
Note: running on previous beta domoticz
It doesn;t mather which device replaces the other. The last(higher number) IDX stays.
Replacing source idx 1668 to target idx 1670 becomes idx 1670.
Replacing source idx 1674 to target idx 1672 becomes idx 1674.
The log/device data get's merged either way. Or beter said: get the new idx-number in the database.
Conflicts (double data) appears to be solved by saving the latest.
Note: running on previous beta domoticz
Re: Other Node ID, change IDX number
So now I am confused.
Who is right waaren or stlaha2007 


-
- Posts: 370
- Joined: Monday 05 October 2015 10:16
- Target OS: -
- Domoticz version:
- Contact:
Re: Other Node ID, change IDX number
I would say: i'mEddyG wrote:So now I am confused.Who is right waaren or stlaha2007

I have tested both ways. So it showed the Manual and mine DO work.
I recommend you to follow the directions according to the Manual.
Sent from my K00C using Tapatalk
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: Other Node ID, change IDX number
Just checked the source for this and it is fair to say @stlaha2007 is right.
But the function acts a bit different than I expected; it checks which of the two (source and target) has the most recent date/time in the LastUpdate field and considers that device as 'newest'.
Then all references in the database to the 'oldest' device will be changed in a reference to the 'newest' device (this includes effectively a merge of the historical data) and as a last step the 'oldest' device will be deleted.
Hope this clarifies
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Re: Other Node ID, change IDX number
Tnx, for the clarification. 

Who is online
Users browsing this forum: No registered users and 1 guest