Announcement

Collapse
No announcement yet.

Jowihue going in a restart loop.

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

  • w.vuyk
    replied
    Deleting them from the HS4 devicelist does not delete them on the bridge. Deleting them through the plugin's bridge maintenance deletes them from the bridge.as well. As long you are doing this from the device list there is no problem.

    Leave a comment:


  • Einar
    replied
    But will that not also delete them from DeConz. I hope not, as it will be a huge job to get them back!
    And it looks like I can delete lights in JowiHue Bridge Maintenance, but not sensors. Do I have to go the slow way of doing it in HS4?

    Leave a comment:


  • w.vuyk
    replied
    Also remove every device from the plugin in HS4.... this holds information that wou ld still create issues

    Leave a comment:


  • Einar
    replied
    I don't think I have a HS3 version that was not touched by HS4. If I do, it is so in need of corrections that I can as well start from nothing. I hope I can do a proper "cleanup".
    Also I hope that deConz can stay as it is since much of the "cleaning" is there.
    So the HS4 JowiHue will get the devices from there.
    So:
    Uninstall JowiHue.
    Remove every file and directory I can find that have the string "JowiHue" in the filename.
    Install JowiHue for HS4 and take it from there.

    Leave a comment:


  • w.vuyk
    replied
    How do you switch between HS3 and HS4? Did you use the HS3 plugin in HS4, moved to the HS4 version of the plugin and then switched back to the HS3 plugin in HS4 etc. but did not revert the devices to a backup from an earlier version while running the HS3 plugin?
    Because that is what I am seeing in the log.... it looks like a broken conversion of HS3 devices to HS4 devices. That is lso why you see the serialization errors in the log... it id doing the serialization on HS3 devices, thinking it is a HS4 device.

    There is no other repair possible other then reverting the HS4 devices to a backup where you had the HS3 version of the plugin running (without even been touched by the HS4 plugin) and then install the HS4 plugin again. Or you have to delete all devices from HS4 and reconnect the bridges as new install.
    Once the HS4 version of the plugin has been active you cannot run the HS3 version anymore unless you restore a backup.

    If you have a correct backup available, make sure to enable the verbose options in the HS3 version of the plugin. During the install of the HS4 version of the plugin, you will have a complete log. There are some issues to be expected, but most users get past them quite good normally.

    In the HS4 version of the plugin the use of the all lights group is no longer supported by deCONZ, Philips is also moving away from that group. Part of the issue is that the all lights group includes plugs and other devices that that you do not want to be controlled that way. The Homeseer errors you are seeing is probably caused by the incomplete conversion from the devices.... either remove them or return to a backup before the HS4 plugin touched the devices

    Wim​

    Leave a comment:


  • Einar
    replied
    I went to HS4 version. It does not get past initialization. I sent some logs in PM, hope you got them.

    Leave a comment:


  • Einar
    replied
    Im back in legacy now. Trying to clean up as much as I can. Devices not used ATM is being thrown out. Deleting groups as they seems to be much of the problem. I don't really use them much anyway. Log is getting much more calm now. But there is one thing going all the time:
    "05.11.2022 08:26:57 Legacy-Plugin JowiHue Error: (InitialSensors)::Konvertering fra strengen Error deserialize Version --- Un til typen Integer er ikke gyldig."
    I don't know why it is in Norwegian. The PC use English locale and Windows adress me in english. What the log try so say is something like Conversion from string Error deserialize Version -- Un to type Integer is not valid.

    There is one group "All lights" I do use, and it does not work now. HS4 ( not JowiHue ) is throwing me warnings:
    05.11.2022 09:05:36 HomeSeer Warning Device JowiHue JowiHue All Lights (root) All Lights is set a feature but points to a non existent device, try the repair option in setup"
    I did not find any repair option!

    I'll be back here after I go to HS4 version. Then I will enable detailed logging. The PC is pretty modern so should not be bogged down by that.

    Leave a comment:


  • w.vuyk
    replied
    Maybe share the log to see what is happening? What warning did you see? I am guessing here not knowing what you see
    Which version of the HS4 plugin did you use?
    As I am testing for the new version I went through a fresh install of the plugin today on my test system and I had no real issue? So maybe there is something on the system you are using causing this?
    Maybe share the configuration you use at this point? How many bridge/gateways are you using, Philips and/or deCONZ?

    Leave a comment:


  • Einar
    replied
    I installed the HS3 plugin and it works. At least it does not do the restart thing.
    But renaming devices does not show up in JowiHue-Bridge Maintenance, and not in DeConz.
    Maybe I should swap to JowiHue for HS4 now to see what happens.

    Edit: That did not go so well! It seems I have to go back to the old version again. Lots of warnings in the log.

    Leave a comment:


  • w.vuyk
    replied
    Sorry for my late answer. Clicking the wastebin would not be enough. You would need to check the \Data\JowiHue and the \bin\JowiHue directories as well to completely remove all information of the plugin.

    Wim

    Leave a comment:


  • Einar
    replied
    Your suggestions are good. In fault finding divide and conquer is usually a good strategy.

    What I already did is to go through the Raspberry HS3 / JowiHue setup and clean it up as good as I can. Removing devices that are not going to come online soon ( or ever ).
    Also checking that all devices that are referred in events are present and working. Although I will not import events to HS4. But just trying to see if I can get a somewhat stable HS3 going.

    Then I imagine I will start HS4 with a network without ( known ) errors. And I will then follow your advice using the HS3 plugin first by uninstalling JowiHue, then installing the HS3 plugin. Before that I will make a backup of the cleaned and polished DeConz setup in HS3 and pull into DeConz in the HS4 PC.

    It seems to me the cleanup of HS3 did something good. It did not crash yet even if there is almost 2 days since last restart. ( Going for a shower now to wash off the jinx! ).

    There will be a delay, as next week I am totally busy, and cannot do anything with this.

    But please mention here if just removing the plugin by clicking the wastebasket in Plugins->Manage is not good enough. I mean do I need to manually remove any files also?

    Leave a comment:


  • w.vuyk
    replied
    Yes you can. But did you try to run the HS3 plugin first on HS4? A graduate step up is lwys better to know what to blame. The upgrade from the H3 plugin to the HS4 plugin is no perfect, but most users seem to manage the twerks in it. What I advice most often is to instll HS$, but let the HS3 plugin do the work for a few days (t this you would need to go back to a backup I am sure, so it only works if you did not transfer a longer time ago.
    Then, at some time do the upgrade to the HS4 plugin, while holding a backup at hand. The plugin will upgrade the devices and throw few errors. After a restart it will start running nice again, and normally do its job like normal. Scanning for devices should not start an issue like you are seeing, so I am wondering what is happening.

    If you can go back to a backup with the HS3 plugin running, enable the detailed tracing. This will be enabled still with an upgrade or a restart.
    Non powered devices should never kill the plugin, they are just unreachable probably, nothing the plugin cannot survive...

    Leave a comment:


  • Einar
    replied
    Thanks for responding,

    Yes, I have done several things as this is trying to go over to HS4. As far as I can remember the last thing I did before it went south was to scan for new lights ( or sensors, I never remember )
    If there is a way to enable debug log in JowiHue before it starts up, that may give some clues? Is there a config setting for that?

    One of the reasons for going from HS3/Raspberry to HS4/Windows is that this HS3 setup crashes about each 24 hours. So maybe I should ditch the DeConz backup/restore and restart everything from scratch. But I do not love the thought of screwing out every bulb to bring it to the programming socket. What I'm thinking is that the DeConz setup may for some reason bomb JowiHue? There are quite a few devices in DeConz that are not powered up, dead, or otherwise not reachable if that matters.

    Leave a comment:


  • w.vuyk
    replied
    That is a bad situation, but I cannot guess what is happening. There is one situation where the plugin can restart, but that gets accompanied with a warning from the plugin that a unrecoverable error happend and the plugin is restarted. But in your log the restart is not expected for sure.

    Did you change anything before it happend the first time that might have caused it? A new device, a sudden restart of HS, Windows updates, etc?

    There is a new version of the plugin available, not sure if it changes anything, but maybe worth trying?

    Leave a comment:


  • Einar
    replied
    Then it steadily grew worse.

    First this:
    "17.10.2022 20:37:09 HomeSeer Warning Plugin JowiHue is not responding but it is still running, not restarting yet."

    Then HS4 became totally locked up. Even a restart of the PC did not make it responding again.

    Suddenly just now it came back! That made it posible to see the log. And it has been doing restarts of JowiHue in a tight loop. Less than one minute!
    That gave me the possibility to stop the JowiHue plugin.

    Leave a comment:

Working...
X