Jump to content

Plugin using deprecated server.json version?


Recommended Posts

Posted (edited)

 

I noticed a warning in plug-in log that this plug-in is using some deprecated stuff. Is it just a reporting issue? If not, will it be upgraded to remain compatible? Is it at or near end of life/support? What's the impact of this?

 

 
2024-03-17 09:40:07,331 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.20 [ISY: 5.8.0, Slot: 5]
2024-03-17 09:40:07,331 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.100.249', 'netmask': '255.255.255.0', 'broadcast': '192.168.100.255'}
2024-03-17 09:40:07,332 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883
2024-03-17 09:40:07,332 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version
2024-03-17 09:40:07,333 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: <myISYaddr>_5.cert key: <myISYaddr>_5.key ca: /usr/local/etc/ssl/certs/ud.ca.cert
2024-03-17 09:40:07,333 MainThread udi_interface INFO evldscns:<module>: Starting EnvisaLink DSC Nodeserver...

 

 

Edited by johnnyt
Posted

There hasn’t been any (other) reason to rollout a new version, so it’s always been a “if it ain’t broke…” sort of thing. If it becomes necessary to get rid of server.json, I will change it.

As far as future support, I no longer use this plugin (I have a Honeywell panel) so I don’t notice problems and will have to rely on posts from users to be informed of issues.

Guest
This topic is now closed to further replies.

×
×
  • Create New...