Announcement

Collapse
No announcement yet.

Plugin connection to Raspbee lost and unable to re-establish

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • zguy
    replied
    Originally posted by w.vuyk View Post

    In the log image you posted in the opening post, in the bottom I found the version. Had to zoom in a lot, but that where I saw it. Otherwise I would have asked probably as I could not think why the plugin would miss that in its current state.

    And the answer of TC1 is the best in my opinion. I am using jon00's plugin as well there and it works nicely.

    Great it is solved!

    Wim
    You have the eyes of your avatar, Wim!

    Jon00 utility installed. I won't get caught with this again.
    ​​​​​​​

    Leave a comment:


  • w.vuyk
    replied
    Originally posted by zguy View Post

    Now, how did you figure out the version I was running? I didn't mention that.
    In the log image you posted in the opening post, in the bottom I found the version. Had to zoom in a lot, but that where I saw it. Otherwise I would have asked probably as I could not think why the plugin would miss that in its current state.

    And the answer of TC1 is the best in my opinion. I am using jon00's plugin as well there and it works nicely.

    Great it is solved!

    ​​​​​​​Wim

    Leave a comment:


  • zguy
    replied
    Thank!

    Leave a comment:


  • TC1
    replied
    Originally posted by zguy View Post


    I'm wondering if there is a way to detect when a plugin update is available.


    https://forums.homeseer.com/forum/3r...er#post1411397

    Leave a comment:


  • zguy
    replied
    Originally posted by w.vuyk View Post
    zguy , ​​​​​​ Guy,

    I just noticed you are way behind in version of the JowiHue plugin. I was already scratching my head on why it would not fit the value as I thought I had is solve quite a while ago.... But the current version of the plugin is 4.0.6.0. You are running 4.0.4.10, 6 versions behind the current version
    Install the latest version and I am sure you are up and running again.
    Darn man! You are right, again. I'm suddenly much happier.

    Update and a restart fixed the error and most things were working again. Just 3 of the blinds I had to reset and rescan.

    Now, how did you figure out the version I was running? I didn't mention that.

    On that subject, while I have a tendency to not fix what is not broken, I found there are a few plugins that usually benefits from the update, yours included. Problem is, I don't often check the plugin page, and even when I do, the tiny black blob in HS4 easily goes unnoticed.

    I'm wondering if there is a way to detect when a plugin update is available.

    Thanks Wim!

    Leave a comment:


  • w.vuyk
    replied
    zguy , ​​​​​​ Guy,

    I just noticed you are way behind in version of the JowiHue plugin. I was already scratching my head on why it would not fit the value as I thought I had is solve quite a while ago.... But the current version of the plugin is 4.0.6.0. You are running 4.0.4.10, 6 versions behind the current version
    Install the latest version and I am sure you are up and running again.

    Leave a comment:


  • zguy
    replied
    @w.vuyk,

    Originally posted by w.vuyk View Post
    I agree with you it should not cripple the plugin. But it needs work s it is not prepared for it...
    But you cannot reset it through the plugin. You need to reset it through the physical device. Do not know the sequence on it. But once you found the sequence, be sure to run the scan for devices at the same time, the plugin will refresh its information on it. It is not disabling the device or whatever, make sure you reset it....
    I finally managed to reset the thermostat. Attempt to rescan from the plugin didn't work. I'm still getting the error.

    I also tried to start the plugin while deCONZ was stopped. It started fine, just saying the Phoscon was not reachable. But as soon as I restarted deCONZ, the error started again.

    At this point, there is not much more I can do. And the impact is, well, substantial. No control whatsoever on the 1st floor temperature because 3 thermostats connected to the plugin no longer responds. 8 Ikea blinds no longer automated, and the whole house and some exterior presence functions based on Hue motion sensors no longer work.

    I'm managing the thermostats manually and the blinds thru deCONZ. Not fun to say the least. I'm loosing an hour a day that I don't have doing that. And I don't have the time to invest in a workaround. I had faith in your plugin and added about 25 devices in deCONZ and about a dozen in the Philips Hue hub. None of them have been working for close to a week now. The worst are the Hue motion sensors with which I can do absolutely nothing. Until I get a fix, I have to keep the plugin off.

    I don't mean to put any pressure, we all have our life to take care of. But I do need to have an idea when you'll be able to fix the plugin so I can take a decision about what to do with this situation.

    Thanks,

    G.

    Leave a comment:


  • zguy
    replied
    Originally posted by w.vuyk View Post
    I agree with you it should not cripple the plugin. But it needs work s it is not prepared for it...
    But you cannot reset it through the plugin. You need to reset it through the physical device. Do not know the sequence on it. But once you found the sequence, be sure to run the scan for devices at the same time, the pugin will refresh its information on it. It is not disabling the device or whatever, make sure you reset it....
    The only reset available on those thermostats is a "factory reset". That will clear the connection to the zigbee bridge and I'll have to re-add it in deCONZ first. Historically, I've always had to add the device via deCONZ before the plugin sees it.

    Any way, I'll try to find some time to do this but I'm extremely busy with a home renovation project that is no going too well so it may take a while.

    When do you expect to have a fix for that value?

    Leave a comment:


  • w.vuyk
    replied
    I agree with you it should not cripple the plugin. But it needs work s it is not prepared for it...
    But you cannot reset it through the plugin. You need to reset it through the physical device. Do not know the sequence on it. But once you found the sequence, be sure to run the scan for devices at the same time, the pugin will refresh its information on it. It is not disabling the device or whatever, make sure you reset it....

    Leave a comment:


  • zguy
    replied
    Originally posted by w.vuyk View Post
    Guy,

    One of your power plugs is reporting a high value in consumption the plugin is not prepared for. It is the plugin with the ID 25 (check the JowiHue tab on the properties of the plugs).
    I will have to update the plugin to enable using the new value here. But for you the easiest way out of the mess is to reset the outlet, while doing a scan for devices on the Bridge Maintenance page. This will reset the consumption value to 0 and the plugin will function again.
    And before it reaches the high value again I hope to finish the updates in the plugin......

    Wim
    It would be that device then, one of the damn Sinope thermostats, not a plug:

    Code:
     [TABLE]
    [TR]
    [TD][B][URL="http://192.168.1.12/devices.html?ref=168&subpage=devprop"]Plancher Nord Status[/URL][/B]
    [URL="http://192.168.1.12/devices.html?ref=168&subpage=devprop"]• Plancher Nord Status Temperature
    			• Plancher Nord Status kWh
    			• Plancher Nord Status Watts[/URL][/TD]
     			[TD]• 24
    			• 25
    			• 26[/TD]
     			[TD]• ZHATemperature (Temperature)
    			• ZHAConsumption (kWh)
    			• ZHAPower (Watts)[/TD]
     		[/TR]
    [/TABLE]
    I turned the power off to it, disabled the plugin, restarted deCONZ then the plugin. Still getting the error. Why would that be if the device is not transmitting? Cached in deCONZ even after a restart?

    It's sad the whole plugin stops working because of one error.

    I'll check if there is a way to reset the thermostat without resetting the zigbee connection but I doubt there is.

    I noticed this in the Status/Graphics page of the device:

    Advanced Information
    ID 170
    Device Version 4
    Value 1000
    Status 1000.00 kWh

    Interface JowiHue
    Device Type Api: Feature
    Priority Order 2
    Relationship Feature (Child)
    Associated Devices Salon Chauffage Plancher Nord Status (168)


    Can I reset it somewhere in the plugin files?



    Leave a comment:


  • w.vuyk
    replied
    Guy,

    One of your power plugs is reporting a high value in consumption the plugin is not prepared for. It is the plugin with the ID 25 (check the JowiHue tab on the properties of the plugs).
    I will have to update the plugin to enable using the new value here. But for you the easiest way out of the mess is to reset the outlet, while doing a scan for devices on the Bridge Maintenance page. This will reset the consumption value to 0 and the plugin will function again.
    And before it reaches the high value again I hope to finish the updates in the plugin......

    Wim

    Leave a comment:


  • zguy
    started a topic Plugin connection to Raspbee lost and unable to re-establish

    Plugin connection to Raspbee lost and unable to re-establish

    Hello @jowiehue,

    Looks like I need your help again. This happened last evening.

    The plugin has lost connection to the Raspbee bridge. Blinds, some thermostats and Hue motion sensors connected to the bridge obviously no longer respond in HS.

    Not sure what is happening. From the HS server, I can ping the Pi Raspbee. I installed the Postman utility on the HS server. It can communicate with the Pi Raspbee, so the "not reachable" error below is ambiguous.

    HS logs show a few things, plugin startup seems fine but there is an error unrelated to the "not reachable" one (more below on this) apparently occurring during the plugin start up and regularly afterward:

    Click image for larger version  Name:	Capture.PNG Views:	0 Size:	196.5 KB ID:	1523521

    The error above is fludding the log every 5 seconds or so even when the plugin starts.

    Here you can see the:Phoscon being not reachable:

    Click image for larger version  Name:	Capture.PNG Views:	0 Size:	94.5 KB ID:	1523522
    As stated above, Postman, from the HS4 box to deCONZ Pi works:

    Click image for larger version  Name:	Capture.PNG Views:	0 Size:	49.8 KB ID:	1523523

    So, the questions:
    • If Postman can connect from the HS box to the Pi deCONZ API, why is the Jowiehue plugin suddenly can reach the deCONZ API?
    • The repeating error, what does it mean? How to Identify the device generating that error? It doesn't seem related to the "not reachable" error either.
    1/3rd of the house automation just went belly up, including part of heating, occupancy, blinds and a few other things. It's also impacting the whole system. I"m seeing delays in the remaining working systems/devices.

    I'm sad. Hope you can help.


Working...
X