This object is in archive!
Problem with oregon probes
Known
Hello,
since October 8th, my Zipabox does not communicate any more with my 6 probes oregon (3 THN132N and 3 THGR122NX).
October 28th, I have deleted them and added again, but either probes do not communicate their results, or the shown results are wrong.
I think it is a problem with the box or module, rather than a default related to the probes.
Indeed, during my various deletions and additions, the same module is sometimes recognized, sometimes not.
Furthermore, the temperature displayed on the THGR122NX probe is not that shown by the box.
Have you a solution?
Thank you for solving this problem.
Kind regards.
The same problem 
No connection
Real-time notifications may not work
Same problem for me, at least after upgrade to 0.9.999.2.
Since then Zipabox has become very unresponsive to updates from Oregon probes. My two THGR810:s still manage to get some messages thru, but not all. My THGN132N became essentially useless. I tried restarting it, change battery, change channel and reset probe and rebooting Zipabox all this while removing and readding the probe and logging in and out of the web interface.
It seems like readding also don´t work proberly, the box says that the probe has been discovered (after several tries, since only a few update messages from the probe is recognized by Zipabox) but the add device dialog hangs at saving. It works as bad, or even worse, afterwards. Even if and when it appears in the device list...
At the same time one of my Nexa wall transmitters seems to work slightly better after the update, but my Nexa remote controls on the other hand seems to work slightly worse, which is strange since it looks like they have the same transmitter chip...
Obviously something was changed in how Zipabox receives 433 MHz messages, and the change was not necessarily a good one. Option to downgrade to previos firmware is absolutely needed, and a bit more quality control on new firmware releases would also be a Good Thing!
Same problem for me, at least after upgrade to 0.9.999.2.
Since then Zipabox has become very unresponsive to updates from Oregon probes. My two THGR810:s still manage to get some messages thru, but not all. My THGN132N became essentially useless. I tried restarting it, change battery, change channel and reset probe and rebooting Zipabox all this while removing and readding the probe and logging in and out of the web interface.
It seems like readding also don´t work proberly, the box says that the probe has been discovered (after several tries, since only a few update messages from the probe is recognized by Zipabox) but the add device dialog hangs at saving. It works as bad, or even worse, afterwards. Even if and when it appears in the device list...
At the same time one of my Nexa wall transmitters seems to work slightly better after the update, but my Nexa remote controls on the other hand seems to work slightly worse, which is strange since it looks like they have the same transmitter chip...
Obviously something was changed in how Zipabox receives 433 MHz messages, and the change was not necessarily a good one. Option to downgrade to previos firmware is absolutely needed, and a bit more quality control on new firmware releases would also be a Good Thing!
pareil demande meilleur gestion des sondes et thermostat
merci a zipato en hiver c bien utile la qualité domotique ....
pareil demande meilleur gestion des sondes et thermostat
merci a zipato en hiver c bien utile la qualité domotique ....
I didn't understand much of that, but yes it screwed up my thermostats too when temperature probe's messages was not recognized. I had 30 degrees (Celsius) in my greenhouse when, after one and and a half hour, Zipabox decided it should eventually listen to what my probe was screaming and shut of the heater...
Bad news for both my plants and my wallet, unfortunately, since I was gone over the weekend. :-(
I didn't understand much of that, but yes it screwed up my thermostats too when temperature probe's messages was not recognized. I had 30 degrees (Celsius) in my greenhouse when, after one and and a half hour, Zipabox decided it should eventually listen to what my probe was screaming and shut of the heater...
Bad news for both my plants and my wallet, unfortunately, since I was gone over the weekend. :-(
Do you have a date for the correction of this dysfunction?
In winter, the temperature sensors are still very useful.
Do you have a date for the correction of this dysfunction?
In winter, the temperature sensors are still very useful.
Still no news on this subject? It is Winter now and having thermostats malfunction due to Zipabox ignoring repeated messages from temperature probes really is a Bad Thing!
Could you perhaps re-relese an earlier firmware as a new version to enable users to revert to something that works with Oregon probes until you either get it fixed or add a firmware downgrade function?
Still no news on this subject? It is Winter now and having thermostats malfunction due to Zipabox ignoring repeated messages from temperature probes really is a Bad Thing!
Could you perhaps re-relese an earlier firmware as a new version to enable users to revert to something that works with Oregon probes until you either get it fixed or add a firmware downgrade function?
Replies have been locked on this page!