A problem of my own creation.

[ewkearns]

After Jowihue ran fine for a month, my router decided that it would use the IP reservation after all and now the RPi has the IP I originally wanted, but the software is pointing to the "old" IP address. Where/how do I fix this?

[w.vuyk]

I would expect the plugin should change the IP after a while. Otherwise it is best to stop the plugin and remove the bridge device and its features in the HS4 devicelist. Do not delete any other devices, nor use the bridge maintenance page for this. After removing the bridge device restart the plugin. It will complain not having the bridge, but after the first search by the plugin it will recreate the bridge device holding the right IP again.

Wim

[ewkearns]

I believe that the bridge has been found, but the devices have not been found by the bridge. I only have two (identical) devices and they both report:

ZHAHumidity
DisplayObjectInfo ------------------ Empty object send -----------------------

ZHATemperature
DisplayObjectInfo ------------------ Empty object send -----------------------

ZHAPressure
DisplayObjectInfo ------------------ Empty object send -----------------------

Any thoughts about how I should proceed?

[ewkearns]

Does anybody have any advice on getting these devices going again? The RaspBee seems fine, but the devices are not updating...

[Richel]

Just to be clear: you can access the RaspBee/Phoscon GUI and see your devices with their connections and the devices are not updating in RaspBee or HS? If it is just an HS issue, try deleting one of your devices in HS, disable the plug in and then re-enable. The plug in should discover the deleted device, as long as it is connected to RaspBee.

[ewkearns]

OK, first, thanks to everybody trying to help. I have to plead a little bit of stupid, a little bit of Raspberry/Xinux ignorance, and a little bit of got-hosed-by-the-power-company. I think what actually happened is about 2 weeks ago our power went out for about 5-6 hours. Apparently, that was enough to exhaust the UPS from which the RaspBee unit was feeding. I hadn't checked and didn't realize things had gone wrong that early. So, basically, the Raspberry went down and when it restarted the Phoscon software didn't get executed and the RPi rebooted with a different IP address. Confusion reigned. So, now, I gotta go see how to make sure the software executes at boot time.... Thanks, again, for the help. I think all is working, again.

[w.vuyk]

The issue you probably experienced after the blackout is that all devices booted at the same time when power was restored. So the Raspbee (or any computer device) starts up at the same time as the router. So the device does not yet get an IP address of the router and uses the backup address to be able to start anyway.
I do not know how to set this on a Raspbee, but on a Windows machine you can set the backup address yourself. I always do this and set the backup address to the address the Windows machine gets from the assigned IP's from the router instead of one of those bad 169 addresses. This way you ensure the machine always starts with the correct IP address, even when the router is offline for some reason.

Wim

[ewkearns]

I have experienced the "timing" problem in the past, even with other PIs. Trying to get all of the IPs set in the proper order is a bit like herding cats.

In this case, your PI actually found the RPi after the IP changed, but as reported earlier, it took a couple of days. It DID, however, work.

Part of my current handicap is a lack of understanding of the RPi nuances.

After the IP issue was solved, I ran into the problem that PhosCon was not configured to start at boot time. I *hope* I have that fixed, now, but as I learn about the RPi and the associated operating system I am in little better than cut-and-paste mode.

Thanks for your help!