-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CheckWindowSensors: Cannot read property 'name' of undefined #93
Comments
please activate debug logging for this adapter and post the log again. You can also ask for help in forum |
@CaptainBalou any feedback on that? If not than I will close this issue... |
I was investigsting how to activate debug to collect more logs but I was unable to get it done. Can you give me a hint, a link to a how to document? Otherwise we would have to close this issue until I am more experienced with iobroker and adapter debugging. |
I guess you got an answer in forum? There are only two steps: activate expert mode and then you can change log level for the adapter from info to debug. Log output is than again under logging where you got alreay above posted error messages... |
Indeed I got one but I have not realized it because I received no notification even if I requested one by clicking on the appropriate button. Sorry for the delay. I did it as mentioned and here is the new log.
Maybe this is because I currently have no thermostate in this room 'WC'. I just want to have the window sensor in the heatingcontrol to see the overall window open status of everything. But I have no thermostate yet. |
I assume you use version 0.3.19? can you show me your configuration for that room? You just have configured one sensor and nothing more for that room? but this should'nt be a problem... |
Version is 0.3.19 that is correct. Don't be that much focused on my assumption of that room with no thermostates. I was just giving that hint because it could be that this is something "unsupported" - but I have no glue if this is really a reson for the error message. If have this in a room called "Bad" as well. Same configuration. I enjoy seeing that window status via heatingcontrol in a single view at the end. Very useful for me. I am able to install something via github. At least I installed one adapter for a vacuum cleaner via this way. But I don't know what you mean exactly. I at least have never tried to install a "dev" version of heatingcontrol or so while keeping the current configuration. But if you could give some hints or a link to a wiki page I would be able to. |
@CaptainBalou i pushed version 0.4.0 into latest repo. If you like you can install it, enable debug log and send me the log again. I hope I added logs on the right places now... |
@rg-engineering Thanks for your efforts. As I am on the official release I am wondering how I could upgrade to 0.4.0. Can I just install via own URL and take the 0.4.0 repo? Will my installation and instance be upgraded or do I need to follow a different procedure? I just want to be sure to don't lose my current configuration in the running instance. |
Thanks a lot. Did it that way and updated to 0.4.0. Since I upgraded I have not seen this message anymore in the log even if I had it a lot before the upgrade. I keep watching out for it... |
@rg-engineering Since I upgraded to 0.4.0 I have not seen this log message anymore. I tried everything I did before but I cannot reproduce the log message. |
@rg-engineering I tried a lot but had no chance to get this error back into the log. Do you want me to go back to the official version and then integrate some manual debugs there or do we quit searching here? The question I have is if I get updates while being on 0.4.0 or do I have to do something to update always to the latest adapter version? |
I think we stop searching here. I did some changes on that part of code and probably this solved yor problems as well. |
The heatingcontrol script seems to work fine but I see errors in the log.
I don't know how to further debug this as I am very new to iobroker.
The text was updated successfully, but these errors were encountered: